Getting Blue Screen - Please Help if Possible

Hello,

I have been getting the blue screen on my system after having it on for several hours.

I started getting the errors before I upgrading to service pack 3. I seen a thread that said to try and update all drivers and make sure system was updated with windows update, so i did this.

I installed debugging tools for windows xp but I could not read the logs. I am dumb founded in regards to what it is saying.

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

Symbol search path is: SymbolPath
Executable search path is: ImagePath
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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sun Jun 15 17:03:23.663 2008 (GMT-10)
System Uptime: 0 days 1:13:38.261
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
.............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {4, 2, 1, 804dbe9b}

***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+4e9b )

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

kd> referenced nt!_KPRCB
^ Bad register error in 'referenced nt!_KPRCB'
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 804dbe9b, address which referenced memory

Debugging Details:
------------------

***** 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 ***
*** ***
*************************************************************************

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48025eab

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000004

CURRENT_IRQL: 2

FAULTING_IP:
nt+4e9b
804dbe9b 894204 mov dword ptr [edx+4],eax

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804dbeff to 804dbe9b

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f7c0ae74 804dbeff fffe7960 ffffffff 497d4170 nt+0x4e9b
f7c0ae90 804e3be7 fffe7960 ffffffff 844ac128 nt+0x4eff
f7c0afa4 804dc378 497d4170 0000000a ffdff000 nt+0xcbe7
f7c0afd0 804dbbd4 8055a020 00000000 0006bb66 nt+0x5378
f7c0aff4 804db89e b8de7d54 00000000 00000000 nt+0x4bd4
00000000 00000000 00000000 00000000 00000000 nt+0x489e


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+4e9b
804dbe9b 894204 mov dword ptr [edx+4],eax

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+4e9b

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

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

kd> g
^ No runnable debuggees error in 'g'
kd> g
^ No runnable debuggees error in 'g'
kd> gn
^ No runnable debuggees error in 'gn'
kd> gh
^ No runnable debuggees error in 'gh'
kd> .restart /f

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

Symbol search path is: SymbolPath
Executable search path is: ImagePath
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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sun Jun 15 17:03:23.663 2008 (GMT-10)
System Uptime: 0 days 1:13:38.261
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
.............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {4, 2, 1, 804dbe9b}

***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+4e9b )

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

kd> g
^ No runnable debuggees error in 'g'
kd> nt!_KPRCB
^ Syntax error in 'nt!_KPRCB'
kd> referenced: nt!_KPRCB
^ Bad register error in 'referenced: nt!_KPRCB'
kd> g
^ No runnable debuggees error in 'g'


Not sure what all this means, hopefully you can provide what I need.

I am also attaching file for my dump file in rar format.

Your help is greatly appreciated.

Thanks
:smile: