Why you do dis Prime 95

[pjsmith727]

Ok, so I get my brand new 6600k and I'm even a good little boy with it, and I break it in for a full 2 days. I finally can't wait, so I hop into the bios, and go for the coveted 1.35v 4.8 GHz overclock blessing. Won't get past the log in without crashing. No big deal, I was able to finish a Cinebench at 4.7 GHz, same voltage. So I began to stress test with p95 and noticed things were being funny. The CPU would open the program at 4.7, start it at 4.5 and hop all over the place, with a locked core multiplier, until finally hopping it's way all the way down to stock. How the fuck am I supposed to test my OC if the program forces it back down to stock! Any suggestions? Also, if anyone has any recommendations for free stress testing programs, that would be amazing. Just so you know, Cinebench r15 finished with the CPU locked at 4.7 for the whole thing, which is why I'm confused as fuck??

 

**Not retarded, just forgot to mention; temps haven't made it over 70 Celsius. They usually sit around 65 under full load. Gotta love the 212 Evo

Edited August 23, 2016 by pjsmith727

[79wjd]

What are the temps? It sounds like it's throttling. 

[pjsmith727]

1 minute ago, djdwosk97 said:

What are the temps? It sounds like it's throttling. 

Knew I forgot something, max temps have never been over even 70 Celsius 

[DrM]

are you making sure to use small ffts only, because p95 after 26.2 causes voltage and temp spikes on 4th+ gen chips and that might be related to the issue

[pjsmith727]

1 minute ago, DrM said:

are you making sure to use small ffts only, because p95 after 26.2 causes voltage and temp spikes on 4th+ gen chips and that might be related to the issue

Actually, tried switching to that about 30 minutes ago, and in about 10 minutes, I was down to a measly 3.5 GHz

[Imakuni]

10 minutes ago, pjsmith727 said:

**Not retarded, just forgot to mention; temps haven't made it over 70 Celsius. They usually sit around 65 under full load. Gotta love the 212 Evo

I call BS on that. Unless you live in the Alasca, you should not be getting these temps. I have basically the same setup as you, but mine gets roughly to 85 with 1.296v and 4263mhz, which is a way lower OC than you.

 

Anyhow, fire the test along with HWMonitor and take a screenshot. Make sure it shows all mobo and CPU info, you can minimize the rest. Let us see what's happening inside that PC of yours.

[Clanscorpia]

1 minute ago, Imakuni said:

I call BS on that. Unless you live in the Alasca, you should not be getting these temps. I have basically the same setup as you, but mine gets roughly to 85 with 1.296v and 4263mhz, which is a way lower OC than you.

 

Anyhow, fire the test along with HWMonitor and take a screenshot. Make sure it shows all mobo and CPU info, you can minimize the rest. Let us see what's happening inside that PC of yours.

I get 47 with a stock heat sink on a 6500

[GirlFromYonder]

4 minutes ago, Imakuni said:

I call BS on that. Unless you live in the Alasca, you should not be getting these temps. I have basically the same setup as you, but mine gets roughly to 85 with 1.296v and 4263mhz, which is a way lower OC than you.

 

Anyhow, fire the test along with HWMonitor and take a screenshot. Make sure it shows all mobo and CPU info, you can minimize the rest. Let us see what's happening inside that PC of yours.

ur cpu is not that great

[Imakuni]

5 minutes ago, Clanscorpia said:

I get 47 with a stock heat sink on a 6500

And why exactly is that relevant? I know the reason why this completely irrelevant (considering the context of the topic), but I'll let you tell me why and prove that you know that you are saying.

2 minutes ago, DeezNoNos said:

ur cpu is not that great

Yes, I know. Mine doesn't OC all that well, I know that. But I wasn't calling BS on OP's settings, I was calling BS on the temperatures he claims.

[GirlFromYonder]

Just now, Imakuni said:

And why exactly is that relevant? I know the reason why this completely irrelevant (considering the context of the topic), but I'll let you tell me why and prove that you know that you are saying.

Yes, I know. Mine doesn't OC all that well, I know that. But I wasn't calling BS on OP's settings, I was calling BS on the temperatures he claims.

Yes it does not oc that well because it gets too hot with barely any voltage. Or you did not mount ur cooler proper or ur TIM is shit

[Clanscorpia]

2 minutes ago, Imakuni said:

And why exactly is that relevant? I know the reason why this completely irrelevant (considering the context of the topic), but you can tell me why and prove that you know that you are doing.

