Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\Kubul\040212-9079-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e12000 PsLoadedModuleList = 0xfffff800`03056650
Debug session time: Mon Apr 2 10:47:17.657 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:46.766
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc000001d, fffff80002e4cb3f, fffff880031e09f8, fffff880031e0250}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80002e4cb3f, The address that the exception occurred at
Arg3: fffff880031e09f8, Exception Record Address
Arg4: fffff880031e0250, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
nt!KiExecuteAllDpcs+10b
fffff800`02e4cb3f 07 ???
EXCEPTION_RECORD: fffff880031e09f8 -- (.exr 0xfffff880031e09f8)
ExceptionAddress: fffff80002e4cb3f (nt!KiExecuteAllDpcs+0x000000000000010b)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff880031e0250 -- (.cxr 0xfffff880031e0250)
rax=0000000000000000 rbx=fffff80003006020 rcx=fffff80003006000
rdx=fffff800030087a0 rsi=0000000000000001 rdi=0000000000000001
rip=fffff80002e4cb3f rsp=fffff880031e0c30 rbp=fffff80003003e80
r8=0000000000000001 r9=0000000000000000 r10=0000000000000001
r11=fffffa8006ae5970 r12=0000000000000000 r13=fffff80003008798
r14=fffff80003003e80 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010046
nt!KiExecuteAllDpcs+0x10b:
fffff800`02e4cb3f 07 ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
LAST_CONTROL_TRANSFER: from fffff80002e4cc87 to fffff80002e4cb3f
FAILED_INSTRUCTION_ADDRESS:
nt!KiExecuteAllDpcs+10b
fffff800`02e4cb3f 07 ???
STACK_TEXT:
fffff880`031e0c30 fffff800`02e4cc87 : fffff800`03003e80 fffffa80`06a26180 fffffa80`06a26180 fffff800`02e4cca4 : nt!KiExecuteAllDpcs+0x10b
fffff880`031e0cf0 fffff800`03128f7a : 00000000`00000000 fffffa80`06a26180 00000000`00000080 fffffa80`06a0a040 : nt!KiExecuteDpc+0xcb
fffff880`031e0d40 fffff800`02e7f9c6 : fffff880`02f64180 fffffa80`06a26180 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031e0d80 00000000`00000000 : fffff880`031e1000 fffff880`031db000 fffff880`031e0a90 00000000`00000000 : nt!KxStartSystemThread+0x16
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80002e4cb3f - nt!KiExecuteAllDpcs+10b
[ 0f:07 ]
1 error : !nt (fffff80002e4cb3f)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BIT
STACK_COMMAND: .cxr 0xfffff880031e0250 ; kb
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
---------
