BSOD While running various games

[Sickofguessing]

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)

 

[zigzag3143]

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.

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






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)

 

[Sickofguessing]

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?

 

[zigzag3143]

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.

 

[Sickofguessing]

Ran mem test and accidently left it for 5 hours but when I came back after quite alot of passes there was no errors.

Ran driver verifier and it wouldnt get past windows logo before BSOD' got the blue screen I left in an attachment as a .txt file. I did go into safe mode but I couldn't play a game to get it to BSOD.

Although on the screen it did display usbfilter.sys which by the table you linked is the AMD USB Filter Driver

 

[writhziden]

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

 

[Sickofguessing]

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*

 

[zigzag3143]

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

 

[Sickofguessing]

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.

 

[zigzag3143]

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.

 

[Sickofguessing]

I thought I updated the usbfilter.sys with the newest chipset drivers from AMD that include usbfilter.sys but it didnt seem to stop the BSOD so I unticked it from the drivers in verifier.

Updated the drivers for my graphics accidently so I couldnt play Company of Heroes without having texture tearing to BSOD so I played World of Warcraft until it just BSOD.

as a consequence I cant get catalyst control center to install or work sadly.

So with this BSOD from gaming whilst using Driver verifier what does this show?
*.dmp attached*

 

[zigzag3143]

Most recent is verified and related to usbfilter.sys.

CCC is often problematic in terms of stability.

 

[Sickofguessing]

I got CCC back working albeit an older version but with the same drivers that is bug free for my IGC.

but if USBfilter.sys is causing the BSOD during games and even when I update it to the newest chipset I can find what can I do? Do I remove it from the computer? Or should I contact AMD to get advice on it?

 

[zigzag3143]

I got CCC back working albeit an older version but with the same drivers that is bug free for my IGC.

but if USBfilter.sys is causing the BSOD during games and even when I update it to the newest chipset I can find what can I do? Do I remove it from the computer? Or should I contact AMD to get advice on it?

I would first rename USBFILTER.sys to USBfilter.bak to prevent it from loading.

Just to be safe make sure you have a backup first.

If there are no complaints from the system and nothing uses it, leave it that way.

If that doesnt fix the problem contacting AMD cant hurt.

 

[Sickofguessing]

I totally removed it by uninstalling it and removing it in RegEdit as the readme from the driver folder instructed and no problems at the moment.

Thought it was all clear till I got two BSOD, one from kmode exception not handled with ntoskrnl.exe and atikmpag.sys ( seems the computer is just finding problems to piss me off with )
And another system service exception from ntoskrnl.exe

I'll upload dmp late gmt tomorrow as I am away from my computer/internet at the moment ... hopefully you can still help me and figure what's going wrong

 

[Sickofguessing]

Sorry about this had a total mess on with truecrypt and other stuff ended up reinstalling.

I emailed gigabyte and they didnt really answer my question just stated to download the chipset which includes the exact same old usbfilter.sys

Left it uninstalled and downloaded the new gear drivers but it still BSOD but this time during a youtube video.

Been playing the new Diablo 3 for hours on end without a single BSOD at all. Quite confusing but its frustrating me more so.

Dropped the last dmp file if this doesn't show any reason what's going on im just going to upgrade my PSU and install my graphics card to see if I ever have any problems with nVidia graphics.

Thanks for the help so far!

 

[writhziden]

Problematic software:

Start Menu\Programs\Defraggler	Public:Start Menu\Programs\Defraggler	Public

I recommend against 3rd party defrag tools. Windows has some nice command line flags for the defrag command that will accomplish the same tasks as 3rd party programs. The -b and -w flags will defrag boot files and the boot registry items as well as compact the data to the center of the disk for faster access.

defrag c: -b
defrag -c -v -w
​

The first command optimizes boot performance for the Windows drive by defragmenting boot files and boot registry items.

The second command includes all drives on the system through the -c command and optimizes the drives by compacting the data to the center of the disk. Verbose output through the -v option is optional to provide the user with more information about the defrag tasks. The commands have to be run in an http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html


Your crash indicates DirectX, which could mean you have corrupted DirectX files, corrupted graphics card drivers, or other graphics card issues.

• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.
  
  
• Re-install or install the latest drivers for your display card. Your current drivers may be corrupt and/or outdated. Use the following method to re-install the drivers.
  
  1. Download the drivers you want for your display card(s)
  2. Click Start Menu
  3. Click Control Panel
  4. Click Uninstall a program
  5. For NVIDIA:
     • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
     • Restart your computer
     • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
     • If any remain of the above, uninstall one at a time
     • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
  6. For AMD:
     • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
     • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
       1. Click Start Menu
       2. Right Click My Computer/Computer
       3. Click Manage
       4. Click Device Manager from the list on the left
       5. Expand Display adapters
       6. Do the following for each adapter (in case you have multiple display cards)
          • Right click the adapter
          • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
          • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
          
          Alternatively:
          1. Login as an adminstrative user
          2. Click Start Menu
          3. Click Control Panel
          4. Click Hardware and Sound
          5. Click Device Manager (the last link under Devices and Printers)
          6. Expand Display adapters
          7. Do the following for each adapter (in case you have multiple display cards)
             • Right click the adapter
             • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
             • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
     • Restart your computer after uninstalling drivers for all display cards
     • Install the driver you selected for the display cards once Windows starts

 

[Sickofguessing]

Done SFC scan 5 times with restarts in between and nothing came up. Removed defraggler I cant even remember installing that.

Un-installed and re-installed my AMD drivers before and I got the same BSOD's whether I was using the new 12.4 (which are buggy and broken for my G-Card) or the older 12.3 (which work perfectly) Still get BSOD's either way.

Done all that I regularly do the SFC scan when I reinstall windows anyway but no faults at all. I even burned off a clean disc when I re-installed windows the other day.

 

[writhziden]

You may want to try 11.9 or older drivers. The 12.x drivers have been causing issues on a number of systems of late; I am not sure why. Even my own system with an ATI card hangs every once in a while, but I do not get any blue screens, and the hangs are infrequent enough that I have not felt the need to roll back my driver yet.


The crashes themselves are inconclusive and blaming Windows processes. This typically indicates either Windows corruption or hardware. If changing out drivers for your graphics card does not help, run some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• I realize you already ran Memtest86+, but it may be worth running a second time when you have time to do so. Sometimes, Memtest86+ will miss testing parts of the RAM that are failing on a first run and will catch them on a second or third set of 7-10 passes.
  
  Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[Sickofguessing]

Read what you said about the drivers and the "AMD recommended" say 11.6b rollback which is pretty far back so I guess i'll try these.

What I will do is run through these tests I recognise furmark I just was not sure if I should do it. See if anything happens. But chances are I am just going to end up buying a new PSU to use my other G-Card as the problems with the Integrated GPU are getting on my nerves.

I literally have a anti-static mat /w the strap on my desk at all times so ESD protection is somthing I practice but I never would have thought about draining the circuit.

Thanks for the guide.