[5badov]

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffffffffffffff, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e83c16, address which referenced memory

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

READ_ADDRESS: ffffffffffffffff

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeSetEvent+16
fffff800`02e83c16 f6037f test byte ptr [rbx],7Fh

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff880009b0930 -- (.trap 0xfffff880009b0930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80052fe000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e83c16 rsp=fffff880009b0ac0 rbp=fffff880009b0b70
r8=0000000000000000 r9=fffff880009b0c80 r10=fffffa80060affc0
r11=fffff880009b0ce8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KeSetEvent+0x16:
fffff800`02e83c16 f6037f test byte ptr [rbx],7Fh ds:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e7f2a9 to fffff80002e7fd00

STACK_TEXT:
fffff880`009b07e8 fffff800`02e7f2a9 : 00000000`0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009b07f0 fffff800`02e7df20 : fffffa80`05f1b990 fffff880`00e6630f fffffa80`04e29838 ffffffff`ffffffff : nt!KiBugCheckDispatch+0x69
fffff880`009b0930 fffff800`02e83c16 : 00000000`00000000 fffffa80`04e17c10 00000000`00000001 fffffa80`060bc338 : nt!KiPageFault+0x260
fffff880`009b0ac0 fffff880`0527aac1 : fffff800`02e8a8a5 fffff800`00000000 00000000`00000000 fffff880`04c731cf : nt!KeSetEvent+0x16
fffff880`009b0b30 fffff800`02e8a8a5 : fffff800`00000000 00000000`00000000 fffff880`04c731cf fffffa80`060bb0a0 : atikmdag+0x29ac1
fffff880`009b0b38 fffff880`05334a49 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIpiInterrupt+0x135
fffffa80`053f3668 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0xe3a49


STACK_COMMAND: kb

FOLLOWUP_IP:
atikmdag+29ac1
fffff880`0527aac1 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: atikmdag+29ac1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f7e4b69

FAILURE_BUCKET_ID: X64_0xA_atikmdag+29ac1

BUCKET_ID: X64_0xA_atikmdag+29ac1

Followup: MachineOwner
---------