Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\WINDOWS\Minidump\Mini073007-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 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, suite: TerminalServer SingleUserTS
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Mon Jul 30 22:05:55.484 2007 (GMT+2)
System Uptime: 0 days 0:08:47.046
*********************************************************************
* 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 User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 1000008E, {c0000005, 8058e3a7, f5bbfa78, 0}
 
ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D4000,1F2700,3D6DE35C
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
 
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
 
Probably caused by : ntoskrnl.exe ( nt+ba3a7 )
 
Followup: MachineOwner
---------
 
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: 8058e3a7, The address that the exception occurred at
Arg3: f5bbfa78, Trap Frame
Arg4: 00000000
 
Debugging Details:
------------------
 
ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D4000,1F2700,3D6DE35C
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
 
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
 
 
MODULE_NAME: nt
 
FAULTING_MODULE: 804d4000 nt
 
DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de35c
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction "0x%08lx" emploie l'adresse m moire "0x%08lx". La m moire ne peut pas tre "%s".
 
FAULTING_IP:
nt+ba3a7
8058e3a7 83782400 cmp dword ptr [eax+24h],0
 
TRAP_FRAME: f5bbfa78 -- (.trap fffffffff5bbfa78)
ErrCode = 00000000
eax=00000000 ebx=ff8c5408 ecx=0000013f edx=000dc000 esi=ff8a7da8 edi=000dcfff
eip=8058e3a7 esp=f5bbfaec ebp=f5bbfc08 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt+0xba3a7:
8058e3a7 83782400 cmp dword ptr [eax+24h],0 ds:0023:00000024=????????
Resetting default scope
 
CUSTOMER_CRASH_COUNT: 1
 
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
 
BUGCHECK_STR: 0x8E
 
LAST_CONTROL_TRANSFER: from 804da140 to 8058e3a7
 
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f5bbfc08 804da140 ffffffff f5bbfcd4 00000000 nt+0xba3a7
f5bbfc28 00000000 00000000 00000010 00000020 nt+0x6140
 
 
STACK_COMMAND: kb
 
FOLLOWUP_IP:
nt+ba3a7
8058e3a7 83782400 cmp dword ptr [eax+24h],0
 
SYMBOL_STACK_INDEX: 0
 
FOLLOWUP_NAME: MachineOwner
 
IMAGE_NAME: ntoskrnl.exe
 
SYMBOL_NAME: nt+ba3a7
 
BUCKET_ID: WRONG_SYMBOLS
 
Followup: MachineOwner
---------