Dr Debug "64" on one CPU, auto shutdown on another.

[PeregrineX]

Oops! Sorry for double posting!

Hello,

So yesterday, while I was at work, my dad was on my computer and MBAM or something said that there was a virus and it needed to restart. When it booted back up to the BIOS splash, however, it would just sit there and be stuck. I can't go into the BIOS, or do anything of that sort. It does end up going past that, but only after a LONG time.

I checked on the mobo for the Dr Debug code, since I have an AsRock 970 Extreme4: it was stuck on "64" which results in a CPU DXE initialization failure. The CPU at the time was an AMD FX 6300.

So, it's my CPU then, I thought, but I wanted to make sure. So I put in my Phenom II X6 (yes, it is supported by my AM3+ mobo), only to result in an automatic shutdown after a second of booting. The only thing with that CPU is it had one pin a little bent, but I fixed it with a tiny phillips head screwdriver (the flat one, I forget), but I could be wrong.

So is it my CPU, or my mobo? I can't decide which. Can any of you help me?

Thanks in advance!

 

[junkeymonkey]

tough call on that can a bios reset/reflash help?? was it corrupted in some way ?

bout all I know is google up that CPU DXE initialization failure. and see whats said on that

 

[PeregrineX]

How would I flash without entering the bios/getting past the splash? I'm just curious.

EDIT: I have also tried resetting it numerous times. No luck.

 

[junkeymonkey]

ok I see I was going to get back on this to see if it for sure 64 and not b4

but if you cant get into the bios that don't help I would unhook everything but the bare min. for the board to start -- no hard drive no nothing but chip what ever for video onboard card and keyboard like you did for burn in to see of a hardware is not hanging it in some way and see what happens

 

[PeregrineX]

OHHH now that you mention it, it might read "b6," which means failure on Cleanup of NVRAM. I read somewhere that I should try with one RAM stick, I'll see what happens...

 

[junkeymonkey]

ok I got to go be back in about 16 hrs,

 

[PeregrineX]

Ok, I tested with one stick and got the same result. Then I tried with the other and got 3 long beeps with no display. It is still stuck on either 64 or b4, I cant tell...

Any help would be appreciated, since junkeymonkey is gone for today!

 

[junkeymonkey]

http://www.asrock.com/support/faq.asp?id=286

you may have memory that went bad in some way??? you may want to re look up the asrock beep codes for your board to see if its the same

be sure you test the sticks one at a time in all slots and as I said un hook the hard drive its not needed to test to enter the bios

the other bad part would be not having parts to try like a extra set of memory to see if different sticks of another brand or kit would work
seeing how one stick still just failed and the other stick totally failed you may be on the right path [??]