Tag Archives: bios

Samsung SM951 NVMe on Asus x99 Deluxe – Baseclock <> CPU strap magic

Samsung SM951 M.2 2280 MZVPV512
Samsung SM951 M.2 2280 MZVPV512

 

“I did buy a new little toy, the Samsung SM951 NVMe 512 GB M.2 SSD Drive.”

 

I tested the Samsung SM951 NVMe M.2 on Windows 7 and Windows 10 by using the M.2 slot on the motherboard and by using the M.2 addon card which comes shipped together with the Asus x99 Deluxe.

System:

  • Asus x99 Deluxe BIOS 1901 @ ~ 125.5 MHz Baseclock (while 125 MHz CPU strap)*
  • i7-5930K @ ~ 4.4 GHz, 125 MHz Strap, 1.31 Vcore, 1.24 Vcache, 1.24 Vsysagent
  • NV GTX 770
  • 16 GB Corsair DDR4 @ ~ 3 Ghz, 1.35 Vmem
  • 2x  SSD OCZ Vertex 2 (Sata2) (Raid0)
  • 2x  Seagate HDD  3 TB/HDD (Raid1)
  • PSU Corsair AX1200i (why the heck an AX1200i?)
  • Corsair Obsidian 450 D

 

*The ‘Baseclock’ and the ‘CPU strap’ will become more important over time in this SSD benchmark drama-post. I couldn’t think of the Baseclocks offset to the CPU strap affecting the benchmarks. At first i thought its overclocking on this motherboard in general, which affects the benchmarks.
Theres is an old problem known to Windows 8 respecting system timers and clocks leading to incorrect benchmarks. Seems that Windows 10 and 7 are affected too.

 

Driver

 

Asus x99 Deluxe M.2 slot populated with unrelated m.2 device. Image source: http://rog.asus.com
Asus x99 Deluxe M.2 slot populated with unrelated m.2 device. Image source: http://rog.asus.com
Asus Hyperkit M.2 Addon Card. Image source: http://rog.asus.com
Asus Hyperkit M.2 Addon Card. Image source: http://rog.asus.com

 

IMAG1047“No matter which OS or which PCIe slot i use, the SSD seems to be throttled or bottlenecked.”

 

 

 

“As soon as the Baseclock is higher than my CPU strap. The benchmarks do no longer represent the correct values!”

“Baseclock frequency below CPU strap frequency may result in the same behaviour”

“You can say that any offset between the CPU strap and Baseclock may result in “bogus” or shifted benchmarks”

 

 


The trip to find the cause for the benchmark results:

 

 

“A bad driver can also act as a bottleneck.”

 

First ATTO run on Windows 7 – smells like bottleneck.

The SM951 M.2 2280 MZVPV512 NVMe SSD is using the Asus x99 Deluxe onboard M.2  slot.

Some people may not be able to see the device on OS side (Win 7 !). And those people may make their way through the internet and find a “Hotfix” by Microsoft (Windows6.1-KB2990941-v3-x64). I did  install the Hotfix. It may work for you but you may not get 100% out of your device.

Because of the “bad” results i got, i did install Windows 10. I did hope that i can get the drivers off the SSD when installing a fully UEFI compatible OS. But …

 

atto_first_run_nvme_samsung_2280_951_512_GB
SM951 M.2 2280 MZVPV512 NVMe SSD, Baseclock @ 125.5 MHz, CPU strap 125 MHz, not system drive, connected using onboard M.2 slot

 

 

 

“There is a throttle …”

 

 

There is a throttle

Keep in mind that the SM951 NVMe model indeed is able to throttle itself to prevent overheating. What if this throttle mechanic is not working properly? Keep that in mind. It is possible …

… but it’s not  threating us here. 🙂

 

 

“Expectation”

 

First ATTO run on Windows 10 – smells like bottleneck.

…even with Windows 10 i still do seem to be using the NVMe drivers provided by Windows (or worse the previously installed Hotfix).

