BSOD while Gaming, Error 0x0000003B

bode1971 · 27 Jun 2015

Windows 7 Ultimate x64
Gigabyte GA-Z77X-D3H

CPU i7-3770k
Radeon R9-290

Over the past 4 months I have been getting random BSOD with error 0x0000003B. I can go anywhere between 2 to 10 days between a Blue Screen event and they all show with the same error code.

I have been slowly trying to update / replace drivers and thought I had sorted it after installing a new NIC earlier in the week however tonight there was another crash. This only happens when gaming and isnt tied into any specific game. I game professionally recording to upload online. Last weekend I added a PCIE NIC to rule out the on board Lan. System is close to 3 years old and the only hardware change since it was build was adding the r290 and the recent NIC.

The last 4 minidump files are attached.

bode1971 · 28 Jun 2015

I have just reinstalled my old GPU as this is the only hardware component that has changed in the last 2 years to rule out the R9-290 being a problem.

Arc · 28 Jun 2015

Apparently it is Avast that is causing the issue.

Uninstall Avast using Avast Uninstall Utility. At least as a test. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Report us for any further BSOD after doing it.

Edit:

You have both Avast and MSE installed at the same time!!!! Never install two different real time protection programs at the same time. It is a dangerous idea.

Go uninstall Avast.
_________________________________________________

Code:

BugCheck 3B, {c0000005, fffff88001c3be9d, fffff8800cb56f80, 0}

*** WARNING: Unable to verify timestamp for aswStm.sys
*** ERROR: Module load completed but symbols could not be loaded for aswStm.sys
Probably caused by : NETIO.SYS ( NETIO!StreamCalloutProcessingLoop+ad )

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

bode1971 · 28 Jun 2015

Seems a little odd that the system has been running with avast for 3 years and only the last few months since changing GPU the issue has occured. However the logs dont lie. As mentioned it usually happens once a week, I will remove Avast and update the post in a week or 2 either way.

Thanks for your time Arc.

Arc · 29 Jun 2015

bode1971 said:

Seems a little odd that the system has been running with avast for 3 years and only the last few months since changing GPU the issue has occured. However the logs dont lie. As mentioned it usually happens once a week, I will remove Avast and update the post in a week or 2 either way.

Thanks for your time Arc.

You used Avast and MSE together over 3 years?

Then it is the only odd that it did that late to cause the BSOD.

bode1971 · 11 Jul 2015

I havent had any further blue screens since the above.

As noted above I removed the r290 when I made the post as it was the only thing that changed in the system since I started getting the crashes. I ran the system for 12 days with my old GPU in and didnt have any issues, at this point I had not removed Avast as I wanted to be sure if the GPU was the cause. I am now sure there was a problem with the GPU and have uninstalled Avast from my system as per advice as although it hadnt caused me problems for 3 years having 2 anti virus active is definitely not advised as they will definitely conflict at some point.

Thanks for the help Arc. If I see any further issues I will open another post..

Arc · 12 Jul 2015

No problem mate. The computer is running stable at this moment, that is good enough. :)