F5F Stay Refreshed Hardware Desktop Occasional system failures

Occasional system failures

Occasional system failures

R
rocra12
Member
52
02-19-2016, 05:29 PM
#1
I've been facing unexpected shutdowns for months now. It's really frustrating to try diagnosing the problem, as there can be days between each incident. The entire system will power off and restart repeatedly, regardless of what I'm doing—whether it's playing a game or browsing the web. This issue occurs with Windows 10 and 11. I replaced my power supply, but that didn't resolve it. I've run various stress tests like OCCT, MemTest64, CrystalDiskMark, and Cinebench, yet none triggered a crash. The crashes seem completely random. They began after I updated my BIOS. Since then, I've tested every BIOS version and even used the Asus AI Suite to update or downgrade it. Now I'm on the newest release, but it's still taking a long time between crashes. It's making troubleshooting really difficult. My next steps are: clearing the CMOS and removing one RAM stick. I'd appreciate any additional advice, and I hope we can solve this together. Specs: https://pcpartpicker.com/user/MagnusLund...iew=YfD3RB Thank you for your help. Best regards, Magnus
R
rocra12
02-19-2016, 05:29 PM #1

I've been facing unexpected shutdowns for months now. It's really frustrating to try diagnosing the problem, as there can be days between each incident. The entire system will power off and restart repeatedly, regardless of what I'm doing—whether it's playing a game or browsing the web. This issue occurs with Windows 10 and 11. I replaced my power supply, but that didn't resolve it. I've run various stress tests like OCCT, MemTest64, CrystalDiskMark, and Cinebench, yet none triggered a crash. The crashes seem completely random. They began after I updated my BIOS. Since then, I've tested every BIOS version and even used the Asus AI Suite to update or downgrade it. Now I'm on the newest release, but it's still taking a long time between crashes. It's making troubleshooting really difficult. My next steps are: clearing the CMOS and removing one RAM stick. I'd appreciate any additional advice, and I hope we can solve this together. Specs: https://pcpartpicker.com/user/MagnusLund...iew=YfD3RB Thank you for your help. Best regards, Magnus

M
51
02-19-2016, 08:08 PM
#2
You might want to use the memory diagnostic tool to inspect for damaged files, would you?
M
Mushroombowl05
02-19-2016, 08:08 PM #2

You might want to use the memory diagnostic tool to inspect for damaged files, would you?

T
TomTMR_NL
Junior Member
42
02-20-2016, 11:14 PM
#3
Open Event Viewer right after rebooting from a crash and review the logs. You’ll see details about the error that led to the PC crashing, helping you diagnose and fix the problem.
T
TomTMR_NL
02-20-2016, 11:14 PM #3

Open Event Viewer right after rebooting from a crash and review the logs. You’ll see details about the error that led to the PC crashing, helping you diagnose and fix the problem.

L
Lorddoom139
Posting Freak
956
02-25-2016, 10:39 PM
#4
I attempted that, but the error seemed unhelpful. I can try again whenever it decides to crash again.
L
Lorddoom139
02-25-2016, 10:39 PM #4

I attempted that, but the error seemed unhelpful. I can try again whenever it decides to crash again.

J
Jarniz
Junior Member
6
02-27-2016, 05:17 AM
#5
Using the event viewer requires navigating through various tabs. Under the system section, crashes are often unclear or attributed to issues like CPU problems. Record the time and date, then compare with app logs to identify which application or process caused the issue. Clearing logs after each boot helps avoid overwhelming information during unexpected crashes. Event details are listed, but you can also review other areas in the viewer where an app or process experienced a problem without crashing. These incidents may repeat, leading to sudden failures.
J
Jarniz
02-27-2016, 05:17 AM #5

Using the event viewer requires navigating through various tabs. Under the system section, crashes are often unclear or attributed to issues like CPU problems. Record the time and date, then compare with app logs to identify which application or process caused the issue. Clearing logs after each boot helps avoid overwhelming information during unexpected crashes. Event details are listed, but you can also review other areas in the viewer where an app or process experienced a problem without crashing. These incidents may repeat, leading to sudden failures.

L
lurado04
Member
106
02-28-2016, 11:39 PM
#6
I used the built-in utility, mdsched.exe, on Windows for memory testing and scanned for corruption with "sfc /scannow". No issues detected.
L
lurado04
02-28-2016, 11:39 PM #6

I used the built-in utility, mdsched.exe, on Windows for memory testing and scanned for corruption with "sfc /scannow". No issues detected.