The SM951 M.2 2280 MZVPV512 NVMe SSD is using the Asus x99 Deluxe onboard M.2  slot. Comparing with other tests on the internet you expect read speeds > 2.2 GB/s.

 

atto_first_run_windows_10_nvme_samsung_2280_951_512_GB
SM951 M.2 2280 MZVPV512 NVMe SSD, Baseclock @ 125.5 MHz, CPU strap 125 MHz, not system drive, connected using onboard M.2 slot

 

Second ATTO run on Windows 10 – smells like bottleneck.

The SM951 M.2 2280 MZVPV512 NVMe SSD is using the Asus x99 Deluxe onboard M.2  slot. This time i did set x4 mode manually and did disable a couple unneccessary stuff in the BIOS to make sure nothing weird is going on there. With no reward. Same results.

 

atto_second_run_4x_mode_manually_set_windows_10_nvme_samsung_2280_951_512_GB
SM951 M.2 2280 MZVPV512 NVMe SSD, Baseclock @ 125.5 MHz, CPU strap 125 MHz, not system drive, connected using onboard M.2 slot

 

 

“Alternative”

 

 

Third ATTO run on Windows 10 – smells like bottleneck.

This time i did use the Hyperkit Card shipped with the Asus x99 Deluxe. Same results.

 

atto_third_run_pci_express_m.2_addon_card_manually_set_windows_10_nvme_samsung_2280_951_512_GB
SM951 M.2 2280 MZVPV512 NVMe SSD, Baseclock @ 125.5 MHz, CPU strap 125 MHz, not system drive, connected using M.2 addon card for PCIe

 

IMAG1047
ASUS M.2 addon card “Hyper” for PCIe 3.0

 

 

 

The drivers Windows 10

Just for the records. Unfortunately i did not make screenshots of the Windows 7 drivers. The MS drivers were mentioned already in the past when it led to problems with NVMe like this. But they do pretty well now. They improved it

Storage Controller

Windows 10 Device Manager-> Storage Controller->Standard or Basic NVM Express-Controller->Properties->Driver->Driver details

 

Image4

Storage Device

 

hw_drv_properties_nvme_drive_sm951_2280_mzvpv512_samsung

 

hw_list_properties_volume_f_nvme_samsung_2280_sm951

 

BUT

“It’s not the drivers fault”

 

But it turned out, that it is not the driver who is causing these “bad” results.

Silence.

 

“The drama …”

 

 

The relief – no bottleneck

It was the fact that the System was overclocked. As soon as i lowered the Baseclock back to 100 MHz. The results became better. The Baseclock was previously set to 125.5 Mhz. I then had read results > 2.2 GB/s and write results > 1.7 GB/s with SM951 SSD used as non-system drive. Unfortunately i did not make a screenshot of it. (What i did not think of here is, that the CPU strap also was set back to 100 MHz – the same frequency the Baseclock is running at)

Last ATTO run on Windows 10 @ 100 MHz Baseclock (system drive!)

However i then did configure the Samsung SM951 NVMe SSD as system drive. The performance results would be a bit better when it is not used as system drive.

 

samsung_sm951_nvme_2280_512_gb_windows_10_system_disk_baseclock_100_mhz_no_overclock
SM951 M.2 2280 MZVPV512 NVMe SSD, Baseclock @ 100 MHz, system drive !, connected using onboard M.2 slot

 

(I noticed the following before i finally discovered that the baseclock<>CPU strap offset is causing the shifted benchmarks, but i then ignored it because of the Anti Virust software which came out as a potential cause when configured to be super sensitive)

What’s left to say?

If you multiply the old results with (Baseclock of 125.5  MHz) with 1.255 you get results matching pretty well with the results of Baseclock of 100 MHz.

For example the 8 MB result of the first run:

1398442 Write     x     1.255 = 1755044,71
1717986 Read     x     1.255 = 2156072,43

 

  • Was the higher Baseclock really throttling or bottlenecking  the SSD?

 

  • Or is it just the benchmark not being aware of a higher Baseclock  and mucking up the results? Possible that the realtime clock is affected by Baseclock?

 

  • Will i ever be able to overclock and enjoy the Samsung SM951 NVMe performance at the same time?

 

