F5F Stay Refreshed Hardware Desktop Following the PC downgrade, the DRAM error light appears and there is no post. Fans and lights are not turning on.

Following the PC downgrade, the DRAM error light appears and there is no post. Fans and lights are not turning on.

Following the PC downgrade, the DRAM error light appears and there is no post. Fans and lights are not turning on.

Pages (2): 1 2 Next
T
TesGo
Member
85
12-20-2018, 06:02 AM
#1
Just installed a brand new PC and want to repurpose my old one as a secondary unit. Original specs included an Asus Z-390 i Mini-ITX with an i7-8700K, EVGA RTX 2070, and Corsair Vengeance RAM at 3200MHz. Storage was a 500GB SATA SSD housed in an InWin A1 case. I haven’t confirmed the BIOS version yet. I’ve used Win10 64-bit for about six months before making this switch. Previously, a G Skill Trident Z 4400 at 32GB was installed, but I moved it to the new build, replacing the old SSD with a Corsair SFX 750W and keeping the new RAM.

Before swapping RAM, I reset the BIOS to defaults because I was overclocking with faster memory. After downgrading, the PC wouldn’t boot and I tried one stick in each slot, clearing CMOS. I reinstalled the old RAM too, but it still wouldn’t boot. When I reinstalled Corsair 3200 in the new system, it worked perfectly. On startup, the DRAM light appeared and fans started up normally, though I noticed it was taking longer to reach full speed.

It seems the issue might be with the RAM itself, but I’m not sure what caused it. I don’t think I broke anything and wasn’t removing the board from its case. Since I’m comfortable building PCs, I’m looking for next steps and possible fixes. I haven’t had any post problems before, but this one behaves oddly—fans don’t jump to 100% right away, and I see a DRAM error light without a proper boot.

I tried installing an older RAM from a previous system, but it didn’t work well and failed on my bench. Could this have permanently affected the board?
T
TesGo
12-20-2018, 06:02 AM #1

Just installed a brand new PC and want to repurpose my old one as a secondary unit. Original specs included an Asus Z-390 i Mini-ITX with an i7-8700K, EVGA RTX 2070, and Corsair Vengeance RAM at 3200MHz. Storage was a 500GB SATA SSD housed in an InWin A1 case. I haven’t confirmed the BIOS version yet. I’ve used Win10 64-bit for about six months before making this switch. Previously, a G Skill Trident Z 4400 at 32GB was installed, but I moved it to the new build, replacing the old SSD with a Corsair SFX 750W and keeping the new RAM.

Before swapping RAM, I reset the BIOS to defaults because I was overclocking with faster memory. After downgrading, the PC wouldn’t boot and I tried one stick in each slot, clearing CMOS. I reinstalled the old RAM too, but it still wouldn’t boot. When I reinstalled Corsair 3200 in the new system, it worked perfectly. On startup, the DRAM light appeared and fans started up normally, though I noticed it was taking longer to reach full speed.

It seems the issue might be with the RAM itself, but I’m not sure what caused it. I don’t think I broke anything and wasn’t removing the board from its case. Since I’m comfortable building PCs, I’m looking for next steps and possible fixes. I haven’t had any post problems before, but this one behaves oddly—fans don’t jump to 100% right away, and I see a DRAM error light without a proper boot.

I tried installing an older RAM from a previous system, but it didn’t work well and failed on my bench. Could this have permanently affected the board?

S
SkaxDK
Junior Member
47
12-20-2018, 06:41 AM
#2
Dram light indicates either a dram issue was detected or the process halted during that post test for another reason. For me, this suggests the memory might need inspection for faults. It could be that no faults exist, but it’s a bit thorough. Memtest86 is presently the benchmark for this task.
S
SkaxDK
12-20-2018, 06:41 AM #2

Dram light indicates either a dram issue was detected or the process halted during that post test for another reason. For me, this suggests the memory might need inspection for faults. It could be that no faults exist, but it’s a bit thorough. Memtest86 is presently the benchmark for this task.

