Solved Random BSOD's persisting after clean Windows install

[Shad0121]

Hello everyone I am hoping someone here can possibly help me as I have no idea whats going on any more.
A few weeks back I updated my Nvidia drivers to 320.49 and shortly after began having BSOD's relating to the drivers. I rolled back to 320.18 which had previously worked fine for me but the random BSOD's continued so I did a complete wipe of the drivers and ran Driver Sweeper before putting 314.22 drivers on. Then my BSOD's began relating to various Windows processes rather than Nvidia and after attempting to resolve one error, another popped up. I ended up wiping the whole computer and putting on a fresh copy of Windows in case something had borked my previous Windows install. I was running perfectly fine for the past few days until today where I had another BSOD, this time relating to ntoskrnl.exe whilst playing War Thunder.
All of my BSOD's occur when I am on games, either Civ 5, Tomb Raider, APB Reloaded, Bioshock Infinite and War Thunder. I did originally think maybe my computer was overheating as it has been rather hot (35C +) in my room and my temps were higher than usual but even whilst maxing my fans the BSOD's have continued. I'm completely stumped as to what is going on here and would greatly appreciate any help anyone may be able to give me.

 

[x BlueRobot]

BSOD Analysis:

[COLOR=Red]BugCheck 3B[/COLOR], {[COLOR=SeaGreen]c0000005[/COLOR], fffff80002db45ad, fffff8800a5bffa0, 0}

Probably caused by : [COLOR=Red]memory_corruption[/COLOR]

Usual causes:  System service, Device driver, graphics driver, memory

3: kd> [COLOR=SeaGreen]!chkimg -lo -d -db !nt[/COLOR]
[COLOR=Red]1 error : !nt[/COLOR] (fffff80002db45a9)
fffff80002db45a0  9c  56  08  00  65  48  8b  34  25 [COLOR=Red]*8c[/COLOR]  01  00  00  44  0f  b6 .V..eH.4%....D..

CHKIMG_EXTENSION:[COLOR=SeaGreen] !chkimg -lo 50 -d !nt[/COLOR]
    fffff80002db45a9 - nt!NtQueryVirtualMemory+59
    [ 88:[COLOR=Red]8c[/COLOR] ]
1 error : !nt (fffff80002db45a9

I'm guessing a range of corrupt virtual memory addresses may be been referenced.

------------------------------------------------------------------------------------

3: kd> [COLOR=SeaGreen]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff880`04840000 fffff880`052eb000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR=Red]Fri Mar 15 01:37:00 2013[/COLOR] (51427B3C)
    CheckSum:         00A8D47C
    ImageSize:        00AAB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Since, you have tried a range of different graphics card drivers, then I would suggest stress testing the graphics card for any problems:

• http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Run the test for 2-3 hours; stop the test immediately when the temperature exceeds 80*C.

 

[marsmimar]

Hello Shad0121 and welcome to Seven Forums. Sorry to hear you're having these issues. Sometimes failing hardware can be the problem when software has been ruled out. In looking through your dump file I noticed several flagged problems. In the interest of saving space I edited the file to show a single reference of each item. The links provide additional info about each of the problems as well as where to go for the latest updates.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002db45ad, Address of the instruction which caused the bugcheck
Arg3: fffff8800a5bffa0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!NtQueryVirtualMemory+5d
fffff800`02db45ad 440fb68ef6010000 movzx   r9d,byte ptr [rsi+1F6h]

CONTEXT:  fffff8800a5bffa0 -- (.cxr 0xfffff8800a5bffa0)
rax=0000000000000030 rbx=fffffa8006f638c0 rcx=0000000000000030
rdx=0000000000000000 rsi=00000000fffffa80 rdi=000000000055f000
rip=fffff80002db45ad rsp=fffff8800a5c0980 rbp=fffff8800a5c0b60
 r8=0000000000000000  r9=000000000036e9b0 r10=fffff80002db4550
r11=0000000000000000 r12=000000000036e9b0 r13=000000000055f000
r14=ffffffffffffffff r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246
nt!NtQueryVirtualMemory+0x5d:
fffff800`02db45ad 440fb68ef6010000 movzx   r9d,byte ptr [rsi+1F6h] ds:002b:00000000`fffffc76=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

[B][COLOR="Red"]BUGCHECK_STR:  0x3B[/COLOR][/B]

[B][COLOR="red"]PROCESS_NAME:  chrome.exe[/COLOR][/B]

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002db45ad

STACK_TEXT:  
fffff880`0a5c0980 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtQueryVirtualMemory+0x5d

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002db45a9 - nt!NtQueryVirtualMemory+59
	[ 88:8c ]