Apart from ATTO i sure did run other benchmarks on the overclocked system and they sure came up with not the same results because they dont “measure” all the same way but they all left you thinking of either a bottleneck or throttle. I unfortunately made no screenshots of the runs before but i will present some with stock clock speeds and Samsung SM951 as system drive.

 

Samsung SM951 NVMe M.2 SSD as system drive Windows 10 @ 100 MHz Baseclock
samsung_sm951_nvme_2280_512_gb_windows_10_system_disk_baseclock_100_mhz_no_overclock_qd32_th1 samsung_sm951_nvme_2280_512_gb_windows_10_system_disk_baseclock_100_mhz_no_overclock_qd32_th6
CrystalDiskMark: Queue depth 32 Threads 1 CrystalDiskMark: Queue depth 32 Threads 6
samsung_sm951_nvme_2280_512_gb_windows_10_system_disk_baseclock_100_mhz_no_overclock_qd64_th12 samsung_sm951_nvme_2280_512_gb_windows_10_system_disk_baseclock_100_mhz_no_overclock_qd128_th12
CrystalDiskMark: Queue depth 64 Threads 12 CrystalDiskMark: Queue depth 128 Threads 12

As system drive and some disturbing stuff going on the whole time in the background the results are OK.  But to answer the questions of “How did the Baseclock affect the benchmarks?”  or “Will i ever be able to overclock and enjoy the Samsung SM951 NVMe performance at the same time?” we would’ve to pick another route.

 



As soon as the Baseclock is higher than my CPU strap. The benchmarks do no longer represent the correct values!

No matter if the ‘useplatformclock’ is enabled or not. The benchmark results do look like the SSD was throttled or bottlenecked as soon as the ‘Baseclock’ is higher than the ‘CPU strap’. I thought i revealed my Anti Virus software to be the root of al evil but it was not.

The realtimeclock RTC

Just for the records:
The value for useplatformclock was initially set to Yes on Win 10
The default value on Win 7 may be unset or No

This fact was one thing that concerned me that i was right following the Baseclock- / hwclock- / timer-way

 

bcdedit_useplatformclock_yes_windows_10_cmd_shell
‘bcdedit’ output while not a single parameter was handed over

I did play with this setting with overclocked and non overclocked system. But it took some days to finally notice that it has something to do with the ‘Baseclock’ and ‘CPU strap’. I did step away from this setting, when i thought it had something to do with the Anti Virus software. However this setting does not help to solve the problem on systems with not equal Baseclocks and CPU straps.

 

“Finally i could narrow down the cause but i couldn’t solve it yet.”

 

 



 

 

What i thought and wrote, when it seemed to be the Anti Virus software compromising the benchmark results. I trapped myself when i quick-overclocked the system again (by leaving Baseclock and CPU strap the same) to test different situations:

OK folks.. scratch all that

i tend to play now with “useplatformclock” (bcdedit) and overclock the system again. But guess what. Neither overclocking nor playing with useplatformclock variable did make any difference to the benchmarks.

 
But i think i revealed who was in charge for the performance trouble in the beginning …

 

… it was …

… my freaking Anti Virus software!

 

I did compare the useplatformclock setting of a Windows 7 system to my Windows 10 system to make sure that this could be a true reason for the mucked up results and it turned out to really be a root for the mess. You now need to know that i went from Windows 7 to Windows 10, just because of this performance mess, by upgrading Windows 7 to Windows 10. There was a chance that some important settings wern’t migrated or merged correctly. Upgrading does leave room for a lot of mistakes at this level. Later on i made a complete fresh install of Windows 10 and this time i installed it directly on the SM951 NVMe SSD, but as i already mentioned, the results didnt change anymore no matter what i touched.

  • Because the Baseclock and CPU strap are equal during this period i never had any shifted benchmark results again

