*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc000001d, fffffa8007fae653, fffff88003584808, fffff88003584060}
*** WARNING: Unable to verify timestamp for igdpmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdpmd64.sys
Probably caused by : igdpmd64.sys ( igdpmd64+36fb7 )
Followup: MachineOwner
---------
3: 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: fffffa8007fae653, The address that the exception occurred at
Arg3: fffff88003584808, Exception Record Address
Arg4: fffff88003584060, Context Record Address
Debugging Details:
------------------
FAULTING_IP:
+0
fffffa80`07fae653 07 ???
EXCEPTION_RECORD: fffff88003584808 -- (.exr 0xfffff88003584808)
ExceptionAddress: fffffa8007fae653
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff88003584060 -- (.cxr 0xfffff88003584060)
rax=fffffa8007fae5e0 rbx=fffff88003584aa0 rcx=fffffa8007fadf40
rdx=b40031ce2807aabd rsi=fffffa8007fadf40 rdi=00000000c00000bb
rip=fffffa8007fae653 rsp=fffff88003584a40 rbp=fffff8800903d000
r8=46fbb3f9fde5bba4 r9=0000000000000000 r10=0000000000000018
r11=fffff88003584ac8 r12=0000000000000001 r13=fffffa800ac9c130
r14=fffffa800a390190 r15=0000000000000038
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210282
fffffa80`07fae653 07 ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffffa8007fae5e0 to fffffa8007fae653
FAILED_INSTRUCTION_ADDRESS:
+0
fffffa80`07fae653 07 ???
FOLLOWUP_IP:
igdpmd64+36fb7
fffff880`09073fb7 ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: igdpmd64+36fb7
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdpmd64
IMAGE_NAME: igdpmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e4152eb
STACK_COMMAND: .cxr 0xfffff88003584060 ; kb
FAILURE_BUCKET_ID: X64_0x7E_BAD_IP_igdpmd64+36fb7
BUCKET_ID: X64_0x7E_BAD_IP_igdpmd64+36fb7
Followup: MachineOwner
---------
3: kd> lmvm igdpmd64
start end module name
fffff880`0903d000 fffff880`09bf55c0 igdpmd64 T (no symbols)
Loaded symbol image file: igdpmd64.sys
Image path: \SystemRoot\system32\DRIVERS\igdpmd64.sys
Image name: igdpmd64.sys
Timestamp: Tue Aug 09 21:31:55 2011 (4E4152EB)
CheckSum: 00BB861A
ImageSize: 00BB85C0
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
rb: