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

Page 1 of 5 123 ... LastLast

  1. Posts : 23
    Windows 7 Professional x64
       #1

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


    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.
      My Computer


  2. Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       #2

    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.
      My Computer


  3. Posts : 23
    Windows 7 Professional x64
    Thread Starter
       #3

    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!
      My Computer


  4. Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       #4

    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.

    Code:
    PROCESS_NAME:  firefox.exe (for instance)
    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.
    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.
      My Computer


  5. Posts : 23
    Windows 7 Professional x64
    Thread Starter
       #5

    fxblaze said:
    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.
      My Computer


  6. Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       #6

    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:
    Code:
    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.
      My Computer


  7. Posts : 23
    Windows 7 Professional x64
    Thread Starter
       #7

    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".
      My Computer


  8. Posts : 23
    Windows 7 Professional x64
    Thread Starter
       #8

    Problem persists.
      My Computer


  9. Posts : 23
    Windows 7 Professional x64
    Thread Starter
       #9

    Still nothing?
      My Computer


  10. Posts : 23
    Windows 7 Professional x64
    Thread Starter
       #10

    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.
      My Computer


 
Page 1 of 5 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:39.
Find Us