GA-P67A-UD7-B3 - Boot Loop won't POST

[Argyll]

Yes, I am afraid I have to agree.  I am contacting the Newegg as I type this to get an RMA.

Thanks again for all of your time and persistent help, it was greatly appreciated!

[Dark Mantis]

No problem buddy. Please let us know how things progress though.

[Argyll]

Well... trying to keep a good attitude about all this, but man it is certainly hard.

OK, I received a brand new GA-P67A-UD7-B3 yesterday in the mail.  Installed in case, hooked everything up and first power-on goes 2 seconds on-->re-cycle, 2 seconds on->re-cycle.  No post code and no screen as it doesn't get that far.  Re-checked connections.  Tested components in another computer  one by one and they all let that computer boot up, so I see how it is the other components.  The first board booted to FF with all of these same components on first boot.  But subsequently got stuck in the power-loop no post thereafter.

Now last time I tried random stuff I found by googling around the internet regarding this board and boot-up loop problems.  Perhaps something I followed last time got me into the state I ended up in and had to RMA the board.  Therefore, before I start trying stuff again, please advise.

Remember this is right out of the box, first power on.  Whatever you suggest next will be my second power on.

Any and all help and suggestions greatly appreciated!

[Dark Mantis]

Hello again

Right well I think the best thng is to start by removing it from the case and laying it out on the motherboard box. Connect just the CPU/heatsink/fan, PSU (24 pin and 8 pin), one stick of RAM in the first slot and the buzzer. When done try and boot and see what happens.

[Argyll]

No joy... same cycle... 2 seconds-->cycle no post code.

[Dark Mantis]

OK then. Next clear the CMOS as it might still have factory settings in it.

Remove the power cable from the mains supply and then press the power switch on the case for a few seconds just to drain any residual energy in the PSU capacitors.

Once done remove the motherboard battery for at least one hour before replacing it.
 
Next plug back into the mains supply and boot.
 
You will now need to enter the BIOS by pressing DEL and load Opimised BIOS Defaults.

Make any other changes to the BIOS settings to suit your self like disabling the floppy drive, disabling the full screen logo and making the HDD the primary boot device and then press F10 to save and exit.

[Odiebo]

My 2 cents, replace the CPU. If its in the 30 day return, do it now. If its outside of that start with Intel's Live tech chat. Have your components info with you, specifically board & memory model numbers.

I had this very same problem with a GA-P67A-UD3 board and after a replacement board seemed to make the problem worse I opted for the buy back from NewEgg until the B3 boards were out.

My problem was: reboot during any OS install, reboot during any flash attempt (dos flash), reboot before POST completion and finally reboot cycling before bios could be loaded, before video could be enabled.

 I ended up going with an Asus P67 Evo once the B3 boards were hitting the shelves, partly due to another build using an Asus board, and partly due to fear I was going to have another issue with the Gigabyte (their tech support wasn't supportive). Assembled everything on top of a box and I have the same damned problem.

Only the Evo board has helpful LED's that indicate where the board is having an issue, CPU, Memory, PSU.  And the Memory LED was steady on. So now I've swapped out memory, again, to a verified QVL module and no change. At this point in the game I"ve replaced everything except CPU. Got online with Intel's Live Chat, suspecting the CPU is bad but really hoping that they'll tell me its a hardware mismatch. In less than 5 minutes I have a ticket number to get a replacement CPU.  Next day on the phone to complete that ticket and the following week I have a working system.

The ease in which the tech at Intel concluded the CPU was bad was surprising. He basically asked me 3 or 4 questions about hardware, setup, ect and issued the replacement ticket number, which leads me to think there's an internal bulletin concerning this problem.

It will mimic a memory fault and I suppose it is a memory fault, but not with the DDR memory but the cpu's pathways to that memory.

Date of original order: Jan 17
Date of working, stable system April 14
Number of components used:  3 motherboard, 3 power supplies, 3 memory module sets (all 1.5v), 3 video cards
                                                 

[Dark Mantis]

I wouldn't be surprised Odiebo  as that was the way I was heading if the last effort didn't work.

[Argyll]

This is killing me...

OK, I contacted NewEgg and RMA'd the CPU.  Still confused how it booted once in the original board if it was bad, but I will just take it on faith that this must be the problem as the new board has not booted a single time and all of the other components have been tested separately and the motherboard wouldn't boot even with just one stick of ram in the cardboard holder.

It will take about 7-8 days total turnaround until a new CPU arrives here.  I will let you know what happens after that.

 

[Dark Mantis]

Thanks we will look forward to hearing if we were right in our diagnosis. It is quite possible the processor was alright to start with and then just went. Sometimes the inital startup will be ok and then if it is not quite up to scratch it can just give up.

[Argyll]

Thanks we will look forward to hearing if we were right in our diagnosis. It is quite possible the processor was alright to start with and then just went. Sometimes the inital startup will be ok and then if it is not quite up to scratch it can just give up.

To be really honest, I had my doubts.  But I did get the replacement CPU from NewEgg and for a few heart stopping minutes the machine continued to cycle without posting.  Then magically after about the fifth cycle it posted!

I was able to then lay down Windows 7 on the RAID 0 drives, load device drivers from the website and get a stable and consistent boot.  I have subsequently flashed the BIOS to F4.  Made changes to the BIOS to turn the RAID 0 back on (ironically the RAID Bios remembered, but the main BIOS didn't).

For those who may find this message, if after flashing the BIOS the machine won't boot to the OS, use the Win 7 DVD or as in my case, thumb-drive to boot, select repair from the menu and select boot repair.  It appears that the flash mungs up the boot block on the HD or RAID, but after doing the 1 second repair machine booted right up.

I still find the BIOS on this board and it's posting process a bit 'twitchy' but it IS working and so I am greatly relieved.

Thanks to everyone how continued to help even after all of the twists and turns this adventure took.  I greatly appreciate your time, thoughts and efforts!

[Dark Mantis]

No problem and thanks for returning to let us know how things eventually turned out.