******************************************************************************** *
* 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8011efa9dbb, The address that the exception occurred at
Arg3: ffffd00122d4b1b8, Exception Record Address
Arg4: ffffd00122d4a9c0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.
FAULTING_IP:
atikmdag+c7dbb
fffff801`1efa9dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h]
EXCEPTION_RECORD: ffffd00122d4b1b8 -- (.exr 0xffffd00122d4b1b8)
ExceptionAddress: fffff8011efa9dbb (atikmdag+0x00000000000c7dbb)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000006a8
Attempt to read from address 00000000000006a8
CONTEXT: ffffd00122d4a9c0 -- (.cxr 0xffffd00122d4a9c0;r)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=00000000000f0000 rdi=0000000000000002
rip=fffff8011efa9dbb rsp=ffffd00122d4b3f0 rbp=ffffe001dfdb9060
r8=0000000000000002 r9=000000f4188c8000 r10=0000000000000000
r11=fffff8011e850447 r12=ffffe001e03fb500 r13=ffffe001df75eb40
r14=ffffe001e1fd8010 r15=fffff8011eee2000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
atikmdag+0xc7dbb:
fffff801`1efa9dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=00000000000f0000 rdi=0000000000000002
rip=fffff8011efa9dbb rsp=ffffd00122d4b3f0 rbp=ffffe001dfdb9060
r8=0000000000000002 r9=000000f4188c8000 r10=0000000000000000
r11=fffff8011e850447 r12=ffffe001e03fb500 r13=ffffe001df75eb40
r14=ffffe001e1fd8010 r15=fffff8011eee2000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
atikmdag+0xc7dbb:
fffff801`1efa9dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000000006a8
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8035b579138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
00000000000006a8
FOLLOWUP_IP:
atikmdag+c7dbb
fffff801`1efa9dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h]
BUGCHECK_STR: AV
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8011efa9dbb
STACK_TEXT:
ffffd001`22d4b3f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe001`e1fd8010 : atikmdag+0xc7dbb
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+c7dbb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53508a3c
STACK_COMMAND: .cxr 0xffffd00122d4a9c0 ; kb
FAILURE_BUCKET_ID: AV_atikmdag+c7dbb
BUCKET_ID: AV_atikmdag+c7dbb
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_atikmdag+c7dbb
FAILURE_ID_HASH: {0471d6b8-06e1-47c6-22ba-995dd0010efa}
