Had been having problems with my rig getting stuck in a boot loop a while back, which I thought was either mobo/cpu (see here) and picked up a Z97 and 4790k to replace them. Have never had the 4790k above 1.30Vcore and 1.15Vring.
Now having the same/similar(ish) problem which is: boots, few codes flash on the debug LED and hits C2, C3 (sits here pretty long), C4 (sits here longer) then powers down and repeats. Needed to load optimized defaults a few times to get in, setting default clocks/voltages crashed on windows loading before that. NOW when booting in, my cpu is set at 800mhz and doesn't move from there even when Intel XTU/P95 ect are run (and when clocks/voltages are set manually).
Only parts same from previous build:
Case
RAM - have had the issue with each stick of ram running individually in different slots
PSU - Seasonic 750 Gold
Just did this once and afterward I let windows do it's recovery thing, after that was stuck at 800mhz. This looks like it might have been my fault (flipped the TAG switch instead of bios), fixed now. Still having the loop on boot often, especially from cold boot.
If i had a bad PSU, I should expect a crash during stress testing shouldn't I? Have had cpu/gpu both pulling as much as I can manage and have absolutely no issues once I make it into windows. Getting there is the issue...
If i had a bad PSU, I should expect a crash during stress testing shouldn't I? Have had cpu/gpu both pulling as much as I can manage and have absolutely no issues once I make it into windows. Getting there is the issue...
No. Had almost the same issue about a year ago with my Corsair PSU. PC would just turn off or reboot when idleing (but never when gaming/stressing). After that it would usually get into a reboot loop.
Took me almost 2 months to figure out it was actually the PSU.
Not saying it´s the same issue for you, but I would really try out another PSU if you have one lying around.
Other than that it could be you RAM if you reused your old modules.
I've had this similar issue with an old Gigabyte Z68 board. The only fix I found that worked was not to OC. Once I OC'd boot loop half the time during cold boots.
No. Had almost the same issue about a year ago with my Corsair PSU. PC would just turn off or reboot when idleing (but never when gaming/stressing). After that it would usually get into a reboot loop.
Took me almost 2 months to figure out it was actually the PSU.
Not saying it´s the same issue for you, but I would really try out another PSU if you have one lying around.
Other than that it could be you RAM if you reused your old modules.
Sounds promising, have my PSU like perfectly wedged against a 240 rad at the bottom of the case... hope they still make the same one so i can just swap out then. It would be pretty unlikely to be the modular cables from the PSU causing the problem vs the PSU itself right?
Quote:
Originally Posted by xP_0nex
I've had this similar issue with an old Gigabyte Z68 board. The only fix I found that worked was not to OC. Once I OC'd boot loop half the time during cold boots.
Most likely, it is the PSU itself. Sadly, they are by far the most likely components to fail.
You may want to RMA it.
Do you have any tools that can test the voltage of the PSU lines? A multimeter in particular would be useful to see if the 12V lines are stable. There's also the tools available to see what voltages each line is getting. Actually, you might be able to access the BIOS. Boot in and see what the voltages are. If they are really low or really high, then it's time to take the power supply out. Especially if they are really low (it could mean that the power supply is facing catastrophic failure if the current rises to try to compensate for the lack of voltage).
It seems unlikely that 2 motherboards in a row would be defective. If possible, clear the CMOS and get the latest BIOS flashed in. Check the forums to see if other owners have had motherboard stability issues. You should probably also re-seat the CPU and see if there's any bent pins. Most likely though, it's a bad PSU as I said.
If you think it's the RAM, get MemTest 86+ and test it out. This does not seem like a RAM issue though.
So work has been REALLY busy, but issue its still ongoing (and intermittent). Replaced the PSU with a new 750w (also seasonic) and still had problems. Then went no OC and had a few weeks of less issues on boot (but still would see it occasionally). Could be same frequency, just not using the pc as often.
Also now after the C3/4/5 loop if I hit restart the board will go straight to debug code "8" (or B?) and hang, power off and back on to hang at the same code or get stuck in the C's again. Only way I've found to clear it is power the PSU off and back on, and them sometimes it takes a few times + reset CMOS. So that's new.
Still annoying as hell that once i'm into windows, OC'd or not, it's perfectly stable. Didn't see the last two posts, so will try swapping sata cables out to see if that helps; where did you find that the C3/4/5 are related to mobo/boot device communication? If nothing then, guess I should be taking it apart and looking for bent pins?
So work has been REALLY busy, but issue its still ongoing (and intermittent). Replaced the PSU with a new 750w (also seasonic) and still had problems. Then went no OC and had a few weeks of less issues on boot (but still would see it occasionally). Could be same frequency, just not using the pc as often.
Also now after the C3/4/5 loop if I hit restart the board will go straight to debug code "8" (or B?) and hang, power off and back on to hang at the same code or get stuck in the C's again. Only way I've found to clear it is power the PSU off and back on, and them sometimes it takes a few times + reset CMOS. So that's new.
Still annoying as hell that once i'm into windows, OC'd or not, it's perfectly stable. Didn't see the last two posts, so will try swapping sata cables out to see if that helps; where did you find that the C3/4/5 are related to mobo/boot device communication? If nothing then, guess I should be taking it apart and looking for bent pins?
Debug codes are universal from one board to another, at least they are the same from the boards that I have used/using. So I check that up on the manual or you can google it.
You can check for bent pins if you want, but before you do that, you can try to do another clear CMOS but with the motherboard battery removed. For some reason, resetting CMOS with and without the battery are two different things xD
This is more of a guess but you may also want to try playing around C-states in the BIOS if by any chance you can boot to BIOS, but I doubt it will fix it.
As electro2u said, you can try reseating the RAM if you haven't done it already.
thanks. Has a bare bench build been attempted yet? Bench build: only bare essentials, eliminate case and accessories as possible failure points... put mobo on cardboard box, install cpu + cooler, 1 stick of ram, PSU, and boot drive only. Short power pin with a key or screwdriver to power on machine if no onboard power button is available.
I would completely switch out the RAM to eliminate it as a variable. I know you said you tried one stick at a time but it seems to be the only component that went along from old board to new that has not been isolated
New set of ram picked up today and played with it a bit. Make it through the C3/4/5 quickly now but was getting stuck on 95 (pcie). Reseated the 980 and haven't been able to get stuck in a boot loop yet with it on one bios, the other (primary) bios gets stuck initializing with any cconfig now...will test a few more days but looking like possibly bad gpu seat and ram issues.
So, definitely was the ram. Threw my old rig back together sitting on my desk and put the old ram in, would stop at code 15 and die (as before). Same with the Z97 setup. Soon as I put in the corsair kit (picked the cheapest from gigabyte's compatible ram list) had no issues with booting either pc after many turn-on/turn-off cycles. Cold boot, boot from reset CMOS all fine.
Only issue now is the Z97 still has a bad BIOS that I can't get past but the other is fine; can a bad set of ram corrupt a BIOS? Is it possible to flash BIOS 1 while in BIOS 2?
Nice, thanks for that link. Will give it a go shortly!
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Related Threads
?
?
?
?
?
Ask a question
Ask a question
Overclock.net
27.8M posts
541.2K members
Since 2004
A forum community dedicated to overclocking enthusiasts and testing the limits of computing. Come join the discussion about computing, builds, collections, displays, models, styles, scales, specifications, reviews, accessories, classifieds, and more!