i7 4790k temps okay?

RSmoovd

Honorable
Jul 27, 2013
58
0
10,630
Hello :)

I've oc'd my 4790k to 4.7ghz and run prime95 for about 7min.
Im using a noctua dh15.

in HWMonitor got around 61-63c then suddenly had a massive spike to close to 80 :ouch: stopped the test and instantly dropped back to 28-30 witch is what i get at idle.

(Just ran a second test for 5min and stayed at low to mid 60s)

Are these good temps? Thanks :)
 
Solution
I had a really bad bad run of luck w/ Asus Z87 boards and since then we have been using MSI and Giga ... Z170 reviews and user ratings are up substantially over Z97 so we may give Asus a try again with some upcoming Z170 builds. What I am getting at is, we never did get around to doing a script for our Asus Z97 users to OC their boxes. We'd show them how to get sat 42 multi and let them take home and do from there. But here's the Z87 Asus script.... easily adaptable for Z97. Of course, w/ 4790k, you'd start at 45 or 46 CPU multi


=========================================

This is a "Minimalists Guide to Haswell Overclocking on Asus Boards". I don't have the patience to invest 100 of hours but I admire those who do. Using...

G-star93

Honorable
Oct 19, 2014
560
0
11,060
Yes they are great and keep in mind that Prime95 and other stress tests programs, will have higher temps than you would actually have in gaming, rendering etc..so if you have mid 60's in P95 you will have high 50s in games. :)
 

RSmoovd

Honorable
Jul 27, 2013
58
0
10,630


Yeah of course i havent seen cpu usage go over 10% yet lol :D

 

RSmoovd

Honorable
Jul 27, 2013
58
0
10,630


I will run another test tomorrow just to make sure it isnt actually hitting 80 since the second test didnt go over 65.

 
OK for what ? Which P95 ? ... the old one with no AVX or other modern instruction sets of the new one ? P95 really doesn't tell you anything except if your cooling system can keep and it does a poor job of that since it will show way higher temps than your machine will ever see. With modern MoBos auto adjusting voltages and modern instruction sets requiring huge voltage bumps P95 presents quite a quandry. Old version won't cause those scary voltage bumps but OTOH, those bumps are caused by instructions sets used by modern programs..... so if you are 4 hour p95 stable using the old version (26.6) .... all you have shown is that youe CPU is stable and not too hot .... except if it runs any program w/ modern instruction sets.

Question is, did ya build ya PC to run P95 or to run programs ?

I would recommend that ya download these

http://rog.asus.com/forum/showthread.php?43233-Realbench-v2-Discussion-Thread-Download-Links
http://www.hwinfo.com/download.php

Rather than retype, I just gonna point you to the post here:

http://www.tomshardware.com/answers/id-2929619/4690k-safe-temperatures.html#17279145

As said there, I find I can be P95 stable at 80+C and then fail in RoG RB at 70C, so I don't bother to use P95 for anything other than thermal cycling to set TIM.

In the 90s your getting close to throttling once ya get to 85C for sustained periods, you can expect degradation to be occuring
 

Slurpee12

Reputable
Nov 19, 2015
240
0
4,710

Okay, sounds good. I'm running an i7 3820 @ 4.2GHz with Corsair H80i GT and my temps peaked at 65 on Prime95. While gaming, the maximum temp I have yet to see is 54 degrees. If your temps are at 61-63 in Prime, then your cooling is perfect.
 

RSmoovd

Honorable
Jul 27, 2013
58
0
10,630


I believe it was latest version of P95 i think the voltage stayed at 1.350
But ofcourse to run programs :pt1cable: (Im a music producer)
 
If it stayed, then one of two things was going on:

1. It wasn't the latest version.... after 26.6 the new instruction sets started being added.
2. You have locked the voltage and eliminated the power saving features of the system.

MoBo manufacturers incorporate techniques into the control system whereby the CPU gets more juice when it needs it. Look in BIOS for terms like LLC and adaptive voltage control. Adaptive means that when ya turn on ya PC, it will shoot right up to your 4.7 but after a minute or two will drop down to 0.8 until ya actually start doing something.

When ya lock the voltage to a certain number "manually", you lock your self into that number and 4.7 GHz 24/7 .... Not Recommended

try it with RoG Real Bench and HWiNFO64

