Dump File (Has anyone seen this and how to fix)

  • Thread starter Thread starter John Cilluffo
  • Start date Start date
J

John Cilluffo

Microsoft (R) Windows Debugger Version 6.3.0011.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\jgry\Mini051804-02.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 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 2000 Kernel Version 2195 (Service Pack 3) UP Free
x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0
Debug session time: Tue May 18 13:37:10 2004
System Uptime: not available
***********************************************************
**********
* 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+ *
***********************************************************
**********
***********************************************************
********************
*
*
* Bugcheck
Analysis *
*
*
***********************************************************
********************
Bugcheck code 000000D1
Arguments ff7b5ca0 00000002 00000000 ba2e7646

ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following
frames may be wrong.
ba5a74d4 00000000 ff7b5ca0 00000002 00000000 nt+0x690f3

WaitForEvent failed
 
Microsoft (R) Windows Debugger Version 6.3.0011.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\jgry\Mini051804-02.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 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 2000 Kernel Version 2195 (Service Pack 3) UP Free
x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0
Debug session time: Tue May 18 13:37:10 2004
System Uptime: not available
***********************************************************
**********
* 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+ *
***********************************************************
**********
***********************************************************
********************
*
*
* Bugcheck
Analysis *
*
*
***********************************************************
********************
Bugcheck code 000000D1
Arguments ff7b5ca0 00000002 00000000 ba2e7646

ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following
frames may be wrong.
ba5a74d4 00000000 ff7b5ca0 00000002 00000000 nt+0x690f3

WaitForEvent failed
Click to expand...

You are not getting any useful information because you don't have
symbols. Look at this info to get to the Microsoft public symbol server.

http://www.microsoft.com/whdc/devtools/debugging/symbols.mspx

Leonard Severt
Microsoft Enterprise Support
 
Back
Top