Maximus XI System issues please help

[animalmom]

Hi, I had to rebuild my system because of a dead CPU

I changed out the Mobo and CPU.

After reassembly I could get to BIOS but now cannot - I was having trouble with the build recognizing the boot Flash drive

Now when I fire it up I get stuck on b6 with white VGA light on

I have reset CMOS, I have switched cables (from Displayport to HDMI), I have reseated the GPUs. Same issue. I have removed the SLI bridge.

It just gets to D6.

https://rog.asus.com/forum/showthread.php?29906-Maximus-V-Gene-Post-Hang-Q-Code-B6-and-(mostly)-72

This thread mentions maybe reflashing bios? Corrupted BIOS?


Any ideas?

Corsair 760t Graphite Case
Intel® Core™ i9-9600KF CPU
Corsair Dominator Platinum 64GB DDR4 @ 3200 MHZ 4x16
ASUS Maximus Xi Hero Wi Fi
Samsung 960 Pro 1TB M.2
EVGA SuperNOVA 1200 P2
Windows 10
2xNvidia Titan X Pascal 12GB

[animalmom]

Ok I just Reflashed the Bios and now I am stuck on Error A2, not D6

I have not installed Windows yet.

The M2 drive is installed with my old windows and data.

I have removed the M2 drive

[1mluer]

I think it's bad or not supported memory error...

I just went through some issues with memory which was absolutely bad. b6 and a few other qcodes popped up. Check the QVL for your motherboard to see if your old memory is supported then check it with 2nd set of memory if you have it. I am pointing to memory..

[animalmom]

Thanks I will try that

The memory was fine prior when I first started - it would post/go to BIOS and I could see the memory in the BIOS

[1mluer]

animalmom wrote:
Thanks I will try that

The memory was fine prior when I first started - it would post/go to BIOS and I could see the memory in the BIOS

Like I was saying it might just be that the old memory will not work in the new motherboard. Just gotta check. I actually had bad memory and got those codes. I put in a 2nd set of QVL qualified memory and it ran perfect.

[animalmom]

I am embarrassed to say the issue was a bad Display Port Cable

[1mluer]

Well at least it's fixed. weird codes for display port cable 🙂