When you open Real Bench, move both windows to left side of screen. Open HWiNFO64, run "sensors only", you may get a pop up asking whether to disable reading the Asus EC chip or something specicifc to your MoBo, click "Disable this sensor". Move the HWiNFO64 window to upper right hand corner of screen. Stretch bottom of window to full screen height. Make the following changes:

-Right Click on "System" right at the top, select hide.
-In the next section, hide the last 4 lines starting "Core CPU Thermal Throttling" (if you watch temps, this is useless)
-Skip over the next section and Hide the section after that (section includes CPU Package thru DRAM Power)
-Now the whole reasons we did that was so you could see everything you wanna see at same time. You should be able to see Vcore 0, 1 and 2 at -the bottom of the window. If not hide a few more lines. Save and Quit will save your edits.

If ya watch the 4 core temps, assuming your are on adaptive and allowing the MoBo to add voltage when needed, these will jump up and down, I always wait till the CPU speed as at 0.800 Ghz before starting .... may take a few minutes.


Here's what I see for voltage as a peak (lowest core / highest core) during each phase of the test on my 4770k (4.5 GHz CPU/ 4.2 Ghz Cache) on my "normal day" BIOS profile. Guess which test is loaded w/ AVX :) (Open CL)

Image Ed. 1.328
Encoding 1.344/1.376
Open CL 1.424/1.440
Multitask 1.392/1.440
Core temps = 63, 67, 61, 57


This is 4.6 / 4.6 This was just a test I did to see what would happen with a high cache multiplier .... normally I set cache to CPU - 3 (46/43)

Image Ed. 1.392
Encoding 1.408
Open CL 1.488/1.504.... I didn't like breaking 1.5 if only for a microsecond or so)
Multitask 1.408
Core Temps = 72, 72, 68, 62

 

RSmoovd

Honorable
Jul 27, 2013
58
0
10,630


I will try this tomorrow and see what happens if im correct i think the voltage was on auto in the bios i dont even know how its running perfectly fine at stock voltage also with the cpu clocking down when not using the full power ive been trying to look for it since i really dont want to run 4.7 constantly even though temps are fine with it 28-34c idle witch ill go down to maybe 4.5ghz anyway and not have it constantly running at that clock. Thanks for the information n help :D
 

RSmoovd

Honorable
Jul 27, 2013
58
0
10,630


Yeah i just noticed it sits at v1.3 at 4.5ghz and v1.1 at stock clock
mobo is asus maximum vii ranger
 
I had a really bad bad run of luck w/ Asus Z87 boards and since then we have been using MSI and Giga ... Z170 reviews and user ratings are up substantially over Z97 so we may give Asus a try again with some upcoming Z170 builds. What I am getting at is, we never did get around to doing a script for our Asus Z97 users to OC their boxes. We'd show them how to get sat 42 multi and let them take home and do from there. But here's the Z87 Asus script.... easily adaptable for Z97. Of course, w/ 4790k, you'd start at 45 or 46 CPU multi


=========================================

This is a "Minimalists Guide to Haswell Overclocking on Asus Boards". I don't have the patience to invest 100 of hours but I admire those who do. Using this method, most can knock it off in a weekend.

1. Stop using AIDA, Prime 95 or anything else like that. Download RoG Real Bench, HWiNFO64 and Intel ETU.

http://rog.asus.com/forum/showthread.php?43233-Realbench-v2-Discussion-Thread-Download-Links
http://www.hwinfo.com/download.php


Usage of testing and monitoring programs:

When you open Real Bench, move both windows to left side of screen. Open HWiNFO64, run "sensors only", you will get a pop up asking whether to disable reading the Asus EC chip, click "Disable this sensor". Move the HWiNFO64 window to upper right hand corner of screen. Stretch bottom of window to full screen height. Make the following changes:

-Right Click on "System" right at the top, select hide.
-In the next section, hide the last 4 lines starting "Core CPU Thermal Throttling" (if you watch temps, this is useless)
-Skip over the next section and Hide the section after that (section includes CPU Package thru DRAM Power)
-Now the whole reasons we did that was so you could see everything you wanna see at same time. You should be able to see Vcore 0, 1 and 2 at -the bottom of the window. If not hide a few more lines. Save and Quit will save your edits.


