Thanks.
PAGE_FAULT_IN_NONPAGED_AREA (50)
This indicates that invalid system memory has been referenced.
Code:
0: kd> .bugcheck
Bugcheck code 00000050
Arguments fffff900`c27007a0 00000000`00000000 fffff960`0064dc51 00000000`00000000
Code:
0: kd> r cr2
cr2=fffff900c27007a0 // This is invalid
Code:
0: kd> !pte fffff900c27007a0
VA fffff900c27007a0
PXE at FFFFF6FB7DBEDF90 PPE at FFFFF6FB7DBF2018 PDE at FFFFF6FB7E403098 PTE at FFFFF6FC80613800
contains 0000000122B2A863 contains 0000000124E37863 contains 000000003D585863 contains 000897E000000000
pfn 122b2a ---DA--KWEV pfn 124e37 ---DA--KWEV pfn 3d585 ---DA--KWEV not valid // < -- See?
PageFile: 0
Offset: 897e0
Protect: 0
Code:
0: kd> kv
Child-SP RetAddr : Args to Child : Call Site
fffff880`07b2a548 fffff800`02f02024 : 00000000`00000050 fffff900`c27007a0 00000000`00000000 fffff880`07b2a6b0 : nt!KeBugCheckEx
fffff880`07b2a550 fffff800`02e7f7ee : 00000000`00000000 fffff900`c00bf010 00000000`00000000 fffff900`c21c55a0 : nt! ?? ::FNODOBFM::`string'+0x427f7
fffff880`07b2a6b0 fffff960`0064dc51 : 00000000`00000000 0000178c`00000000 00001af3`00000000 fffff900`c21c55a0 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`07b2a6b0) // Here's where we crashed.
fffff880`07b2a840 fffff960`00197718 : 00000000`00000001 fffff900`c00bf010 00000000`00000001 fffff900`c2419010 : cdd!CddBitmapHw::Release+0x31
fffff880`07b2a880 fffff960`0019f9c1 : 00000000`00000000 00000000`00000001 fffff900`c2419010 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x358
fffff880`07b2a9d0 fffff960`00196fbc : 00000000`0000178c 00000000`00000000 fffff900`c2092cd0 00000000`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`07b2aa30 fffff960`00196703 : fffffa80`05f4a000 00000000`00000001 fffffa80`0444c060 00000000`00000001 : win32k!GdiProcessCallout+0x200
fffff880`07b2aab0 fffff800`0316557d : fffffa80`05f4a090 00000000`00000000 00000000`00000000 fffffa80`0444c060 : win32k!W32pProcessCallout+0x6b
fffff880`07b2aae0 fffff800`0313e7cb : 00000000`00000000 00000000`00000001 fffffa80`05406000 00000000`00000000 : nt!PspExitThread+0x561
fffff880`07b2aba0 fffff800`02e80953 : fffffa80`05406060 fffff880`00000000 00000000`fffdb000 fffffa80`0444c060 : nt!NtTerminateProcess+0x25b
fffff880`07b2ac20 00000000`77a9001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`07b2ac20)
00000000`0028db58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a9001a
Code:
0: kd> .trap fffff880`07b2a6b0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c2700020 rbx=0000000000000000 rcx=fffff900c1f48d30
rdx=fffffa800444c060 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600064dc51 rsp=fffff88007b2a840 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=00000000000050d9
r11=fffff88007b2a860 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cdd!CddBitmapHw::Release+0x31:
fffff960`0064dc51 483b9080070000 cmp rdx,qword ptr [rax+780h] ds:fffff900`c27007a0=????????????????
The instruction at address
fffff960`0064dc51 dereferenced the rax register + 780. rax =
fffff900c2700020. This ends up all writing to the memory at address
fffff900`c27007a0, seems pretty familiar.. right? It's out first bug check argument. So why did the write end up failing in the first place?
Code:
0: kd> !pte fffff900c2700020
VA fffff900c2700020
PXE at FFFFF6FB7DBEDF90 PPE at FFFFF6FB7DBF2018 PDE at FFFFF6FB7E403098 PTE at FFFFF6FC80613800
contains 0000000122B2A863 contains 0000000124E37863 contains 000000003D585863 contains 000897E000000000
pfn 122b2a ---DA--KWEV pfn 124e37 ---DA--KWEV pfn 3d585 ---DA--KWEV not valid // Invalid, why?
PageFile: 0 // It's paged out, that's why
Offset: 897e0
Protect: 0
Here's
why we failed, which is because the virtual page we're looking to use here to ultimately dereference regarding the rax register is off on the pagefile instead of being resident in physical memory like it should have been. It was specifically on pagefile # 0, and 897e0 offsets from the start of the pagefile. Since we're in kernel-mode and can't fetch it from the pagefile without a disaster, we just fail like so because it's paged out.
This is probably a driver issue, although a hardware memory issue is very possible (GPU or RAM).
1. AODDriver2.sys is listed and loaded in your modules list which is AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7 & 8.
Please uninstall either software ASAP! If you cannot find either software to uninstall, or it's not installed, please navigate to the following filepath:
C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys and rename AODDriver2.sys to AODDriver.2old and then Restart.
2. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.
Let me know how it goes after the above.
