Back in 2014 the Intel Processor Diagnostic Tool (IPDT) was not working for 2011-v3 CPUs but now in 2015 they released an update on 20th January and maybe also earlier this year. However i just want to let you know.
When i started in September 2014 with my 2011-v3 RIG i did test a lot and sometimes you’d like to know if you already burned or damaged something on your chip due to overclocking. A Diagnostic Tool, made by the same people who produce our chips, is the best choice if you want to check your CPU for injuries.
Powersavings were introduced back in the 90 at the end of the last century and there is no reason anymore to not make use of it, even when overclocking. These days SpeedStep or PowerNow technology could cause several stability problems but today we are facing software and hardware which has improved significantly. Go Offset! Time to make a change, time to make a cut here and use it. Only when using offset mode the processor can apply its power saving steps ontop of it. Maybe in the future they will be able to scale.
It’s nothing of a big deal
Just go into your BIOS and switch from fixed value to offset mode. You just have to do the math. Get the base voltage of your CPU and add that extra voltage you already applied in your fixed voltage and add the difference as offset voltage.
This post becomes old, however, even when it may have been stupid to call prime95 a bad choice to test overclocks it somehow may have saved peoples wallet. In the beginning when x99 was thrown onto the market, things were very new and everyone had to get closer to the new design step by step, carefully. As you have to admit, there were many articles about mainboards that were catching fire, go up in smoke, or break in any other possible way. Things are getting more stable and people are making their way through the jungle of architechture. Today i still would recommend people to be careful with prime95 but i would no longer discourage people from using it.
Update: 06. October 2014
Well i can not completely revise this.. when i started to think that prime95 doesn’t go well with Haswell-E i did run future tests with other tools like cinebench, sisoftware sandra, aida64 and had no problems even with lower voltages (1.28 V). Rendering videos, playing games and whatever you do with your computer also did work quite well. Today i tested with OCCT and it goes the same direction (1.35 V stable). With prime95 i ended at 1.37 V or even 1.39 V . So prime95 still does require lot more voltage to run stable than for example OCCT does, so im not sure yet where this journey is gonna end. I can not recommend using prime95.
Hellow peeps. The long journey comes to an end now. [Due to Update on 06. October i have to over-think this] I finally or accidently came to the “conclusion” that prime95 isn’t the right choice to test the Haswell-E processor series, like the i7-5930K to run any sort of stresstests.
In the end of the day this processor, the i7-5930K will be running at 4.5 Ghz with everything else overclocked at reasonable temperatures and stable. Well, not prime95-stable but Aida64-Cinebench-and-SiSoftware-Sandra-stable. Prime is just no longer an option or relevant for 2011 and x99.
Now prime95 has been replaced by Aida64 and Cinebench, while SiSoftware Sandra stays in the club. Benchmarks and graphs are always nice, but i intentionally use the software to make sure components are working fine together in harmony.
It’s already a month now since x99 and friends have been thrown on the market. A lot of you guys were sure smarter than i am/was and already knew that prime95 is a bad idea – when it comes to Haswell-E. While the hole world already OC’ed their CPUs with success i will just stick to some pictures. After i decided to no longer use prime95, i revoked / undid most of the changes i made there, to start from zero.
CPU i7-5930K in GHz:
Corsair LPX DDR4 in MHz:
Asus x99 Deluxe Baseclock in MHz:
3,7 @ base values, unknown voltage (release BIOS 0505)
2166 @ base values, unknown voltage (release BIOS 0505)
100 @ base (BIOS 0505)
2800 @ 1.5 V or 1.35 V (XMP didn’t work and Memory was very unstable at higher frequencies – or let’s say, with prime95 it was)
4,1 @ 1,23 V (release BIOS to BIOS 0801)
2800 @ 1.35 V (release BIOS + BIOS 0701, XMP started to work with 0701)
Some values were tested on different BIOS versions, some were stable some were not, some or many of them don’t even show up here. The table doesn’t show all combinations. In all cases you can say, that the newer setting also did run at least 1 BIOS version behind. For example 4.5 GHz was also tested on 0801 with Vcore from 1.27 to 1.390 and a lot of changes in voltages for other parts like Input Voltage or Agent Voltage or Cache Voltage or Changes in the DIGI Tab. But i do not recommend this especially because this happend in the prime95 period. In a previous post i said that XMP with BIOS 0701 was unstable. Thats not correct. This was also affected by prime95.
To the edge 4.6 GHz but prime95
As i mentioned already in a previous post, i could easily clock that Haswell-E jewel to 4.6 GHz. Problem had been, that it just didn’t pass the prime95 tests and that i found myself increasing and increasing over and over again the Vcore. At this moment i was noticing something weird with prime95 the first time, but i didn’t know about that bad relationship between prime95 and Haswell before, so i kept using it. What in the end led to a super hot CPU and with a crying Kraken X60 with stock fans. I made a short clip to demonstrate the Kraken stock fans at 1000% load (yes, that extra zero was intended). [Video quick link].
CPU – i7-5930K
DRAM – Corsair LPX 2800 DDR4
On 30. Sept. 2014 (2 days after publishing this post) - got a bluescreen 0x3B occasionally during SiSoftware Sandra Multicore Efficiency Test (this test did already run a few times with no error or bluescreen); will increase Vcore slightly from 1.276 to 1.29. This update doesn't show up in the BIOS screenshots below!!!
Now starting from zero with default settings and new crew
So starting from zero with some basic settings (CPU, DRAM, Cache and Baseclock will be set), and some of them are the result of the past few weeks. Initially will reset all voltage values and any performance related values to “Auto” again and boot the system.
Not that surprising but defaults deliver
And find myself happy with it. Now where the Vcore is back to normal and due to the absence of prime95 the temperatures during stress tests are lovely ( the funny thing here is, they never were bad, just prime95 made appear everything worse ). And more important the Kraken X60 stock fans do not have to go crazy anymore. Win-Win situation for me and the computer parts. Maybe i can get back to my Corsairs purple fans? When i run prime95 now with these settings, the system instantly goes down, but on the other hand i can normally use it. Can run any (non-prime95)benchmark, can render videos etc, can play any game … etc. somethign weird is burrowed in prime95.