Hello spl313,
I read your initial post wrong, please discard the downgrading to 314.22 WHQL part.
Instead, have you tried the new 327.23 WHQL and the 331.40 beta yet?
If not, both can be found here.
I still advice you to run Furmark.
----------
I will analyze the dump files in chronological order, from when you last got a BSoD to when you first got one.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80003345cee, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )
Followup: MachineOwner
---------
Usual cause: Incompatible hardware, faulty drivers.
More info Bug check 0x1E_5.
Code:
2: kd> dps fffff8800988c000 fffff88009892000
fffff880`09890538 00000000`00000000
fffff880`09890540 fffffa80`03b695f0
fffff880`09890548 00000000`00003384
fffff880`09890550 00000000`000186a0
fffff880`09890558 fffff880`05883a48Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
nvlddmkm+0x1daa48
Driver reference table: nvlddmkm.sys.
----------
This dump file also points to your nvidia driver. Let's see if changing to either the 327.23 or 331.40 changes anything.
----------
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa8016bfe690, 0, fffff880063cb750, 2}
Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+6dc )
Followup: MachineOwner
---------
Usual cause: Incompatible hardware, faulty hardware, wrongly installed hardware, faulty RAM.
More info Bug check 0x50.
Code:
fffff880`0a29cf38 fffff800`031115d4 : 00000000`00000050 fffffa80`16bfe690 00000000`00000000 fffff880`0a29d0a0 : nt!KeBugCheckEx
fffff880`0a29cf40 fffff800`03092cae : 00000000`00000000 fffffa80`16bfe690 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x43836
fffff880`0a29d0a0 fffff880`063cb750 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0a29d230 fffff880`063b13e7 : fffffa80`043d2601 fffffa80`03cbb010 00000000`03910248 fffff880`00000061 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x6dc
fffff880`0a29d320 fffff880`0632a072 : fffff880`060be465 00000000`00000200 fffff880`0a29da40 00000000`00000000 : dxgmms1!VidMmReferenceDmaBuffer+0x43
fffff880`0a29d370 fffff880`06329837 : fffff8a0`00000001 fffff8a0`09ea31c0 fffff880`0a29d9f0 fffff880`063cae50 : dxgkrnl!DXGCONTEXT::Render+0x326
fffff880`0a29d980 fffff960`002514ce : 00000000`0807e380 fffffa80`086f2fe0 00000000`00002711 00000000`06f2d78c : dxgkrnl!DxgkRender+0x3e7
fffff880`0a29dbf0 fffff800`03093e13 : 00000000`03b5c210 fffff880`0a29dca0 00000000`00000000 00000000`1258bf70 : win32k!NtGdiDdDDIRender+0x12
fffff880`0a29dc20 000007fe`fdcb13fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0807e358 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fdcb13fa
The stacks point to both dxgmms1.sys and dxgkrnl.sys, which are Windows' DirectX drivers.
----------
Please first follow my suggestion from my previous post to update to DirectX 11.1 to see if anything changes.
----------
Code:
2: kd> dps fffff8800a297000 fffff8800a29e000
fffff880`0a29d350 fffff880`0a29d998
fffff880`0a29d358 fffff880`0a29d410
fffff880`0a29d360 fffff8a0`09ea31c0
fffff880`0a29d368 fffff880`0632a072 dxgkrnl!DXGCONTEXT::Render+0x326
fffff880`0a29d370 fffff880`060be465*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
nvlddmkm+0x8af465
As we can see this dump file also points to nvlddmkm.sys, which is the nvidia GPU driver.
----------
Until now all dump files point to faulty hardware, graphic related drivers and faulty GPU drivers, which makes me suspect the GPU. Let's see what Furmark comes up with.
----------
I see that you have already tested your RAM with Memtest. Question; for how many passes did you let each test run? It is recommended to let each pass run for at least 10 passes.
If you let it run for less passes, please test the RAM again by following this;
Please run Memtest86+ to test your RAM for issues.
Tip
Let
Memtest run for
at least 10 passes and preferably overnight as it may take very long to complete.
Especially read part three of the
tutorial, which explains you to test each RAM stick in all DIMM slots to filter out failing slots.
Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.
But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.
----------
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff960001cf6ff, 0, 39}
Probably caused by : win32k.sys ( win32k!PDEVOBJ::bAllowShareAccess+3 )
Followup: MachineOwner
---------
Another stop 0x1E_5 bug check. But this time it points to a Windows driver; one that shouldn't fail on it's own.
----------
To my debugging knowledge this dump file shows no finite cause of the BSoD.
----------
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa8005f63060, fffffa8005f63340, fffff800033900d0}
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
Followup: MachineOwner
---------
Usual cause: Terminated system process.
More info Bug check 0xF4.
----------
This dump file points to csrss.exe, which stands for Client/Server Run time SubSystem and it is, as expected, needed by Windows in order to operate. Termination of this process will result in the BSoD you received.
This should be a one-of-a-time BSoD.
----------
Until now I have analyzed all dump files until the 23rd. And with the exception of one or two, they all point to graphics related drivers/hardware.
A big part of the older dump files from before the 23rd are stop 0x3B bug checks, which all point to faulty GPU drivers.
More info Bug check 0x3B.
I am fairly certain that your Nvidia GeForce GTX 460 is the issue here, but just to be sure I will ask someone else to double check. Please be patient until they arrive here.
----------
Just for good order, let's scan Windows with SFC to see if it comes up with any integrity violations;
Please use the SFC /SCANNOW command as displayed in option two of this tutorial.
- Click on the .
- Open an elevated command prompt.
- Type "SFC /SCANNOW" without the quotations.
- Let SFC do it's thing, and then prompted to, restart.
If SFC found and repaired anything, please do the following: - When restarted, open an elevated command prompt.
- Type (or copy) the following, this will create a .txt file on your desktop;
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" - In your next reply, please attach this file using the method displayed in this tutorial.
Good luck and keep us posted,
Nommy