V
Vity
I have a Win2000 server which is running only a DC and DNS
server. It is repeatedly crashing since it was migrated
to a virtual machine (VMWare).
I set it to create minidump's during the crash so it was
easier to see what was going on, below is the dump file.
Anyone have any suggestions? I replaced the file already
from another server in case it was corrupt. Every crash
dump refers to the file ntosknrl.exe in it with each dump
file being exactly the same.
Any help appreciated.
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINNT\Minidump\Mini083104-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 4) UP Free
x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0
Debug session time: Tue Aug 31 19:19:23 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 f2630a84 00000002 00000000 f7272c2f
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following
frames may be wrong.
f6630c68 00000000 f2630a84 00000002 00000000 nt+0x690f3
WaitForEvent failed
server. It is repeatedly crashing since it was migrated
to a virtual machine (VMWare).
I set it to create minidump's during the crash so it was
easier to see what was going on, below is the dump file.
Anyone have any suggestions? I replaced the file already
from another server in case it was corrupt. Every crash
dump refers to the file ntosknrl.exe in it with each dump
file being exactly the same.
Any help appreciated.
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINNT\Minidump\Mini083104-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 4) UP Free
x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0
Debug session time: Tue Aug 31 19:19:23 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 f2630a84 00000002 00000000 f7272c2f
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following
frames may be wrong.
f6630c68 00000000 f2630a84 00000002 00000000 nt+0x690f3
WaitForEvent failed