2. I am going to assume that you want your PC to power down and reduce voltages when not needed so for this we'll use Adaptive settings. Adaptive will throw an extra 0.10 to 0.13 volts at your CPU when AVX instructions are present. Again, I would NOT use P95 or AIDA on this setting without constant attention.

3. After setting BIOS to defaults, Input the following settings and then right click on them to add them to your favorites page. This will allow you to access all the settings you need to without bouncing all over the BIOS:

AI Overclock Tuner = Auto
1-Core Ratio Limit = 42 (all others should automatically change with Sync all cores selected above)
Max. CPU Cache Ratio = Auto
Min. CPU Cache Ratio = Auto
Fully Manual Mode = Disabled
Core Voltage = Adaptive
Additional Turbo Mode CPU Core Voltage = 1.200
Core Cache Voltage = Adaptive
Additional Turbo Mode CPU Cache Voltage = Auto
Eventual CPU Input Voltage = 1.90
DRAM Voltage = Auto

I'd suggest taking a screen shot (F12) of the favorites page when ya have successfully passed the stress tests.

4. Open Real Bench, select Benchmark Tab Check only the last box. Open HWiNFO64, run "sensors only" as described above. Start Real Bench and don't touch mouse till finished. Observe voltages and temps. If you can get thru these 2 minutes, your close.

5. Then try checking all 4 boxes and run again NOTE: During the 3rd test Open CL will send AVX instructions to CPU; pay close attention to Vcores as they will spike as described above. If passes.....

