Problems using debugging tools

I keep getting BSOD's so tried following the instructions here for using the debugging tools. I keep running into problems. It says I'm not using the correct symbols. I tried to reload them, but am still having no luck.

Any help in figuring this out would be greatly appreciated!

Here is the error:

Loading Dump File [C:\WINDOWS\Minidump\Mini080911-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'C:\Windows|Symbols'
Symbol search path is: C:\Windows|Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Aug 9 11:59:35.617 2011 (UTC - 4:00)
System Uptime: 0 days 0:07:58.640
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
...........................................................
Loading User Symbols
Loading unloaded module list
........
Unable to load image OsaFsLoc.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for OsaFsLoc.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e1584000, 0, 80539fe3, 1}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for eLock2FSCTLDriver.sys
*** ERROR: Module load completed but symbols could not be loaded for eLock2FSCTLDriver.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : OsaFsLoc.sys ( OsaFsLoc+d73 )

Followup: MachineOwner
---------



1: kd> !sym noisey
!sym <noisy/quiet - prompts/prompts off> - quiet mode - symbol prompts on
1: kd> .reload ntoskrnl.exe
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

 

Really need the info from the Blue Screens. What shows in Admin Tools > Event Viewer > Windows Log, under the Application & System event logs.

 

Most of the time, I'm not getting anything in the event viewer, but once in while something shows up. It's crashed 4 times already today, but there is only one error for today. I cleared out the event log yesterday and so far the error from today (the system error) and one error from yesterday (an application error) are the only two.

In Application:

Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 8/14/2011
Time: 4:11:32 PM
User: N/A
Computer: CFCPC20
Description:
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\comxp_sp3\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


In System:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/15/2011
Time: 11:16:04 AM
User: N/A
Computer: CFCPC20
Description:
Error code 10000050, parameter1 e430c000, parameter2 00000000, parameter3 80539fe3, parameter4 00000001.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 35 1000005
0020: 30 20 20 50 61 72 61 6d 0 Param
0028: 65 74 65 72 73 20 65 34 eters e4
0030: 33 30 63 30 30 30 2c 20 30c000,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 38 30 35 33 39 66 , 80539f
0048: 65 33 2c 20 30 30 30 30 e3, 0000
0050: 30 30 30 31 0001

 

Also, the info on the BSOD changes from crash to crash, but one I've seen a couple of times says Page_Fault_In_NonPaged_Area with a stop error of 0x00000050.

 

Need the complete info of what the BSOD states, when it happens, even though it may change. Who manufactured this machine, and what model. Also, are there any add-on cards that have been installed, along with RAM previously? How old is this machine? Was XP the original OS that came with it, and how long has the hard drive been in the machine?

Look under the Windows logs in Event viewer, and see if there is anything that is critical, or showing up as bad. You can scroll through to see.

 

Just had another crash. Same error as the last time ~ Page_Fault_in_NonPaged_Area with a Stop error of: 0x00000050 (0xE393c000, 0x00000000, 0x80539FE3, 0x00000001)

It's an Acer, but I'm not sure of the model (I'm not near the machine. The user gave me the error message over the phone). I will find that out as soon as I can. The machine is about 3-4 years old. Nothing added to it. Everything is factory. XP is the original OS. Nothing at all shows up in the Windows log.

It ran for about 5 hours yesterday with no issues. The user started it up this morning, logged in and within a very short time, it crashed.

I've run every virus scan I can think of, as well as a memory test to check out the RAM. Everything comes back ok. I'm thinking maybe I should just wipe it. If it's a software issue that may very well take care of it. At the same time though, I don't like to wipe unless it's the last option. Working things out through trial and error is a good way to for me to learn.

 

Have you tried to do a repair install of XP. I know that there were issues with SP3, with some machines, due to there are drivers out there that do not play nice with XP-SP2 & 3. Also, if it is infected with the Haxdoor virus, it can also cause this error. Also, a bad RAM module can cause it. I would try swapping out the RAM with new known good RAM, and make sure that you blow the dust bunnies out of the card edge connectors where they slide in.

http://support.microsoft.com/kb/903251