I was freaking out because i really need to know the cause for the performance drama at the beginning to wipe out any missconfigurations and make sure every component is running fine and smooth and then when i was almost giving up i took the Anti Virus software into account.

It’s not that i never was thinking about it but i did underestimate it and i also wasn’t aware anymore of the configuration of my Anti Virus software.

  • Apart from the Baseclock and CPU strap there was only one more thing that could form a bridge  between all these odd things.

As tired as i might be the Anti Virus software was the only thing that could “transport” or “connect” the performance mess from one OS to another – if you are changing the OS by upgrading it. The complete fresh install i mentioned earlier wasn’t affected by the Anti Virus software, because i didn’t install it, but the old Windows 7 and the upgraded Windows 10 installations both had the same Anti Virus installation running.

  • But they also had a Baseclock CPU strap offset

So i went ahead and installed the Anti Virus software. With said software running in the background i still did get normal results. Again that did hit me hard. I thought i got it. But in the same moment, i realized that i didn’t change it’s configuration.

With the configuration window infront of me the settings, i usually made, came into my mind and i set them according previous installations of this Anti Virus software. And guess what. I finally could reproduce the ‘BAD RESULTS’. With its settings set back to defaults, everything is fine. No performance issues.

THE END

samsung_sm951_nvme_2280_512_gb_windows_10_system_disk_baseclock_125_mhz_no_overclock_qd32_th4
CrystalDiskMark: Samsung SM951 NVMe M.2, Queue depth 32 Threads 4, Baseclock 125 MHz, system drive !, onboard M.2 (Baseclock and CPU strap are equal here!)

 

 

I know what some people will say. 🙂 All i can respond is, that i am aware of Anti * ware digging into things and some other things. My problem in this case relies more in the experience i had with this Anti Virus software. I’m using it for years now and never had any issues like denied or failed or interrupted installations due to scanning attempts or  or any kind of interruption that would ask for my attention or a closer look. It always had been the perfect Anti Virus software for me. “Install it and forget it”. Now it got its revenge for all the years not paying attention, not treating it like a tamagotchi and not taking care of it.

I promise i will treat you better now, dear Anti Virus.

But i can say now that i was right not believing my Anti Virus software to be the one compromising the results.

Another BIOS release for x99 Deluxe

Asus just did release another BIOS for the Asus x99 Deluxe. We are now at Version 1601 1702.

With BIOS 1502/1601 .. the problem width Audio somehow disappeared for now or maybe the emitting component in my circuits. However i wasn’t happy with the digital to analog converter since it requires additional power supply and using usb power insead of power supply was a bad choice since the emitted frequencies i had earlier were injected in that converter too.

 

 

Asus Crystal Sound on x99 Deluxe audio problem

with BIOS 1601 the problem somehow disappeared for now. however i wasn’t happy with the digital to analog converter since it requires additional power supply and using usb power insead of power supply was a bad choice since the emitted frequencies i had earlier were injected in that converter too  through USB. What i then did was buying a Mass-Loop Devider (i dont know the correct english term for this). And even without this tiny piece the “noise” is almost gone.. In case it was a mass loop i can not tell where “problem” relied. It is not clear if the BIOS update was part of the solution or not. Could also have been any electrical device of my neighbours.

http://www.amazon.de/Massetrennfilter-Mantelstromfilter-Stereo-Line-%C3%9Cbertrager-Monacor-FGA-40/dp/3817133103

 

“Meanwhile i do not know who to blame but due to the problems that came up with Asus Motherboard i kept throwing la culpa at Asus.”

Read the Updatepost >>

Additional noise / frequency / ground loop (?)

As soon as my graphics card now is under load – the mainboard or its components emit some additional frequencies… Audio Jacks / Chinch have been used. The problem didn’t exist in the past but i can’t tell when it occured. I don’t play games very often using my Hifi. Cable etc. has been tested and even different sources. In the end its the computer the additional frequency is originating from.