6. Switch to the Stress Test Tab and select the amount of RAM you have in your system and 2 hours..... (Note: If you plan on raising cache and / or RAM after a run, I will usually save the two hours and skip this step until I have Multiplier / Cache and RAM speed at my targets.

7. If at any point you fail, up Core Voltage to 1.225 (+0.025)...Always watch temps and stop tests if you reach temperatures of concern (> 85C in my book). Record the following:

42/A/A/Auto - Shorthand for 42 Multiplier / Auto Max. Cache / Auto Min, Cache / Auto DRAM setting
Actual RAM Speed - i.e. 1600
Ambient = Room Temperature
Coolant Temp at Idle = Requires a sensor
Idle Core Temps Before Test on Each Core = i.e. 25, 26, 24, 22
Average Core Temps for Each Core During Test = i.e. 59.6, 58.2, 52.7, 49.4
Max Core Temps During Test on Each Core = i.e. 65, 62, 59, 54
Settings you input in BIOS for VCore, VCC Ring (Cache), VCCIN (Eventual), DRAM i.e. 1.2000, Auto, 1.900, Auto
Actual Readings in BIOS for VCore, VCC Ring, VCCIN, DRAM i.e. 1.040, 1.122, NA, 1.671
Actual Readings in HWiNFO64 for VCore, VCC Ring, VCCIN, DRAM i.e. 1.296, NA, 1.920, 1.681
Highest Voltage Reading on any Core During each of the 4 Benchmarks, i.e. Image Ed. 1.200 / Encoding 1.216 / Open CL 1.296 / Multitask 1.248

7. If at any point you fail, up Core Voltage to 1.250 (+0.025). If ya fail again, go another notch (1.275) but I'd stop there.

8. Once you pass, it's time to consider cache voltage. Some are content to leave at Auto (39) as it affects very, very few applications (skip to step 9 if this is you), others try and get as close as they can to the CPU Multiplier. If you want cache up, go to 42/42/42/Auto. If ya fail, bring up cache voltage in same 0.025 increments.

Settings will look like this when starting:

Max. CPU Cache Ratio = 42
Min. CPU Cache Ratio = 42
Additional Turbo Mode CPU Cache Voltage = 1.200

9. Once stable, it's now time to get ya RAM up to its rated 2133, 2400 or whatever. Change 1st setting above to XMP

AI Overclock Tuner = XMP

Referring back to step 6, this is the point I normally do the 2 hour test when I am "done" with a given multiplier. So run the 2 hour test here, followed by an 8 hour test w/ Intel ETU.

10. If ya fail.... up ya voltages as per above..... as long as things don't get too hot.....see limits below. If ya pass, it's time to see if we can lower temps and voltages. I dunno if it matters what order ya do it in but I did VCCIN 1st till I failed then bumped up till I got lowest stable setting. Then did VCCring (Cache Voltage Setting in BIOS) till I got lowest stable setting....and finally VID (BIOS CPU Voltage setting) last. I leaped in "half" amounts.

For example.... Default VCCIn is reportedly less than 1.8 .... so if 1.9 worked, i went "half way" to 1.85 .... if 1.85 failed, I went halfway between known good and bad to 1.875 ....same deal with VID and VCCring.

11. With the 42 series if tests complete, "rinse and repeat" with steps 3 thru 10 after moving up to CPU Multiplier to 43, then 44 or as high as you are willing to go. At 46 multiplier I found 1.9 VCCIN to be inadequate.... this is the one voltage I found that going too high or too low is problematic (other than heat and maximum upset voltage limits of course). I went to 1.98 (last yellow setting) and it was too low..... 2.08 was too high. 2.04 worked for me w/ 46 multiplier,

12. These were my initial settings to give ya an idea of luck I had "1st day" .... your mileage will vary. Asterisked ones are those I didn't go back and try and get better temps / voltages cause I was never gonna use them.

42/42/42/XMP (2400) *
VCore 1.200
VCC Ring 1.200
VCCIN (Ev) 1.880
DRAM 1.700
Avg Max Core Temp = 59.0C (28.0C Ambient)

43/43/43/XMP (2400) *
VCore 1.225
VCC Ring 1.225
VCCIN (Ev) 1.880
DRAM 1.700
Avg Max Core Temp = 56.5C (27.4C Ambient)

44/44/44/XMP (2400) *
VCore 1.260
VCC Ring 1.260
VCCIN (Ev) 1.880
DRAM 1.700
Avg Max Core Temp = 59.0C (24.5C Ambient)

45/45/45/XMP (2400)
VCore 1.325
VCC Ring 1.325
VCCIN (Ev) 1.880
DRAM 1.700 *
Avg Max Core Temp = 63.0C (22.9C Ambient)


46/43/43/XMP (2400)
VCore 1.385
VCC Ring 1.385
VCCIN (Ev) 2.020
DRAM 1.700
Avg Max Core Temp = 69.0C (23.0C Ambient)

46/46/46/XMP (2400)
VCore 1.385
VCC Ring 1.410
VCCIN (Ev) 2.040
DRAM 1.70
Avg Max Core Temp = 72.0C (24.4C Ambient)

In subsequent BIOS builds and with more tweaking, these were improved upon


13. As for cooling / heat / voltage concerns

Here's Asus recommendations:

A very good air cooler is required for voltage levels above 1.15V.
1.20V-1.23V requires use of closed loop water coolers.
At 1.24V-1.275V dual or triple radiator water cooling solutions are advised.

My thinking is:

Up to 1.200v = Very Good Air Cooler (Hyper 212)
Up to 1.250v = Best Air Coolers (Phanteks PH-TC14-PE, Silver Arrow or Noctua DH14) ....... Dual 140mm CLC / AIO Cooler w/ 1500 rpm fans (Corsair H110)
Up to 1.275v = Extreme Speed Dual Fan CLC / AIO w/ 2700 rpm fans (too noisy for most folks)
Up to 1.287v = Best air coolers (Cryorig R1 / Noctua DH-15)
Up to 1.300v = Swifteh H240-X
Up to 1.325v = Custom Loop w/ 15C Delta T (3 x 120mm / 140mm) *
Up to 1.400 = Custom Loop w/ 10C Delta T (5 x 140mm or 6 x 120mm) *

* At this level having the GPU(s) also under water is assumed

Also, if you are not running AVX, you can add as much as 0.10 to all those voltages.

14. NEVER WALK AWAY from your machine while stress testing until you are sure that temps have stabilized.
Be AWARE if test uses multiple instruction sets like Real Bench who throws out its hardest load voltage wise with the 3rd test in the Benchmark but the 4th test results in higher temps.

Remember some AVX instructions are present during RoG Real Bench type loads which will raise VCores by 0.10 to 0.13 for short periods. I would not suggest running Prime 95 w/ AVX under adaptive under above conditions.

15. Having 4 sticks of memory will hinder ya OCs a bit.

16. If ya want the best OCs ya machine can get, this is not the guide to use. If ya wanna get it done over the weekend in between taking work home, course work, Honey-Do Lists, Daddy Taxi and other life demands, this may get it done in a weekend :) .

