I'm building a pc and upon startup, all components turn on but then the debug LED on my Extreme4 motherboard shows codes 14, 15, and finally ends on and remains at C5. There is no output to my display which is connected to the GPU. The manual only tells me that code 15 is PEI_CAR_NB_INIT (which I don't really understand), but codes 14 and C5 are entirely unknown. I've played around with my RAM and my storage, and found that with ram uninstalled, I then remain on error code 10. If my storage is uninstalled, I get the same 14, 15, C5 sequence of codes, so I assume that my storage is not being read at all. I plan to return my storage and get one that is compatible as per this sheet. My storage is WDS500G2B0C, which is just 1 serial number away from the one listed there.
However, I also notice that my ram is not explicitly stated on the memory QVL sheet, so I'm not certain that this will not also cause problems after I install the new storage. If anyone has any idea what those 14, 15, and C5 error codes mean, I would greatly appreciate if you could share. My bios is on 1.00, which is what it shipped with. I think there is a later version available, but I can't even get into POST to try and update it. The full mobo manual is available here, and my parts list is here.
CPU 9950x
GPU 5090 Astral
MOBO X870E Nova
RAM Corsair Titanium 6600Mhz 2x48GB
Just built my workstation and couldnโt get it to post.
Tomorrow should try to reseat the sticks. If doesnโt work then try both of the sticks separately in A2.
Before installing CPU pins were fine, even made a post on Reddit since I was worried and it was said that everything is how itโs supposed to be.
Installed CPU carefully.
How deep am I? I didnโt wait for Noctua Edition TX1600 since it wouldโve been 3 months when I wouldโve gotten it and replaced it with ASUS ROG STRIX PLATINUM 1200W.
Need this workstation to be up and running tomorrow, I need to render 3D animations asap.
Hello fellow redditors. I have posted this in r/buildapc as well. I humbly come before you today in hopes that the reddit community might endow me with the grace that is the unfathomable wisdom of the reddit community, should you decide that I am worthy. Google, unfortunately, decided no such thing and so now I sit here before you, thumb fully up ass.
Now that that's out of the way, lets get to the issues... WHAT THE FUCK DOES A "5F" DR. DEBUG CODE MEAN AND HOW DO I FIX IT?! ๐ฐ
So how did we get here, you ask? No worries, I'll fill you in.. probably with more details than you wanted, but my adderall is kicking in so here goes. Back in May, I built my very first PC (hardware components listed below). After sorting out some initial difficulties, she ran beautifully for about a month. I got roped into house sitting for my parents for a week. Naturally I decided to pack up my new rig in styrofoam and take it with me on my 3 hour drive, so that my eyes would not go hungry for their daily dose of UltraWide HD (I mean what else could I do, return to a 16:9 aspect ratio?). Ready to show my baby off, I hunt down a surge protector, connect all the wires, and call the 'rents into the room. As the power is turned on to the PC, the motherboard RGBs light up, as does my AMD CPU cooling fan, all good so far. Busy trying to hide my throbbing penis from my mother, it takes me a second to realize that there is no HDMI output to my monitor. Upon closer inspection, I spot a Dr. Debug code โ 5F โ displayed on the motherboard. Instantly flaccid. My parents, completely unimpressed, remind me that I'm still disappointment (nobody likes change, right?). After a session of extensive Google searching and a popping a few beta blockers for the resulting blood pressure spike, I retreat and pack my tower back up. When I got back home the next week though, there was apparently no problem!! She worked:-)
Well, not quite. I discovered that the problem is intermittent. By this, I mean that it works fine sometimes. At other seemingly-random times though, it returns. Anecdotally, I've found that unplugging all peripherals and the power cable seems to sometimes fix the issue. Probably coincidence. This has been going on awhile now, which has given me the opportunity to observe the start-up cycle through the Dr. Debug codes in both scenarios. One thing that I've noticed is that if the cycle proceeds from 61 to 62, the computer will work. If it stalls at 61, it then goes to 5F and my monitor never lights up. I'm not sure if this is helpful at all. I have sporadically seen other "not working" codes; some I can't remember, but I know that 30 is one of them.
A search for this code shows that the 5F Dr. Debug code is "Reserved for future AMI error codes" โ What does this even mean?! My complete build is listed below the Dr. Debug cycles I typically see.
When the PC works fine, it cycles through a series of codes that ends like:
15โ[...]โ33โ61โ62โ99โ00โ**[enters start up]**
When the PC does NOT work fine, the cycle goes like:
[...]โ33โ63โ61โ๐ญ๐ญ๐ญโ 5F
Motherboard: ASRock X570 Taichi CPU: Ryzen 7 3800X CPU Cooler: came stock with CPU PSU: Corsair RM650 gold SSD: Sabrent Rocket NVMe 4.0 1TB GPU: MSI Gaming GeForce GT 710 2GB RAM: Vengence LPX 32GB (2x16GB)
TL;DR My x570 Taichi motherboard randomly displays a Dr. Debug "5F" code and will not send signal to monitor. There is always a startup cycle through various codes that more or less always goes from 61 to 62 close to the end. If the PC decides to cooperate, it will transition from 61 to 62, then to 98, and then the PC boots and no code is displayed. If it is not going to work, it will transition from 61 to a lingering 5F. This occurred for the first time after transporting my PC, but it suffered no obvious problem-causing blows and has worked about 60%-70% of the time since then.