Solved Random BSoD's, Possibly gaming/ram related

[klawful]

I've been having random BSoD's the last couple of weeks, generally when I exit a video game, but never during the game except SOMETIMES when I alt-tab. Last BSoD mentioned a CDD.DLL, if that helps.

I have ran a full memtest, and the memory completes 4 passes. Local technician seems to think it's the ram anyway, but I thought I'd get a second opinion.

Attached is the file from the SF Diagnostic Tool, if anyone can help that'd be great.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c00c07a0, 0, fffff9600069dc51, 0}


Could not read faulting driver name
Probably caused by : cdd.dll ( cdd!CddBitmapHw::Release+31 )

Followup: MachineOwner
---------

I have ran a full memtest, and the memory completes 4 passes.

It looks memory related - you need to run a minimum of 8 passes of MemTest86+ (note the +):
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[klawful]

Thankyou for that, I will run a whole couple of tests in the morning.

Thanks Golden

 

[Golden]

No worries - I've subscribed to this thread and will follow up your findings.

 

[klawful]

Well, I completed a 10 hour 8-Pass memory test last night, with no errors. I'm at a loss.

I have previously asked the local PC technician Modster-PC (Gaming PC specialists) his thoughts, and he said it could still be the ram at fault, as he's had on occasion ram in the past complete memory tests, but still be the fault. What are the odds of that?

I also borrowed 4gb of ram for a night of gaming, and managed no problems, but that was only 1 night, could of been a fluke. Do I try borrow some ram for a couple of days?

Also, any chance it could be my SSD? If so, which tool would I use to test it? It's an OCZ Agility 3 120gb.

 

[Golden]

Can you give me a few hours to look into this in more detail? In the meantime, please follow this:

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[klawful]

Will do, cheers

 

[Golden]

I have previously asked the local PC technician Modster-PC (Gaming PC specialists) his thoughts, and he said it could still be the ram at fault, as he's had on occasion ram in the past complete memory tests, but still be the fault. What are the odds of that?

I think its highly unlikely that the RAM is the issue (unless you are overclocking).

Its more likely to be a driver, but Driver Verifier will confirm that or not.

As far as the SSD goes, please check to see if you are running the latest firmware.

 

[klawful]

I installed verifier and enabled it via instructions. Soon as I reset, it SBoD'd and gave me this. I tried to boot into safe mode with F8, but my system wouldn't goto the Safe Boot mode screen no matter how hard I tried. Ended up having to do a system restore.

Not sure if it created a dump file, if so where would I find it?

 

[Golden]

Look in C:\Windows\Minidump.....you want the .dmp files.

You need to copy the .dmp files to another folder (since \Windows\Minidump is a protected folder), then zip them and upload them here.

 

[Golden]

Hold on, I think I missed something......your Windows looks to be quite outdated.

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version [B][COLOR="Red"]7600[/COLOR][/B] MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e4a000 PsLoadedModuleList = 0xfffff800`03087e50
Debug session time: Fri Mar 27 23:17:22.139 2015 (UTC + 10:30)
System Uptime: 0 days 5:45:55.419
Loading Kernel Symbols

Many BSOD's are caused by outdated system files clashing with newer 3rd party drivers, and vice versa. The first thing to do is to update Windows fully, including SP1.

 

[klawful]

There, attached. Hope that helps

 

[klawful]

Outdated? Ok, that sounds fair enough. I'll get the latest updates now

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff8800191d324, fffff9800a866ee0, 0}

*** WARNING: Unable to verify timestamp for [B][COLOR="Red"]dtsoftbus01.sys[/COLOR][/B]
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )

Followup: MachineOwner
---------

Whilst you do that, uninstall Daemon Tools - its flagged in the latest BSOD .dmp file, and is one the most common cause of BSOD's

 

[klawful]

Well, I think that's solved it. Windows Update SP1. lol. 2 days and no crashes while gaming or alt-tabbing.

Thanks again Golden

 

[Golden]