jeffy
10th June 2007, 09:57
This is the output of the "Debugging Tools for Windows"
Windows XP SP2. X264 - sudden crash and restart.
X264 downloaded from X264.nl, --version x264 0.54.654
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.061030-0016
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Jun 10 04:32:53.562 2007 (GMT+2)
System Uptime: 5 days 20:13:01.270
Loading Kernel Symbols
.....................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, f78c6d43, f78a2df8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiUnlockDispatcherDatabase+1c )
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: f78c6d43, The address that the exception occurred at
Arg3: f78a2df8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005
FAULTING_IP:
+fffffffff78c6d43
f78c6d43 0078d9 add byte ptr [eax-27h],bh
TRAP_FRAME: f78a2df8 -- (.trap 0xfffffffff78a2df8)
ErrCode = 00000002
eax=00049749 ebx=c00000c3 ecx=8a79ff60 edx=8a87feec esi=f78c6d34 edi=f78c6d2c
eip=f78c6d43 esp=f78a2e6c ebp=f78a2e78 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202
f78c6d43 0078d9 add byte ptr [eax-27h],bh ds:0023:00049722=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: x264.exe
LAST_CONTROL_TRANSFER: from f78c6d2c to f78c6d43
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f78a2e78 f78c6d2c 00000000 f78a2e84 f78a2e84 0xf78c6d43
f78a2e8c 804dc766 f78a2f02 804e5a63 4915a0aa 0xf78c6d2c
f78a2e94 804e5a63 4915a0aa 00000051 f78a2fbc nt!KiUnlockDispatcherDatabase+0x1c
f78a2f02 97408a87 494489c3 2f485052 68a4f78a nt!KiTimerListExpire+0x1ab
f78a2f06 494489c3 2f485052 68a4f78a 6f44baaa 0x97408a87
f78a2f0a 2f485052 68a4f78a 6f44baaa 60e0026e 0x494489c3
f78a2f0e 68a4f78a 6f44baaa 60e0026e 60e08a87 0x2f485052
f78a2f12 6f44baaa 60e0026e 60e08a87 00008a87 0x68a4f78a
f78a2f16 60e0026e 60e08a87 00008a87 60e00000 0x6f44baaa
f78a2f1a 60e08a87 00008a87 60e00000 d0088a87 0x60e0026e
f78a2f1e 00000000 60e00000 d0088a87 63e888eb 0x60e08a87
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiUnlockDispatcherDatabase+1c
804dc766 59 pop ecx
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4545d2fd
SYMBOL_NAME: nt!KiUnlockDispatcherDatabase+1c
FAILURE_BUCKET_ID: 0x8E_nt!KiUnlockDispatcherDatabase+1c
BUCKET_ID: 0x8E_nt!KiUnlockDispatcherDatabase+1c
Followup: MachineOwner
Windows XP SP2. X264 - sudden crash and restart.
X264 downloaded from X264.nl, --version x264 0.54.654
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.061030-0016
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Jun 10 04:32:53.562 2007 (GMT+2)
System Uptime: 5 days 20:13:01.270
Loading Kernel Symbols
.....................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, f78c6d43, f78a2df8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiUnlockDispatcherDatabase+1c )
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: f78c6d43, The address that the exception occurred at
Arg3: f78a2df8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005
FAULTING_IP:
+fffffffff78c6d43
f78c6d43 0078d9 add byte ptr [eax-27h],bh
TRAP_FRAME: f78a2df8 -- (.trap 0xfffffffff78a2df8)
ErrCode = 00000002
eax=00049749 ebx=c00000c3 ecx=8a79ff60 edx=8a87feec esi=f78c6d34 edi=f78c6d2c
eip=f78c6d43 esp=f78a2e6c ebp=f78a2e78 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202
f78c6d43 0078d9 add byte ptr [eax-27h],bh ds:0023:00049722=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: x264.exe
LAST_CONTROL_TRANSFER: from f78c6d2c to f78c6d43
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f78a2e78 f78c6d2c 00000000 f78a2e84 f78a2e84 0xf78c6d43
f78a2e8c 804dc766 f78a2f02 804e5a63 4915a0aa 0xf78c6d2c
f78a2e94 804e5a63 4915a0aa 00000051 f78a2fbc nt!KiUnlockDispatcherDatabase+0x1c
f78a2f02 97408a87 494489c3 2f485052 68a4f78a nt!KiTimerListExpire+0x1ab
f78a2f06 494489c3 2f485052 68a4f78a 6f44baaa 0x97408a87
f78a2f0a 2f485052 68a4f78a 6f44baaa 60e0026e 0x494489c3
f78a2f0e 68a4f78a 6f44baaa 60e0026e 60e08a87 0x2f485052
f78a2f12 6f44baaa 60e0026e 60e08a87 00008a87 0x68a4f78a
f78a2f16 60e0026e 60e08a87 00008a87 60e00000 0x6f44baaa
f78a2f1a 60e08a87 00008a87 60e00000 d0088a87 0x60e0026e
f78a2f1e 00000000 60e00000 d0088a87 63e888eb 0x60e08a87
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiUnlockDispatcherDatabase+1c
804dc766 59 pop ecx
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4545d2fd
SYMBOL_NAME: nt!KiUnlockDispatcherDatabase+1c
FAILURE_BUCKET_ID: 0x8E_nt!KiUnlockDispatcherDatabase+1c
BUCKET_ID: 0x8E_nt!KiUnlockDispatcherDatabase+1c
Followup: MachineOwner