WORD OF WARNING: Some of us are having problems with the BIOS clock freezing and a suspected cause is the use the saving, loading and backing up of OC profiles in the Tools section of the BIOS. I would avoid use of that feature until such time as the cause is confirmed or a fix is available. PS: tho after month of efforts, tho Asus announced a BIOS that fix was going to be available the next day, it was never released. After finishing your OC setup, reboot and check BIOS clock.... if it's stops, this is the temporary fix ... and by that I mean, it will fix it ... till it happens again :)
http://rog.asus.com/forum/showthread.php?36676-Frozen-Time-Clock-in-UEFI-The-Fix
 
Solution

The_Tester

Reputable
Nov 22, 2014
202
1
4,760

What wattage is HWMonitor reporting? Also what was the exact test you were running? If mixed it can cause some rather heavy loads to be applied every now and then (also gives the ram a good "workout"). You may want to pay more attention to wattage rather than what program you are using. I have prime95 26.6 and 28.7(newest) and many other programs. They absolutely do not stress the cpu the same as each other. I've seen as much a 10~15% increase in temperature just buy changing which program I use.

Whatever you end up doing, I would try to stay at VCORE 1.3V or less (play around with 1.24~1.27). As far as wattage vs temp, try to stay under 110W sustained until you know it's not going to run away on you. If you can crack 110~115W with that cooling solution while staying under 70C you got a fairly good/well applied integrated heatsink (IHS).

 
I have prime95 26.6 and 28.7(newest) and many other programs.

I have a slew of them which I keep on hand but rarely use anymore.

P95 is great for TIM curing.... I have come to like OCCT better tho cause I can set it and walk away knowing it will shut the test down when it reaches the temperature target I have set.....usually allows me a bathroom break as system is idling when i get back :)

I still will stress test with P95 it now and then just for sheetz and giggles, but since P95 stable OC's crash under RB (sometimes within 2 minutes), I don't find running P95 for 4 hours worth theT&E

I've seen as much a 10~15% increase in temperature just buy changing which program I use

That's another reason I stopped using.... if my goal say is to get the highest OC possible running any combination of programs that I might throw at it, what is the point of running a synthetic program that will take it 10C higher than any combination of real life usages ?

When doing several builds at a time, I can detect a bad OC usually within 2 minutes with RB, if the 2 minute test passes, I'll go to the 8 ... if it passes the 8, I know I am real close. With synthetics, those can take hours.

I would try to stay at VCORE 1.3V or less

Are you talking about the VCore setting or the level at which vcore rises to when stress tested ? A Vcore setting of 1.3 will typical allow 1.43 volts when AVX is present unless you have disable power saving features. I agree tho on the 1.3 volt *setting* (1.43 when test running AVX) .... I recommend 1.2875 for Haswell on the D15 but , you can bump all the numbers in the above table up one notch with Devils Canyon

BTW, have you tried HWiNFO64 ? ... it's HW monitor on steroids, think you'd like all the extra info it provides. It's also updated at least one a month, most others get updated like twice a year
 

The_Tester

Reputable
Nov 22, 2014
202
1
4,760

Pretty much the same with me. My setup is a 4770K and h105 so I honestly don't have much legitimate need to test it unless i'm board lol. As for core voltage I usually lock down a limit based on what the manufacturer states. I'm not a fan of certain things deciding it knows better than me. I'm the type to keep things lasting as long as possible however. I actually still have a working AMD thunderbird CPU OC setup (pencil trick) from early 2000's lmao! I do have hwinfo, but actually don't use it that much unless i'm trying to see particular things. HWMonitor gives you the bare bones basic stuff that I mostly look at. I will say that NOTHING I have used yet will allot me to observe the current temperature of my 950 PRO. The response i've gotten at this point is to basically "wait and see" if a new NVMe driver and or update fixes it. It is (supposedly) a known issue with the ASRock Extreme9 and WIN10. That or my 950 is not going to work as long as it should because I got a day one release :heink:.
 


I spend 2-3 days setting it up.... and then maybe a day after each BIOS upgrade. I normally don't do them unless there's some benefit but I kept looking for a fix to the Asus Z87 / Z97 clock freeze bug on my Asus Maximus Formula.

Like old stuff >... I just retired a 8088 Wang APC that I got in mid 80s and also a Server that I built in the last millenium :)