[SOLVED] No post, DRAM error light

[ajdemoulpied]

So been looking through forums and videos trying to figure this issue out, but I am thinking it's the MOBO at this point.

Specs:
MOBO- Gigabyte X570 Aorus Master 1.2 rev
CPU- Ryzen 7 3800X
GPU- Gigabyte 2080 Super
RAM- G. Skill Trident Z 8GBx2 3800MHz
PS- EVGA Supernova 850W 80+ Gold
All storage are Samsung M.2's

Computer has been running fine, no issues ever, built literally a year ago to the month. Came into my office this morning and all my fan LED's where white (normally blue and pink). Monitor was blank, keyboard and mouse LED's where off. Computer wouldn't respond to any inputs. Shut it down, started it back up and wouldn't boot. No splash screen, no BIOS, no nothing.... Boot code gets to 15, which is "Pre-memory North-bridge initialization is started" in the manual. Then goes to EE. Does this a few times, then stays on EE. EE is "reserved" in the manual, whatever that means. Additionally, the DRAM error light is on and solid. It will flash back and forth to the CPU light, but is predominantly the DRAM light.

So popped everything out, except the CPU and cooler, which is an AIO, popped it all back in, no change. Did one RAM stick at a time in slot 2, no change. Put them both in slot 1 and 3 instead of 2 and 4, no change. Booted without GPU, no change. Downloaded the latest BIOS update, Q Flashed the MOBO, no change. Went to Best Buy and bought brand new RAM sticks, no change. Ugh, I'm stuck and frustrated. As soon as I was really getting into Humankind 🙁

If there is anything that someone can think of to try, I would greatly appreciate it. I am at the point of sending the MOBO to Gigabyte since it has the 3 year warranty, but would love to avoid the downtime of shipping and troubleshooting, if it is something I can fix here. That and with the current situation Gigabyte is facing, who knows if or when I will get this thing back from them. But like I said, pretty sure it's a RAM chip on the MOBO at this point.

Thanks everyone!!!

 

[drea.drechsler]

..... But like I said, pretty sure it's a RAM chip on the MOBO at this point.

Thanks everyone!!!

Aside from the DIMM's the only RAM chip on the MOBO I can think of is the CPU since that's where the memory controller is located in Ryzen. Luckily, you can send that back to AMD if still in warranty period.

Have you tried to reset CMOS to see if running in full-defaults did anything?

Did you run overclocked at any point? If so, what settings and how long?

Too late now but doing the Q-Flash was probably a bad idea as all that does is introduce a potential new problem: a bad flash.

 

[ajdemoulpied]

Aside from the DIMM's the only RAM chip on the MOBO I can think of is the CPU since that's where the memory controller is located in Ryzen. Luckily, you can send that back to AMD if still in warranty period.

Have you tried to reset CMOS to see if running in full-defaults did anything?

Did you run overclocked at any point? If so, what settings and how long?

Too late now but doing the Q-Flash was probably a bad idea as all that does is introduce a potential new problem: a bad flash.

Tried CMOS, nothing different. That's what lead me to update the main BIOS. Left the backup one alone just incase I got a bad flash. It was overclocked, but conservatively and let the MOBO do it based on XMP settings and made sure it was within specs of the RAM. Nothing too crazy. Let the AMD software handle the CPU, again made sure it was nothing that would push it to far. It had been like that since I built it though and never showed any signs it didn't like it.

Luckily everything is still under warranty. But again with the cluster F at Gigabyte right now, not interested in going down that path with them. Haven't hit up AMD yet since nothing with the error codes and light indicates a CPU problem, but I guess it could be...

 

[drea.drechsler]

... Haven't hit up AMD yet since nothing with the error codes and light indicates a CPU problem, but I guess it could be...

Actually...the error codes, and the lack of response with new DIMM's, suggests to me it's the CPU. The memory controller and "north-bridge" are internal to the CPU now. All I know of that the motherboard does for memory is provide the DIMM and CPU sockets and the trace path interconnects between them.

Oh yes...and the VRM for the various voltages needed to power the DIMM's and CPU. I suppose one of those could be at fault but I'm not really certain what indications you'd get from the motherboard. One would hope there'd be a fault code for that. Getting hold of GB's tech support would be helpful for that, I suppose. If you can.

 

[ajdemoulpied]

Actually...the error codes, and the lack of response with new DIMM's, suggests to me it's the CPU. The memory controller and "north-bridge" are internal to the CPU now. All I know of that the motherboard does for memory is provide the DIMM and CPU sockets and the trace path interconnects between them.

Oh yes...and the VRM for the various voltages needed to power the DIMM's and CPU. I suppose one of those could be at fault but I'm not really certain what indications you'd get from the motherboard. One would hope there'd be a fault code for that. Getting hold of GB's tech support would be helpful for that, I suppose. If you can.

Yea I have been trying to hit them up. Can't get through on the phone and have a 5 day turn around through email...

I did pull the trigger on another MOBO. Will be here Thursday. Worst case that's not it and I have a couple ways to recoup that cost. Could return it to Best Buy I guess lol. Wish I had a Micro Center around here. I just know an RMA for any of the parts is gonna take a few weeks at least and just want to get it figured out. If it is the MOBO, I'll follow up with Gigabyte once they get everything handled there. In the meantime though, I'll hit up AMD and see what they think.