Blue screen issue 0x0000003B - Trying to find the cause

[Cody38]

Win7 64 bit
Asus 980 Strix GPU
MOBO: Manufacturer: Gateway, Model: FX6860
8GB unknown RAM
Unknown hard drive
750W Corsair PSU
i7-2600k CPU

Hello, for the past couple of years I have ignored this issue because it happens randomly and infrequently, but when it happens, it is very frustrating. I've decided to finally make a post since nothing I found helped.

My issue: I am having blue screens at random times, and it has no pattern. Sometimes I am in the middle of a game of Age of Empires or something and it blue screens, other times I am sitting on my desktop and it blue screens. Sometimes I blue screen 2 times in a day, sometimes I go 5 days without blue screening. Also, from time to time, my computer will simply freeze and I'll have to shut it off.

As seen in the title, the error code I get is 0x0000003B. According to this page: https://support.microsoft.com/en-us/kb/980932 the hotfix should be able to fix it, but it didn't for me; I tried that long ago.

Just a few weeks ago I went from a 7870 to a GTX 980, I figured that might fix the issue (uninstalling all AMD drivers and getting the Nvidia ones), but it didn't so to me that means the GPU isn't the issue.

I don't really have any ideas on what to do, and the only way I can know if something fixed my issue is to just wait at least 3 days and see if I bluescreen, since nothing seems to trigger it. Any help is appreciated, thanks.

 

[ICIT2LOL]

Hello and welcome Cody mate you can find the mobo model/number it is usually near the chipset or you can run this and find it Speccy - System Information - Free Download

For the BSOD stuff you need to do the dump files like in these tutorials please
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
&
http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

We can then run them off and try to analyse them.

PS pic of the Speccy output we need

 

[Cody38]

Okay I updated the main post. My computer was prebuilt and this MOBO seems to be made just for it. I used Speccy.

 

[ICIT2LOL]

So it gave you details on the mobo?? If not try this
Using HW Info
PART A:
You can test the volts on the PSU with HW Info HWiNFO, HWiNFO32/64 - Download < download the right bit version and close the right hand window select Sensors and scroll down to the power section where you will see what the volts are doing see my pic. In my pic the section (Nuvoton) with VBATT is a dead give away you are in the section for the rail voltages. There are other section titles and one that pops up often is ITE
Now the voltage on the different rails have to be within 5% =+/- of what is required or the machine will not work properly if at all.
ATX Minimum Specs:

3.3v Rail (ORANGE) (Min: 3.14v Max: 3.47v)

5v Rail (RED) (Min: 4.75v Max: 5.25v)

12v Rail (YELLOW) (Min: 11.4v Max: 12.6v)

(GREY CABLE PIN 8 - 5v = Power Good signal)

0v “Rail” (ALL BLACK cables, case, and board fixing screws)
See this for the rail voltage info
Power Supply 101: A Reference Of Specifications - Power Supplies (Section 2.)
The original right hand window shows the machine running and is handy for that but for looking at the components in some detail close it and use the main left hand side panel
FOR OTHER COMPONENTS
PART B:
Open each small square with + in it on the section the components are in and then click on the individual component/s (it will highlight in blue) - in the right hand side will appear all sorts of details including brands speeds and other essential info that particular device. See pic for example.

Use PART B: and click on the mobo and on the right there will be very detailed info on it - and anything else you would like to find in depth info on.

See my pic yours will probably have much more detail for the mobo

 

[Cody38]

Is this the info you were wanting? Sorry I was confused and thought you only wanted to know the name of the Mobo.

 

[ICIT2LOL]

Yes it was as you had in the first post just wanted to make sure because the drivers for it are best sourced from the manufacturer and now those volts in Speccy though maybe a tad incorrect would be good to see a run off of the HW Info software and post us back a pic of your PSU output because I have measured the readings many times against a dedicated digital multimeter and it is usually on the money.

You can of course get the volts from the BIOS but I prefer the HW run. Now I am only asking this because I like to run through stuff in a reasonably logical manner form simple to harder. For example if the PSU is out of whack then it makes sense that other components are not going to work properly either - remembering as I quoted in that ditty of mine that the voltage rails have to be within 5% of the required voltage otherwise the machine is going to function inappropriately or not at all.

 

[Golden]

The best approach to solving BSOD's is to examine the .dmp files.

The last BSOD was from 6 months ago, and points to the SoundTap driver. See if you can get an updated driver here:
Capture Audio/Music with SoundTap Streaming Audio Recorder

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800036fc1dc, fffff880080270e0, 0}

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

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

fffff880`05507000 fffff880`05523000   stdriver64 T (no symbols)           
    Loaded symbol image file: stdriver64.sys
    Image path: \SystemRoot\system32\DRIVERS\stdriver64.sys
    Image name: stdriver64.sys
    Timestamp:        Fri [B][COLOR="red"]Mar 18[/COLOR][/B] 10:47:45 [COLOR="red"][B]2011[/B][/COLOR] (4D82A4A9)
    CheckSum:         0001A464
    ImageSize:        0001C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Once updated, do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[Cody38]

I didn't even know I had sound tap, I'm just going to uninstall it unless you'd rather me do that process to ensure it was the issue first.

 

[Cody38]

So SoundTap is a part of a recording software called Debut. I got Debut probably 2 years ago and used it only once. I just uninstalled SoundTap, and when doing so, one of my options was to leave it installed but stop it from opening automatically every time I launched my PC. (It wouldn't open in a window or anything and I never noticed it in task manager, if it actually was opening).

Also I'm not sure why my PC hasn't recorded recent BSODs but I have definitely been having them still. I doubt the cause of them has changed in 6 months however.

Hopefully that was it, however stupid that seems but any other leads would be great, like if someone can check another crash file to see if SoundTap was the culprit there too. Thank you Golden.