SYSTEM_THREAD_EXCEPTION_NOT_HANDLED crash error

eman2002826

Reputable
Jan 10, 2017
7
0
4,520
Hi this is my first time ever using Tom's Hardware, so excuse my lack of knowledge.

I've been getting the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error every week or two for the past year, and I'm fed up. Haven't seen any patterns of why it occurs, sometimes happens when I play games, sometimes when I'm only watching youtube. Sometimes when I've had my PC on for hours, sometimes when I've just turned it on. Plz help

Specs:
AMD FX-6300

Gigabyte Technology Co. Ltd.
Model: 970A-DS3P

ATI AMD Radeon (TM) R9 380X

16GB RAM

APEVIA 800-WATT PSU




~Thanks


 
Solution
Have you changed hardware recently? This sounds like a driver issue, have you tried different GPU's? This page isn't very helpful...

(Developer Content) Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

If I had to guess (and I am), out of the 3 common occurrences this one looks the most hopeful "0x80000002: STATUS_DATATYPE_MISALIGNMENT" That could mean a bad driver somewhere. The other 2 look less hopeful as they could come from anywhere (but then again, bad data types can too).

It appears it could be anything, so without debugging the operating system and hardware it may be hard to tell. But I'd suspect the GPU first, then permanent storage, then voltages and finally memory. If it was me, and it was not the GPU, HDD, PSU or...

fluked

Commendable
Jan 25, 2017
66
0
1,660
Have you changed hardware recently? This sounds like a driver issue, have you tried different GPU's? This page isn't very helpful...

(Developer Content) Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

If I had to guess (and I am), out of the 3 common occurrences this one looks the most hopeful "0x80000002: STATUS_DATATYPE_MISALIGNMENT" That could mean a bad driver somewhere. The other 2 look less hopeful as they could come from anywhere (but then again, bad data types can too).

It appears it could be anything, so without debugging the operating system and hardware it may be hard to tell. But I'd suspect the GPU first, then permanent storage, then voltages and finally memory. If it was me, and it was not the GPU, HDD, PSU or a bad DIMM, then I would do a BIOS upgrade if possible. If that didn't help, I'd throw in the towel or actual debug the system (but I wouldn't debug, I'd just throw in the towel :).

BTW, you could boot another operating system off a USB drive and run that for a while. If it crashed in that, you could assume it is hardware related. Sorry I couldn't be more helpful, but windows kernel bugs can be a nightmare :-/
 
Solution

eman2002826

Reputable
Jan 10, 2017
7
0
4,520


I know my GPU drivers are up to date, and I don't have any others to test with (this is my first build). I don't think it matters if I changed my hardware recently because I've been getting this error for almost a year now. I'll check around my other drivers for anything not up to date.