Debug codes
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=17246
Printed Date: 18 Jul 2025 at 10:13pm Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Debug codes
Posted By: xxEzxx
Subject: Debug codes
Date Posted: 14 Nov 2020 at 6:43am
I recently bought a Asrock Taichi z490..
Upo boot im getting codes ...
00
7f
4c
I need to know what i should do in order to get the board up and running.
With these codes should my fans be running at all?
Thanks in advance.
Dave
|
Replies:
Posted By: Xaltar
Date Posted: 14 Nov 2020 at 7:53am
It's supposed to cycle through codes before boot  Each code represents a part of the POST process (Power On Self Test). If the system freezes and does not complete POST then the test that failed will be indicated on the Debug LED display. In other words, there is only a problem if a code remains on the display and the system is frozen. There are even codes that indicate you are in the BIOS, Ab and sometimes A2.
Your board is functioning exactly as it should if these codes are clearing before your OS starts to load.
-------------
|
Posted By: xxEzxx
Date Posted: 14 Nov 2020 at 1:08pm
so as long as the numbers keep cycling then everything is fine.. how long does this process last? it keeps going from code to code to code those three over and over again.
|
Posted By: Xaltar
Date Posted: 14 Nov 2020 at 6:30pm
Ah, what is the last code before it loops? It is triggering a restart because it can't initialize something, most likely your RAM. Make sure you have your RAM installed in slots A2 and B2 and that they are fully seated into the slots. On new boards the slots can be tight and appear like they are all the way in but are not.
If the codes cycle through, clear then the system boots into the OS all is well. If you freeze or the system POST loops (resets after cycling through some codes) then there is an issue and the last code flashed will give you an idea of what the issue is if you look it up.
-------------
|
Posted By: xxEzxx
Date Posted: 14 Nov 2020 at 10:23pm
Ok thank you...
I have moved the ram into the slots that you said to move them to.
I defiantly had that part wrong I had them in the first and third slots.
I moved the to the 2nd and 4th spot which are the indicated slots in the manual for a2 b2
When I did that this is what happens now.
00
4c
00
7f
44
still no fans..
Im building this for my father and hes all kinds of wigged out about the fans not coming on yelling at me like the damn fans should be coming on right. I haven't built one in over 6 years so is there a answer i can give him about the fins not coming on?
|
Posted By: xxEzxx
Date Posted: 15 Nov 2020 at 12:09am
I took the cpu out and took a picture I can't really tell if these are bent pins I took a magnifying glass to it and still can't tell..
CPU https://imgur.com/gallery/VgVDcxm
|
Posted By: xxEzxx
Date Posted: 15 Nov 2020 at 1:05am
I took a video as well..
https://youtu.be/uwIqUP6Wm3E
|
Posted By: Xaltar
Date Posted: 15 Nov 2020 at 1:39am
Looking at the pic (very blurry) there seem to be 2 areas that look off:

