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): Previous 1 2 3 Next
Y
yosoybetog
Junior Member
5
04-07-2019, 07:34 AM
#11
You completed a full 2 hours and 30 minutes of testing with MemTest86, running around 3.5 passes without encountering any issues.
Y
yosoybetog
04-07-2019, 07:34 AM #11

You completed a full 2 hours and 30 minutes of testing with MemTest86, running around 3.5 passes without encountering any issues.

B
byZeto
Junior Member
42
04-27-2019, 05:38 AM
#12
I don't have access to the current BIOS version of the motherboard. You can check it by opening the BIOS settings during startup or using manufacturer-provided tools.
B
byZeto
04-27-2019, 05:38 AM #12

I don't have access to the current BIOS version of the motherboard. You can check it by opening the BIOS settings during startup or using manufacturer-provided tools.

O
onelolo57
Member
62
04-28-2019, 12:22 AM
#13
O
onelolo57
04-28-2019, 12:22 AM #13

M
MavrosGR
Senior Member
579
05-04-2019, 11:01 PM
#14
Alright; remove one RAM stick and check if the system still fails. Wait a while, then replace that stick with the removed one and test again. If it only fails with one stick, a problem might be with that specific stick; if both fail or stop working, another factor is likely involved. It's possible a single stick is damaged, but this shouldn't relate to compatibility. I haven't heard of incompatible RAM causing crashes like this, and it doesn't seem logical for the behavior described.
M
MavrosGR
05-04-2019, 11:01 PM #14

Alright; remove one RAM stick and check if the system still fails. Wait a while, then replace that stick with the removed one and test again. If it only fails with one stick, a problem might be with that specific stick; if both fail or stop working, another factor is likely involved. It's possible a single stick is damaged, but this shouldn't relate to compatibility. I haven't heard of incompatible RAM causing crashes like this, and it doesn't seem logical for the behavior described.

S
SimplyyRaz
Member
202
05-04-2019, 11:50 PM
#15
You don’t need to rely solely on my statements. There should be at least a hundred discussions here showing users reporting issues with Corsair RAM compatibility with Ryzen processors.
S
SimplyyRaz
05-04-2019, 11:50 PM #15

You don’t need to rely solely on my statements. There should be at least a hundred discussions here showing users reporting issues with Corsair RAM compatibility with Ryzen processors.

M
230
05-07-2019, 12:17 AM
#16
I understand, but faulty RAM shouldn't behave this way. The crash OP mentioned points to an issue with the RAM module or a loss of connection in the slot, which is unusual for incompatible RAM and usually results in the system failing to start properly.
M
MaddieStarr801
05-07-2019, 12:17 AM #16

I understand, but faulty RAM shouldn't behave this way. The crash OP mentioned points to an issue with the RAM module or a loss of connection in the slot, which is unusual for incompatible RAM and usually results in the system failing to start properly.

K
Killa_Dx
Senior Member
645
05-07-2019, 01:21 AM
#17
You're thinking about using all three sticks in your Intel system. Did you check if he cleared his CMOS? It’s possible he didn’t. I’ve asked him before and just got ignored. Adding more RAM can cause issues, so I suggested taking it out. You might also try adjusting vdimm a bit higher and trfc a bit lower. Also, is that a 2700X speed? Do they really reach 3200 MT/s?
K
Killa_Dx
05-07-2019, 01:21 AM #17

You're thinking about using all three sticks in your Intel system. Did you check if he cleared his CMOS? It’s possible he didn’t. I’ve asked him before and just got ignored. Adding more RAM can cause issues, so I suggested taking it out. You might also try adjusting vdimm a bit higher and trfc a bit lower. Also, is that a 2700X speed? Do they really reach 3200 MT/s?

C
cheke150
Junior Member
10
05-08-2019, 12:36 AM
#18
That's a different post, right?
C
cheke150
05-08-2019, 12:36 AM #18

That's a different post, right?

L
LorrenK
Senior Member
703
05-11-2019, 01:18 AM
#19
In my view, the problem isn't hardware-related. The system posts and boots to Windows and DRAM LED indicators only during crashes, which might suggest a Windows issue trying to access memory that triggers the crash. This reminds me of the Greg Salazar (YT) case with his AMD GPU drivers. By default, the power switch shuts down the OS, but when it crashes, pressing the power button for 5 seconds forces a shutdown. The issue doesn’t appear on Linux and hasn’t happened in two years, so I’m leaning toward a software problem. Only the lack of BSOD seems to make me think otherwise. Of course, I might be mistaken, but... I have three questions for you, @Blechlawine. 1. Could you describe what you were doing right before the system crashed? 2. Please verify if everything is normal in Device Manager (press Win + X, then Device Manager). (Win + X, Device Manager) 3. Have you installed Corsair LINK for your Commander Pro?
L
LorrenK
05-11-2019, 01:18 AM #19

In my view, the problem isn't hardware-related. The system posts and boots to Windows and DRAM LED indicators only during crashes, which might suggest a Windows issue trying to access memory that triggers the crash. This reminds me of the Greg Salazar (YT) case with his AMD GPU drivers. By default, the power switch shuts down the OS, but when it crashes, pressing the power button for 5 seconds forces a shutdown. The issue doesn’t appear on Linux and hasn’t happened in two years, so I’m leaning toward a software problem. Only the lack of BSOD seems to make me think otherwise. Of course, I might be mistaken, but... I have three questions for you, @Blechlawine. 1. Could you describe what you were doing right before the system crashed? 2. Please verify if everything is normal in Device Manager (press Win + X, then Device Manager). (Win + X, Device Manager) 3. Have you installed Corsair LINK for your Commander Pro?

I
iKegreenS_
Posting Freak
878
05-11-2019, 07:38 AM
#20
You're working with a 2801 board that has two 8GB sticks in a kit. Since you have only two sticks, you can choose either one for your build. Also, you're planning to reset CMOS because you haven't done it yet. You mentioned having three sticks but only two are available—likely due to the ITX size and CPU type. Your CPU is a 2700, not the 2700X, and your RAM is at 2933 MHz, which matches the speed supported by the chip without any overclocking. The DRAM LED sometimes lights up during crashes, but it didn't activate when it crashed today, and the system rebooted immediately afterward.
I
iKegreenS_
05-11-2019, 07:38 AM #20

You're working with a 2801 board that has two 8GB sticks in a kit. Since you have only two sticks, you can choose either one for your build. Also, you're planning to reset CMOS because you haven't done it yet. You mentioned having three sticks but only two are available—likely due to the ITX size and CPU type. Your CPU is a 2700, not the 2700X, and your RAM is at 2933 MHz, which matches the speed supported by the chip without any overclocking. The DRAM LED sometimes lights up during crashes, but it didn't activate when it crashed today, and the system rebooted immediately afterward.

Pages (3): Previous 1 2 3 Next