1 error : !nt (fffff80002db45a9)

[B][COLOR="red"]MODULE_NAME: memory_corruption[/COLOR][/B]

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff8800a5bffa0 ; kb

[B][COLOR="red"]FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT[/COLOR][/B]

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

fffff880`0a5bf0f8  fffff880`010afe1c [B][COLOR="red"]fltmgr[/COLOR][/B]!FltpProcessIoCompletion+0xec

fffff880`0a5bf9b8  fffff880`048f8681Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
[B][COLOR="red"]*** WARNING:[/COLOR][/B] Unable to verify timestamp for [B][COLOR="Red"]nvlddmkm.sys[/COLOR][/B]
[B][COLOR="red"]*** ERROR:[/COLOR][/B] Module load completed but symbols could not be loaded for [B][COLOR="Red"]nvlddmkm.sys[/COLOR][/B]
 nvlddmkm+0xb8681

fffff880`0a5c0278  fffff880`052ee13f [B][COLOR="red"]dxgkrnl[/COLOR][/B]!DxgNotifyInterruptCB+0x83
fffff880`0a5c03f8  fffff880`0493513f [B][COLOR="red"]nvlddmkm[/COLOR][/B]+0xf513f
fffff880`0a5c0638  fffff880`0419df82 [B][COLOR="red"]dxgmms1[/COLOR][/B]!VidSchDdiNotifyInterrupt+0x9e

Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION (Windows Debuggers)

fltmgr.sys

nvlddmkm.sys

dxgkrnl.sys

dxgmms1.sys

I would also recommend going through the troubleshooting guide prepared by one of the Forum experts. He provides additional links for testing hardware such as RAM, hard drive, etc.

http://www.sevenforums.com/tutorials/220165-troubleshooting-steps-windows-7-a.html

EDIT: I see Harry beat me to it.

 

[Shad0121]

Thank you for the replies guys, I will get on with checking all of this momentarily.
Firstly though I did just have another BSOD whilst gaming again and I'm attatching the latest dump file. Windows also refused to boot a few times, even in safe mode, hanging at classPNP.sys. I have finally managed to get into Windows now after leaving it for 15 minutes and will look over the stuff now.
Thanks again for the help, very much appreciated.

 

[x BlueRobot]

BSOD Analysis:

[COLOR="Red"]BugCheck D1[/COLOR], {9, 2, 0, fffff880053277a0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : [COLOR="Red"]memory_corruption[/COLOR]

CHKIMG_EXTENSION: [COLOR="SeaGreen"]!chkimg -lo 50 -d !dxgmms1[/COLOR]
    fffff88005327799 - dxgmms1!VidSchiUpdateContextStatus+1f5
	[ 53:[COLOR="Red"]5b[/COLOR] ]
[COLOR="Red"]1 error : !dxgmms1[/COLOR] (fffff88005327799)

3: kd> [COLOR="SeaGreen"]!chkimg -lo -d -db !dxgmms1[/COLOR]
1 error : !dxgmms1 (fffff88005327799)
fffff88005327790  00  00  e9  d7  00  00  00  48  8d [COLOR="Red"]*5b[/COLOR]  08  bd  01  00  00  00 .......H.[......

---------------------------------------------------------------------------------------------

Again, more memory corruption related to graphics components such as Direct X, I would begin performing some stress testing as soon as possible.

 

[Shad0121]

Right, I ran Furmark for nearly 4 hours yesterday and it was completely stable, no artifacts/crashing/anything. Prior to that I updated Windows to hopefully get the out of date drivers Marsmimar listed and downloaded some additional things from the Asus site. I also opened up the PC and gave it a quick clean, wasn't too dirty but a clean couldn't do any harm. As well as this I reseated the graphics card and checked connections to everything just to be sure something hadn't somehow come loose.
After doing all of this I managed to game for about 2 hours with no issues whatsoever yet I still don't know if it is fixed or not since I didn't really do anything. This is the problem since the BSOD's are completely random, I can go for days with everything running fine and then the next I can have multiple BSOD's in a day and I don't see a way to "force" a BSOD so I can get to the bottom of things.
Any other recommendations you can give me would be appreciated unless there is nothing to try. If that is the case I will mark the thread as solved and open a new one if/when I get another BSOD.
Cheers for the help again.

 

[x BlueRobot]

Scan for any missing, modified or corrupted protected Windows files with:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[Shad0121]

Ran both of those and both finished fine, no errors whatsoever. I'm going to mark the thread as solved since I still haven't had a BSOD so either its fixed or its just biding its time. Either way, thank you very much for your help and hopefully I wont be posting here asking for help again

 

[x BlueRobot]

Welcome, glad to be able to help