BSOD While running various games

I have a problem with my computer BSOD'ing at totally random times on a range of games I play but not all games, for example Java games like minecraft etc will not cause BSOD and other certain games like any Steam Source engine games I can run perfectly such as GMOD, L4D1/2 CSS etc. It does make me wonder if it is Directx games as the most common to die on me are games like World of Warcraft (if that is run on Directx I assume), Company of Hero's (99% of the time within the first 10 minutes) and Sim City 4.

I have ran checkdisk and rfc scannow (or whatever it is called) but I still need to run memtest when I get my dvd drive to boot it from the iso. I have updated directx, updated all my drivers and even going as far as removing every driver to replace again.
(also note I know my graphics driver is outdated but I had to as it was causing graphic errors in games. But have been getting BSOD on the current old driver and the new version.)

This happened only 2 times on 32 bit that I had originally installed but increased in 64 bit windows if that makes any difference but I am not sure if it made any correlation except that I have ran 64 bit longer than 32 bit.

- x64 Windows Home Premium 64x
- This is my own build.
- Full Retail Version
- Less than 1 year old
- The clean install is around 8-6 months old? (guess)

24 of 38 were caused by a memory exception (and I suspect more). While probably caused by a driver you do need to run both memtest and driver verifier. If you cant get it to boot from a cd you can rum memtest from a USB stick


These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+






Driver Verifier

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

Ran memtest and it came back with a pass no errors what so ever.
Tomorrow ill run driver verifier but what do I do if that comes back as ok?

Sickofguessing said:

Ran memtest and it came back with a pass no errors what so ever.
Tomorrow ill run driver verifier but what do I do if that comes back as ok?

First memtest needs to be run for 6-8 passes. If you havent done that many run it again

Verifier will make your system crash (it is supposed to) and when you upload the DMP we probably can tell you what caused it.

Please upload the actual .dmp files. A compressed analysis not containing all information is not as helpful as an actual .dmp file.

Sorry about that I was in a rush.

I assume using the same program in the sticky like I did in the first post

All of them are in that zip just like the first post but there are 4 new ones from today. note though I did take off usbfilter.sys from driver verifier being curious, when I did the verifier again it came up with a differnt error but I assume thats to do with the usb driver being gone so the newest .dmp is the BSOD from that so you may ignore it if its not relevant.

*attached*

Sickofguessing said:

Sorry about that I was in a rush.

I assume using the same program in the sticky like I did in the first post

All of them are in that zip just like the first post but there are 4 new ones from today. note though I did take off usbfilter.sys from driver verifier being curious, when I did the verifier again it came up with a differnt error but I assume thats to do with the usb driver being gone so the newest .dmp is the BSOD from that so you may ignore it if its not relevant.

*attached*

Two issues

1-Related to GEARAspiWDM.sys CD-ROM Class Filter Driver by Gear Software Also comes with iTunes. I would re-install with newest.

2-Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd. I would remove and replace with MagicISO

I did the two changes;
removed Daemon Tools and replaced it with Magic ISO
updated GEAR driver from their website

Ran Driver Verifier again and got another BSOD

Played WoW and BSOD again.

latest .dmp attached.

I wish I knew if it was hardware or software in particular that is causing these BSOD during games so I know what to fix or replace.

Sickofguessing said:

I did the two changes;
removed Daemon Tools and replaced it with Magic ISO
updated GEAR driver from their website

Ran Driver Verifier again and got another BSOD

Played WoW and BSOD again.

latest .dmp attached.

I wish I knew if it was hardware or software in particular that is causing these BSOD during games so I know what to fix or replace.

Only one DMP was verified. The one that was caused by dtsoftbus01.sys

The newest one (not verified) was Related to usbfilter.sys USB Filter Driver from Advanced Micro Devices Inc. Yours is 3 years old. I would update it to the newest.