Multiple ACPI warnings HERO VII

[Karlo666]

I had problem whit drivers.Even i reinstalled system and drivers.
Checked on everything.
Device manager is fine.
AMDA00 is installed and there are no sings of missing drivers.

Just this ACPI warning is in event viewer and it comes from time to time.
BIOS is full default ATM and newest version of BIOS is flashed and still this warning.

"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."

Any tip how to fix this problem?

[Norcus]

There is a problem with some ASUS software installing files into a /tmp directory, and thus routinely gets deleted or are inaccessible to the application trying to use them. There are several threads on the subject.

Worst case scenario: ASUS software will malfunction and be unreliable ... oh no! 🙂

[Karlo666]

Well i didnt used cleaner(not even windows one) and my /tmp directory is untouched.Even on my fathers H87 board it doesnt show this error at all.

[Sparax]

Hi Karlo666

Unfortunately there is nothing you can do about those errors i'm afraid, it is caused because the Asus driver is requesting info from the Windows driver before it has finished initialising so it returns an error however both drivers do eventually load and communicate with each other so there isn't really a problem and the error can be ignored.

Nodens wrote:


a) Those WUDFRd errors are not ACPI errors. No matter if they point to ACPI\PNP0A0A\2&daba3ff&2. This is just a PNP (Plug and Play) indentifier that points to a device class.

b) WUDFRd is Windows User Mode Driver Framework. This is a framework for drivers that run in user mode, in contrast to kernel mode that most drivers run as. These are drivers that do not need Ring-0 security layer access for those familiar with technical details. For the rest it's too complicated to explain.

c) Those errors happen because of bugs in Windows and specifically the Framework itself. WUDFRd is not available when Windows tries to load the driver so you get these errors in the event viewer. Afterwards the driver for the device is loaded normally, if it wasn't then the device that uses WUDFRd (eg your Android phone) would not work (would not be seen by your PC). These errors can be safely ignored untill Microsoft decides to fix those issues. You will usually see these errors when devices that use WUDFRd are connected during boot/reboot. In case of software using a user mode driver, you will see these errors always if the driver get initiated on boot (so yes it's possible to see these errors caused by software BUT again they are harmless).

[Karlo666]

Sparax wrote:
Hi Karlo666

Unfortunately there is nothing you can do about those errors i'm afraid, it is caused because the Asus driver is requesting info from the Windows driver before it has finished initialising so it returns an error however both drivers do eventually load and communicate with each other so there isn't really a problem and the error can be ignored.

This is for AMDA00 driver you are saying and its not for EC thing.I can bet that many people that have same board as me doesnt have EC warning in event viewer.