BSOD while gaming or soon after closing a game

[Ethan6180]

Hello all, I need your collective help. A few weeks ago, I built a new computer and quickly began getting BSODs while gaming or shortly after exiting a game. This is the second time I have built a computer and I never had any problems with the first build. Here are the new build's specs:

Motherboard: Gigabyte GA-990FXA-UD3 Rev. 4001
CPU: AMD FX 6300 6-core 3.5GHz
GPU: XFX Radeon R9 290x
Hard drives: SanDisk Ultra II 240GB SSD (operating system); SanDisk Extreme 240GB SSD; Western Digital 500GB HDD
Memory: Corsair Vengeance LP 8GB (2x4GB)
Power Supply: Corsair HX750 750W
Operating System: Windows 7 Professional 64bit

The BSODs occur while gaming approximately 90% of the time. The other 10% of the time, the BSOD occurs after closing a game or while shutting down my computer after playing a game. Unfortunately, there is no apparent pattern to when the crashes occur. Sometimes I can game all day without any problem, and other times I will get several a day. Also, sometimes I can tell when a crash is about to occur because windows gadgets will stop responding (while gaming) or other programs running in the background will stop responding. I know when that happens, there will soon be a crash, or there will be a crash when I try to shut down the computer.

The only consistent thing about the BSODs is that they are centered around gaming. When I turn on the computer and use it for anything but gaming, I never have a problem. (I am using the computer without a problem while typing this message!)

I have taken several steps to try to diagnose and/or fix the problem.

I have looked at the crash dump files after each crash, but they are largely inconsistent, so I could not pin anything down.

I have tried updating all my drivers, especially the graphics card driver. I found out, however, that the latest AMD driver (14.9) was unstable, so I used Driver Uninstaller software in safe mode to remove all traces of it, and I installed an earlier stable version (14.4). The older driver seemed to help a little, but I still get BSODs.

I have tried updating the motherboard BIOS using the Gigabyte @BIOS software, but that did not change anything.

I tried uninstalling my antivirus software (AVG) and turned off all non-Microsoft services using msconfig. The BSODs still occur.

I tried repairing windows using the operating system disk. This did not help.

I tried running a scan of the windows system files using sfc/scannow in the command prompt. There were no errors found.

I suspected there might be a problem with the hardware, so I started doing stress tests of the different components to try to induce a BSOD. I stress tested the CPU using prime95 for about 2hrs, but there were no problems. I tried testing the memory using MemTest86 for about 4 hours, but there were no errors found. I tried stress testing the GPU by running FurMark for about 40 minutes, but there was no problem.

I have considered doing a complete reinstall of Windows, but decided against it because the problems started with a fresh install with the new computer build, and I don't want to go through the trouble of getting my computer back to the way I like it.

I have tried a bunch of other things that I cant even remember right now. So basically I am frustrated and out of ideas. Please let tell me if you know of something that might help!

 

[Ethan6180]

Anyone with any ideas?

 

[Ethan6180]

Quick update. While I don't think there is anything magical about "8" passes using memtest86, that seems to be the consensus in this forum for thorough testing of the memory. With that in mind, I ran memtest86 overnight for eight passes. No errors were detected.

If anyone has any ideas on my BSOD problem, please let me know!

 

[Ethan6180]

Another update. I take back what I said about the BSODs only occurring during or soon after gaming. I just used my computer without any gaming and it BSOD when I tried to shut it down. What the heck is going on here????

 

[Ethan6180]

I haven't done anything different, but have had no BSODs for a few days. Keeping my fingers crossed.

 

[Ethan6180]

Well my computer did not miraculously heal itself after all. I just got another BSOD while gaming. "Probably caused by : dxgmms1.sys" This BSOD message has come up before. Anyone out there with ideas, please help!!

 

[Ethan6180]

Another update. While gaming, I got another BSOD. So I decided to try out one of AMD's beta drivers that is supposed to be ideal for DA:I, which I have been playing a lot recently. I removed all traces of the old driver using Driver Uninstaller while in safe mode, then I installed AMD's 14.11.2 beta driver. I started up DA:I and immediately noticed that the game ran smoother, which was nice. But within 10 minutes of playing I got another BSOD. The latest crash dump files can be seen in the attached log.

