Re: Dump File (Has anyone seen this and how to fix)
From: Leonard Severt [MSFT] (leons_at_online.microsoft.com)
Date: 05/22/04
- Next message: Leonard Severt [MSFT]: "Re: dubp of physical memory"
- Previous message: Leonard Severt [MSFT]: "Re: SCSI drive error"
- In reply to: John Cilluffo: "Dump File (Has anyone seen this and how to fix)"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 22 May 2004 04:18:25 GMT
"John Cilluffo" <jcff@novonordisk.com> wrote in news:1058301c43f64
$ed0b3270$a001280a@phx.gbl:
>
> 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
>
>
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
-- This posting is provided "AS IS" with no warranties, and confers no rights.
- Next message: Leonard Severt [MSFT]: "Re: dubp of physical memory"
- Previous message: Leonard Severt [MSFT]: "Re: SCSI drive error"
- In reply to: John Cilluffo: "Dump File (Has anyone seen this and how to fix)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
