Hi,
this is realy causing me hassles now. I recently added a ram chip 512mb to my laptop. I can use xp for a while and then it will just blue screen with the above error. It normaly blue screens when I am writing more than one cd or installing an app that requires more than 1 cd for installation.
I am using xp pro on an hp evo laptop. i have used the restore cd that came with it, the cd restore is sp1 as well about 2 weeks ago.
I downloaded the debugger for windows off the ms site and tried to analise the dump file caused by the crash,
I have loaded it in here below
##########################
##########
##########
##########
########
Loading Dump File [C:\WINDOWS\Minidump\Mini0
22404-01.d
mp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
**************************
**********
**********
**********
**********
**********
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
**************************
**********
**********
**********
**********
**********
Executable search path is:
**************************
**********
**********
**********
**********
***
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
**************************
**********
**********
**********
**********
***
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debugger can not determine kernel base address
KdDebuggerData.KernBase < SystemRangeStart
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x00004000 PsLoadedModuleList = 0x00003530
Debug session time: Tue Feb 24 16:09:19 2004
System Uptime: 0 days 6:44:20.475
**************************
**********
**********
**********
**********
***
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
**************************
**********
**********
**********
**********
***
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debugger can not determine kernel base address
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
.......................Ima
ge path too long, possible corrupt data.
.Image path too long, possible corrupt data.
..Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
..........................
..........
..........
..........
..........
..........
..........
..........
..........
........
Loading unloaded module list
..............
Loading User Symbols
**************************
**********
**********
**********
**********
**********
***
* *
* Bugcheck Analysis *
* *
**************************
**********
**********
**********
**********
**********
***
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 80534de3, a964f848, 0}
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+60de3 )
Followup: MachineOwner
---------
##########################
##########
##########
##########
########