Solved BSOD playing CS:GO/APB/ARMA II, error 0x0000003b & 0x000000a

[fxblaze]

I've been having very random BSOD's while gaming. I can't seem to find a pattern for it. Sometimes it can happen several times within and hour or not for 12 hours. It only occurs during gaming. Normal operation, web browsing ect.. is not affected.

Specs:

Windows 7 Professional 64bit
i7 3770k
Asus P8z77-v
(4) 4G DDR3 1600 mhz
Sapphire 7970 OC 3Gb (running an eyefinity display group)
240G Sandisk SSD (OS Drive)
1 TB Seagate
Antec 620 cooler
1100w Majesty PSU

I have already ran mem tests (6 passes) with no errors. I also did a system verifier that also came back with no errors. I just reformatted as well thinking that it would solve it (hence only 2 dump files at this time), no luck. I also did a video card stress test with FurMark at max settings for an hour in an attempt to replicate the BSOD. No luck with that either (though that card took the stress like a boss ).

Sledgehammer is already on standby at this point.

 

[FredeGail]

Hello fxblaze and welcome to Sevenforums.

As it's only happening during gaming, what's the temperatures just before a crash? You can download Speccy and monitor those numbers.

Different culprits pointed towards your ATI Graphics Driver. Driver Sweeper will ensure that you'd have a clean install at the end of the procedure, and by that no leftover files that'd bork the system.

* Make your way to ATI Drivers - Downloads and download the latest driver for your card, save it to your desktop for instance
* Uninstall the Graphic driver you currently have and all its extensions (do not reboot yet)
* Download Driver Sweeper
* Get to safe mode (without network) and search for Driver Sweeper in your START
* Select all the ATI components and analyse them
* Clean them, head into Windows without internet and install the driver you've downloaded previously​

Best Regards,
Frederik.

 

[fxblaze]

Thanks for the reply. To answer your question, yes. Though it is only certain games and not all. I thought it might have been a heat issue as well, but as I was stressing the system to max I didn't experience any high temps (I think max was my GPU at 71 and that was average temp for an hour of stress).

I just did the sweeper and reinstall of my drivers. I also installed the monitor just in case. Question, does it save to a cache file if the system crashes? If not it will be hard to monitor as I only crash while in games.

I'm going to include the dumps from after my original post just so it will shed some more light to the issue. Hopefully..


Thanks for the help!

 

[FredeGail]

Question, does it save to a cache file if the system crashes?

Crash dumps, those you're uploading, tells us where your system crashed. You do not have to worry about monitoring where your system crashed, because I'll keep an eye on that pattern. What we'd need you to do, is to do our recommendations and suggestions obviously, and just keep uploading the dumps as they grow.

PROCESS_NAME:  firefox.exe [color="#00B050"](for instance)[/COLOR]

For now..

Combining your crash dumps and the general view of BSODs culprits, I'd suggest you to have a look at your memory, the sticks. Through decades people have been using the bootable tool called Memtest86+ and it's basically very unique in these manners.
:info: Be sure to check your warranty rules and regulations before opening your case.

* Memtest86+ is USB-ready, and can be booted directly from it. Download the flashdrive wizard.
* To ensure that either your sticks OR your motherboard slots are broken, it's necessary to do the below procedure-
* Pull out all sticks except ONE, scan it.
* If no errors, pull the scanned stick into another slot.
* Proceed like this until you've scanned all sticks individually, and all the slots.​

​

Cheers,
Frederik.

 

[fxblaze]

I have already ran mem tests (6 passes) with no errors

It's not the ram. That was the first thing I checked. Took quite a while to do I might add.

I'm just waiting right now. After doing the driver sweeper and reinstalling. I'll update you as more crashes come. Hopefully they won't.

 

[FredeGail]

Oh alright. I'm sorry I missed that detail.

Let's enable verifier then--

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.