Sobald die Grafikkarte unter Last gerät kommt am Audio Ausgang ein zusätzliches Geräusch hinzu. Hört selbst. Zum Einsatz kommen normale Klinke / Chinch Kabel. Kabel u.s.w. sind getestet. Auch verschiedene Quellen. Problem ist der Rechner.

 

I will just record the versions i’ve tested

Bios Version 1305 / 1401 / 1502
(no matter if overclocked or not)

Audio Driver
Realtek_audio_Win7-8-8-1_V6017344
Realtek_Audio_Win7-8-8-1_V6017329

EVGA GTX 770
Driver Ver. 344.11

The Crystal Sound isn’t that crystal when the PCIe slots are stressed it seems. Other cause could be an emitted electronical field to the soundchip? But why did i not experience it on previous versions? What did i forget? What did i miss?

 

 

Mass-Problem or emitted by components

Some people would consider this a Mass-Problem. And they may probably right. All cables have been changed and all components are on the same power-socket. When i connect the cable to he mobile the noise can not be reproduced. The source may be the graphics card / mainboard / sound chip. Any toys like Bluetooth and WiFi are disabled.

 

bahuett

Asus x99 Deluxe BIOS Ver. 1305

slight base Vcore increase

So many BIOS Versions have been released by ASUS for the x99 Delux series. What you might experience with 1203 and 1305 is a slight increase of “base voltage” on the Vcore.

When i keep using my old offset values (0.24 V) for the Vcore i do get 1.3 V on that i7-5930K. Pre 1204/1305 i did get 1.28 V.  Thats an increase of 0.2 V just by updating the BIOS.

 

CPU seems to respond better to what you throw at it

What i did also notice is that the CPU does respond, let’s say, more accurately to the frequencies and voltage you put through. It feels more straight.

In the past i could clock the CPU to 4.6 GHz @ 1.3 V and were able to boot and use Windows. That’s no longer possible. I would have to add quite a lot more voltage ontop of it to get it going at these settings.

What did the board achive so far with 1305?

Currently (02. feb. 2015) i am at

 

CPU freq. RAM freq. Uncore freq. CPU Vcore RAM Vcore Uncore
4350 Mhz 3070 MHz 3584 MHz 1.32 V 1.35 V 1.2 V

 

I just started to play with it and will slightly decrease the Vcore. I am still using offset values. Go Offset!

 

cpu-z_5930k_asus_x99_1305

 

Old sad story – prime95

After all the trouble and questions we had regarding prime95 and Hasswell-E. I decided to run prime95 tests with the Kraken x60 at “silent” and at “custom” mode.  I noticed that Core 0 is behaving quite unimpressed – because the Worker 0 in prime95 stopped stressing the Core for unknown reason. Kraken x60 is a ready-to-use watercooling solution for noobs and lazy people. However as you can see in the bottom box in Kraken Cam, the temperature peaked at almost 90 °C (86 °C) with “silent” configuration.

 

kraken_cam_kraken_x60_asus_x99_1305
BUT: this was NOT a prime95 HEAT test. Keep that in mind. Just ordinary stress test.

 

So i started the prime95 test again due to unknown abstinence of Core 0 and the temperature peaked at 78 – 81  °C.  Fans are NOT at 65%, Kraken CAM is fooling us here.

 

 

LED of your Kraken Heatsink lit up 24/7?

If you want your LED flavoured Kraken/Watercooling Heatsink to not glow when the system is powered off, change the ErP Setting in the BIOS to “S4 + S5”.

I still use Kraken x60 standard Fans. I do want to change those since weeks, or months but never completed this task yet. Maybe you can recommend some.

 

Asus Deluxe BIOS 1004 x99 – Problems solved?

Update 06. November 2014:

One good thing i have to mention is, that i had no problems yet to wake the system from standby-mode nor did i have any problems that occured with BIOS 0904. BUT I went to do the shopping and put my system or tried to put my system into standby-mode, but it never did. This is a strange behaviour.

 

