Is my motherboard dead?

vikingtons , 6 hours ago

for whatever it’s worth, my powercolor red devil 5700 died in a similar way to this several years ago. Got to a point where it failed to output any display signal at all.

Powercolor had an insane return rate for their NV10 GPUs, at least in Europe.

Are you getting WHEA logs here? Do they implicate a specific component?

TheBat OP , 2 hours ago

for whatever it’s worth, my powercolor red devil 5700 died in a similar way to this several years ago. Got to a point where it failed to output any display signal at all.

That’s what I thought too but as I’ve mentioned, keyboard and mouse are not getting any power from motherboard.

If it was GPU issue, those would have active lights with only monitor not getting any signal from GPU.

Are you getting WHEA logs here? Do they implicate a specific component?

When the system still used to turn on properly, I’d get these in Windows’ event viewer:

Reported by component: Processor Core

Error Source: Machine Check Exception

Error Type: Cache Hierarchy Error

Processor APIC ID: This kept changing

Provider Name: Microsoft-Windows-WHEA-Logger

Event ID: 18

When I started looking up information about this error I found out it could be caused by literally anything. Faulty CPU, board, memory, PSU. Sometimes setting CPU voltage around 1.30-1.35 helped. In one case the guy replaced his custom power cables with default ones and that solved the issue.

Brkdncr , 2 hours ago

Remove the video card, use inboard video, and use a single stick of ram. If it’s still wonky try a different power supply.

TheBat OP , 1 hour ago

There’s no onboard video for this setup.

TheBat OP , 6 hours ago

You can’t see in the pic but the white glitch columns aren’t continuous. Those are white lines interspersed with what’s on display.

comador , 1 hour ago

I agree with Brkdncr, this sounds like a video card issue.

I’ve had this problem multiple times before. The combination of display glitches and the fans spinning but no numlock or keyboard functionality simply points to the video card first.

In short, during POST of the BIOS it attempts an init to the display, fails and then stops attempting the boot sequence. It, the video card, is just as important during init as the motherboard registers, RAM and CPU all starting.

So, start with video, see if it works without the 5700XT and using the onboard or some other cheap pcie card. If that fails too, then it’s most likely the mobo as assumed. This just doesn’t sound like a mobo issue though.

TheBat OP , 1 hour ago

There’s no onboard video for this setup* but I’ll try to boot without GPU.

*Only Ryzen CPU with G suffix have integrated graphics. Plus, my CPU is Zen 2 which didn’t have integrated graphics at all.

In short, during POST of the BIOS it attempts an init to the display, fails and then stops attempting the boot sequence. It, the video card, is just as important during init as the motherboard registers, RAM and CPU all starting.

I wasn’t aware of this. I assumed display check would be last considering there can be systems without display.

Let me check if I get NUM LOCK and CAPS LOCK LEDs after removing GPU.

comador , 38 minutes ago

While I call it init, many will assume I am referring to the boot init, but I am actually referring to the bios initialization (init).

That said, most BIOS inits go in this order:

• Power Detection check. If enough power, proceed.
• CPU program link, CPU calls the BIOS to basically wake up and run the bios program.
• Ram Detection check. If RAM is present, the BIOS will use about 64k to load from ROM to RAM (called the bios reserve area) that then does the next steps.
• Hardware Detection check. Identifiers of the hardware are detected, enumerated, configured and initialized.
• Boot Sequence is initialized whereby the BIOS does a handoff to the bootloader.

It’s during the hardware detection phase when the display is initialized by the gpu and you often see it displaying the bios version, then counting RAM. If the gpu is working BUT the display out isn’t, it’ll actually continue to boot 100% of the time (it doesn’t care). If the gpu hardware itself doesn’t respond correctly to the BIOS request however, it sends the hardware detection of the BIOS into a loop or shuts the system down, never getting to the final step: boot sequence.

Depending on the bios type, it may or may not show numlock. I’ve also seen it act differently on UEFI enabled systems than when it’s set to classic bios. So, it just depends.

Regardless, see if you can source another pcie gpu for testing this. It only takes a minute and tbh, it doesn’t hurt to have a cheap used pcie vid card in your pc tools for such things.

Good luck!