Anyone with Asus Z170-P or Z170-K Windows 7?

Soldato
Joined
20 Oct 2002
Posts
11,999
Location
Derby
Hi All, Does anyone else have this combo?

I have installed this system and as the USB does not fall back to legacy for Windows 7 Installation the drivers supplied with the motherboard have to be slipstreamed into the installation for the Keyboard/Mouse and the Autounattend.xml file to work. Not an issue, I have done that and it works. The problem that I seem to have is that upon every reboot I am getting an error in the Event Log.

Event 56, Application Popup

Driver ACPI returned Invalid ID for a child device (5)

Unfortunately google doesn't come up with anything significant. I have the guys at asus on the case. I am pretty certain that its either the Intel or the ASMEDIA USB3 driver that is causing the fault but they have to be installed to be able to setup windows. Its a good job my hair is short already! :(
 
Last edited:
Hi ZXSpectrum

Misery loves company!
Yes, I have a similar combo and the error. I'm also looking for a solution, but like you so far haven't found anything much.
I tried my clean install from a flash drive but omitted to add the USB drivers, so ended up installing from the DVD instead.
I'm running W7 Ultimate 64bit on a Z170-Deluxe (BIOS 0701) with an i7-6700K and EVGA Titan X Hybrid.
All patches and drivers up to date, so far as I know.
It will be interesting to see if you get any response from ASUS. Seems pretty likely it is a MOBO issue. I did experiment with W10 for a while and believe this error was present there too (along with tens of others, hence me falling back).

Simon
 
Apologies for not posting a reply to this.

I did get a new BIOS for the Z170-K and Z170-P That sorted the fault. The problem sounded like it related to the MEI somewhere along the line with the BIOS. I have just checked and the BIOS with the fix does not appear to have been posted on the Asus website yet. Keep an eye out for it. If you don't have it in a little while just drop me an email and I will see if I can get it sorted for you.

BTW the problem is also persistent in Windows 8/8.1 as well as 10.
 
Not at all.
Glad to hear that a fix is there even if it isn't generally available.
Thanks for working with ASUS on this - the error is widely reported, so many will be very happy to see the new BIOS when it does appear - and thanks for keeping me in the loop.
 
Not at all.
Glad to hear that a fix is there even if it isn't generally available.
Thanks for working with ASUS on this - the error is widely reported, so many will be very happy to see the new BIOS when it does appear - and thanks for keeping me in the loop.

No worries at all. We buy a load of Asus boards for integration and they are usually on the ball if they are given the correct information and all the possible causes have already been sorted.
 
Bad news!
I checked the ASUS site and discovered there had been several BIOS updates in recent weeks. Anyhow, I flashed mine from 0707 to 1101 but the error still persists for me. Maybe ASMedia is the issue. Care to let me know which version of that driver you have and from where you got it?
 
Unfortunately I do not have the fixed BIOS release for the Deluxe just the P and K versions. I can ask tho.

I only received the fix for the BIOS week before last and looking at the release dates for the P and K BIOS revisions there has not been one since I notified them of the issue.

Looking at the last release of the BIOS for the Z170-Deluxe was released on the 5th of Dec. I only notified them on the 12th and received the fix on the 13th. Hopefully they will roll it out within the next couple of weeks.
 
OK. Now I'm confused!
I see 5 BIOS versions on the ASUS website.

0504 10AUG2015
0701 21AUG2015
0801 28AUG2015
0901 06SEP2015
1101 05OCT2015

So, I presume you meant October not December!
The notes for 0901 talk about upgrading to MEI 1168.
I was back level there as well (1140) so have installed the latest on the ASUS website, namely 1160.
So, perhaps what I am waiting for is a new MEI (1168) to be posted on the website.
It isn't really that urgent, but I do like to eliminate error messages from my system where I can.
 
I checked earlier and the latest version was the 1101 released 5th OCT (DOH!!!) I never had to upgrade the MEI separately as its incorporated in most BIOS upgrades.

I would say that you will be waiting for the newer BIOS that should be released AFTER about the 15th OCT.
 
Well, 1203 appeared today. I've installed it but sadly it doesn't fix this error for me.
I'm surprised about what you said about the MEI. It gets updated through Windows Update if you let it, but of course I'd usually install it from the applicable OEM site. I now appear to have 1163 so looks like the BIOS does update it, but I think it is 1168 that will fix this error. So, hopefully yet another BIOS update to be issued in the coming days or weeks. Seems odd that 0901 talks of 1168 when even 1201 seems to install 1163.
 
That's very kind of you. As a single user I'm not convinced they would pay much attention to me, and contacting ASUS isn't the easiest of procedures.
I've now rolled forward to W10 but, as you already said, the error is present in all flavours of Windows.
It will be great if you do get some clarification from them.
 
Thanks so much for staying the course on this one - much appreciated.
Brilliant idea. You figure the MEI was not incorporated into 1101 and 1203, right?
I fell back to 0901 as you suggested. No change, I'm afraid. The rolled forward to 1101 (just to be on the safe side) and then 1203. Still no change.
So, looks like 0901 delivered 1163 rather than 1168 as documented and, presumably, required. Which version do you have, by the way?
 
FYFI
I located a copy of MEI 1168 on Station-Drivers.
I've installed it, but that doesn't fix the problem either.
I'm thinking I'll just have to live with it.
 
Just flashed to 1302 and the problem still exists :-(
ASUS website still has 1160 as the latest chipset available for download but BIOS 0901 claims to load MEI 1168.
I'm running 1168 albeit from station-drivers.
No updates to ASMedia drivers since launch as far as I can see.
Just FYI.
 
Back
Top Bottom