I was talking with a guy “Wei Liu” about these issues and he told me that increasing VTT voltage may help here. He just heard of it or read it somewhere. So i decided to increase voltages. What i didn’t mention yet is, that with BIOS 1004 i tested only with stock-settings the first days. Now when i will run the system oc’ed i’m going to apply the tips. Results coming soon.

 


 

Asus Deluxe BIOS 1004 released in the end of October

I’m currently testing the Asus Deluxe BIOS 1004 they obviously released already in october. I didn’t notice that. However the first 3 tests were successful. Which means the standbymode, that i mentioned in a previous post with BIOS 0904 (and earlier), did work properly with 1004 (… to their Downloadpage)  so far. But the last test is pending. The standby-problem tend to occur, when the system is cold, what indeed is currently not the fact. Even a 10 minuten power-break doesn’t simulate a cold system correctly. I have to wait, then when i wake up the next time to proceed with it.

Asus Deluxe BIOS 1004 - Problems solved?
Asus x99 Deluxe

 

Few words about the previous BIOS 0904

By time passing by, i experienced some other problems with the previous BIOS 0904. Once it happend that the system forgot about the Boot-Settings. Another strange situation came up, when the system started on its own after a clean shutdown.

I will try observ this too for sure on the new BIOS 1004. Or lets say, you can’t ignore these mal-behaviours since your perception can’t elude these.

Nothing solved at this moment. Status is open.

Asus x99 Deluxe standby mode not working properly

Update Jan. 2016
Try disabling these settings:

 

160110191334

 

Update 06.11.2014: When using Corsair Power Supplies:

Go to http://www.corsair.com/en/rm-series-rm1000-80-plus-gold-certified-power-supply and click “Haswell compatibility” under the FAQ & Support Tab.

Quote “According to Intel’s presentation at IDF, the new Haswell processors enter a sleep state called C7 that can drop processor power usage as low as 0.05A. Even if the sleeping CPU is the only load on the +12V rail, most power supplies can handle a load this low. The potential problem comes up when there is still a substantial load on the power supply’s non-primary rails (the +3.3V and +5V). If the load on these non-primary rails are above a certain threshold (which varies by PSU), the +12V can go out of spec (voltages greater than +12.6V). If the +12V is out of spec when the motherboard comes out of the sleep state, the PSU’s protection may prevent the PSU from running and will cause the power supply to “latch off”. This will require the user to cycle the power on their power supply using the power switch on the back of the unit.”

