Well, they seem to be pretty consistent in that they are somewhat related to display functionality.
Driver Verifier doesn't seem to be picking anything up, and you've changed your graphics card.
I'm thinking this is a faulty motherboard but there isn't really a way to test it.
Is it still under warranty? If so, I would seriously consider an RMA to get a piece of mind.
Code:
//Access violation during a system service, generating an exception, and therefore a bugcheck
18: kd> .bugcheck
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`a2736df7 ffffd000`23aedf70 00000000`00000000
18: kd> kn
# Child-SP RetAddr Call Site
00 ffffd000`23aed6b8 fffff800`905747e9 nt!KeBugCheckEx
01 ffffd000`23aed6c0 fffff800`905740fc nt!KiBugCheckDispatch+0x69
02 ffffd000`23aed800 fffff800`905701ed nt!KiSystemServiceHandler+0x7c
03 ffffd000`23aed840 fffff800`904e10a5 nt!RtlpExecuteHandlerForException+0xd
04 ffffd000`23aed870 fffff800`904e545e nt!RtlDispatchException+0x1a5
05 ffffd000`23aedf40 fffff800`905748c2 nt!KiDispatchException+0x646
06 ffffd000`23aee630 fffff800`90573014 nt!KiExceptionDispatch+0xc2
07 ffffd000`23aee810 fffff800`a2736df7 nt!KiPageFault+0x214
08 ffffd000`23aee9a0 fffff800`905744b3 dxgkrnl!DxgkQueryAdapterInfo+0x517 //Faulting instruction, let's check the registers
09 ffffd000`23aeeb00 00007ffd`675f175a nt!KiSystemServiceCopyEnd+0x13
0a 0000004f`c5b2f6b8 00000000`00000000 0x00007ffd`675f175a
18: kd> .frame /r8
08 ffffd000`23aee9a0 fffff800`905744b3 dxgkrnl!DxgkQueryAdapterInfo+0x517
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe801835cd080
rdx=000000000a6d63fa rsi=ffffffffffffffff rdi=ffffcf809d136fb0
rip=fffff800a2736df7 rsp=ffffd00023aee9a0 rbp=ffffd00023aeeb80
r8=ffffe000f3de7450 r9=ffffe801835cd7c8 r10=0000000000000000
r11=ffffe801835cd7c8 r12=ffffcf809dfe6e80 r13=ffffcf8095a74ee0
r14=ffffcf808ecb8540 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000286
dxgkrnl!DxgkQueryAdapterInfo+0x517:
fffff800`a2736df7 483908 cmp qword ptr [rax],rcx ds:002b:00000000`00000000=????????????????
//Compare failed, most likely an invalid value @ rax rather than rcx
Code:
7: kd> .bugcheck
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff802`a5e5cc6f
//Referenced bad memory, either null or bad context, most likely the latter.
7: kd> kn
# Child-SP RetAddr Call Site
00 ffffd000`22b2f588 fffff802`a5f6c7e9 nt!KeBugCheckEx
01 ffffd000`22b2f590 fffff802`a5f6b03a nt!KiBugCheckDispatch+0x69
02 ffffd000`22b2f6d0 fffff802`a5e5cc6f nt!KiPageFault+0x23a
03 ffffd000`22b2f860 fffff800`c5429a8f nt!KeWaitForSingleObject+0x1ff
04 ffffd000`22b2f8f0 fffff800`c5484569 dxgkrnl!DXGAUTOMUTEX::Acquire+0xbf
05 ffffd000`22b2f930 fffff800`c5484507 dxgkrnl!OUTPUTDUPL_MGR::QueryActiveContextCount+0x49
06 ffffd000`22b2f980 fffff800`c551d8ec dxgkrnl!OutputDuplQueryActiveContextCount+0x9f
07 ffffd000`22b2f9b0 fffff802`a5f6c4b3 dxgkrnl!DxgkQueryAdapterInfo+0x994
08 ffffd000`22b2fb00 00007ff8`8cad175a nt!KiSystemServiceCopyEnd+0x13
09 0000006c`9a18f488 00000000`00000000 0x00007ff8`8cad175a
7: kd> !address fffff802a5e5cc6f
Mapping user range ...
Mapping system range ...
Mapping non addressable range ...
Mapping page tables...
Mapping hyperspace...
Mapping HAL reserved range...
Mapping User Probe Area...
Mapping system shared page...
Mapping system cache working set...
Mapping loader mappings...
Mapping system PTEs...
Mapping system paged pool...
Mapping session space...
Mapping dynamic system space...
Mapping PFN database...
Mapping non paged pool...
Mapping VAD regions...
Mapping module regions...
Mapping process, thread, and stack regions...
Mapping system cache regions...
Usage:
Base Address: fffff800`00000000
End Address: fffff802`a61610e7
Region Size: 00000002`a61610e7
VA Type: BootLoaded
VAD Address: 0x27676e69727473
Commit Charge: 0x603a3a5000010001
Protection: 0x7fffd4efa320 []
Memory Usage: Private
No Change: yes
More info: !vad 0xfffff80000000000
7: kd> !search fffff802a5e5cc6f
Warning: unable to dereference MmPfnDatabase at fffff802a61610e8.
Search: READ_PVOID error
Search: READ_PVOID error
Searching PFNs in range 0000000000000000 - 0000000000000000 for [FFFFF802A5E5CC6F - FFFFF802A5E5CC6F]
Pfn Offset Hit Va Pte
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Search: READ_PVOID error
Search: READ_ULONG error
Search error: cannot allocate system memory descriptor
//Joys of a minidump
I recommend trying memtest86+ to test your RAM before going with a motherboard RMA. It's one of those two, I'm almost certain unless you're having some very bad luck with software, which I find unlikely with different graphics cards.
You need to run Memtest86+ for at least 8 passes.
Which one should I download?
You have two options to choose from, you can either download the ISO version then burn it do a CD and boot it from there.
The other option is downloading the auto installer for USB sticks, you then boot from that USB stick.
Be warned though, it will format your USB then install the files needed to make it bootable so any files left over will be wiped off.
Download it here:
Memtest86+ - Advanced Memory Diagnostic Tool
So how does it work?
It works by writing a series of test patterns to most memory addresses over 9 tests, it then reads the data back to compare it for errors.
The default pass does 9 different tests varying in access patterns and test data. A tenth pass is optional from the menu which writes all the memory in zeroes then sleeps for 90 minutes and compares it to see if any address have changed, this takes 3 hours per pass each time.
My memtest86 isn't booting! What should I do?
This can be caused by a number of different reasons, common ones include your BIOS not setting using the correct settings, you might want to change your boot priority order.
Other causes include your motherboard not supporting bootable USB sticks in which case you'll need to use a CD (or floppy drive).
Any other issues you might want to look here:
FAQ : please read before posting
