Temps never get above 50°c and even then its only the video card
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80001ffed8e, The address that the exception occurred at
Arg3: ffffd000277bd428, Exception Record Address
Arg4: ffffd000277bcc30, Context Record Address
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nvlddmkm+118d8e
fffff800`01ffed8e ff9038030000 call qword ptr [rax+338h]
EXCEPTION_RECORD: ffffd000277bd428 -- (.exr 0xffffd000277bd428)
ExceptionAddress: fffff80001ffed8e (nvlddmkm+0x0000000000118d8e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffd000277bcc30 -- (.cxr 0xffffd000277bcc30)
rax=fffff8000242a000 rbx=ffffc0000e921460 rcx=ffffe0000520b000
rdx=ffffc0000e921460 rsi=0000000000020000 rdi=ffffe00004244e28
rip=fffff80001ffed8e rsp=ffffd000277bd660 rbp=ffffd000277bd731
r8=0000000000000000 r9=ffffe00005285000 r10=0000000000000001
r11=fffff78000000008 r12=ffffc0000e92176c r13=ffffe0000511d000
r14=ffffe00004244e28 r15=ffffd000277bd868
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nvlddmkm+0x118d8e:
fffff800`01ffed8e ff9038030000 call qword ptr [rax+338h] ds:002b:fffff800`0242a338=fffff800028356ec
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: fffff8002eeb2340: Unable to get special pool info
fffff8002eeb2340: Unable to get special pool info
GetUlongFromAddress: unable to read from fffff8002ef4d208
ffffffffffffffff
FOLLOWUP_IP:
nvlddmkm+118d8e
fffff800`01ffed8e ff9038030000 call qword ptr [rax+338h]
BUGCHECK_STR: AV
LAST_CONTROL_TRANSFER: from ffffc0000e921460 to fffff80001ffed8e
STACK_TEXT:
ffffd000`277bd660 ffffc000`0e921460 : 00000000`00020000 00000000`00000000 ffffe000`04244e28 ffffe000`04fac000 : nvlddmkm+0x118d8e
ffffd000`277bd668 00000000`00020000 : 00000000`00000000 ffffe000`04244e28 ffffe000`04fac000 fffff800`02870739 : 0xffffc000`0e921460
ffffd000`277bd670 00000000`00000000 : ffffe000`04244e28 ffffe000`04fac000 fffff800`02870739 ffffc000`0e921460 : 0x20000
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+118d8e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5315b408
STACK_COMMAND: .cxr 0xffffd000277bcc30 ; kb
FAILURE_BUCKET_ID: X64_AV_nvlddmkm+118d8e
BUCKET_ID: X64_AV_nvlddmkm+118d8e
Followup: MachineOwner
---------
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80001ffed8e, The address that the exception occurred at
Arg3: ffffd000277bd428, Exception Record Address
Arg4: ffffd000277bcc30, Context Record Address
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nvlddmkm+118d8e
fffff800`01ffed8e ff9038030000 call qword ptr [rax+338h]
EXCEPTION_RECORD: ffffd000277bd428 -- (.exr 0xffffd000277bd428)
ExceptionAddress: fffff80001ffed8e (nvlddmkm+0x0000000000118d8e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffd000277bcc30 -- (.cxr 0xffffd000277bcc30)
rax=fffff8000242a000 rbx=ffffc0000e921460 rcx=ffffe0000520b000
rdx=ffffc0000e921460 rsi=0000000000020000 rdi=ffffe00004244e28
rip=fffff80001ffed8e rsp=ffffd000277bd660 rbp=ffffd000277bd731
r8=0000000000000000 r9=ffffe00005285000 r10=0000000000000001
r11=fffff78000000008 r12=ffffc0000e92176c r13=ffffe0000511d000
r14=ffffe00004244e28 r15=ffffd000277bd868
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nvlddmkm+0x118d8e:
fffff800`01ffed8e ff9038030000 call qword ptr [rax+338h] ds:002b:fffff800`0242a338=fffff800028356ec
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: fffff8002eeb2340: Unable to get special pool info
fffff8002eeb2340: Unable to get special pool info
GetUlongFromAddress: unable to read from fffff8002ef4d208
ffffffffffffffff
FOLLOWUP_IP:
nvlddmkm+118d8e
fffff800`01ffed8e ff9038030000 call qword ptr [rax+338h]
BUGCHECK_STR: AV
LAST_CONTROL_TRANSFER: from ffffc0000e921460 to fffff80001ffed8e
STACK_TEXT:
ffffd000`277bd660 ffffc000`0e921460 : 00000000`00020000 00000000`00000000 ffffe000`04244e28 ffffe000`04fac000 : nvlddmkm+0x118d8e
ffffd000`277bd668 00000000`00020000 : 00000000`00000000 ffffe000`04244e28 ffffe000`04fac000 fffff800`02870739 : 0xffffc000`0e921460
ffffd000`277bd670 00000000`00000000 : ffffe000`04244e28 ffffe000`04fac000 fffff800`02870739 ffffc000`0e921460 : 0x20000
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+118d8e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5315b408
STACK_COMMAND: .cxr 0xffffd000277bcc30 ; kb
FAILURE_BUCKET_ID: X64_AV_nvlddmkm+118d8e
BUCKET_ID: X64_AV_nvlddmkm+118d8e
Followup: MachineOwner
---------
