F5F Stay Refreshed Hardware Desktop System experiences unexpected shutdowns intermittently, but no blue screen appears.

System experiences unexpected shutdowns intermittently, but no blue screen appears.

System experiences unexpected shutdowns intermittently, but no blue screen appears.

Pages (3): 1 2 3 Next
K
KaisaSD2
Member
69
02-03-2019, 08:31 PM
#1
Over the past week my PC has been crashing frequently, sometimes multiple times a day. The issues vary—sometimes it restarts quickly and works fine afterward, other times the power button fails and the fans spin at high speed, around 4000 RPM or more. On the first day these problems appeared, I added two new fans (bringing the total to four), installed Commander Pro, set up Linux alongside Windows on a separate drive, and also experienced a thunderstorm followed by a brief power outage. Diagnosing the problem has been challenging since no error messages appear during crashes. My suspicion is that one component may be damaged. I built this system two years ago and it has always functioned properly until now. It would help if someone could confirm whether my guess is correct and identify the likely faulty part. Here are the details of your setup: Windows 10 Pro 64bit, AMD Ryzen 2700, Asus ROG Strix B450-I, Corsair Vengeance 16GB RAM, Seasonic M12 II Evo 520W, RTX 2060 Super FE, Crucial P5, 1TB boot drive (for Windows).
K
KaisaSD2
02-03-2019, 08:31 PM #1

Over the past week my PC has been crashing frequently, sometimes multiple times a day. The issues vary—sometimes it restarts quickly and works fine afterward, other times the power button fails and the fans spin at high speed, around 4000 RPM or more. On the first day these problems appeared, I added two new fans (bringing the total to four), installed Commander Pro, set up Linux alongside Windows on a separate drive, and also experienced a thunderstorm followed by a brief power outage. Diagnosing the problem has been challenging since no error messages appear during crashes. My suspicion is that one component may be damaged. I built this system two years ago and it has always functioned properly until now. It would help if someone could confirm whether my guess is correct and identify the likely faulty part. Here are the details of your setup: Windows 10 Pro 64bit, AMD Ryzen 2700, Asus ROG Strix B450-I, Corsair Vengeance 16GB RAM, Seasonic M12 II Evo 520W, RTX 2060 Super FE, Crucial P5, 1TB boot drive (for Windows).

J
Juan2610
Posting Freak
875
02-18-2019, 08:36 PM
#2
I would begin by unplugging the newly connected fans and controller, then check if the issue continues, considering they were installed just before the problem began.
J
Juan2610
02-18-2019, 08:36 PM #2

I would begin by unplugging the newly connected fans and controller, then check if the issue continues, considering they were installed just before the problem began.

M
MONSTERmoose91
Senior Member
526
02-28-2019, 04:39 PM
#3
First I’d ensure to trigger a BSOD to gather some details. Of course, you can check the Event Viewer, but you could also turn off automatic restarts. Open the command prompt with admin privileges and run: wmic RecoverOS set AutoReboot = False. Now you should see a BSOD and at least you’ll have more information to troubleshoot. To revert to the previous state, just set she a BSOD and make True for False.
M
MONSTERmoose91
02-28-2019, 04:39 PM #3

First I’d ensure to trigger a BSOD to gather some details. Of course, you can check the Event Viewer, but you could also turn off automatic restarts. Open the command prompt with admin privileges and run: wmic RecoverOS set AutoReboot = False. Now you should see a BSOD and at least you’ll have more information to troubleshoot. To revert to the previous state, just set she a BSOD and make True for False.

L
liflem
Member
163
03-06-2019, 03:26 AM
#4
I'm testing this now. If it doesn't work, I'll try this alternative: I checked the event viewer and the only issue I found was 41, which from my research indicates the PC didn't stop properly.
L
liflem
03-06-2019, 03:26 AM #4

I'm testing this now. If it doesn't work, I'll try this alternative: I checked the event viewer and the only issue I found was 41, which from my research indicates the PC didn't stop properly.

A
AllMightyPeco
Junior Member
23
03-06-2019, 11:35 AM
#5
I removed the commander pro feature and connected the two original fans to the motherboard as they were previously. That didn’t solve the issue. I’ve executed the command now, hoping for a blue screen when it crashes again.
A
AllMightyPeco
03-06-2019, 11:35 AM #5

I removed the commander pro feature and connected the two original fans to the motherboard as they were previously. That didn’t solve the issue. I’ve executed the command now, hoping for a blue screen when it crashes again.

M
Mali249
Member
68
03-08-2019, 08:37 PM
#6
It just stopped working again without triggering a blue screen.
M
Mali249
03-08-2019, 08:37 PM #6

It just stopped working again without triggering a blue screen.

F
FreshPrincess
Junior Member
23
03-08-2019, 11:08 PM
#7
F
FreshPrincess
03-08-2019, 11:08 PM #7

C
CytoPvP
Junior Member
13
03-11-2019, 05:08 AM
#8
I just replaced my RAM, restarted my PC, but it kept crashing again—both power button and pressing it failed. Only switching off and turning it back on worked to boot Windows normally. The issues aren’t limited to long usage; yesterday it didn’t crash at all, and today it happened for the second time. I’m still trying to figure out a pattern for when they occur.
C
CytoPvP
03-11-2019, 05:08 AM #8

I just replaced my RAM, restarted my PC, but it kept crashing again—both power button and pressing it failed. Only switching off and turning it back on worked to boot Windows normally. The issues aren’t limited to long usage; yesterday it didn’t crash at all, and today it happened for the second time. I’m still trying to figure out a pattern for when they occur.

L
Lipstick_Craft
Junior Member
3
03-11-2019, 10:54 AM
#9
It kept crashing again and this time the DRAM indicator on your motherboard lit up, unlike before. I looked up the issue and discovered it might be because your RAM isn’t properly connected to the memory slots. That could explain the instability. Your BIOS is outdated—your system uses 2801 from 2019 while the latest is 4901 from 2022. Updating the BIOS might help, but you should be cautious as it could affect compatibility with your older CPU.
L
Lipstick_Craft
03-11-2019, 10:54 AM #9

It kept crashing again and this time the DRAM indicator on your motherboard lit up, unlike before. I looked up the issue and discovered it might be because your RAM isn’t properly connected to the memory slots. That could explain the instability. Your BIOS is outdated—your system uses 2801 from 2019 while the latest is 4901 from 2022. Updating the BIOS might help, but you should be cautious as it could affect compatibility with your older CPU.

X
xxxLazersxxx
Member
117
03-27-2019, 08:50 PM
#10
If the DRAM light appears, it likely points to a RAM problem, though reseating it might only indicate a faulty stick. Rarely, incompatible modules can prevent booting instead of causing immediate errors. It doesn’t usually relate to BIOS settings. You could run Memtest86 to check for issues or observe crashes, which may suggest a broken or misaligned RAM module.
X
xxxLazersxxx
03-27-2019, 08:50 PM #10

If the DRAM light appears, it likely points to a RAM problem, though reseating it might only indicate a faulty stick. Rarely, incompatible modules can prevent booting instead of causing immediate errors. It doesn’t usually relate to BIOS settings. You could run Memtest86 to check for issues or observe crashes, which may suggest a broken or misaligned RAM module.

Pages (3): 1 2 3 Next