ASRock z77 extreme4, does not post

scratchmonkey

Reputable
Jun 11, 2015
4
0
4,510
Specs:

Motherboard: ASRock Z77 Extreme4 LGA 1155 Intel Z77 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard
CPU: Intel Core i5-3470 Ivy Bridge Quad-Core 3.2GHz (3.6GHz Turbo Boost) LGA 1155 77W BX80637i53470 Desktop Processor Intel HD Graphics 2500
RAM: Crucial Ballistix Sport 8GB 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model BLS8G3D1609DS1S00
PSU: Rosewill CAPSTONE-450-M – 450-Watt Modular Active PFC Power Supply – Continuous @ 122 Deg. F (50C), 80 PLUS Gold, ATX12V v2.31 & EPS12V v2.92, Intel Haswell, SLI, & CrossFire Ready

BIOS is 2.90, which is the most recent according to the ASRock website.

Symptoms:
Powers on, light and fans start, no display, Dr. Debug readout on mobo rapidly cycles through codes before sticking on 4F -- it will then restart the sequence every 10 seconds or so. Beep code sounds like three short beeps, slight pause, three more short beeps, then repeats whenever it goes through the sequence. I've tried removing the RAM and then I get three long beeps and a RAM error code on the Dr. Debug, which seems 'correct' to me and which leads me to believe that the code I'm getting is a keyboard controller error, which could mean any number of things (and yes, I've tried booting with two different keyboards (DAS mechanical via USB and a vintage Model M) and without a keyboard at all.

History:
Had rig since last November, has been working fine. Two days ago, I saw the Patch Tuesday Windows Update was ready (Windows 7 64-bit) and shut down the computer to install it. The next day, the computer failed to post -- I've gradually removed all peripherals from it, including video card and am currently just running off on-board video and the PSU attached to the board (and the CPU of course) -- I've also swapped out the PSU, trying a Corsair TX650M, with the same results. I've also tried resetting the CMOS, both using the onboard button and by manually removing the battery. All of those get me the same results on boot.

I'm thinking at this point that it has to be the motherboard or some sort of short between the board and the case -- my next step is to remove the board from the case and see if it still has issues and if it does, to try and get ASRock to send me a replacement BIOS chip. Then if that doesn't work, replacing the dang thing. I've done a search of similar issues, including on here and none of the various solutions have worked

I'm posting here just in case there's something obvious (or non-obvious) that I've missed and/or if anybody has any good suggestions for next steps.

Thanks!
 
Solution

I removed it from the mobo and reinstalled it and got the same 4F. The reason i'm not as concerned about the CPU is they rarely are bad and I only use the dr.debug code that it says on. All other codes are just the process of starting up the mobo, not errors (from my research).

I switched the PSU out and have everything outside of the case on anti-static bags. I've submitted a request to ASROCK.
I have the same problem with the same hardware. Last week on June 10, i got the 4F error. the following day, after keeping the computer unplugged all day, it finally booted up. However, yesterday i had to restart and now i have the same 4F error problem.
I've narrowed it down to either the Mobo or PSU. Tomorrow, i'll test the PSU.

Please update if you have a solution!
 
Tried some more troubleshooting (going slow as I've got two kids and there was a big family wedding this weekend) and a different memory stick doesn't help and after recording the Dr. Debug on boot and scrubbing through it, I get the following sequence:

8 10 15 98/38/88? (hard to tell as it flips so fast) 56 48 49 55 36 92? 4F -- it sticks on 4F until it presumably retries and then the sequence re-starts.

Given the 56 code, I would suspect something wrong with the CPU; however, the build was working completely fine the day before and the machine didn't get jostled or wet or anything strange, possibly a power spike?

Still waiting for a BIOS chip, my next step is to take the board completely out of the case and then try booting it, then try removing and reseating the CPU and see if that does anything.
 


How did you eliminate the CPU as a possible failure point? At this point it seems like the mobo or the CPU for me; I'm not entirely sure how to say that it's one for sure without having a second one of either to swap in.
 

I removed it from the mobo and reinstalled it and got the same 4F. The reason i'm not as concerned about the CPU is they rarely are bad and I only use the dr.debug code that it says on. All other codes are just the process of starting up the mobo, not errors (from my research).

I switched the PSU out and have everything outside of the case on anti-static bags. I've submitted a request to ASROCK.
 
Solution