So, 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) - and create a System Repair Disc (Win7) if you don't have a full installation DVD.
You can do this by going to Start...All Programs...Maintenance...Create a System Repair Disc (don't forget to test the disc to make sure it works).

For Vista, you can download the repair discs from different websites. If unable to locate them, shoot me a PM and I'll point you to them.
For Win8, BSOD's are different - and we'll have to adjust how we do this with them.

Also, to ensure that you can recover, here's another couple of additional steps:
- Get to the Safe Mode menu (rapidly tap F8 just before the Windows splash screen comes up). Scroll down to and select "Disable automatic restart on System Failure"
- Get the RED information from this picture (in particular we will need the name of the file that the error occurred in):
Picture of a BSOD

Then, here's the procedure to run Driver Verifier:
- 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 "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- 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.

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 (an estimate on my part).

Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Best Regards,
Frederik.

 

[fxblaze]

NO luck with verifier yet.

The ATI driver crash was also most likely because of new beta drivers. I'd ignore that one personally. However, ntoskrnl.exe needs to die.

P.S. Sorry for late reply, but it has frustrated me to the point of "living with it".

 

[fxblaze]

Problem persists.

 

[fxblaze]

Still nothing?

 

[fxblaze]

I'm still at a complete loss. I've even ran memtest again for a full 24 hours. I've has BSODs while even just browsing the web. Could it possibly be a graphics card defect? I don't even use my less than 6 month old desktop anymore because it just keeps crashing.

 

[koolkat77]

Can you please upload all the files following http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

(.dmps including all other files e.g msinfo etc.)

 

[fxblaze]

I've already cleaned out temp system files like that. If you want you can look back at my OP and look at those dumps as they are basically the same across the board. As new ones come in I'll post them as well. I had a sneaking suspicion that my .NET framework might have something to do with this, so I reinstalled that along with a fresh install of graphic drivers. Several people have already pitched the "reinstall windows" card. This is my fourth install of windows since September. I highly doubt it got corrupted 4 times in 4 months.

 

[fxblaze]

Here. These were all within like 10 mins.

 

[koolkat77]

Upload a screenshot of your hard disk using CrystalDiskInfo:

• CrystalDiskInfo - Software - Crystal Dew World
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Run Disk Check on your hard disk for file system errors and bad sectors on it:

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

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

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

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

 

[fxblaze]

Alright, I finally got frustrated with trying to solve this issue on my own. I took my PC to a repair store to have someone else look it over instead. He called me after a week and said that he couldn't find anything hardware related wrong with my PC. Tonight I decided that it must be corrupted files or something on my hard drives.

I reformatted BOTH my SSD (os drive) and my HDD (data drive) and reinstalled all my programs. I have received the same problems when trying to run a game. I was able to play for a few minutes before getting a BSOD. I honestly can't understand what the crap is going on.

All these checks you are asking me to do are coming back with absolutely no errors. I have no idea at this point. I will run it some more later and do a posting with the dumps as they come in.

 

[Vir Gnarus]

Interesting enough, the first two crashdumps you provided before sending it into the shop and having your drives wiped were both identical in that TeamSpeak was involved. These latest ones, however, aren't so definitive, and are pretty scattered. One did mention some USB device I/O, however. Perhaps there's an issue with your mic/headset? Try gaming with it disconnected and drivers/software for it uninstalled (and obviously leave TeamSpeak out too!).

I recommend turning on Driver Verifier and let it crash the system some more. Scrounge up the new crashdumps and send em on over.

 

[fxblaze]

Well I played around on it for a while and this is what I've gotten since the reformat.

 

[Vir Gnarus]

Did you remove the headset/mic and uninstall the software associated with it? I noticed you also did not turn on Driver Verifier. Please do so and provide us the crashdumps for any crashes that occur following its activation. If it causes a boot loop, you can enter Safe Mode and turn it off. You must restart the system cleanly to save any changes to DV.

 

[Northernsoul55]

hi fxblaze,

Just thought I would put my 2 peneth in :

Does the driver package you installed, contain these drivers and Catalyst Control Center?:

Display Driver
OpenCL(tm) Driver
AMD Integrated Driver
Catalyst Control Center

AMD Catalyst

You could give this solution a try:
Please Unistall (dont reinstall) the Catalyst Control Center and catalyst install manager:
Reboot in normal mode and see if issue remains, (you can re-install the Catalyst Control Center and manager if issue remains).
Worth a try at this point as CCC is well known to throw up BSOD's.

Please see my previous post and solution on this issue:

http://www.sevenforums.com/performance-maintenance/272174-frequent-bsod-7.html

Cheers and Good luck!!


Dave

 

[fxblaze]

Did you remove the headset/mic and uninstall the software associated with it? I noticed you also did not turn on Driver Verifier. Please do so and provide us the crashdumps for any crashes that occur following its activation. If it causes a boot loop, you can enter Safe Mode and turn it off. You must restart the system cleanly to save any changes to DV.

Headset unplugged and drivers removed. Just use the same settings from the first time verifier was suggested?

hi fxblaze,

Just thought I would put my 2 peneth in :

Does the driver package you installed, contain these drivers and Catalyst Control Center?:

Display Driver
OpenCL(tm) Driver
AMD Integrated Driver
Catalyst Control Center

AMD Catalyst

You could give this solution a try:
Please Unistall (dont reinstall) the Catalyst Control Center and catalyst install manager:
Reboot in normal mode and see if issue remains, (you can re-install the Catalyst Control Center and manager if issue remains).
Worth a try at this point as CCC is well known to throw up BSOD's.

Please see my previous post and solution on this issue:

http://www.sevenforums.com/performance-maintenance/272174-frequent-bsod-7.html

Cheers and Good luck!!


Dave

Thanks for the input!

I'm going to give the driver verifier a whirl for a day or so and then I'll try your idea if the problem persists. I can say I've never had these sort of issues with CCC. It's almost enough to make me go NVidia!