F5F Stay Refreshed Hardware Desktop Problem with restarting the system. Issue detected during reboot process.

Problem with restarting the system. Issue detected during reboot process.

Problem with restarting the system. Issue detected during reboot process.

Y
YogurtPants
Junior Member
2
12-19-2017, 12:49 AM
#1
CPU model is I7 9700KF, motherboard H310M, M.2 slot, 8GB RAM Kingston 2600MHz, 750W Thermaltake 80 gold full form factor GPU, RX 6650XT AIO from ASUS, power supply brand new (about two days old), storage includes WD SATA M.2 500GB and WD 1TB drives, BlueSeagate 1TB.

I’ve been experiencing random restarts and bluescreens for months. Initially, I thought it was GPU driver issues, but even after updating the latest drivers for my RX 6650XT, the problem persisted. Over time I stopped noticing it because it wasn’t frequent. I began playing games like ARK or ROR2—ARK occasionally crashes after about ten minutes, but ROR2 never does.

My first suspicion was the PSU; I replaced it since it was four years old. However, the issue remains unchanged. I also swapped RAM and tested another brand new GPU from a friend, which still crashes. My final thought is that either the motherboard or CPU might be faulty. I don’t have a spare CPU to test, but I’m working on it.

Additionally, I observed unusual behavior in the motherboard’s MOSFETs. I’ll attach a photo so you can see if this is normal. I also reinstalled Windows 10 and performed a clean driver update, but nothing resolved the problem.
Y
YogurtPants
12-19-2017, 12:49 AM #1

CPU model is I7 9700KF, motherboard H310M, M.2 slot, 8GB RAM Kingston 2600MHz, 750W Thermaltake 80 gold full form factor GPU, RX 6650XT AIO from ASUS, power supply brand new (about two days old), storage includes WD SATA M.2 500GB and WD 1TB drives, BlueSeagate 1TB.

I’ve been experiencing random restarts and bluescreens for months. Initially, I thought it was GPU driver issues, but even after updating the latest drivers for my RX 6650XT, the problem persisted. Over time I stopped noticing it because it wasn’t frequent. I began playing games like ARK or ROR2—ARK occasionally crashes after about ten minutes, but ROR2 never does.

My first suspicion was the PSU; I replaced it since it was four years old. However, the issue remains unchanged. I also swapped RAM and tested another brand new GPU from a friend, which still crashes. My final thought is that either the motherboard or CPU might be faulty. I don’t have a spare CPU to test, but I’m working on it.

Additionally, I observed unusual behavior in the motherboard’s MOSFETs. I’ll attach a photo so you can see if this is normal. I also reinstalled Windows 10 and performed a clean driver update, but nothing resolved the problem.

G
green_Ateh
Member
56
12-19-2017, 12:49 AM
#2
I don't have personal knowledge of specific blue screen codes, but I can help you identify them if you provide more details about the error message or system behavior.
G
green_Ateh
12-19-2017, 12:49 AM #2

I don't have personal knowledge of specific blue screen codes, but I can help you identify them if you provide more details about the error message or system behavior.

Z
zMadeus
Posting Freak
755
12-19-2017, 12:49 AM
#3
I don't recall, the screens only showed issues a while back, now it's just a restart and it functions properly until I launch those two programs.
Z
zMadeus
12-19-2017, 12:49 AM #3

I don't recall, the screens only showed issues a while back, now it's just a restart and it functions properly until I launch those two programs.

P
ProSkipperz
Member
129
12-19-2017, 12:49 AM
#4
I can review the Windows Event Viewer to identify any critical or error events that happened prior to the crash.
P
ProSkipperz
12-19-2017, 12:49 AM #4

I can review the Windows Event Viewer to identify any critical or error events that happened prior to the crash.

S
Splax67
Member
190
12-19-2017, 12:49 AM
#5
I started ROR2 for 30 seconds and it turned blue after 5 months. The error code was WHEA_UNCORRECTABLE_ERROR. It looks like the same issue appeared previously.
S
Splax67
12-19-2017, 12:49 AM #5

I started ROR2 for 30 seconds and it turned blue after 5 months. The error code was WHEA_UNCORRECTABLE_ERROR. It looks like the same issue appeared previously.

M
MigosATL
Member
213
12-19-2017, 12:49 AM
#6
The issue is typically related to hardware, possibly involving various components like the power supply, graphics card, and RAM. Since you've already checked other parts, we can focus on those. Are you overclocking at the moment? This error may arise from unstable voltages or inconsistent data on your CPU and SSD. It’s not a definitive answer, but I recommend using Crystaldiskinfo to assess your SSD's health and running Chkdsk in the command prompt to scan for bad sectors.
M
MigosATL
12-19-2017, 12:49 AM #6

The issue is typically related to hardware, possibly involving various components like the power supply, graphics card, and RAM. Since you've already checked other parts, we can focus on those. Are you overclocking at the moment? This error may arise from unstable voltages or inconsistent data on your CPU and SSD. It’s not a definitive answer, but I recommend using Crystaldiskinfo to assess your SSD's health and running Chkdsk in the command prompt to scan for bad sectors.

B
Bigzwerg1998
Junior Member
11
12-19-2017, 12:49 AM
#7
I've completed everything before; I ran chkdsk but it didn't help. I can't perform an OS installation because my motherboard doesn't support it.
B
Bigzwerg1998
12-19-2017, 12:49 AM #7

I've completed everything before; I ran chkdsk but it didn't help. I can't perform an OS installation because my motherboard doesn't support it.

A
Alexandrea1
Member
233
12-19-2017, 12:49 AM
#8
Generally, the most probable issue is RAM, followed by the motherboard, and then the CPU is least likely. Since you’ve already replaced the RAM to check, the next step should be the motherboard. I’d like to know if you can swap it with another unit or proceed with a return warranty claim if it’s still covered. The CPU causing the problem is possible but unlikely. You may have tried this before, so consider performing a BIOS reset and removing the CMOS battery for 15 minutes.
A
Alexandrea1
12-19-2017, 12:49 AM #8

Generally, the most probable issue is RAM, followed by the motherboard, and then the CPU is least likely. Since you’ve already replaced the RAM to check, the next step should be the motherboard. I’d like to know if you can swap it with another unit or proceed with a return warranty claim if it’s still covered. The CPU causing the problem is possible but unlikely. You may have tried this before, so consider performing a BIOS reset and removing the CMOS battery for 15 minutes.