Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I personally checked Deluxe/PRO/HERO/EXTREME/FORMULA/Z87-PLUSM6H I have it turned off I don't get cold boots unless complete disconnected power to the mobo.
Raja@ASUS
All motherboards Asus z87 has a bug, if turn off the onboard controller ASMedia Sata is presented double cold boot.
Passed more than half a year, when the problem will be fixed!!!??? why such a lousy service
I personally checked Deluxe/PRO/HERO/EXTREME/FORMULA/Z87-PLUS
We all have this problem, so I do not believe that you do not have this problem.
Authorized service center concluded that the problem occurs in all versions of the BIOS.
If turn off Realtek LAN also be a cold start double....
Problem affects only motherboards Asus.
Yeah it's understandable. Hardware fast boot doesn't work with win 7 so that's possibly part of it. I'll test on win 8.1 later.
Ok with you seeing different results, I kept playing around and found the reason (I believe on my board at least): drivers.
ASUS doesn't provide Asmedia SATA drivers for Win8.1 for my board (they do however for Win8). I also don't use Asmedia ports so have always disabled it and never cared about it's drivers of course.
So I installed the 1.16.x whatever driver, rebooted to make sure it now sees it as such. Once confirmed, rebooted again and turned off Asmedia in BIOS and guess what, no double-boots anymore once I go beyond 10 seconds.
Thanks to these last few posts I've been able to fix half of my problem (granted, the more annoying part) but the mystery why Fast-Boot disappears after 10 seconds remains.
After uninstalling AI Suite, I haven't had a single freeze yet. Computer ran fine for about 13 hours yesterday. Was that really it...?
Edit: I'm still annoyed by my hard drives spinning up after shutdown. Anyone has an idea how to fix that? It's like this: shutdown - drives spin down - monitor and fans turn off - drives spin up - drives spin down.
Raja@ASUS
All motherboards Asus z87 has a bug, if turn off the onboard controller ASMedia Sata is presented double cold boot.
Passed more than half a year, when the problem will be fixed!!!??? why such a lousy service
The Corsair Force GT is not SF1200 based, it's a SF2200 controller. As the drive is hooked up directly to the first SATA port on the board using the Asus provided SATA leads and only thing only variable was the UEFI version for the Z87 Deluxe (1405 to 1502) I'd say it's pretty clear that it's a firmware issue as rolling back immediately resolves the problem. The system was not over clocked during the update or during testing (only a crazy person would try to troubleshoot like that). The drive is running the most recently available firmware (5.05a).
There should be a setting in BIOS for Fast Boot after Power Cycle. Something like that. Is that ON?
Is ErP ON?
One of those two changes if available should fix that issue. You can have ErP on if you have a PSU that is cert. for ErP6 iirc. If you have ErP ON you must turn Fast Boot after Power Cycle to ON as well. Then you will need to use Asus's software to get into BIOS or reset BIOS manually on the board.
Thought that disabling hybrid shutdown would make it go away, but it didn't.
I dont't care about double BOOT, I think people worry about this too much - and I've never seen anything die as a result of it, so not going to engage with these things and waste time.. You'll need to take this up with your local service. I don't see it as a bug at all, sorry.
Okay so you have an issue with the Corsair SF2200 (GT) SSD. I guess the 840 Pro was not an issue at all correct (seeing as you removed the info about that drive from the quote of my post)? You'd be surprised how many crazy people are out there, so I have to ask some of these bizarre questions.
Have you tried enabling the "Hot plug" setting in in UEFI on the port the SF2200 controller drive is attached to? That should cure any issue with this controller on the latest firmware going by what I heard from OCZ recently (they have drives with this controller too and apparently the latest FW will do this if the hot plug setting is not enabled).
I will ask HQ about the SF2200 also. You will need to supply a screenshot of UEFI this time (as the 840 Pro was a wild goose chase) - HQ wont look into it unless there is some form of effort on the end-user's part to be accurate.
-Raja
I still have a problem with the 840 pro, however I suspect that is related to this boards somewhat temperamental behaviour with solid state drives being plugged into the Corsair 800D's hot swap bays (seems to change it's mind on what works and what doesn't between firmware revisions). I just wanted to correct the mistake with regards to what flavour of sata controller the Force GT comes with.
.
Clear, as mentioned earlier, terrible service! for me and for many it is a critical bug...
Asus probably made ​​a mistake in the PCB layout that's BIOS not correct the problem.
I have no other explanation.
I throw Asus Hero, and go to buy ASRock Fatal1ty Z87 Killer! she had no such problems and support staff work very quickly! write to technical support is possible directly from the BIOS! solve the problem for a week and then send the beta BIOS for testing! That's what I understand service!
Good luck, I'm sorry for Asus
Edit: I'm still annoyed by my hard drives spinning up after shutdown. Anyone has an idea how to fix that? It's like this: shutdown - drives spin down - monitor and fans turn off - drives spin up - drives spin down.
Seems to be a bit of misadventure here concerning fast boot. Q-Code 40 indicates the system is resuming from the S4 power state not fast boot. Pre-Win8 the S4 state is what has previously been referred to as hibernation. If using Win8/8.1 with default settings the S4 state is a hybrid form of hibernation. The current state of the kernel is saved to the hard drive, all other user sessions are dumped and all components are put in the D3 state. If upon resuming the system does not boot from the S4 state there is a system configuration error, power has been removed from the system or not all components properly support the D3 state.When I look at the codes I can see it going to 04 mode when I turn the computer off. I start it within 10 seconds, it'll show 40 (fast-boot). I start it over 10 seconds, it'll show A0 (normal boot).
This is not correct. ASRock ultra-fast is equivalent to the ASUS hardware fast boot. To use either requires that all devices initialized during POST are UEFI compatible. Also, as noted above if there is no hibernation file fast boot cannot be implemented. At this point I would suggest reviewing Microsoft and Intel docs related to the S and D states to understand how mucking about with settings can affect the behavior of these states and the requirements of the used components needed to use these states.Fast Startup isn't related/option which disables access to BIOS (ie: Asrock ultra-fast or whatever which disables mouse/keyboard during POST).
Disable hibernation file and issue solved (that's if you have no use for it).
Seems to be a bit of misadventure here concerning fast boot. Q-Code 40 indicates the system is resuming from the S4 power state not fast boot. Pre-Win8 the S4 state is what has previously been referred to as hibernation. If using Win8/8.1 with default settings the S4 state is a hybrid form of hibernation. The current state of the kernel is saved to the hard drive, all other user sessions are dumped and all components are put in the D3 state. If upon resuming the system does not boot from the S4 state there is a system configuration error, power has been removed from the system or not all components properly support the D3 state.
This is not correct. ASRock ultra-fast is equivalent to the ASUS hardware fast boot. To use either requires that all devices initialized during POST are UEFI compatible. Also, as noted above if there is no hibernation file fast boot cannot be implemented. At this point I would suggest reviewing Microsoft and Intel docs related to the S and D states to understand how mucking about with settings can affect the behavior of these states and the requirements of the used components needed to use these states.
Seems to be a bit of misadventure here concerning fast boot. Q-Code 40 indicates the system is resuming from the S4 power state not fast boot. Pre-Win8 the S4 state is what has previously been referred to as hibernation. If using Win8/8.1 with default settings the S4 state is a hybrid form of hibernation. The current state of the kernel is saved to the hard drive, all other user sessions are dumped and all components are put in the D3 state. If upon resuming the system does not boot from the S4 state there is a system configuration error, power has been removed from the system or not all components properly support the D3 state.
This is not correct. ASRock ultra-fast is equivalent to the ASUS hardware fast boot. To use either requires that all devices initialized during POST are UEFI compatible. Also, as noted above if there is no hibernation file fast boot cannot be implemented. At this point I would suggest reviewing Microsoft and Intel docs related to the S and D states to understand how mucking about with settings can affect the behavior of these states and the requirements of the used components needed to use these states.
- Disable HW Fast Boot and even in EFI / CSM disabled mode and in RAID0 SSD you're stuck with a very, very long POST screen. It does not affect/change BOOT at all.
- Enable HW Fast Boot and suddenly your POST is very fast, yet you can still access BIOS no problems, again enabling it has no impact on your BOOT at all.
HW Fast Boot works beyond 10 seconds, it's a separate functionality from Fast Boot. My system is listed below with everything up-to-date. ErP in BIOS is disabled and the computer is plugged into a wall socket (not a power-saving add-on etc).
There is now a Z87-EXPERT BIOS 1602 out. Anyone tried that with the 840 pro? Specifically two or more 840 pro in raid?
Why do you think there would be an issue with the 840 pro?
Maybe SLI breaks D3 somehow. In the APM section of the motherboard's UEFI set the PCIe entry to enabled. This will keep minimal power to the PCIe slots when in the S4 state if Win8 does not override it.However, after a reboot Windows installed Nvidia drivers for me (full set of 331.65 for those playing at home). Anyhow, with them installed I went ahead and enabled SLI - tried Fast Boot: gone, no worky, back to square one. Disabled SLI (didn't touch drivers) and tried again - back to working.
This is normally the AMDA000 driver being install during Win8/8.1 updates. This is a low level interface driver for ASUS software such as AI Suite and ASUS Boot Setting.Raja, what installs all this ASUS stuff onto my computer?
http://i.imgur.com/CXXIFDx.png
I did not install any ASUS software myself. There was also a service called ASUS COM or something which I had to remove using AI SUITE III uninstaller. Why are these getting installed?
Link me to the earlier post and provide as much detail as you can about the problem in a single post that I can link HQ to please. If you are using any drive bay or interconnect other than a SATA cable to connect the drives tell me about that as well.
EDIT: 1504 is an ME update, so it's possible that breaks RAID config on older ME version. If that's the case, you're going to to make a new array on the ME.