Also check out their forums (http://forum.corsair.com/v3/showthread.php?t=118456). Possible that you need a new PSU but at first you could try to disable C7 state (if possible) in your BIOS settings and see if it helps.

 


 

You may know or not that i bought a new system this year. However the Asus x99 Deluxe standby mode seems to confuse some of the components of this system or its the mainboard itself messing around with it.

 

Infinite loop

When i put my system into standby or suspend mode i can’t really wake it from there. When i try to wake it: the hardware responds, fans are starting to spin, harddrives etc, but the system is not really recovering from the standby mode, instead the system goes to Q-CODE bF and sits there until it starts to reboot automatically. Even a 4-sec-press-hold the power button doesn’t help to cold boot the system. The system sure goes down, but it does keep the system to do the bF loop. It keeps infinite (re)booting.

 

Q-CODE: [bF]

 

The first thing i did was CMOS reset but it is NOT necessary!

Instead: turn off your power supply wait a few seconds and turn it on again. Then the system should boot normally.

I already did play with some BIOS settings and there was something strange happening when i enabled ASPM Support in “Advanced->Onboard Device Config->ASPM Support” ….

 

Asus x99 Deluxe standby mode messed up?
Asus x99 Deluxe standby mode messed up?

When i enabled ASPM Support, i was able to put the system in suspend/standby mode and wake it with either keyboard or power button, right on the first attempt. This made me think i found a solution. It did work 3 times in a row. I then wanted to know if i can reprocude this by undoing the changes to see the bF code again and redoing the changes to see a working standby mode, and failed. Disabling and reenabling ASPM Support didn’t come up with a working suspend/standby mode.

 

 Asus Technical Support

I already wrote to Asus Technical Support and the first “conclusion” was, that i may have defect hardware with the aim at power supply.

 

Do you have same or similar problems? Different Q-CODE? Let me know!!

 

Update: Well sometimes its working and sometimes not. And when i try to record it with a camera, take a guess, its working…. to be continued

 

Asus x99 Deluxe, i7-5930K overclock – don’t use prime95 on Haswell-E and 2011-v3

Update: 12. March 2015

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.

 

So this is going to be a big round-up confusing

The truth is, that i stumbled over a forum thread, while i was searching for wprime95, saying that prime95 doesn’t go well with Haswell-E. So, while it’s still saturday night/sunday in the very morning and i was about to leave the system for today as it is, i decided to repeat some steps on the Asus x99 Deluxe, i did in the past weeks. In the beginning of the OC-adventure, i started with prime95 only and later took SiSoftware Sandra into the boat.

 

Quick Overview of the System (or have a quick look at previous posts):

  • Asus X99 Deluxe (white/black) Motherboard
  • Intel i7-5930K  at 3.5 GHz (will use MX-4 paste)
  • Corsair Vengeance LPX DDR4, 16 GB, 2800MHz  4-Modules-Memory-Kit
  • Corsair RM1000 Power Supply
  • Kraken X60 Watercooling
  • 4x Corsair 140mm Fans (purple/violet)
  • Corsair Obsidian 450D Case

 

 

Replacing prime95

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.

Quick overview:

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) 100 (BIOS 0505 – 0701)
4,2 @ 1,25 V (BIOS 0701 + BIOS 0801) 2800 @ 1.2 V (BIOS 0701 + 0801) 127,5 (BIOS 0801)
4,25 @ 1,25 V (BIOS 0801) 3000 @ 1.35 V (BIOS 0801) 125 (BIOS 0801)
4,375 @ 1,265 V (BIOS 0801) 3000 @ 1.35 V (BIOS 0801) + (BIOS 0904) 125 (BIOS 0801)
4,427 @ 1,31 V (BIOS 0904) 3034 @ 1.35 V / 3416 MHz Cache (BIOS 0904) 126,5 (BIOS 0904)
4,462 @ 1,276 V (BIOS 0904) 3000 @ 1.35 V (BIOS 0904) 127,5 (BIOS 0904)
4,5 @ 1,276 V (BIOS 0904) 3088 @ 1.35 V (BIOS 0904) 128,7 (BIOS 0904)
4,5 @ 1,35 V OCCT stable 128,7 (BIOS 0904)
4,5 @ 1,37 – 1,39 V prime95 stable, requires extreme² cooling 128,7 (BIOS 0904)

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.

 

Intel i7-5930K now finally at 4.5 GHz with peacful 1.27 V vcore
Intel i7-5930K now finally at 4.5 GHz with peacful 1.27 V Vcore

 

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 Cache Baseclock
4.5 GHz 3088 MHz 3860 MHz 128.7 MHz
1.276 V 1.35 V 1.2 V
1.29 V
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.

 

 

Corsairs LPX Vengeance DDR4 2800 MHz Memory Kit at 3088 MHz and a cache speed at 3861 MHz
Corsairs LPX Vengeance DDR4 2800 MHz Memory Kit at 3088 MHz and a cache speed at 3861 MHz

 

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.

 

Aida64 Benchmark

The Aida64 Report has been uploaded to let you guys and girls see some graphs. If that’s not enough, i would like you to visit the SiSoftware Sandra Result / Ranking Page. No graphs but benchmaaaarks. SiSoftware Link 2

 

Cinebench Results

 

cinebench3 cinebench2

 

Temperature peak during tests 69 °C

the temperatures are very good in my opinion and the Kraken fans aren’t even close to the speed they were running when i used prime95 in previous overclocking attempts and tests.

 

Temperature results after Cinebench and Aida64 test runs
Temperature results after Cinebench and Aida64 test runs

 

 

Since all changes i made in the BIOS during the overclocking-journey are no longer necessary, it remains pretty much basic. Just for you, the…

