BSOD playing computer games, multiple error codes (0x0000003B, ect)

Superfrog · 05 Dec 2015

Hello, and thanks for trying to help with this. I am having issues with several crashes, and one thing is constant. It only happens when graphics are involved. My pc crashes on games such as LoL, CoD:BO 1 and 2, Minecraft, and (for that random variable) Grim Fandango Remastered. I get 0x0000003B, 0x1000007e, and 0x00000109. If there was audio playing, it usually bugs out the speakers.

Only recently (as of the date of this thread) has something stranger occurred. 0x0000003B happened, but the audio looped back on the last 10 seconds of music playing. Attached is the crash report. Again, thanks for any help

**axe0** · 10 Dec 2015

Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD. Be sure to ONLY install the drivers.

Please uninstall AMD Quick Stream while troubleshooting.

Please update the Realtek network driver
Driver Reference Table - Rt64win7.sys

Please update NetBalancer or remove it while troubleshooting.

Code:

fffff880`0891a7d8  fffff880`111144f2Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0xa84f2
1: kd> lmvm atikmdag
start             end                 module name
fffff880`1106c000 fffff880`12576000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Tue Aug 04 05:28:52 2015 (55C03174)
    CheckSum:         014A6ED0
    ImageSize:        0150A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

fffff880`0891ac78  fffff880`05a6f096Unable to load image \SystemRoot\system32\DRIVERS\appexDrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for appexDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for appexDrv.sys
 appexDrv+0xe096
1: kd> lmvm appexDrv
start             end                 module name
fffff880`05a61000 fffff880`05aac000   appexDrv T (no symbols)           
    Loaded symbol image file: appexDrv.sys
    Image path: \SystemRoot\system32\DRIVERS\appexDrv.sys
    Image name: appexDrv.sys
    Timestamp:        Wed Jul 30 01:22:07 2014 (53D82C9F)
    CheckSum:         0003D974
    ImageSize:        0004B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

fffff880`0891af58  fffff880`04301ef6Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 Rt64win7+0x12ef6
1: kd> lmvm Rt64win7
start             end                 module name
fffff880`042ef000 fffff880`043ce000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Tue Mar 18 03:27:09 2014 (5327AEFD)
    CheckSum:         000EAC84
    ImageSize:        000DF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

fffff880`0891b168  fffff880`03e05225Unable to load image \SystemRoot\system32\DRIVERS\nbdrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nbdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for nbdrv.sys
 nbdrv+0x5225
1: kd> lmvm nbdrv
start             end                 module name
fffff880`03e00000 fffff880`03e0d000   nbdrv    T (no symbols)           
    Loaded symbol image file: nbdrv.sys
    Image path: \SystemRoot\system32\DRIVERS\nbdrv.sys
    Image name: nbdrv.sys
    Timestamp:        Fri Apr 19 21:13:41 2013 (51719765)
    CheckSum:         0000AE39
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Superfrog · 10 Dec 2015

I have uninstalled and reinstalled AMD Graphics drivers, removed Raptr and Quickstream, have removed NetBalancer for the time being, and have installed the update. Now what do I need to do to test?

**axe0** · 10 Dec 2015

Try to produce a crash, if a crash occurs run the dm log collector again > upload the new zip > give some description of what happened and what you were doing.

Superfrog · 11 Dec 2015

I can't seem to create another crash. However, they were pretty random when they would happen, but once they did, they would happen repeatedly

**axe0** · 11 Dec 2015

Sounds good :)
Hope it stays that way.

Superfrog · 12 Dec 2015

Question: If I mark it as solved, and it busts again, should I just make a new thread, or can I removed the mark as solved?

**axe0** · 13 Dec 2015

If another crash happens anytime soon, you can just unmark this thread as solved and reply here with a new zip from the dm log collector in a new post. I'll then be notified and reply when I have time.

If another crash happens some time after the last crash, it is better to create a new thread and upload a new zip from the dm log collector.

Superfrog · 16 Dec 2015

It seemed to hold. In fact, I have no issues with league anymore. Now I have two new issues. 0x000000fe, and a 0x0000001e. The fe occurred on shutdown. The pc hanged at the "Shutting Down..." screen, and gave me that issue. The next issue happened while online gaming on Path of Exile. Relevant data attached.

**axe0** · 16 Dec 2015

The 0xFE is caused by USB drivers, as is the 0x1E.
This has a few possibilities

USB port is faulty,
USB connection from connected device is faulty,
USB drivers are causing problems

Please disconnect every USB device, exception for mouse and keyboard, and see if you can produce another crash.
If you have any device attached that is very important, please be aware that you have to disconnect them too in order to proceed proper with troubleshooting and not loose anything important. It rarely happens that bluescreens and other problems are causing data corruption, the bluescreen is there to prevent it, but it might happen if troubleshooting is not done properly.