F5F Stay Refreshed Software Operating Systems Exception in system thread not managed properly

Exception in system thread not managed properly

Exception in system thread not managed properly

S
Silvinha10
Senior Member
694
08-01-2016, 05:17 PM
#1
You're experiencing BSOD on startup with your Asus TUF saber tooth 990fx R3 running AMD 8350 CPU and Windows 10 Pro 64-bit. The message indicates a system thread exception isn't handled, often linked to driver issues. Even after booting in minimal safe mode via Command Prompt and using bcdedit, the problem persists. You're considering creating a repair disk but lack access to another machine.
S
Silvinha10
08-01-2016, 05:17 PM #1

You're experiencing BSOD on startup with your Asus TUF saber tooth 990fx R3 running AMD 8350 CPU and Windows 10 Pro 64-bit. The message indicates a system thread exception isn't handled, often linked to driver issues. Even after booting in minimal safe mode via Command Prompt and using bcdedit, the problem persists. You're considering creating a repair disk but lack access to another machine.

J
Just_Golden
Junior Member
9
08-01-2016, 10:12 PM
#2
It seems windows might be affected, but I’d appreciate additional perspectives since I can’t obtain a repair disk.
J
Just_Golden
08-01-2016, 10:12 PM #2

It seems windows might be affected, but I’d appreciate additional perspectives since I can’t obtain a repair disk.

A
Acekilla
Junior Member
40
08-03-2016, 12:33 PM
#3
Open Event Viewer, locate the critical and warning entries for the event, then match the ID and parameters against Microsoft's documentation.
A
Acekilla
08-03-2016, 12:33 PM #3

Open Event Viewer, locate the critical and warning entries for the event, then match the ID and parameters against Microsoft's documentation.

A
akjosh47
Member
190
08-04-2016, 06:15 AM
#4
I attempted to launch Event Viewer via the command prompt in the Windows Recovery Environment, but it reported it couldn't be identified as a valid command.
A
akjosh47
08-04-2016, 06:15 AM #4

I attempted to launch Event Viewer via the command prompt in the Windows Recovery Environment, but it reported it couldn't be identified as a valid command.

C
CandyLover100
Junior Member
45
08-07-2016, 11:49 AM
#5
It occurred on my computer as well. Removing one of my RAM modules fixed it. After a month, I reinstalled it and everything worked again. No issues have arisen since then. Begin removing your RAM.
C
CandyLover100
08-07-2016, 11:49 AM #5

It occurred on my computer as well. Removing one of my RAM modules fixed it. After a month, I reinstalled it and everything worked again. No issues have arisen since then. Begin removing your RAM.

_
_Sheep_Guy_
Member
53
08-07-2016, 12:19 PM
#6
It's disappointing, but I bought the same motherboard just three weeks ago after my older one failed. I'm using an AMD FX 8370 black and so far everything is working smoothly except for some overclocking challenges. Right now it's running at 4.334 GHz and I'm aiming for 4.5 GHz. Please help identify the issue quickly. Good luck, and let me know your findings. I've noticed this board offers more features than Carter had peanuts.
_
_Sheep_Guy_
08-07-2016, 12:19 PM #6

It's disappointing, but I bought the same motherboard just three weeks ago after my older one failed. I'm using an AMD FX 8370 black and so far everything is working smoothly except for some overclocking challenges. Right now it's running at 4.334 GHz and I'm aiming for 4.5 GHz. Please help identify the issue quickly. Good luck, and let me know your findings. I've noticed this board offers more features than Carter had peanuts.

S
SuperGlasses
Member
57
08-07-2016, 04:37 PM
#7
I used both my present 8GB dimmers individually in each port and also tried one of my previous 4GB dimmers in each port, but the issue persists.
S
SuperGlasses
08-07-2016, 04:37 PM #7

I used both my present 8GB dimmers individually in each port and also tried one of my previous 4GB dimmers in each port, but the issue persists.

F
Fabista
Member
175
08-11-2016, 10:45 AM
#8
Personally, the board works well for me. The only issue is that the high TDP chipsets get warm, though liquid cooling helps. The Windows software and some poorly designed programs have caused several problems.
F
Fabista
08-11-2016, 10:45 AM #8

Personally, the board works well for me. The only issue is that the high TDP chipsets get warm, though liquid cooling helps. The Windows software and some poorly designed programs have caused several problems.

T
TheFallenRose
Senior Member
616
08-18-2016, 06:36 PM
#9
Hope they come together quickly. My next endeavor is an AIO. Regarding the VRM, I placed a 40cm fan beneath the shroud as directed before enclosing the board in the case.
T
TheFallenRose
08-18-2016, 06:36 PM #9

Hope they come together quickly. My next endeavor is an AIO. Regarding the VRM, I placed a 40cm fan beneath the shroud as directed before enclosing the board in the case.