Hi Punk & Welcome to the forums ^_^,
I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-
Code:
2: kd> .cxr 0xffffd000b9216e20;r
rax=ffffe001c59b3dc0 rbx=ffffe001c59b3d80 rcx=ffffe001c658a3e0
rdx=ffff6001c58f9ca0 rsi=0000000001419fde rdi=ffffc0011a28ec90
rip=fffff8000987d734 rsp=ffffd000b9217850 rbp=ffffd000b9217950
r8=ffffc0011b941380 r9=0000000000000008 r10=0000000000000021
r11=00000000000000f9 r12=0000000000000000 r13=ffffe001c30de108
r14=ffffe001c3bf0320 r15=ffffe001c4f1e000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x7b4:
fffff800`0987d734 48394208 cmp qword ptr [rdx+8],rax ds:002b:ffff6001`c58f9ca8=????????????????
Last set context:
rax=ffffe001c59b3dc0 rbx=ffffe001c59b3d80 rcx=ffffe001c658a3e0
rdx=ffff6001c58f9ca0 rsi=0000000001419fde rdi=ffffc0011a28ec90
rip=fffff8000987d734 rsp=ffffd000b9217850 rbp=ffffd000b9217950
r8=ffffc0011b941380 r9=0000000000000008 r10=0000000000000021
r11=00000000000000f9 r12=0000000000000000 r13=ffffe001c30de108
r14=ffffe001c3bf0320 r15=ffffe001c4f1e000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
[COLOR=#FF0000]dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x[/COLOR]7b4:
fffff800`0987d734 48394208 cmp qword ptr [rdx+8],rax ds:002b:[COLOR=#0000FF]ffff6001`c58f9ca8[/COLOR]=????????????????
So, we can see that the DirectX was preparing the Buffer for Direct Memory Access which caused the bug check. Let's check the Page Table Entry in blue -
Code:
2: kd> !pte [COLOR=#0000FF]ffff6001`c58f9ca8[/COLOR]
VA ffff6001c58f9ca8
PXE at FFFFF6FB7DBED600 PPE at FFFFF6FB7DAC0038 PDE at FFFFF6FB58007160 PTE at FFFFF6B000E2C7C8
Unable to get PXE FFFFF6FB7DBED600
[COLOR=#FF0000]WARNING: noncanonical VA, accesses will fault ![/COLOR]
It means bad memory is being referred/accessed which is causing the problems. But, this problem is present in every dump file. In every dump file, the accesses are faulting in different routines. I think this might be a RAM problem.
Below is a list of 3rd party drivers present on the system -
Code:
**************************Sat Oct 18 22:20:14.383 2014 (UTC + 5:30)**************************
[COLOR=#FF0000][U][B]Lycosa.sys Fri Jan 18 14:21:42 2008 (4790689E)
P17.sys Mon Aug 3 16:41:59 2009 (4A76C5FF)
[/B][/U][/COLOR]Rt630x64.sys Fri May 10 15:29:08 2013 (518CC4EC)
SCDEmu.SYS Fri Jun 27 10:44:20 2014 (53ACFDAC)
nvhda64v.sys Mon Jul 21 19:47:53 2014 (53CD2111)
sshid.sys Wed Aug 13 00:48:09 2014 (53EA6871)
nvvad64v.sys Thu Sep 4 22:40:48 2014 (54089D18)
nvlddmkm.sys Sun Sep 14 01:29:50 2014 (5414A236)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Oct 16 17:38:29.056 2014 (UTC + 5:30)**************************
NvStreamKms.sys Sat Sep 6 10:07:11 2014 (540A8F77)
http://www.carrona.org/drivers/driver.php?id=Lycosa.sys
http://www.carrona.org/drivers/driver.php?id=P17.sys
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
http://www.carrona.org/drivers/driver.php?id=SCDEmu.SYS
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
sshid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
Before proceeding further, I would suggest you to disconnect your Razer Lycose since it's drivers are very old. Furthermore, update your drivers for Creative Devices.
Post back the results of the Memtest as well. Follow the below
**GUIDE** on how to run the Memtest.
Furthermore, your BIOS dates back to 2011, I would suggest you to check for BIOS Updates. Keep in mind that the updating of BIOS is a very risky process and one small mistake could damage your motherboard physically.
Let me know how it goes ^_^
