J
John
I GOT 2 CRASH DUMP AND THEN RAN MICROSOFT DEBUGGER THIS
IS WHAT I GOT. WHAT SHOULD I DO.
----------------------------------------------------------
* 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 \WINDOWS\system32\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
Windows XP Kernel Version 2600 (Service Pack 1) UP Free
x86 compatible
Product: WinNt
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Sat Feb 28 16:20:10 2004
System Uptime: 0 days 4:11:31.199
**********************************************************
***********
* 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 \WINDOWS\system32\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
Loading Kernel Symbols
...........................................................
...........................................................
..............
Loading unloaded module list
...................................
Loading User Symbols
**********************************************************
*********************
* *
* Bugcheck Analysis *
* *
**********************************************************
*********************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bfa82fd9, b1e5ea04, 0}
***** Kernel symbols are WRONG. Please fix symbols to do
analysis.
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be
loaded for ati3duag.dll
Probably caused by : ati3duag.dll ( ati3duag+68fd9 )
Followup: MachineOwner
---------
----------------------------------------------------------
THIS IS MY SECOND ONE
----------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.3.0011.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini022704-01.dmp]
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 \WINDOWS\system32\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
Windows XP Kernel Version 2600 (Service Pack 1) UP Free
x86 compatible
Product: WinNt
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Fri Feb 27 21:19:42 2004
System Uptime: 0 days 1:11:47.293
**********************************************************
***********
* 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 \WINDOWS\system32\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
Loading Kernel Symbols
...........................................................
...........................................................
..............
Loading unloaded module list
.................
Loading User Symbols
**********************************************************
*********************
* *
* Bugcheck Analysis *
* *
**********************************************************
*********************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {800b, 2, 0, f7c49bd2}
***** Kernel symbols are WRONG. Please fix symbols to do
analysis.
Unable to load image \SystemRoot\system32
\drivers\cmuda.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for cmuda.sys
*** ERROR: Module load completed but symbols could not be
loaded for cmuda.sys
Probably caused by : cmuda.sys ( cmuda+5dbd2 )
Followup: MachineOwner
IS WHAT I GOT. WHAT SHOULD I DO.
----------------------------------------------------------
* 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 \WINDOWS\system32\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
Windows XP Kernel Version 2600 (Service Pack 1) UP Free
x86 compatible
Product: WinNt
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Sat Feb 28 16:20:10 2004
System Uptime: 0 days 4:11:31.199
**********************************************************
***********
* 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 \WINDOWS\system32\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
Loading Kernel Symbols
...........................................................
...........................................................
..............
Loading unloaded module list
...................................
Loading User Symbols
**********************************************************
*********************
* *
* Bugcheck Analysis *
* *
**********************************************************
*********************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bfa82fd9, b1e5ea04, 0}
***** Kernel symbols are WRONG. Please fix symbols to do
analysis.
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be
loaded for ati3duag.dll
Probably caused by : ati3duag.dll ( ati3duag+68fd9 )
Followup: MachineOwner
---------
----------------------------------------------------------
THIS IS MY SECOND ONE
----------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.3.0011.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini022704-01.dmp]
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 \WINDOWS\system32\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
Windows XP Kernel Version 2600 (Service Pack 1) UP Free
x86 compatible
Product: WinNt
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Fri Feb 27 21:19:42 2004
System Uptime: 0 days 1:11:47.293
**********************************************************
***********
* 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 \WINDOWS\system32\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
Loading Kernel Symbols
...........................................................
...........................................................
..............
Loading unloaded module list
.................
Loading User Symbols
**********************************************************
*********************
* *
* Bugcheck Analysis *
* *
**********************************************************
*********************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {800b, 2, 0, f7c49bd2}
***** Kernel symbols are WRONG. Please fix symbols to do
analysis.
Unable to load image \SystemRoot\system32
\drivers\cmuda.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for cmuda.sys
*** ERROR: Module load completed but symbols could not be
loaded for cmuda.sys
Probably caused by : cmuda.sys ( cmuda+5dbd2 )
Followup: MachineOwner