Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini030806-04.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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Mar 8 01:16:11.078 2006 (GMT+1)
System Uptime: 0 days 0:00:57.671
*********************************************************************
* 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
Loading Kernel Symbols
.....................................................................................................................
Loading unloaded module list
...........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 831c7e22, b7b7da38, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image Cdfs.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for Cdfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Cdfs.SYS
Probably caused by : Cdfs.SYS ( Cdfs+1ce2 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 831c7e22, The address that the exception occurred at
Arg3: b7b7da38, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: Cdfs
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 41107eb1
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.
FAULTING_IP:
+ffffffff831c7e22
831c7e22 6681384d5a cmp word ptr [eax],0x5a4d
TRAP_FRAME: b7b7da38 -- (.trap ffffffffb7b7da38)
ErrCode = 00000000
eax=01201000 ebx=831c7e8f ecx=00000000 edx=f73cf8cc esi=01201000 edi=00000000
eip=831c7e22 esp=b7b7daac ebp=b7b7daac iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
831c7e22 6681384d5a cmp word ptr [eax],0x5a4d ds:0023:01201000=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 831c7db9 to 831c7e22
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b7b7daac 831c7db9 b7b7dabc 831c818a b7b7db20 0x831c7e22
b7b7dabc 831c8121 b7b7daec 01201000 b7b7db20 0x831c7db9
b7b7db20 831c7dc6 00000000 82ce1000 b7b7db84 0x831c8121
b7b7dc30 f77bdce2 f77be058 00000000 b7b7dc64 0x831c7dc6
b7b7dcf0 80538c20 804d9570 ffffffff b7b7dd34 Cdfs+0x1ce2
ffffffff 00000000 00000000 00000000 00000000 nt+0x61c20
FOLLOWUP_IP:
Cdfs+1ce2
f77bdce2 ?? ???
SYMBOL_STACK_INDEX: 4
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: Cdfs+1ce2
IMAGE_NAME: Cdfs.SYS
STACK_COMMAND: .trap ffffffffb7b7da38 ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