IF ANYONE HAS ANY SUGGESTION ON HOW TO FIGURE OUT WHAT IS GOING ON, PLEASE LET ME KNOW!

 

[Ethan6180]

Update. Crashes seem to be happening more frequently for no apparent reason, whether gaming or not. Also, I just had this new non-crashing issue where I tried to shut down my computer but got a repeated error message telling me that windows explorer has stopped responding. I had to manually force a shutdown of the computer to turn it off.

I am about ready to give up on technology entirely. I will burn all my electronic possessions then move into the woods and live off the land.

 

[Golden]

Sorry, the BSOD section gets very busy, and sometimes things slip through the cracks.

Can you upload the very latest ZIP file you have by following this please:

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

 

[Ethan6180]

Here you go. Thanks for the help.

 

[Golden]

*** WARNING: Unable to verify timestamp for SYMEFA64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880015c1b65, fffff880071927c8, fffff88007192020}

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

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

fffff880`040b36f0  00000000`00000138
fffff880`040b36f8  fffff880`04b197a2Unable to load image \??\C:\Program Files (x86)\Norton Security\NortonData\22.0.0.110\Definitions\BASHDefs\20141209.001\BHDrvx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR="red"][B]BHDrvx64.sys[/B][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
 BHDrvx64+0xa07a2
fffff880`040b3700  fffffa80`0bed1101
fffff880`040b3708  00000000`00000001

fffff880`040b2fa0  fffffa80`086de010
fffff880`040b2fa8  00000000`00000000
fffff880`040b2fb0  fffffa80`0be21170
fffff880`040b2fb8  fffff880`044ae7c0Unable to load image \??\C:\Windows\system32\Drivers\SYMEVENT64x86.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR="red"][B]SYMEVENT64x86.SYS[/B][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
 SYMEVENT64x86+0xc7c0
fffff880`040b2fc0  00000000`00000000
fffff880`040b2fc8  fffffa80`09a24dc0
fffff880`040b2fd0  00000000`00000000
fffff880`040b2fd8  00000000`00000030
fffff880`040b2fe0  fffffa80`06ffea20
fffff880`040b2fe8  fffffa80`09b08010
fffff880`040b2ff0  fffffa80`09d04bb0
fffff880`040b2ff8  fffffa80`0c1b49e0
fffff880`040b3000  fffffa80`086de010
fffff880`040b3008  fffff880`0118e785 fltmgr!FltpFreeIrpCtrl+0x145
fffff880`040b3010  fffff880`0ab2b520Unable to load image \SystemRoot\System32\Drivers\NSx64\1601000.009\SRTSP64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR="red"][B]SRTSP64.SYS[/B][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
 SRTSP64+0x54520
fffff880`040b3018  00000000`00000001
fffff880`040b3020  00000000`00000000

Norton causes havoc on another system! Replace it with MSE, which is known to have never caused a BSOD.

 

[essenbe]

I may suggest running the Norton Removal too as well https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us

 

[Ethan6180]

I will try removing Norton. I recently installed it, which may account for the more frequent problems lately. But The BSODs were happening when I had no antivirus software at all. After I remove Norton, I will upload a new dm log collector file if/when I get another BSOD.

 

[Golden]

 

[Ethan6180]

Ok, so Norton has been removed several days ago using the Norton Removal Tool and I am now using MSE. I just turned on my computer and got a crash for no apparent reason. No gaming, no opening of programs. I just turned my head away from the computer for a second and boom, a BSOD. The latest DM Log collector file is attached. Please let me know if you have any ideas, thanks!

 

[Ethan6180]

I started out the new year with another random BSOD. This time it happened while I was watching a hilarious youtube video of a baby cockatiel. The latest dm log collector file is attached.

 

[essenbe]

Please run Seatools for DOS http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

And check disk http://www.sevenforums.com/tutorials/433-disk-check.html

 

[Ethan6180]

I ran the Disk Check for all three drives. No errors were found. I will run Sea Tools some time soon and let you know the results.

 

[essenbe]

OK, no problem.

 

[Ethan6180]

I just ran a short test of each of the three drives using SeaTools. All the drives passed. Is it correct to assume that there is no benefit to running a "Long Test" or "Acoustic Test" if they all passed?