Dr. Debug Crazy codes

Kisushi wrote: Yesterday i turn on my computer but no lights showed up, it took a couple of times like 20 for the lights of the mobo to turn on , even the lights of the case was not lighting up even with the cable connected. Sometimes the computer turn on and sometimes it didn't, but in every time he didn't POST. I tested every memory stick in each slot individually, and there were times that it appeared the error 53 and when i reseted it appeared the error 00 but still no image in the monitor, then i reseated the memory in the same slot appeared the same error of the multiple codes of dr. debug. i am thinking this is either a Mobo or PSU altough after the lights turned on the computer always turned on but no sign of it POST.

The Dr Debug display shows the POST procedure codes of each test done during POST. These POST codes are NOT error codes, but just identify different tests done during the whole POST procedure.

If one of the POST tests does fail, that code will be displayed on the Dr Debug display. The only POST code that matters, if POST fails, is the last one that is displayed. All the other POST codes you see are of the tests that passed. They don't matter at all.

If you get a POST code that stays on the Dr Debug display, and the PC does not boot or let you go into the BIOS, then you have a problem. The problem is ONLY related to the last code shown on the Dr Debug display.

If no lights were on, on the board or PC case, I would think the power supply (PSU) is bad, or the board has a problem.

If you are getting a 00 code, that means the CPU is not working. But that could just mean the CPU is not getting power from a bad PSU, or the board's VRMs for the CPU are bad.

This might be the situation of an AMD board with a small 4 + 1 VRM circuit used with an FX-8350. The CPU support list has the usual warning for the 125W TDP AM3+ processors. Additional cooling for the VRM chips/heat sink are needed with 125W TDP processors:

http://www.asrock.com/mb/AMD/970%20Extreme4/?cat=CPU

The CM tower style cooler you are using does not blow any air across the VRM heat sink, and we don't know how good the cooling in your PC case is. I hope this is not the problem, but it might be.

Did you OC your CPU?

If you can try another power supply, do that first. If you still have the same problem, then you know the power supply is not the problem.

Your G.Skill memory is on G.Skills Compatibility List(QVL) for this board.
http://www.gskill.com/en/product/f3-12800cl7d-8gbxm
http://www.gskill.com/en/configurator?manu=52&chip=42&model=562


Well, like anything else, memory does go bad for unknown reason. I'm NOT saying one or both of yours is bad at this point, yet they do go belly up occasionally.

Using abrasive erasures on the memory's electrical fingers should be considered a last ditch effort. Certainly not as a ritual or done regularly. Those electrical "traces' are laid down very thinly. Abrasives only serve to remove minute portions each time they're scrubbed down with one.

Now knowing this do look at/check the fingers of both sticks. Not saying anything in particular, but do look.



And always the promising news for last. That your MB and CPU respond properly when no memory is installed is a good sign. To me, IMO, that says the board and CPU aren't the issue.

Kisushi wrote: Everything is lighting up, and the fans spool as well. When you say spool you metan if the fans rotate? I am not and english user so some words i don't know.

Sorry, Spool = Spin up

OK. It "sounds' like you're using incompatible memory. What is the G.Skill PN of the 2x4GB kit you have?

Another posibility is one stick went belly up. Test each stick when/as installed individually and not as a pair.

But do provide the Kit PN too please.

Everything is lighting up, and the fans spool as well. When you say spool you metan if the fans rotate? I am not and english user so some words i don't know.

i don't know who edited it but it wasn't me.