Yes, I know. Mine doesn't OC all that well, I know that. But I wasn't calling BS on OP's settings, I was calling BS on the temperatures he claims.

Because compared to mine they are normal

[pjsmith727]

2 minutes ago, Imakuni said:

And why exactly is that relevant? I know the reason why this completely irrelevant (considering the context of the topic), but I'll let you tell me why and prove that you know that you are saying.

Yes, I know. Mine doesn't OC all that well, I know that. But I wasn't calling BS on OP's settings, I was calling BS on the temperatures he claims.

If I can't keep my OC for more than 30 seconds in a stress test, then 65 is what I get, those are very reasonable temperatures for a processor that ends up running at stock, without even the help of turbo boost. Which is the whole fucking problem, which I'm starting to think you never even read....

[GirlFromYonder]

Just now, pjsmith727 said:

If I can't keep my OC for more than 30 seconds in a stress test, then 65 is what I get, those are very reasonable temperatures for a processor that ends up running at stock, without even the help of turbo boost. Which is the whole fucking problem, which I'm starting to think you never even read....

try 3.8 with no over voltage. Try to reduce your oc to 4 or something. U might have lost the lottery

[pjsmith727]

12 minutes ago, Imakuni said:

I call BS on that. Unless you live in the Alasca, you should not be getting these temps. I have basically the same setup as you, but mine gets roughly to 85 with 1.296v and 4263mhz, which is a way lower OC than you.

 

Anyhow, fire the test along with HWMonitor and take a screenshot. Make sure it shows all mobo and CPU info, you can minimize the rest. Let us see what's happening inside that PC of yours.

I'll get the screen shots tomorrow, literally lying in bed rn, contemplating how tf I'm going to fix this when I get up.... *sigh*

[GirlFromYonder]

Just now, pjsmith727 said:

I'll get the screen shots tomorrow, literally lying in bed rn, contemplating how tf I'm going to fix this when I get up.... *sigh*

play with OCs with no voltage. 

 

 

ad there could be someother reason to this, but this is what i would have done.

[pjsmith727]

Just now, DeezNoNos said:

try 3.8 with no over voltage. Try to reduce your oc to 4 or something. U might have lost the lottery

It makes it through a full Cinebench tho! I ran through Cinebench 3 or four times at 4.7, everything was good, stayed locked at 4702 MHz to be exact, for the whole test. It's just p95 being a fucking asshole, and not using the power it is given. Which is why I'm confused. 4725 MHz, and Cinebench will crash. 4702 MHz and I get a score of 766 or something like that, which I think is reasonable

[GirlFromYonder]

1 minute ago, pjsmith727 said:

It makes it through a full Cinebench tho! I ran through Cinebench 3 or four times at 4.7, everything was good, stayed locked at 4702 MHz to be exact, for the whole test. It's just p95 being a fucking asshole, and not using the power it is given. Which is why I'm confused. 4725 MHz, and Cinebench will crash. 4702 MHz and I get a score of 766 or something like that, which I think is reasonable

try a lower oc. 4.5 or 4.6

[Imakuni]

1 minute ago, pjsmith727 said:

If I can't keep my OC for more than 30 seconds in a stress test, then 65 is what I get, those are very reasonable temperatures for a processor that ends up running at stock, without even the help of turbo boost. Which is the whole fucking problem, which I'm starting to think you never even read....

Believe it or not, I did read your post. And that's why I'm asking you to provide some screenshots, so I can have a better grasp at what's going on. You'd be surprised at how many people I've got which had a similar problem as you, with the "reason" being that the OC was unstable and P95 stopped the test, for example. Or there was some massive vdroop. Or they were using the wrong test. And others.

 

That's why I wanna check things myself, so I can be sure that your description was accurate before I try to troubleshoot it.

6 minutes ago, DeezNoNos said:

Yes it does not oc that well because it gets too hot with barely any voltage. Or you did not mount ur cooler proper or ur TIM is shit

Alright. Do you happen to have a 6600k as well, then? If so, let's talk via PM and we can reach an agreement. If not, then don't just take what you've read online and apply it as a rule for every single person, as most don't stress nearly 1/100th as hard as I do.

7 minutes ago, Clanscorpia said:

Because compared to mine they are normal

EDIT: I just realized, you didn't post your settings. I'll wait for those before commenting any further. Ignore below in the mean time.

Yup, you don't know what you are talking about. Then let me explain to you.

 

