ASUS Z87 Motherboards - Overview, Guides and Official Support

Whoa, whoa... Why wasn't I aware of the LiveKernelReports folder inside the Windows folder???

It seems to store dumps even when there's no BSOD!!! I have 15 of them and of the 3 I analyzed...

FAULTING_IP:
atikmpag+ae80
fffff880`04481e80 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_ENGINE_TIMEOUT

BUGCHECK_STR: 0x141

...

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5253fa42

FAILURE_BUCKET_ID: X64_0x141_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x141_IMAGE_atikmpag.sys


You've got to be kidding me. Like, seriously. The graphics card kernel driver?

Now check this out: there are exactly four (4) entries for "GRAPHICS_DRIVER_ENGINE_TIMEOUT" on Google. Three of those are for Nvidia. And no solutions. Edit: ah, well, that's probably because of the analyzer I'm using, linked below. Have to google more.

For now, I have disabled the AMD External Events Utility service. This says to get rid of Catalyst Control Center and only leave the drivers. CCC is running on .Net, and I haven't installed any updates. Be as it may, both things are gone.

Oh boy.

Warl0rd - go check your LiveKernelReports folder and upload it here.

So basically after I have fixed this, I'm left with the hard drives spinning down, spinning up and spinning down on shutdown. That, and undoing all the stuff I've done in the past two weeks trying to find what's causing the freezing :)
 
Last edited:
With your HDDs spinning up and down during shut-down, that's because of the RST driver (not the GUI). If you're using version 12.0.x you're fine, I bet you won't see that behaviour anymore but that's over 11 months old now so who'd use that. Anything newer, for example 12.5 onwards will have this behaviour.

Another solution is to move your HDDs to the Asmedia ports, I didn't install any SW for the controller and now when I shutdown they don't spin-up anymore during that said shut-down process.

The third solution is; remove hibernation file as mentioned before. If you have no use for it, remove it.
 
Matija said:
And I had another freeze a few minutes ago :) Left the computer idling for about 45 minutes, came back, frozen as usual. Replugged the KB and mouse and like you said, no power is being delivered. But I guess that's normal - I mean, the system is frozen solid and the USB controller misbehaves.

The good news seems to be that I proooobably don't get freezing while I'm doing stuff on the PC, like typing or moving the mouse (which happened before, when I had AI Suite installed). The bad news is that I still get freezing when the computer goes idle for a while. I'm tempted to run something that loads the cores, then go away for an hour or two and see what happens.

Either something goes to sleep and can't wake up, or a voltage for something drops below the stability treshold.

The experiments continue... Tomorrow is BIOS tweaking time.
Click to expand...

My computer has problem waking up from sleep. Maybe something related?
 
What happens, it won't wake via keyboard/mouse or it won't wake up even via power button? Do you see any errors/problems in eventlog (kernel-power related more than likely).
 
error-id10t said:
Another solution is to move your HDDs to the Asmedia ports, I didn't install any SW for the controller and now when I shutdown they don't spin-up anymore during that said shut-down process.
Click to expand...
Can't. I have a RAID-1 array and the system drive is an SSD. For both those reasons, I'm wary of downgrading RST to such an old version.


error-id10t said:
The third solution is; remove hibernation file as mentioned before. If you have no use for it, remove it.
Click to expand...
I did. Hibernation, hybrid boot, all that stuff is removed.

If you're certain it's a RST issue, and not something related to motherboard power settings, I'll go write Intel.
 
To confirm either way, you can change the RST driver and GUI.

https://downloadcenter.intel.com/Se...="Intel+Rapid+Storage+Technology+(Intel+RST)"

I went through all of these yesterday and it did not brake my RAID0 which is my OS drive. Now, I cannot guarantee the same for you but I can't see a reason it'd brake it (you've updated it here and there right?) - if you download version 12.0.0.x you shouldn't experience this problem.

Version 12.5+ you will.

If you see something else, it's not RST.

Also, just to confirm when you say hibernation is off, you did: powercfg /hibernation off
 
Well, on XP I didn't even have RST. It was called differently. So I haven't had 12.x at all - and this is a new OS, new chipset, new SSD, lots of new stuff. Maybe I'll try it, but I should first whip out my external and do a full backup.

Yeah, I did the powercfg (and dumppo) stuff.
 
Matija said:
Warl0rd - go check your LiveKernelReports folder and upload it here.
Click to expand...
Done, I get:

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.

STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+153034
fffff880`03fa1034 ?? ???
SYMBOL_NAME: nvlddmkm+153034
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52676afe
FAILURE_BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys
Followup: MachineOwner