A
AllStarLoser
Junior Member
16
12-24-2018, 02:27 AM
#3
I ran a memory test on my other computer, and everything is working properly. Beyond that, MemTest86 can help verify your RAM stability, detect any corruption, and ensure your system runs smoothly.
A
AllStarLoser
12-24-2018, 02:27 AM #3

I ran a memory test on my other computer, and everything is working properly. Beyond that, MemTest86 can help verify your RAM stability, detect any corruption, and ensure your system runs smoothly.

L
LoopyTehNeko
Member
55
12-25-2018, 10:04 PM
#4
Memory issues often occur when specific memory areas are affected, which can happen frequently. However, if the problem persists even after booting, it suggests another underlying issue. It might point to a motherboard fault rather than a memory problem. Running the DRAM test on the motherboard BIOS could reveal if it's a simple lockup or something more serious. A 4400mhz memory setup means the CPU exceeds its threshold, causing the Infinity Fabric to shift from 1:1 to 1:2. This could disrupt system stability.
L
LoopyTehNeko
12-25-2018, 10:04 PM #4

Memory issues often occur when specific memory areas are affected, which can happen frequently. However, if the problem persists even after booting, it suggests another underlying issue. It might point to a motherboard fault rather than a memory problem. Running the DRAM test on the motherboard BIOS could reveal if it's a simple lockup or something more serious. A 4400mhz memory setup means the CPU exceeds its threshold, causing the Infinity Fabric to shift from 1:1 to 1:2. This could disrupt system stability.

I
i0cean
Member
218
01-10-2019, 01:29 AM
#5
No, I did not perform any resets. Please confirm the steps you took regarding the CMOS and BIOS.
I
i0cean
01-10-2019, 01:29 AM #5

No, I did not perform any resets. Please confirm the steps you took regarding the CMOS and BIOS.

O
Oversuun
Junior Member
7
01-13-2019, 05:30 PM
#6
I reinitialized the CMOS, BIOS was current as of six months prior when I stopped using the PC. The system functioned perfectly then; I only removed the SSD and RAM, and recently decided to attempt a second use. Encountered these problems with the new RAM and SSD.
O
Oversuun
01-13-2019, 05:30 PM #6

I reinitialized the CMOS, BIOS was current as of six months prior when I stopped using the PC. The system functioned perfectly then; I only removed the SSD and RAM, and recently decided to attempt a second use. Encountered these problems with the new RAM and SSD.

B
Bonnibel
Posting Freak
794
01-20-2019, 08:05 AM
#7
I can access the BIOS settings. Could you confirm the current version running?
B
Bonnibel
01-20-2019, 08:05 AM #7

I can access the BIOS settings. Could you confirm the current version running?

C
Carsland123
Senior Member
398
02-06-2019, 04:27 AM
#8
Ok this may be stupid questions but if the PC doesn't boot at all, will I be able to use Memtest86? I'm not familiar with the process. If this is the case, why does the computer not boot with the 4400 ram that was previously installed with no issues?
C
Carsland123
02-06-2019, 04:27 AM #8

Ok this may be stupid questions but if the PC doesn't boot at all, will I be able to use Memtest86? I'm not familiar with the process. If this is the case, why does the computer not boot with the 4400 ram that was previously installed with no issues?

8
8thEmmett
Junior Member
20
02-06-2019, 11:52 AM
#9
I don’t even manage to open BIOS, it powers on but the fans spin up without being fully functional. I can’t get into BIOS with either stick, tried both slots. I also attempted to install the old RAM I removed earlier, but still can’t access BIOS.
8
8thEmmett
02-06-2019, 11:52 AM #9

I don’t even manage to open BIOS, it powers on but the fans spin up without being fully functional. I can’t get into BIOS with either stick, tried both slots. I also attempted to install the old RAM I removed earlier, but still can’t access BIOS.

P
Persiphany
Member
159
02-06-2019, 01:42 PM
#10
Connect the monitor to the motherboard, then reset the CMOS and attempt to power up again.
P
Persiphany
02-06-2019, 01:42 PM #10

Connect the monitor to the motherboard, then reset the CMOS and attempt to power up again.

Pages (2): 1 2 Next