Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp3_gdr.080814-1236
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Fri Jan 9 22:12:43.820 2009 (GMT-5)
System Uptime: 0 days 13:16:27.578
Loading Kernel Symbols
................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 0, f78bea8c, f78be788}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : ntoskrnl.exe ( nt!IoPageRead+1b )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 00000000, The address that the exception occurred at
Arg3: f78bea8c, Exception Record Address
Arg4: f78be788, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
+0
00000000 0000 add byte ptr [eax],al
EXCEPTION_RECORD: f78bea8c -- (.exr 0xfffffffff78bea8c)
Cannot read Exception record @ f78bea8c
CONTEXT: f78be788 -- (.cxr 0xfffffffff78be788)
Unable to read context, Win32 error 0n30
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7E
EXCEPTION_STR: 0x0
LAST_CONTROL_TRANSFER: from 804f95ff to 00000000
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f78beb5c 804f95ff 8a661ee8 88ef410b 88ef40f8 0x0
f78beb7c 804f92c9 88cb53f0 88ef41e8 88ef40f8 nt!IoPageRead+0x1b
f78bebf0 804eba6a 6950d8c0 c6020000 c0318080 nt!MiDispatchFault+0x2fc
f78bec40 804f67f3 00000000 c6020000 00000000 nt!MmAccessFault+0x5bc
f78bec80 804ff901 c6020000 00000000 80557398 nt!MmCheckCachedPageState+0x461
f78bed2c 804ff6b4 8a6bfd60 805622c0 8a67e340 nt!CcPerformReadAhead+0x1f1
f78bed74 804e426b 8a6bfd60 00000000 8a67e340 nt!CcWorkerThread+0x147
f78bedac 8057aeff 8a6bfd60 00000000 00000000 nt!ExpWorkerThread+0x100
f78beddc 804f88ea 804e4196 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
nt!IoPageRead+1b
804f95ff 5d pop ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!IoPageRead+1b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48a404ab
STACK_COMMAND: .cxr 0xfffffffff78be788 ; kb
FAILURE_BUCKET_ID: 0x7E_nt!IoPageRead+1b
BUCKET_ID: 0x7E_nt!IoPageRead+1b
Followup: MachineOwner
