F5F Stay Refreshed Hardware Desktop Boot failure detected. Diagnostic results indicate issues with DRAM or boot process.

Boot failure detected. Diagnostic results indicate issues with DRAM or boot process.

Boot failure detected. Diagnostic results indicate issues with DRAM or boot process.

Y
Yoshix
Member
228
11-20-2021, 03:07 AM
#1
System: i9-11900KF GIGABYTE Z590 UD AC Gigabyte 3080TI 32GB DDR4 G.Skill 3200MHZ 2x 16GB sticks EVGA Supernova 1000 Watt power supply Windows 10 home New here. I fixed the issue, but I'm still unsure what led to it. I took the machine apart by unplugging parts, moved it just a bit, then plugged it back in. It didn't start up at all. When I opened the BIOS, it kept showing a failed boot error, possibly due to bad hardware or configuration. I checked the DRAM and found a red diagnostic light for memory and boot status. I removed one stick, swapped it with the original one I had taken out, and it worked fine after resetting the BIOS. After reinserting everything, I removed the CMOS battery to clear settings and got a clean Windows boot. This hasn't happened before—I only build computers for personal use. What might have gone wrong? Could something be faulty?
Y
Yoshix
11-20-2021, 03:07 AM #1

System: i9-11900KF GIGABYTE Z590 UD AC Gigabyte 3080TI 32GB DDR4 G.Skill 3200MHZ 2x 16GB sticks EVGA Supernova 1000 Watt power supply Windows 10 home New here. I fixed the issue, but I'm still unsure what led to it. I took the machine apart by unplugging parts, moved it just a bit, then plugged it back in. It didn't start up at all. When I opened the BIOS, it kept showing a failed boot error, possibly due to bad hardware or configuration. I checked the DRAM and found a red diagnostic light for memory and boot status. I removed one stick, swapped it with the original one I had taken out, and it worked fine after resetting the BIOS. After reinserting everything, I removed the CMOS battery to clear settings and got a clean Windows boot. This hasn't happened before—I only build computers for personal use. What might have gone wrong? Could something be faulty?

M
MehSparky
Member
193
11-20-2021, 04:16 AM
#2
The DDR4 setup places memory in the second and fourth slots, or A1 and B1, similar to how DDR3 did before dual-channel became standard. Nice work getting it sorted!
M
MehSparky
11-20-2021, 04:16 AM #2

The DDR4 setup places memory in the second and fourth slots, or A1 and B1, similar to how DDR3 did before dual-channel became standard. Nice work getting it sorted!

M
martims098
Member
193
11-20-2021, 01:05 PM
#3
The memory was located in the 2nd and 4th positions. I changed the order of the sticks, moving the one from the 4th to the 2nd and vice versa. This might explain why I was confused about the original issue—perhaps a bios-related problem?
M
martims098
11-20-2021, 01:05 PM #3

The memory was located in the 2nd and 4th positions. I changed the order of the sticks, moving the one from the 4th to the 2nd and vice versa. This might explain why I was confused about the original issue—perhaps a bios-related problem?

D
DaLoneDwarf98
Member
54
11-22-2021, 06:01 AM
#4
Maybe one of the sticks wasn't seated all the way in at the bottom where there isn't a clip? Gotta hear both ends click in though.
D
DaLoneDwarf98
11-22-2021, 06:01 AM #4

Maybe one of the sticks wasn't seated all the way in at the bottom where there isn't a clip? Gotta hear both ends click in though.

T
TheRedPhoenixx
Member
95
11-22-2021, 07:59 AM
#5
They sat correctly since the tool that was initially in position 2 was removed and reinserted twice just to confirm, yet the same issue persisted until I swapped the slot 4 stick into slot 2.
T
TheRedPhoenixx
11-22-2021, 07:59 AM #5

They sat correctly since the tool that was initially in position 2 was removed and reinserted twice just to confirm, yet the same issue persisted until I swapped the slot 4 stick into slot 2.

R
RAGINGKODGRIMM
Member
59
11-23-2021, 09:03 AM
#6
I'm experiencing the same problem right now. For a couple of days. Yesterday I posted about an MSI motherboard that kept giving me the same error. After a lot of troubleshooting, it finally worked. After reseating the CPU and memory, and doing some other checks, it started functioning again. I tried turning it on and off after lunch and it worked immediately. It booted right away and stayed operational for the rest of the day. I turned it off and went to bed, and it's been working again today. The screen goes black, I can't access Windows or open BIOS, and the DRAM error light is on. Any clue what might be causing this? I'm not sure. We have similar systems. My setup includes an MSI Z590, an i5 11600K, same RAM speed but HyperX Fury with two 16GB sticks.
R
RAGINGKODGRIMM
11-23-2021, 09:03 AM #6

I'm experiencing the same problem right now. For a couple of days. Yesterday I posted about an MSI motherboard that kept giving me the same error. After a lot of troubleshooting, it finally worked. After reseating the CPU and memory, and doing some other checks, it started functioning again. I tried turning it on and off after lunch and it worked immediately. It booted right away and stayed operational for the rest of the day. I turned it off and went to bed, and it's been working again today. The screen goes black, I can't access Windows or open BIOS, and the DRAM error light is on. Any clue what might be causing this? I'm not sure. We have similar systems. My setup includes an MSI Z590, an i5 11600K, same RAM speed but HyperX Fury with two 16GB sticks.

S
SnafuW
Junior Member
41
11-23-2021, 10:07 AM
#7
My concern appears to be fixed. I restarted several times just to confirm and there are no more problems now. For you, though, it might help to swap the dram and then the mobile. I haven’t seen your post yet, so sorry if you already know. My guess is it could be a bios-related issue with the dram.
S
SnafuW
11-23-2021, 10:07 AM #7

My concern appears to be fixed. I restarted several times just to confirm and there are no more problems now. For you, though, it might help to swap the dram and then the mobile. I haven’t seen your post yet, so sorry if you already know. My guess is it could be a bios-related issue with the dram.