But I was already thinking about vga, since last time fans went 100%. Also remember I told you last week to try unplugin the external vga card :)

I'm running latest nvidia stable drivers.
btw, I was actually planning on replacing the vga card, this time for an AMD. But if you crash on AMD as well :(
 
You're on Windows 7, right? 0x117 in 7 is the same thing as 0x141 on 8. Here's Microsoft's tech paper about TDR. Maybe something will help you... I have tweaked some BIOS stuff for PCI Express regarding power management and disabled ultra-low power state (now ZeroCore) for my card - it survived 75 minutes of idling, so maybe it's fine (but maybe it's not). Check if Nvidia has something similar about "long idle" and try to disable it.

I wrote Intel about my possible RST issue. Wonder what they'll say...
 
error-id10t said:
What happens, it won't wake via keyboard/mouse or it won't wake up even via power button? Do you see any errors/problems in eventlog (kernel-power related more than likely).
Click to expand...

Tried to recreate the problem. It seems that the bios upgrade solved it. I can now go to sleep or hibernate without problem.
 
Matija said:
You're on Windows 7, right? 0x117 in 7 is the same thing as 0x141 on 8. Here's Microsoft's tech paper about TDR. Maybe something will help you... I have tweaked some BIOS stuff for PCI Express regarding power management and disabled ultra-low power state (now ZeroCore) for my card - it survived 75 minutes of idling, so maybe it's fine (but maybe it's not). Check if Nvidia has something similar about "long idle" and try to disable it.

I wrote Intel about my possible RST issue. Wonder what they'll say...
Click to expand...
I'm on W8 64b

But I just bought an Asus 280X, so now both vga and mobo are from the same brand, no excuses not to work properly :p

I did NOT install CCC, just the drivers, let see how it goes.
 
dahlberg said:
Tried to recreate the problem. It seems that the bios upgrade solved it. I can now go to sleep or hibernate without problem.
Click to expand...

Good to hear.

I'm having some good results here myself at the moment. Since I moved the 2 HDDs to the Asmedia ports without installing SW for them, I can now shutdown the computer without the HDDs spinning-up + Fast Boot actually works. It's now been 3 days and it still works so I'm getting confident the hiccups are solved.
 
I decided to try and get all of the bios disk and boot accelerated features working with win 8.1. Everything was great. Had IRST running, fast boot, hardware fastboot, dynamic accelerator all running and boots were faster than I expected. Was no longer seeing the welcome screen w my picture after the win8 splash with the spinning balls. Just straight to desktop. Mostly I guess better boots because installed using uefi method (made a usb installer for my win 8.1 disk) and then can disable CSM completely for secure boot.

Then I got it in mind to figure out why Rapid Start never installs. Wish i hadn't. You have to make a partition the size of your system RAM and then use diskpart to change the partition's type to hibernate reserve. The code to change the ID isn't simple like in win 7 (was 84:rolleyes:) now it's a string that looks like a registry key entry. Once that's done you can install rapid start in win 8.1.

My boots now seem slower. It's working as intended according to the rapid Start application. IRST is working perfect too. System is zippy but I think I'll skip rapid start next time unless someone can tell me if I'm doing something wrong still.
 
Kor said:
Not for that drive, I stopped hooking up the Corsair drive through it after the grief it caused when the board was released. All the tests I performed tonight where done with the drive fully isolated on plug 1 for the Intel controller, nothing else was attached.
Click to expand...

Kor, we suspect this is a COrsair FW issue. You might want to drop them a line and notify them. I had someone test a SF22** drive by another vendor and it has no issue - he suggested FW level problem is a possibility. POssible that the new ME changes timing tolerance on SATA, hence your issues.

-Raja
 
Last edited:
Raja@ASUS said:
Kor, we suspect this is a COrsair FW issue. You might want to drop them a line and notify them. I had someone test a SF22** drive by another vendor and it has no issue - he suggested FW level problem is a possibility. POssible that the new ME changes timing tolerance on SATA, hence your issues.

-Raja
Click to expand...

Thanks Raja, I've raised a support ticket with Corsair outlining the issue.
 
Hmm now that I have a proper hibernation partition and Intel rapid storage + rapid start correctly configured ai suite away mode does something cool I couldn't make work b4. Away mode makes hybrid sleep work with the fans and pciE lighting/cooling still running. This is neat because it will sleep at night and the LED breathing pattern from Nvidia experience still works. Since the fans spin slowly according to preset, any fanLEDs glow dimly. In my case (red lighting) this ends up creating a nice subtle lighting effect in the corner with a barely noticeable green pulse. Score one for ai suite.
 
dahlberg said:
Alright, so I think the problem is solved!

As suggested I removed all but one dimm. Then flashed from 1405 to 1602. After that I changed timings from auto to XMP. Also changed SATA from AHCI to RAID (obviously). Left the rest as is from flash defaults. Computer starts like a charm!

Now, re-installed rest of dimms. Computer still starts like a charm!

Concluded that XMP setting solved the issue and went about changing the rest of my bios settings (except that I keep XMP) back to what it was. Did these settings:

VRM Spread Spectrum [Disabled]->[Enabled]
Boot performance mode [Max Non-Turbo Performance]->[Turbo Performance]
Dynamic Storage Accelerator [Disabled]->[Enabled]
ASPM Support [Disabled]->[Auto]
ASPM Support [Disabled]->[Auto]
PEG - ASPM [Disabled]->[Auto]
PCI Express Native Power Management [Disabled]->[Enabled]
Native ASPM [Disabled]->[Enabled]
Thunderbolt Controller [Enabled]->[Disabled]
Thunderbolt bandwidth [X4 mode]->[X2 mode]
Bluetooth Controller [Enabled]->[Disabled]
Wi-Fi Controller [Enabled]->[Disabled]
USB Support [Partial Initialization]->[Full Initialization]
POST Report [5 sec]->[3 sec]

Problem is back! Computer freezes at "Starting windows" right at GUI start.

So I am changing back the bios settings one by one. It turns out that the computer will not start with Thunderbolt Controller disabled with bios 1602.

Rechecked and confirmed this. My setup and config will not start with Thunderbolt Controller disabled.

Thanks for the suggestions and help! It set me on the right path!
Click to expand...

@Raja - Just curious, are other people able to boot with Thunderbolt controller disabled?
 
I do not know off the top of my head...

Will ask HQ to replicate if possible and get back to you.
 
Last edited:
Dahlberg - TB disable issue replicated by HQ. It'll prolly be patched in a future UEFI update.
 
@Raja, I assume since you did not say anything about the memory I used with Formula VI, Vegeance Pro 1866mhz and Vegeance non pro 1600mhz that the memory would not be an issue correct? I got an RMA for the board and it arrived back to the vender today so I'm wating to hear back now.
 
101010 said:
@Raja, I assume since you did not say anything about the memory I used with Formula VI, Vegeance Pro 1866mhz and Vegeance non pro 1600mhz that the memory would not be an issue correct? I got an RMA for the board and it arrived back to the vender today so I'm wating to hear back now.
Click to expand...

Are you using two kits together? If so that is a recipe for issues..
 
Kor said:
Thanks Raja, I've raised a support ticket with Corsair outlining the issue.
Click to expand...

Out of interest, can you tell me if the system was running at bone stock settings, or was it overclocked in any way on 1504 upwards? Overclocking includes memory running over DDR3-1600. A longshot is that the system is so unstable it cannot BOOT the drive (can happen with memory instability as well in some cases..). HQ are going to try and replicate so I need all the info you can give in a single post I can link them to. Be as complete as you can please and include everything you are changing in UEFI.
 
Raja@ASUS said:
Are you using two kits together? If so that is a recipe for issues..
Click to expand...

Not at all using them together. My concern was the Vengeance pro is not on the compatibility list and tge regular Vengeance is but not th 1600mhz but I doubt that would make a differnce since other types of Vengeance RAM is.
 
Issue regarding Gryphon Mobo. Currrently running to boot issue with windows 7 pro:

- booting would freeze at "starting windows" screen as random occurance (I have good boot 6 times straight and thought issue was gone only to happen again)
- ran the startup repair and it said that it was a driver issue it couldn't fix
- started in safemode and no issue
- checked the device manger and noticed a driver called AMDA00 got a error symbol.

I have looked into into and this seems to be used by the AI Suite? But nothing I do including uninstalling and disabeling it seems to solve the problem. Is there a seperate driver update just for this driver I can use? The mobo dvd doesn't do anything and upon seing a clean install guide on the form for a z87 board it recomended not to use the dvd.

Pleas pm if needed to keep clutter down

Thanks
 
The AMDA00 driver is usually downloaded as part of Windows Update for AI suite.

Could be a a number of things causing the non-BOOT to OS.

1) If it is driver related, then maybe install a test version of Windows on a spare HDD and see if you can nail it down.

2) BOOT issues can also occur due to instability - memory or CPU. In such cases, pegging back an OC, or checking memory for instability is a good idea. Note that on these platforms anything over DDR3-1600 is also defined as overclocked, even if the CPU is at stock.


-Raja
 
Last edited:
This would be a brand new system and new install. And no OC at all, even memory is at 1333mhz.
When you said its from windows updat... would it bee a issue if I didn't install AI Suite at all during the update?
 
Houten said:
When you said its from windows updat... would it bee a issue if I didn't install AI Suite at all during the update?
Click to expand...

Not that I know of.


A system can be unstable at stock if there is a an issue with parts or compatibility, too.
 
Howdy:

Got my brand new Max VI Formula up and running.
All stock for now.
Have enabled HD sound in the BIOS as well as S/PDIF enabled in the BIOIS.

Plugged my TosLink in to my Yamaha receiver (this was previously fine using S/PDIF off a X-Fi Titanium sound card). There is light in the port of the MB.

Drivers are the latest off the ASUS website from RealTek.

No sound.

Sound in the Windows control panel is enabled to RealTek digital-optical.

WTF.
 
magoo said:
Howdy:

Got my brand new Max VI Formula up and running.
All stock for now.
Have enabled HD sound in the BIOS as well as S/PDIF enabled in the BIOIS.

Plugged my TosLink in to my Yamaha receiver (this was previously fine using S/PDIF off a X-Fi Titanium sound card). There is light in the port of the MB.

Drivers are the latest off the ASUS website from RealTek.

No sound.

Sound in the Windows control panel is enabled to RealTek digital-optical.

WTF.
Click to expand...

Not heard of this issue before. What does Windows control panel show as the default audio device? Edit just saw the last sentence. No idea then. If the sound bar in control panel shows sound playing, then there is an issue between the mobo and receiever somehow. If the sound bar does not move, then mobo side/driver problem.
 
@Raja, the question was that I used Vengeance Pro1866mhz ram with a Maximus formula VI mobo and the mobo did not post, I then used standard Vengeance 1600mhz ram seperately and the board still did not post and was wondering if my choice of the two RAM types was the reason? Because both were not on the approved list of tested memory. I doubt that the RAM was the issue becuase the biggest differences was the timing, considering that other types of Vengeance RAM is compatible but wanted to get your feedback.
 
Even if the kit was not compatible the board would have POSTed with a single module in most cases.
 
101010 said:
@Raja, the question was that I used Vengeance Pro1866mhz ram with a Maximus formula VI mobo and the mobo did not post, I then used standard Vengeance 1600mhz ram seperately and the board still did not post and was wondering if my choice of the two RAM types was the reason? Because both were not on the approved list of tested memory. I doubt that the RAM was the issue becuase the biggest differences was the timing, considering that other types of Vengeance RAM is compatible but wanted to get your feedback.
Click to expand...

Heya, I remembered your earlier posts, curious about how the replacement board goes. I thought maybe I shouldn't have said bad board so quick but I guess as long as you tried one dimm by itself and still no go that's a pretty safe call.
 
The replacment board was shipped today, so I should have in a few days. I'll post back and let every one know how it goes.

@Raja, thanks for thr reply, I figured as much RE: the board posting but just wanted to verify.
 
I use Vengence 1866, 4x4 in my M VI Formula and it works just fine. Has from day one.
And Raja....the sound bar moves just fine when I ask for a test. Something is FUBARd.
 
I just built a computer with h100i (z87-a MOBO with 4770k). When I booted for the first time, I got a CPU fan error message (boot device led was turned on in red). I rebooted and the light disappeared. I didn't make any changes to the system so why does it "reset" itself after restart? Is there a way for me to go back and check what that light was about?
 
Have a weird problem, started today.

Twice now my computer has shut-down and upon reboot and I'm greeted with ASUS anti-surge protection message saying it detected problem in the last power-on with regards to the PSU. But this is long time since the last power-on.

What is the anti-surge measuring.. current problems meaning the text isn't really accurate or is it really only now telling me about a problem it believes it picked up ages ago?
 
magoo said:
And Raja....the sound bar moves just fine when I ask for a test. Something is FUBARd.
Click to expand...

No other reports of this from anyone but will report to HQ. Just be sure to check as much on your side as you can as I don't want to send HQ on a goose chase.
 
You must log in or register to reply here.
Back
Top