System Thread Exception Not Handled (BSOD) Windows 8.1

works0fheart

Reputable
Oct 6, 2015
8
0
4,510
So I built my PC in 2012 and I've been running into the same issue ever since with BSOD errors. I thought it may have been something involving the OS I was using so I've switched between Windows 7, 8, and 8.1 several times. From a google search I'd found out that the problem may be an error with a driver for my GPU.

The BSOD usually occurs during any sort of video processes running, which is usually gaming. For instance, i will be playing Battlefield and it's nearly guaranteed to happen everytime. I thought this just may be an issue of the game being powerful, but it happens with almost any video processes, ie. Running less powerful games like Dota 2, or even watching a Twitch stream or YouTube video sometimes. The latter 2 don't usually happen unless I try to do more than one of those at once. If I'm on YouTube for instance and someone links me another video and I open it up it will usually cause a Blue Screen as well. I've also checked for issues with overheating and that hasn't been it either unfortunately.

I have tried updating my GPU drivers as well as my motherboard drivers, and rolling back the GPU ones a few times, so I'm not sure what is causing this.

My specs are as follows.

AMD FX-8350 8 Core 4.00 GHz CPU
MSi 990 FXA - GD80 motherboard
NVidia GTX 680 Video Card
16GB of RAM
Thermal take 1050W 12V PSU
WD 1TB HDD

I also have a few external things I run to my PC, such as my audio interface, the Fractal Audio Axe FX ii Mk ii and of course my peripherals.

The following image link is the Blue Screen Viewer list of error reports.

http://i.imgur.com/ktoD9hY.png


 
Solution
remove overclock driver and network packet injector: see below

directx was trying to resize some user mode buffer and passed a bad memory address.
you have overclocking software installed, you should remove it.

\C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Tue Sep 06 00:11:44 2011

you also have a network injector installed:
WinDivert.sys this is likely corrupting memory.

it also looks like your system is having issues doing sleep/wake cycles.
I would expect this would be a BIOS problem, look for a BIOS update.
machine info:
BIOS Version V11.12
BIOS Starting Address Segment f000
BIOS Release Date 07/24/2012
BIOS Version V11.12
BIOS Starting Address...
most of your bugchecks are in memory managment with a subcode of 0xc0000005 which is a bad memory address.
I would start by running memtest86 and confirming your memory is ok.
if the memory is ok, then remove any overclocking software and see if you still get bugchecks.

if the memtest86 does not find a problem, the boot windows and run cmd.exe as an admin, then run
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth

these will check your copy of windows for corruptions and attempt repairs.

if you don't find a cause, put your memory .dmp files on a server and post a link.

 

works0fheart

Reputable
Oct 6, 2015
8
0
4,510


I also ran the memtest for 4 hours last night, no errors found. I don't have any overclocking software installed that I've been using either.

scannow - http://i.imgur.com/X0uJttb.png
dism - http://i.imgur.com/BSjFPHh.png

Here is the dmp text file.

https://www.mediafire.com/?n9acm2aaj7vdad6

Neither of these seems to have worked.

I'd rather not just replace the hardware because it's been doing this since the PC was built, and being a student who's in school for IT/CET, I'd really like to learn what the problem is so I know how to begin to fix it.
 
start cmd.exe as an admin, then run
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth
then do a malwarebytes scan

(malware can corrupt files and cause this error just like a bios memory timing problem)

-----------
I need the actual memory dump file binary.
they are located in c:\windows\minidump directory by default

just put the last 5 on a server, mark them for public access and post a link.

each memory dump except one indicates a bad memory address passed to the kernel.
the exception was one that indicated a cache error in the CPU.

Cache errors generally indicate power problems. (if not overclocking or overheating)





 

works0fheart

Reputable
Oct 6, 2015
8
0
4,510


Here's the 5 dmp files while the system scans.
https://www.mediafire.com/folder/le852bwc3azf9/Dump_files

 
remove overclock driver and network packet injector: see below

directx was trying to resize some user mode buffer and passed a bad memory address.
you have overclocking software installed, you should remove it.

\C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Tue Sep 06 00:11:44 2011

you also have a network injector installed:
WinDivert.sys this is likely corrupting memory.

it also looks like your system is having issues doing sleep/wake cycles.
I would expect this would be a BIOS problem, look for a BIOS update.
machine info:
BIOS Version V11.12
BIOS Starting Address Segment f000
BIOS Release Date 07/24/2012
BIOS Version V11.12
BIOS Starting Address Segment f000
BIOS Release Date 07/24/2012
Manufacturer MSI
Product 990FXA-GD80 (MS-7640)
Version 2.2
Processor Version AMD FX(tm)-8350 Eight-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 4000MHz
Current Speed 4000MHz



 
Solution

works0fheart

Reputable
Oct 6, 2015
8
0
4,510


Okay, so I went to the location of the AODDriver2.sys and deleted it. I couldn't find anything titled ATI Technologies or Fuel in my programs list when I opened Add/Remove programs. Odd.

Deleted the WinDivert.sys file from C:\Program Files\KMSpico

I just updated my Bios last week using the support page here, so that's really strange as well.

http://us.msi.com/support/mb/990FXA-GD80.html#down-bios

Here are the results of the previous scans as admin.

http://imgur.com/a/bVZtf
 

works0fheart

Reputable
Oct 6, 2015
8
0
4,510
So I just tried to cause a BSOD to test if it worked by running 6 youtube videos and nothing happened so we might be in the clear, but I'm about to try to stress test it a little more just to be sure.
 

works0fheart

Reputable
Oct 6, 2015
8
0
4,510


It turns out I spoke too soon and the error is still occurring.. Very frustrating.