New
#21
Again, this is caused by a similar issue, a driver has attempted to access paged pool at IRQL Level 2. Only non-paged pool is accessible here, and therefore a page fault will not be serviced and will count as a illegal instruction.Code:BugCheck A, {fffffffffffffff8, 2, 0, fffff80002e89d8c} Probably caused by : win32k.sys ( win32k!TimersProc+197 )
Code:fffff88003c596a0 -- (.trap 0xfffff88003c596a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800b2e4140 rdx=fffffa800bce2690 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002e89d8c rsp=fffff88003c59830 rbp=fffffa800b2ec140 r8=ffffffffffffffff r9=0000000000000089 r10=fffff88002fd7180 r11=fffff88002fd7100 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!KiInsertTimerTable+0x1cc: fffff800`02e89d8c 4c3b78f8 cmp r15,qword ptr [rax-8] ds:ffffffff`fffffff8=????????????????I would check for a chipset update, and a possible graphics driver update from the Intel Support Page - Intel® Driver Update UtilityCode:fffff880`0480b000 fffff880`04c25000 igdkmd64 Mon Oct 07 23:56:37 2013 (52533C25) fffff880`03f17000 fffff880`03f2d000 intelppm Tue Jul 14 00:19:25 2009 (4A5BC0FD)