cancel
Showing results for 
Search instead for 
Did you mean: 

Help Multiple ACPI Errors

Sparax
Level 9
Hi all i am having some issues with the ACPI driver for my new Maximus Hero Vii Board Event viewer is reporting several issues as follows

ACPI Event ID 13
: The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly.

ACPI Event ID 15
: The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.

Kernel-PnP Event ID 219
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&2.

System Specs
Asus Maximus VII HERO (BIOS 0904)
Intel Core i7 4790k @ Stock
Corsair Dominator GT (CMT4GX3M2A2000C8)
Windows 7 SP1 on Corsair Force 3 SSD

I Have installed all the latest drivers and updated to the latest bios but I'm still getting these errors anyone got any ideas what I need to do to fix this?
346,181 Views
175 REPLIES 175

Same issues her on Maximus VII Ranger. Seems to have no effect, only PC wakes up from sleep due to On/Off switch (which I did not touched at all). Don't know if it is related.

Latest drivers, latest BIOS, Samsung SSD 250 fresh win 8.1 pro installation...

Edit: PC waking is miraculously solved... But ACPI errors are still present.

Puffnstuff
Level 10
When I first installed my board I was running windows 7 ultimate x64 in a mbr install and I had tons of trouble until I did two things. Upgraded to windows 8.1 x64 professional and did a uefi gpt installation. With a uefi installation of windows it allows the bootloader to merge with stage 3 of the uefi bios and allows the board and os to communicate more effectively. I initially did a uefi gpt instal of windows 7 but even it did not communicate the right way with the bios and I had trouble booting. My system would not consistently boot when I hit the power button and windows would start to load and then reset the bios and start all over again in what seemed like an endless loop. There were times where it would loop 16 times before I could load windows.

With that said not all problems are the same but I've also read articles about the uefi implementation on various boards and how people, especially those who run the apple os with their pc hardware prefer gigabyte's implementation of the uefi standard because it has additional files that the rest do not that allow their boards to run more effectively with uefi. Again I do not understand all of the differences but I do know that my uefi install of windows 8.1 professional x64 works great and is stable. The windows 8.1 interface sucks until you modify it with classic shell and then it is like windows 7 only better.
Asus ROG Crosshair VIII Hero Wi-Fi Gigabyte X570 Aorus Master, AMD 3900X, EVGA 360 aio, 32gb G.Skill Trident Z Neo, Samsung 970 Pro NVME 512gb, WD Black NVME 1 TB, Crucial MX500 2tb, Zotac GTX 1080 AMP!, EVGA Nu Audio, CM HAF 932

Puffnstuff wrote:
With that said not all problems are the same but I've also read articles about the uefi implementation on various boards and how people, especially those who run the apple os with their pc hardware prefer gigabyte's implementation of the uefi standard because it has additional files that the rest do not that allow their boards to run more effectively with uefi.

Hello

This is complete nonsense. They were the last motherboard manufacturer to implement UEFI because of the issues they were having. Any extra files are more likely patches and workarounds for the outstanding problems that still exist.

Puffnstuff
Level 10
The folks who do hackintosh have a different perspective on uefi bios implementations which is why they all recommend using a gigabyte board if you are going to do a uefi os x install.
Asus ROG Crosshair VIII Hero Wi-Fi Gigabyte X570 Aorus Master, AMD 3900X, EVGA 360 aio, 32gb G.Skill Trident Z Neo, Samsung 970 Pro NVME 512gb, WD Black NVME 1 TB, Crucial MX500 2tb, Zotac GTX 1080 AMP!, EVGA Nu Audio, CM HAF 932

volts240
Level 7
Same errors here folks , can't add anything to what's been said
except asus should fix this pronto - its not fair when so many user
are spending hours trying to solve these issues
think of the man-hours gone into this - its frightening

More errors occur with AISuite Installed
Iusing BIOS 2012 , Ranger VII Motherboard, Win 8.1
Devils Canyon Intel i7-4970K ~ Asus Maximus Ranger VII ~ 16 GB HyperX Beast ~ Plextor M6e 256GB M.2 - 2280 SSD ~ CPU Cooler Corsair H105 73.0 CFM Liquid ~ PSU: Thermaltake Smart M 850W 80+ Windows Home Premium x64

Hello Guys!

Same problem here! As i see i am the first one with Rampage IV Black Edition and i7 4960X but i also get:

Załadowanie sterownika \Driver\WUDFRd dla urządzenia ACPI\PNP0A0A\2&daba3ff&2 nie powiodło się.
Which in polish means that the driver connot be loaded. I think that because of that error system startup takes longer.

Any news on the topic? I would be very happy to find a solution.

Windows 7 64 bit using newest Probe II driver

kerrypierce
Level 7
FWIW, I had same problem on an ASUS Maximus VII Hero. The fix was to download the ASUS Probe II Sense Driver 1.0.1.0, (in Utilities section of motherboard downloads) unzip it and then I used the device driver properties window to "update driver" and pointed it to the folder where I'd unzipped the Probe driver. It found the driver that it wanted, installed it and the problem was solved. Hope it works for you.

rwmeyers
Level 7
Same continuing issue on M7 Gene.

lunarstrain
Level 7
i think i have a temporary solution to this issue. 1-From Device Manager, find the AMDA00 deice and update driver, choose microsoft hyper v-s3 2- Find dipawaymode.exe in the program files folder and rename it. (like backupdipawaymode.exe or anything else) 3-From services.msc disable ASUS System Control Service. After having done these changes, my eventv viewer logs are clean from all these acpi errors. Also Asus AI suite works.

TheRealWitblitz
Level 7
Maximus VII Formula, same issue here.

I've been getting hard locks for 3 days for no apparent reason, event viewer is filled with ACPI errors. Specifically EventID 219 \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2