Asus x99 Deluxe BIOS settings, i currently, 28. September 2014, run my system with.

.. meanwhile will run another SiSoftware Sandra Overall Bench.

 

Asus x99 BIOS - Startscreen
Asus x99 BIOS – Startscreen

 

Asus x99 BIOS - Main Page
Asus x99 BIOS – Main Page

 

Asus x99 BIOS - AI Tweak Pages
Asus x99 BIOS – AI Tweak Pages – The Voltage update (1.29) doesn’t show up here.

 

Asus x99 BIOS - DIGI Pages
Asus x99 BIOS – DIGI Pages

 

Asus x99 - Internal CPU Power Management Page
Asus x99 BIOS – Internal CPU Power Management Page

 

Asus x99 BIOS - CPU Power Management Configuration
Asus x99 BIOS – CPU Power Management Configuration

 

 

 

Asus x99 BIOS update – 0904 released with updated microcode!

Asus just released the next BIOS version 0904! I’m currently at work right now and can’t do anything but i will definetly get into this soon. One thing you might want to point out is the updated microcode. Can’t wait, can’t wait…

If you didn’t read previous posts, get the hardware list here.

 

Screen of  Asus Support Website

Asus x99 BIOS Update
Screenshot: Asus x99 BIOS Update

 

 

Can’t wait to download, test, love, hate and condemn this 🙂 If you already could gather some experience, let me know in the comments! I can’t wait to see benchmark results after this update.

 

Time has come – Asus x99 BIOS Update

 

Intel Storage Repair after BIOS Update/FLash
Intel Storage Repair after BIOS Update/FLash
Update 27. September 2014 ,07:32 CEST:

Here we are, the new BIOS installed makes Intel Storage want to repair my raid1 on two Seagate Disks. However, that only means that the testing starts a bit later in the day.The reason for the obviously desynced disks remains unknown. Possible that after loading the new BIOS and first boot attempt one of the disks got touched by the system in non-raid mode.

 

Asus x99 Deluxe new  BIOS 0904
Asus x99 Deluxe new BIOS 0904

 

 

 

 

 

 

 

 

 

Update 27/28. September 2014, 1:15 CEST:

Phew, this was a very unpleasent day. The new BIOS is running fine but i didn’t get a lot more out of it than before. As i mentiond already in another post i could achieve 4.5 GHz with the i7-5930K at BIOS version 0801, but its almost impossible to run it stable and cool at the same time. At least when it comes to prime95. If i don’t care about prime95 i could easily run the CPU at 4.6 GHz. However, currently i’m at

(If you didn’t read previous posts, get the hardware list here.)

Baseclock: 126.5 MHz

CPU clock: 4.427 GHz (Ratio 35), Vcore 1.31, Sys Agent V 1.2, CPU Input V 1.92, Cache V 1.2

Memory: 3034 MHz, DRAM V 1.35

NB:  3416 MHz

 

And even at these speeds i’m getting 0x00000101 or 0x00000124 bluescreens when running prime95 tests but it takes longer to make it happen and the temperatures are not peaking at 90 °C instantly, like they would at 4.5 GHz and 1.38 Vcore. It doesn’t feel anymore like the Vcore is the issue. I think i have to pay more attention to the other voltages. I already started to change some values and even the cache frequency. I also disabled some voltage features, which may drop voltages down when you actually are increasing them.

The most stable combination still is 4.375 GHz, 1.27/1.28 Vcore at 125 MHz Baseclock.

Today i also started to use Asus AISuite to get my first experience with it.

For now thats pretty much it. I will add some more comments and pictures tomorrow/later. I will upload some screens of the BIOS settings. Now i will play a game and chillout.

 

 

bahuett

 

at current settings (see above) during prime95 test
at current settings (see above) during prime95 test

 

In HW Monitor the VCORE equals the CPU Input Voltage. When i say Vcore in my post i refer to CPU core voltage or Vcore and since i installed Intel Management software HW Monitor shows less information and the power consumption is totally wrong.