| Event Id | 3 |
| Source | ACPIEC |
| Description | \Device\ACPIEC: The embedded controller (EC) hardware returned data when none was requested. This may indicate that the BIOS is incorrectly trying to access the EC without synchronizing with the OS. The data is being ignored. |
| Event Information | The problem seems to be well known, an overly chatty ACPI Embedded Controller and Windows XP, which is newly sensitive to this, but no solution is in sight so far. The most likely solution would be a corrected BIOS, but only if it is true what the warning message says. Another solution could be to remove the new sensitivity from Windows XP again and make it as deaf to unwanted ACPIEC babbling as all earlier versions of Windows were. But thats in Microsofts hands. This information from News Group may help:CAUSE: The problem to be known,ACPI Embedded Controller chip and Windows XP, which is newly sensitive to this.The most likely solution would be a corrected BIOS, but only if it is true what the warning message says. Another solution could be to remove the new sensitivity from Windows XP again and make it as deaf to unwanted ACPIEC babbling as all earlier versions of Windows were. But thats in Microsofts hands. It may be a dying problem, as faster processors reduce the impact and newer BIOS versions may prevent the problem in the first place. The errors are triggered by programs like temperature monitors or DVD playing programs, which query the ACPIEC chip for temperature or battery charge information or similar. The DVD player WinDVD, for example, does it to find out whether the battery of a laptop is running low. RESOLUTION: It can do it by modifying ACPIEC.SYS with a hex editor. 1. Go into \windows\system32\drivers and make a copy of ACPIEC.SYS to a new file called acpiecNoLog.sys. 2. Open acpiecNoLog.sys with a hex editor. 3. Most of the file will be unreadable garbage, but near the end you should be able to see a long series of null-terminated strings (the first is MmUnlockPagableImageSection"). These are the names of the external functions dynamically linked by the driver. 4. Look for the function name "IoWriteErrorLogEntry". This is the function that writes the warnings into the system log. Now disable it by repl |
| Reference Links | More Information |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.