Update 12. Dec. 2014:
3 weeks later and still waiting for my mainboard. This really is “a bad situation”. It’s not like we still were back in th 80s or 90s where shipping takes weeks. I wonder what they are doing there. I’m disappointed. Just imagine they had 1 week to receive the mainboard one week to work on it and another to send the mainboard back to me. What the heck is Asus thinking? This was my last Asus product for sure.
Today it happend. I finally brought the Asus x99 Deluxe in to my local hardware dealer to send the board back to Asus. To be honest, i hoped my dealer will keep my old board and let me chose a new one. I will now summarize some problems i was facing. Things became worse during time.
Mystic behaviour: Power on!
Right in the first month it happended once, that i woke up, went into my living room and my computer was powered on. It should be powered off. Hey i’m a computer junky and strange things happen frequently, especially to my mind. Sometimes i even doubt my memories because of that littl sleep i often get. When i saw my computer powered on, i couldn’t believe it and almost instantly rejected the things going on in my head and said to myself “Oh i forgot to power it off….”. So this was the first time.
It happend again yesterday, but i was absent.
The standby problem
I already talked about it. The system was sometimes hard to wake from standby mode. It was possible to put the system into standby but not to wake it, most times. And now a few days ago it also was hard to put it into standby mode. So things are getting worse.
What you like for dinner?
My BIOS decided to forget about its boot-settings. This happend only once in 2.5 months.
System hang during boot
i had my first system hang few days ago during boot. Windows 7 was about to animate its logo / load its bootscreen and the Windows Symbol was about to load but stopped.
US what? USB?
I was able to wake my system from standby the next day but it seemed that the USB devices got power but are not recognized. Keyboard and mouse dead. Nothing. Asus x99 Deluxe was like “OK, that’s it, i’ma shut down” and the system shut down. No reboot. Silence.
Sad but necesary
And then, when things like this happen to you frequently and when you read about Asus x99 Deluxe boards, which burn through your CPU and everything else or turn into “fire” (some people reported a little blue blaze/flame when a component on the board died), then you reached that moment to bring the board back to where it came from. I RMA’d it today.
Its a sad story because this board did perform very well in any benchmark tests, especially in those bigger tests performed by other, bigger tech-sites, but i fear that the problems will never disappear or get solved by asus. I fear that they simply replace the board and that i get a new monster. New but fraught with the same problems. Hope is all you can have at this point.
Stock or Overclocked?
Some of the mentioned problems occured with a OC’ed system, some other occured with a stock system. I didn’t try to reproduce every behaviour under different circumstances but i can tell you that i played a lot with the mainboard and its settings. Starting with slight changes and getting as deep and detailed as possible. I did touch almost all voltage settings you can alter in the BIOS. One thing i didn’t do was playing with memory-timings. It will take weeks to go through all settings and find the “evil” ones causing the system to drive you nuts. Every change follows a test, which in most cases is nothing else than using your computer like you do on daily basis. Only performance tests can be performed intantly in short time. However, the story continues as soon as i get my MOBO back.
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.
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.
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” ….
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
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.