i7-3770k stable at 4.6Ghz.@ 1.22v. Passes IBT at max stress level without a hiccup or CPU throttling.

 

Once I test with Prime95, it will throttle down to 3.5Ghz during the test. I don't think it's temperature related because the temps are around 60-70C (Core Temp) during the test. I get a higher temp reading during IBT (70-80C).

 

Any adjustment to Vcore either way results in either BSOD or crash in both IBT and Prime95 or just very unstable.

 

I have a feeling I have a bad CPU or about to go bad.

 

Any ideas?

 

Thanks in advance.

Is it core temp reporting 3.5GHz? When this happens, how long does it stay at that speed?

You did turn off speedstep, right?

Is it core temp reporting 3.5GHz? When this happens, how long does it stay at that speed?

 

These are Core Temp readings. It stays there for about 10 sec or so or two then ramp up to 4.6 then go back to 3.5 again.

 

You did turn off speedstep, right?

 

Yes.

Have you disabled *all* power-saving features, including the various "C states" in the BIOS?

i7-3770k stable at 4.6Ghz.@ 1.22v. Passes IBT at max stress level without a hiccup or CPU throttling.

 

Once I test with Prime95, it will throttle down to 3.5Ghz during the test. I don't think it's temperature related because the temps are around 60-70C (Core Temp) during the test. I get a higher temp reading during IBT (70-80C).

 

Any adjustment to Vcore either way results in either BSOD or crash in both IBT and Prime95 or just very unstable.

 

 

I have a feeling I have a bad CPU or about to go bad.

 

Any ideas?

 

Thanks in advance.

 

You should use CPU-Z for CPU frequency, and Core Temp only for temperatures and VID readings. Core Temp will not show real GHz.

 

One more thing, i don't know how is i7-3770k(i have i7-2700k), but i think 1.22v vcore is to low for 4.6GHz. What BSOD you get? 124?

Oops, missed the part about the BSOD. You need to see the links in my signature.

Have you disabled *all* power-saving features, including the various "C states" in the BIOS?

 

Everything disabled except CPU thermal throttling.

 

You should use CPU-Z for CPU frequency, and Core Temp only for temperatures and VID readings. Core Temp will not show real GHz.

 

One more thing, i don't know how is i7-3770k(i have i7-2700k), but i think 1.22v vcore is to low for 4.6GHz. What BSOD you get? 124? Yes

 

I will redo the test using CPU-z. I would also reset the BIOS to start from scratch to see if that helps.

 

Again thank you guys for your input.

Everything disabled except CPU thermal throttling.

 

 

 

I will redo the test using CPU-z. I would also reset the BIOS to start from scratch to see if that helps.

 

Again thank you guys for your input.

 

Maybe you don't need to do anything, maybe your CPU is stable. Try one more time using the CPU-Z, your CPU was not throttling, that is just core temp issue.

After that, try to do some long flight(2-3h) and see what happens. Becouse you can pass both - IBT and Prime95, and than get BSOD when CPU is on low or medium load(when on idle or using FSX).

If you don't get any BSOD, everything is fine.

If you get BSOD, just add some vcore, BSOD 124 means that voltage is not ok.

 

Cheers

 

Becouse you can pass both - IBT and Prime95, and than get BSOD when CPU is on low or medium load(when on idle or using FSX).

 

 

Cheers

 

 

Just to clarify, FSX doesn't crash or BSOD. It's only when I do the Prime95 test that drives me nuts. :wacko: When I try to adjust Vcore for the throttling, I get the BSOD or crash during Prime95.

Let's start over. Ignore CPU clock as reported by core temp. Only CPU-Z will report the CPU clock accurately and in real time. Test again and see if the throttling occurs according to CPU-Z. As for any BSOD you are getting, you can solve this problem with a bit of troubleshooting but you need to take my advice and click on the top two links in my signature to figure this out.

Let's start over. Ignore CPU clock as reported by core temp. Only CPU-Z will report the CPU clock accurately and in real time. Test again and see if the throttling occurs according to CPU-Z. As for any BSOD you are getting, you can solve this problem with a bit of troubleshooting but you need to take my advice and click on the top two links in my signature to figure this out.

 

That's right. I'll do the same thing here.

TechguyMaxC, i have a question for you, i was thinking about different oc approach:

using saved OC profiles Instead power saving features EIST and C1E. I mean, i want to use default stock seetings for 24/7 use, and when i want to use FSX - restart PC and load saved stable overclock profile for example 5GHz, with stable GHz and VCore and all power saving features disabled for better stability. After 2-3h or FSX, when i finish the flight - restart PC, an revert to stock settings from BIOS to preserve CPU life.

 

Is anything wrong with this? Maybe is better than run EIST and C1 with all that GHz and voltages fluctuations?

 

Just an idea. What do you think?

What you propose is an excellent idea, I've thought of doing so myself! Theoretically though, there really shouldn't be any detriment to running the power saving features while overclocking and is in fact what I do.

I have differnt saved profiles mostly with differnt settings for the mems and one base

With decent clock and ,low vcore and 1.65v mem .

 

Hasse

Ok, thank you TechguyMaxC and Hasse. That confirms my assumptions. I have one more question for you:

 

I have noctua nh-d14, and I read on some overclockers forums that i should not go above 1.45 vcore on air. Does it have any sense or it's just some too careful overclokers thought?

I have saved profile with very stable 4.9GHz with 1.4 vcore. But now i did 5GHz with 1.48vcore and i just saw that thought about too much vcore on air. So, i am interested in your opinion, what do you think?