Asus Crosshair Hero VIII Wi-Fi encountering error after startup 02 Error code appears post-initialization
Asus Crosshair Hero VIII Wi-Fi encountering error after startup 02 Error code appears post-initialization
Hey everyone, I just changed the cooling setup for my ASUS RTX 2080ti DUAL OC from Kraken G12 + AIO to a custom loop. Everything seems fine—no leaks, no issues. Once I power on the PC, the BIOS splash appears but then the screen goes black and I see a 02 error code on the MB. I’ve heard online that the monitor or cable might be the problem. I’m using the same monitor and cable as before. I tested HDMI and DisplayPort without any changes. What sets my case apart is that I see the BIOS splash but everything else fails. If I try to enter BIOS, it turns black again. Using another older GPU (gt710) works perfectly. Any tips would be appreciated!
My setup:
- CPU: AMD 5950X
- MB: Asus Crosshair Hero VIII Wi-Fi
- RAM: 32GB G.Skill RipJaws V
- GPU: Asus RTX 2080ti DualOC
- PSU: Corsair HX1200
It can happen due to various problems. Sometimes I see 02 after a failed infinity fabric OC or DRAM issue, but also after cleaning the graphics card. After relocating it to another PCIe slot, refreshing CMOS and reinserting it worked fine again. EDIT: One more note. If you encounter a black screen in BIOS and receive 02 code, try restarting the PC and pressing F1 on the black display when prompted; if that fails, press F1 again to access BIOS.
I've attempted to reset the CMOS using the button and by changing the battery. Now I'm trying to switch it to a different PCIe lane. The issue is that previously, with the same GPU and settings, it worked fine. If it wouldn't boot at all, I'd also understand... but it now shows the splash screen and then goes dark.
Review your changes carefully. The setup steps follow a failed BIOS boot, and after pressing F1 the display remains blank despite functionality.
You've completed all troubleshooting steps. The issue persists with a 3E error and no boot. Consider checking the power supply, ground connections, and ensure all components are securely installed. If problems continue, verify BIOS settings or consult manufacturer support.
3E sets up the memory. Test each memory stick in each slot individually, rather than just reinserting them. If this doesn’t resolve the issue, consider using a BIOS flashback via a USB stick to another version—it works without needing the CPU.
After two hours I finally got it to start again. Surprisingly, the issue was CPU-related. Once I cleaned all parts and put the PC back together, it worked once more. Now I’m still facing the same problem with the 02. I recorded a video showing the behavior on the MB. From the moment the green light activated until the end, I noticed the BIOS splash screen appeared. I was able to enter the BIOS, but after about ten seconds it would close again... Video link: https://streamable.com/7vgkde
I’m not sure about everything, but pressing F1 can alter the Qcode even when stuck on a different code. Here’s how I usually move from a failed IF OC with 02 code:
1) After PC reboots and applying 1900MHz+ IF in BIOS, turn off the PC and reset CMOS using button 3.
2) Restart and get stuck again at 02 code with blank screens.
3) Press F1 – the code updates (though I’m not sure which one).
4) Code changes but still shows blank screens; system remains in BIOS even without visibility.
5) Use ESC and Enter to exit BIOS.
6) Wait, it boots into Windows.
Your problem might differ, especially with the 3E memory error. It could point to CPU issues or a corrupted BIOS affecting initialization. You may want to try the suggested BIOS update or a new beta version, which seems stable for high memory OC. If this is unusual, entering BIOS and encountering damage afterward is something I haven’t faced before.
The problem stemmed from insufficient thermal paste between the waterblock and GPU, triggering protection mode each time. Removing the waterblock and adding more paste resolved it. For VRAM, there was extra space and more paste required, which also fixed the issue. Now the GPU won't start in Windows or Linux, showing a "Windows stopped the device" error. I need to debug this but at least I can boot normally now.