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: fffff88005ff9574, The address that the exception occurred at
Arg3: fffff88008668518, Exception Record Address
Arg4: fffff88008667d70, Context Record Address
Debugging Details:
------------------
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
atikmdag+3b6574
fffff880`05ff9574 418b8c28b0040000 mov ecx,dword ptr [r8+rbp+4B0h]
EXCEPTION_RECORD: fffff88008668518 -- (.exr 0xfffff88008668518)
ExceptionAddress: fffff88005ff9574 (atikmdag+0x00000000003b6574)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000004b0
Attempt to read from address 00000000000004b0
CONTEXT: fffff88008667d70 -- (.cxr 0xfffff88008667d70)
rax=00000000cccccccd rbx=fffffa8009e04000 rcx=fffffa8009e22000
rdx=fffff880086687e8 rsi=fffffa800b2a0b00 rdi=fffff880086687e8
rip=fffff88005ff9574 rsp=fffff88008668750 rbp=0000000000000000
r8=0000000000000000 r9=fffff8800611d810 r10=fffff88005c43000
r11=0000000000000000 r12=fffff8a007ea7340 r13=000000000000016c
r14=00000000c0000001 r15=fffffa800c1b53c0
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
atikmdag+0x3b6574:
fffff880`05ff9574 418b8c28b0040000 mov ecx,dword ptr [r8+rbp+4B0h] ds:002b:00000000`000004b0=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000000004b0
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003706100
GetUlongFromAddress: unable to read from fffff800037061c0
00000000000004b0 Nonpaged pool
FOLLOWUP_IP:
atikmdag+3b6574
fffff880`05ff9574 418b8c28b0040000 mov ecx,dword ptr [r8+rbp+4B0h]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 00000000000000a0 to fffff88005ff9574
STACK_TEXT:
fffff880`08668750 00000000`000000a0 : 00000000`00000000 fffffa80`0000004d fffff880`05ff833f 00000000`00000004 : atikmdag+0x3b6574
fffff880`08668758 00000000`00000000 : fffffa80`0000004d fffff880`05ff833f 00000000`00000004 000000ff`096c0000 : 0xa0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+3b6574
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f3b1dc8
STACK_COMMAND: .cxr 0xfffff88008667d70 ; kb
FAILURE_BUCKET_ID: X64_0x7E_atikmdag+3b6574
BUCKET_ID: X64_0x7E_atikmdag+3b6574
Followup: MachineOwner
---------