Here's the deal: P95 uses an instruction set called AVX 2.0. To be precise, FMA3 (and it can use regular AVX as well, but it doesn't matter right now). Now, when you OC a 6500, one of the many downsides is that it disables the AVX instruction set; you just can't use it. As a result, the app has to fall back to the much slower SSE4.1 instruction set, which also to generates much less heat.

 

So you and OP are pretty much using 2 completely different. And that's assuming you are using the Small FTT test, or even P95 in the first place when you validated

[pjsmith727]

9 minutes ago, Imakuni said:

Believe it or not, I did read your post. And that's why I'm asking you to provide some screenshots, so I can have a better grasp at what's going on. You'd be surprised at how many people I've got which had a similar problem as you, with the "reason" being that the OC was unstable and P95 stopped the test, for example. Or there was some massive vdroop. Or they were using the wrong test. And others.

 

That's why I wanna check things myself, so I can be sure that your description was accurate before I try to troubleshoot it.

Alright. Do you happen to have a 6600k as well, then? If so, let's talk via PM and we can reach an agreement. If not, then don't just take what you've read online and apply it as a rule for every single person, as most don't stress nearly 1/100th as hard as I do.

EDIT: I just realized, you didn't post your settings. I'll wait for those before commenting any further. Ignore below in the mean time.

Yup, you don't know what you are talking about. Then let me explain to you.

 

Here's the deal: P95 uses an instruction set called AVX 2.0. To be precise, FMA3 (and it can use regular AVX as well, but it doesn't matter right now). Now, when you OC a 6500, one of the many downsides is that it disables the AVX instruction set; you just can't use it. As a result, the app has to fall back to the much slower SSE4.1 instruction set, which also to generates much less heat.

 

So you and OP are pretty much using 2 completely different. And that's assuming you are using the Small FTT test, or even P95 in the first place when you validated

PM me bro, I feel like you got my answers. I'll hit you up with the screenshots in the morning. Full disclosure, may pass out in a couple minutes here?

[Imakuni]

3 minutes ago, pjsmith727 said:

PM me bro, I feel like you got my answers. I'll hit you up with the screenshots in the morning. Full disclosure, may pass out in a couple minutes here?

Nighty night m8.

[Clanscorpia]

17 minutes ago, Imakuni said:

 

EDIT: I just realized, you didn't post your settings. I'll wait for those before commenting any further. Ignore below in the mean time.

Yup, you don't know what you are talking about. Then let me explain to you.

 

Here's the deal: P95 uses an instruction set called AVX 2.0. To be precise, FMA3 (and it can use regular AVX as well, but it doesn't matter right now). Now, when you OC a 6500, one of the many downsides is that it disables the AVX instruction set; you just can't use it. As a result, the app has to fall back to the much slower SSE4.1 instruction set, which also to generates much less heat.

 

So you and OP are pretty much using 2 completely different. And that's assuming you are using the Small FTT test, or even P95 in the first place when you validated

It's not overclocked, but that it's running at 100% all the time, so at max speed. I know how P95 works

[Imakuni]

6 minutes ago, Clanscorpia said:

It's not overclocked, but that it's running at 100% all the time, so at max speed. I know how P95 works

V

25 minutes ago, Imakuni said:

you didn't post your settings

 

[Clanscorpia]

Just now, Imakuni said:

V

 

What? HWMonitor?

[Imakuni]

2 minutes ago, Clanscorpia said:

What? HWMonitor?

Sigh... let me try to explain.

 

"I get 85C on my 6600k with an H55".

 

That's how I'd tell you my settings if I didn't want you to know what I'm running. It doesn't help you picture my setup AT ALL. If I wanted you to know what's going on, here's how I should say it:

 

I have a 6600k running at 4263mhz on both the core and cache, 1.296v after LLC kicks in. RAM is dual channel, dual rank (matters for the purposes of P95) running at 3045mhz 15-17-17-35 2T, other timings are at the defaults set by my Asrock Z170 Extreme4+. The cooler is an H55 set as an intake, with ambient temps around 27~28C. Using Prime95 ver. 28.9 Small FTT, I get 84C as my peak core temperature, though it can peak at the 87~88 during our 38C in the summer.

 

See the difference?

[Mira Yurizaki]

My i7-6700 starts throttling at 65C-70C when I give it a Prime95 burn. Then again I think the processor was designed to aggressively throttle.

 

Still it maintains stock speeds so that's a plus.