Hi people,
This is an issue that's been going on for quite some months now and I can't seem to narrow the issue down. Everytime I think I've found it, the issue re-appears. I actually posted this issue on here awhile back and no-one gave me any advice, but I thought I'd give it another shot, especially considering I've tried a lot more since then.
My Specs:
PSU: Cooler Master V850
Mobo ASRock 990FX Extreme9
CPU: AMD FX-8320
RAM: 2x4GB AMD Radeon R9 Gamer Series (2400MHz)
GPU: MSI GTX 770 Lightning Edition
Storage: Kingston HyperX 120GB SSD + 32GB Sandisk SSD + WD Blue 1TB HDD + 320GB 2.5inch Hitachi HDD
OS: Windows 7 64-bit
The Issue:
Intermittently during a cold boot my mobo has a fit and throws different POST debug codes. Each time I boot it hangs on a particular error code and will not budge until I turn it off and on again. It’s a case of keep trying to cold boot it until it eventually boots up fine. I once made a note of the POST error codes each time and I got: D7, 62, 0D, 00, 0D, D7 in that order WITHOUT making any changes to the PC each time. On ASRock’s website, here is what they correspond to on this board:
http://www.asrock.co...treme9/?cat=FAQ
I would also like to note when it does decide to boot, I get into the UEFI and sometimes it will hang and just freeze on the same screen. The time also stops counting too. The only way out of it is to turn it off and back on again. I've also had it where no debug code shows, but upon attempting to boot into Windows I get “bootmgr image is corrupt. The system cannot boot” screen.
But again, this is an intermittent issue. Sometimes it will actually boot fine and go straight into Windows with no hassle, usually when turning off and on multiple times it gives up and lets me in. There isn't a pattern to this by the way, it doesn't happen after a certain amount of attempts. Sometimes it will actually just boot up first time, straight into Windows. Once it's in Windows it performs fine and I can browse and play games perfectly fine. No shut downs, no nothing. The issue only occurs when booting.
Diagnostics performed:
¬ Cleared the CMOS several times (Tried both CLR CMOS button and jumper)
¬ Ran Memtest86 for 9 hours and no errors
¬ Purchased new RAM (Was using Avexir Core Series before)
¬ Updated the UEFI to the latest version
¬ Reseated the RAM, GPU and CPU
¬ Tried booting with 1 stick of RAM
¬ Swap tested RAM slots (reseating from DDR3_A1 and DDR3_B1 slots to DDR3_A2 and DDR3_B2 slots) as instructed in the manual
¬ Completely stripped the PC, took the mobo out and rebuilt again (not including the OS)
¬ Attempting to boot with only the OS drive (Kingston SSD) present
¬ Used different wall socket outlets including a Belkin Surge protector
¬ I've even had my motherboard swapped out under warranty
¬ Tried different PSU cables thinking it was a faulty cable (some spares were in the original box unused)
¬ Changed the mobo standoffs thinking mobo wasn't being grounded correctly
¬ Tried using a known working Sempron proccessor
¬ Purchased a cheap working graphics card (one that doesn't need dedicated PSU connections)
¬ Used a different PSU (a Corsair 600watt builder series unit)
Results after diags:
As this is an intermittent issue, it's hard to figure out the cause. For example, I swapped the RAM and my PC would boot first time, everytime, for about 4 days until it decided it wasn't going to do that anymore. No change to my configuration at all, I left everything stock. It also did the same when I tried using a different wall socket outlet. I tried booting about 10 times and it just wouldn't boot, then when I take out the plug and shove it into a different wall socket it boots first time! But that doesn't always fix the issue and I've had it where it will hang on a debugging code the next time I try and boot from that same wall outlet.
I would also like to add, after all the diags, I do notice some of the debugging codes don't appear anymore. They still alternate, but only between 5d, 0d and numbers between 61-91 which on the ASRock Website states it's either memory or a chipset issue. This is on a brand new mobo too. At this point I don't think the issue is component related, but power related. I think there's a short somewhere causing the issue but I can't figure out where it is or how to fix it.
Any ideas people?
Many thanks for the people who do read through this massive wall of text and reply to this thread, your help is greatly appreciated. I'm pulling my hair out at this problem!