It could be bent pins or possibly something spilled in the socket? The image isn't clear enough to see. Code 44 is a memory related code but considering the memory controller is located on the CPU, it could well be bent pins giving you a problem.
-------------
|
Posted By: Xaltar
Date Posted: 15 Nov 2020 at 1:41am
As for the fans not coming on, if they are connected to the board it could be related to the other issue, bent pins can short and trigger the board's protection circuitry.
-------------
|
Posted By: xxEzxx
Date Posted: 15 Nov 2020 at 2:31am
i looked at it under a magnifying glass they dont seem to be bent at all but there is definitely two spots that look strange on the board
|
Posted By: xxEzxx
Date Posted: 15 Nov 2020 at 2:57am
https://youtu.be/jmmD2KliuSg
https://youtu.be/-EGloPBj_tg
|
Posted By: Xaltar
Date Posted: 15 Nov 2020 at 3:02am
Open a support ticket with ASRock Tech Support and make sure you link the image and video: https://event.asrock.com/tsd.asp
If it were not for those marks I would suggest taking the board out of the case and setting it up on top of it's box with just the CPU, RAM and possibly GPU (if you are using a CPU with an "F" designation). If your CPU does not end with an "F" then you don't need the GPU, just use the board's display output. You can go ahead and try this anyway, it will rule out potential shorts against the case. Without a clear image of that socket I can't tell if it's just a harmless molding defect, something spilled or a damaged socket. ASRock's Tech Support department will be able to advise you, likely to return the board to the retailer you purchased it from.
To be clear, there are steps we could take to troubleshoot here but after seeing that pic I would contact support and ask them to clarify. Let us know what they recommend.
-------------
|
Posted By: Xaltar
Date Posted: 15 Nov 2020 at 3:07am
The GPU fans are supposed to spin down when the card is under a certain thermal target, after seeing the video (which you posted while I was posting the above), I can see now what you were concerned about. It's normal for many modern GPUs.
So, am I understanding correctly that you get different codes when you use a single stick of RAM then the other one in the same slot?
When you have the A2 code, is there a signal to your monitor? A2 is at the very end of the POST process and typically the system is showing a display when this code flashes.
If you are getting a display output (something on the screen, likely the ASRock logo) then by the looks of it you may have a bad stick of RAM.
-------------
|
Posted By: xxEzxx
Date Posted: 15 Nov 2020 at 3:26am
I'll uh plug the monitor back in and give it a shot alpha a2 meant that the ram is in the wrong slot
|
Posted By: Xaltar
Date Posted: 15 Nov 2020 at 3:42am
Great, let me know what happens. It may have been RAM all along and those areas in the socket may simply be discolored. Tough doing this via a forum but we will get there.
-------------
|
Posted By: xxEzxx
Date Posted: 15 Nov 2020 at 3:44am
So no display... I tried clearing CMOS and trying each stick again one stick produces 44 and the other stick produces A2.
|
Posted By: Xaltar
Date Posted: 15 Nov 2020 at 3:47am
What happens when you try without any RAM in, you should get a different code.
-------------
|
Posted By: xxEzxx
Date Posted: 15 Nov 2020 at 4:00am
Ram https://imgur.com/gallery/XIOl6Cj
This is my ram going to unplugg ram now one sec
|
Posted By: xxEzxx
Date Posted: 15 Nov 2020 at 4:03am
Posted By: Xaltar
Date Posted: 15 Nov 2020 at 4:05am
That kit is on your board's supported list, I am guessing Z490 Taichi by the pics, which means it should work with your system fine so if it is not working then either the RAM is DOA or there is an issue with that socket as I mentioned earlier. The thing that is throwing me is that it should pop the same code regardless of which stick is installed if it's this socket that is the issue. It's a bit of a head scratcher.
Have you tried a single stick (the one that gives the A2 code) in each slot and see if any slots give you a display?
-------------
|
Posted By: xxEzxx
Date Posted: 15 Nov 2020 at 4:17am
Let's have a little fun while trouble shooting..
The a2 stick in a2 slot put into b2 slot now produces a code of 98.
Oh boy
Were having fun now
|
Posted By: Xaltar
Date Posted: 15 Nov 2020 at 4:25am
98 has to do with PCIe devices. I am pretty sure now there is something up with the board, there is an off chance the RAM may also have issues or have issues caused by the board.
I would return the board to the outlet you purchased it for an RMA. The code changing with that one (A2 code) stick of RAM depending on the socket means the CPU is not communicating with the board as it should.
Damn, I was hoping we could sort you out without an RMA, that it was something simple we overlooked.
When you send back the board, take a note of it's serial number and make sure they don't send you back the same board (unless they somehow fixed it). If the store gives you trouble then contact ASRock directly and show them that pic, or, preferably a clearer one of the socket. I know they don't usually let things like that through their QC so I suspect the store either sold you a return or they did something like update the BIOS before sale and the tech borked it.
Sorry we couldn't crack it.
-------------
|
Posted By: xxEzxx
Date Posted: 15 Nov 2020 at 4:31am
I hate to say this but this is my second bad experience with asrock.. the whole damn manual is worthless as it has no table of contents. I bought it from new egg although I'm guessing I should start a rma with asrock sh*t man was hoping to figure it out
|
Posted By: Xaltar
Date Posted: 15 Nov 2020 at 4:39am
Yeah, nothing worse than getting a dud. Sadly, most of the time the issues come from the retailer, rough handling in shipping or returns put back up for sale. Personally I have never had a bad experience with ASRock (hence accepting the offer to be a moderator here) but I have had bad experiences with just about every other brand at one point or another. I remember having to swallow the cost of over two dozen motherboards from Gigabyte when they all failed within a year because of that batch of bad caps in the early 2000's. Never had a good experience with MSI, just bad luck I am sure. It's all down to luck in the end.
Good luck with the RMA and let me know how you get on 
-------------
|
Posted By: xxEzxx
Date Posted: 24 Nov 2020 at 10:35am
Hello back again.. got my new board.....
Don't have the video card in but it's throwing
4c
7f
Agaun...
|
Posted By: Xaltar
Date Posted: 24 Nov 2020 at 5:14pm
Ouch, sorry to hear that. I would RMA that CPU ASAP. Given all your troubleshooting that would be the next potential guilty culprit. If the board isn't the issue then the only other thing that could cause that array of errors is the CPU itself.
There was a time when the CPU was almost never even suspected, not unless it had bent pins or physical damage of some kind. These days however it's all too common 
-------------
|
Posted By: xxEzxx
Date Posted: 24 Nov 2020 at 10:04pm
Posted By: Xaltar
Date Posted: 24 Nov 2020 at 10:47pm
From ASRock's FAQ:
Dr. Debug is used to provide codes that represent different errors that your system has encountered. Please see the diagram below for reading the Dr. Debug codes and how to troubleshoot. Code Description 00 Please check if the CPU is installed correctly and then clear CMOS. 0d Problem related to memory, VGA card or other devices. Please clear CMOS, re-install the memory and VGA card, and remove other USB, PCI devices. 01 - 54 (except 0d), 5A- 60 Problem related to memory. Please re-install the CPU and memory then clear CMOS. If the problem still exists, please install only one memory module or try using other memory modules. 55 The Memory could not be detected. Please re-install the memory and CPU. If the problem still exists, please install only one memory module or try using other memory modules. 61 - 91 Chipset initialization error. Please press reset or clear CMOS. 92 - 99 Problem related to PCI-E devices. Please re-install PCI-E devices or try installing them in other slots. If the problem still exists, please remove all PCI-E devices or try using another VGA card. A0 - A7 Problem related to IDE or SATA devices. Please re-install IDE and SATA devices. If the problem still exists, please clear CMOS and try removing all SATA devices. b0 Problem related to memory. Please re-install the CPU and memory. If the problem still exists, please install only one memory module or try using other memory modules. * For X79 models, please try installing memory to DDR3 A1, B1, C1 and D1 slots. b4 Problem related to USB devices. Please try removing all USB devices. b7 Problem related to memory. Please re-install the CPU and memory then clear CMOS. If the problem still exists, please install only one memory module or try using other memory modules. d6 The VGA could not be recognized. Please clear CMOS and try re-installing the VGA card. If the problem still exists, please try installing the VGA card in other slots or use other VGA cards. d7 The Keyboard and mouse could not be recognized. Please try re-installing the keyboard and mouse. d8 Invalid Password. FF Please check if the CPU is installed correctly and then clear CMOS.
So 4c = Memory error (suggests reinstalling CPU and RAM) 7f = Chipset initialization error (suggests clearing CMOS)
If you have checked your CPU is correctly installed and you have no bent pins then the issue us very likely a dead CPU. We have already ruled out the board with a replacement yet are getting the same codes. That leaves the CPU or bad RAM, given the odds of getting not one but 2 bad sticks of RAM in the same batch I would lean heavily toward CPU. It is also the most expensive component so an RMA will provide peace of mind here more so than anywhere else. I would not want to miss the warranty window.
-------------
|
Posted By: xxEzxx
Date Posted: 24 Nov 2020 at 10:54pm
I refuse to give up let me try to clear the cmos and try once more. Man what a experience. I currently have one stick in b2.
|
Posted By: xxEzxx
Date Posted: 24 Nov 2020 at 11:20pm
Ok so cleared the cmos crossed fingers.. 2020 dont think anyone is lucky lol..
so one stick the one that worked previously.. in a2
4c 7f... starting to admit defeat..
in b2
4c 7f
was like you know what why the f not try the other stick...
all kinds of codes.. so im like ok this stick is fubared...
no stick
code 53.
|
Posted By: Xaltar
Date Posted: 24 Nov 2020 at 11:40pm
xxEzxx wrote:
2020 dont think anyone is lucky lol.. |
I know the feeling all too well 
I didn't just jump to the suggestion of an RMA on the CPU, given the troubleshooting we have already run through it is the next logical step. I would RMA that RAM along with it just to be sure it isn't bad too. At this point I am about 90% sure it's the CPU. One can never be 100%
This wouldn't be the first time pages and pages of troubleshooting ended up being because of a dud intel CPU. Their memory controllers seem particularly prone to being DOA for some reason. When they work out the gate there is no problem (they don't tend to die).
-------------
|
Posted By: xxEzxx
Date Posted: 25 Nov 2020 at 12:31am
This may be good news but i think i installed the wrong stick of ram now i was trying to show dad what was going on and im stuck on a a2 only code evidently i was too quick to jump to conclusions on the ram before the post cycled
|
Posted By: xxEzxx
Date Posted: 25 Nov 2020 at 2:08am
So I'm getting this...https://youtu.be/Dl25gDG_hC8
|
Posted By: Xaltar
Date Posted: 25 Nov 2020 at 3:10am
A0 - A7 Problem related to IDE or SATA devices. Please re-install IDE and SATA devices. If the problem still exists, please clear CMOS and try removing all SATA devices.
But given we already tried a bare bones test (nothing but RAM, CPU and power) I am thinking the CPU is likely bad. If you have any SATA cables connected to the board you can try removing them, even just a cable with nothing on the other end can cause issues.
I am still leaning toward the CPU however.
-------------
|
Posted By: xxEzxx
Date Posted: 25 Nov 2020 at 4:54am
Yup unplugging the drives and cables produces a a2 code
so a2 is my final code.
you think that the cpu caused the first marks on the pins of the first board.. Im kinda scared to take this cpu back off now for that reason.. I dont wanna look.
|
Posted By: Xaltar
Date Posted: 25 Nov 2020 at 5:59am
No, the CPU couldn't do that. It just has contact pads, you have nothing to worry about.
-------------
|
Posted By: xxEzxx
Date Posted: 01 Dec 2020 at 2:00am
Ok im back
New CPU installed no sata devices installed and im getting A2 still. I havent tried clearing the cmos yet let me do that real fast
|
Posted By: xxEzxx
Date Posted: 01 Dec 2020 at 3:25am
http://www.youtube.com/shorts/Gx5wbF_PAeY
|
Posted By: Xaltar
Date Posted: 01 Dec 2020 at 4:51pm
Did you RMA the RAM too as I suggested? If you have any other RAM to test with then that is our last step outside of double and triple checking the connections.
-------------
|
Posted By: xxEzxx
Date Posted: 01 Dec 2020 at 9:14pm
I RMAed the one stick that was throwing multiple codes and kept the other stick I did take the ram out completely and it was throwing a 53 code I believe can't recall as it was yesterday but it was the code for ram... Stuck it back in b2 and code a2 popped up again. So at least it's being consistent.
|
Posted By: xxEzxx
Date Posted: 04 Dec 2020 at 8:14am
I was looking at my ram just for the heck of it at this point... Still waiting on my rma...anyway I took a video to pass the time I suppose.
http://www.youtube.com/shorts/OfeTC4pM9Tc
|
Posted By: xxEzxx
Date Posted: 07 Dec 2020 at 1:48am
Where on my motherboard do I plug this cable
Pwm cable https://imgur.com/gallery/9bLiy8i
|
|