The other day I noticed my orbx sceneries running a lot slower. And now that I think about it, I also experienced the "boot loop" that has plauged P67 mobo users. Still didn't think much of it.Before the boot loop I've been running auto vcore (runs 1.356v) and 44x multi. Temps avg about 67-68 with a hard test of IBT. Nothing to worry about imho.But today my fps were really low and I checked CPUZ and it said 3300 mhz. I went into BIOS and it gave me the red box saying previous OC settings failed reverting to default etc. Sure enough all my stock stuff was active.Anyway, I guess my question is: Is the boot loop the PSU telling the mobo to reset settings to stock because of an issue or just random and my settings went back to stock?I've been running the auto vcore / 44x multi for about 6months without any boot loops. I did have boot loops initially however.Should I be concerned? I set it back to 44x and auto for now. And before you ask, setting anything other than auto causes instability. Also, FWIW I disabled C1E halt state for the last 4 months... then about 1 month ago decided to enable it again. I think having it enabled (and allowing the CPU to throttle back to 1600mhz) is causing part of the instability.

Edited January 4, 201214 yr by ryanbatcund

Yes, Ryan. You should re-test your overclock. I have the same issue every time I try to run an overclock on my P67-UD3-B3 that is even the slightest bit unstable. I know of some users that complain about the 'cold-boot' issue that plagues the Gigabyte mobos, and I am not sure if a solution has been found as of yet. But, just 3 or 4 days ago, my computer boot-looped on startup after a few weeks of relatively trouble free operation. Only thing I changed was bumping up the multiplier/vcore and doing a quick 2hour prime run. Once I got it back in order, I re-ran the prime test, and it failed within 2.5 hours. Upped vcore a bit, failed again, this time with a blue screen (prior failure was a rounding error). So, dropped speed to 4.7ghz, set vcore a bit lower than I had it for 4.8, ran prime for 12+ hours with no problems. Now, not only is my sim MUCH smoother, but I have had no boot-loops or issues to speak of. Also, the halt-state thingy is not what I have set in my bios...it is c3/c6 or something that downclocks it when there is no load present...I leave c1e disabled...of course, other more qualified people on this forum could probably shed more light on it for you than me....I am still learning lol

C1E can, in a few cases, cause instability for some when overclocking and going over certain CPU voltages. I've personally mostly seen these issues with Asus boards. The Asus Z68 board I had ran fine with it enabled, so does this Asrock at 4.5 and 1.33v. 1.356V seems a bit much for 44x multiplier, not to mention your load temps (I've forgotten which cooler you use Ryan).

I guess 67 doesn't seem too high under Intel Burn Test... that's one of the hardest CPU test out there. Corsair H60 is my cooler. My case needs to be cleaned but it's a pita to get at behind me desk so I'll wait until spring. Still I'm not sure what to think. The thing was stable for 6 months. I've also been playing BF3 very frequently. I wonder if the system just had enough. Yeah it varies between 1.344 and 1.356v at 44x multi.C1E is the one that changes the CPU back to 1600mhz for 2500k's... the c3/c6 is something different. I might just keep it disabled, which makes my CPU run hotter, but more stable imho.Also, let it be known that I'm the guy with the 2500K that could never get above 4 GHz until I ran vcore at auto. In the future I'll invest more in a better board - this one didn't have LLC (single level) until I updated the BIOS.

Edited January 5, 201214 yr by ryanbatcund

I guess 67 doesn't seem too high under Intel Burn Test... that's one of the hardest CPU test out there. Corsair H60 is my cooler. My case needs to be cleaned but it's a pita to get at behind me desk so I'll wait until spring. Still I'm not sure what to think. The thing was stable for 6 months. I've also been playing BF3 very frequently. I wonder if the system just had enough. Yeah it varies between 1.344 and 1.356v at 44x multi.Also, let it be known that I'm the guy with the 2500K that could never get above 4 GHz until I ran vcore at auto. In the future I'll invest more in a better board - this one didn't have LLC (single level) until I updated the BIOS.

Yes, I remember! I just needed a refresher! Perhaps change of season/temperature has affected core temps? It sounds backwards, but I know some folks create a sweat house when it's winter.I'm at a loss. If the only thing you've changed recently is C1E, that'd have to be a contributor, no? What is your LLC set to, btw?

It's set to on LOL! It's either on or off. You make a good point about the temp thing. I usually keep the office really warm during winter months. That combined with my case needed some dusting and the C1E thing... I'll keep an eye on it.

It's set to on LOL! It's either on or off. You make a good point about the temp thing. I usually keep the office really warm during winter months. That combined with my case needed some dusting and the C1E thing... I'll keep an eye on it.

Oh, I see! You said that but I missed it.I'll clean it for a fee+travel

Yes come on up to Duluth... this weekend the high was about 8F. Thankfully the temps rose again to around 35 today. KCLT KDLH should be easy enough :) Cleaning it isn't so hard, only that it's behind my L desk, and in order to move the PC (which is sorta trapped behind prison bars), I've got to move the desk, which means I have to take all my stuff off, because the cords are too short, which means a lot of work.