06-27-2015 11:49 AM - last edited on 03-05-2024 10:02 PM by ROGBot
01-02-2016 10:15 AM
Qwinn wrote:
They're not really correlated. Go ahead and do a normal restart. You should get the 219 error without the 6008 error.
You WILL see a 219 every time your system crashes and reboots (which is what the 6008 error is telling you happened), because you'll see 219 on every single reboot, crash or otherwise. Something is crashing your system, but it's not the 219 error. We all get the 219 error all the time.
02-10-2016 02:20 AM
11-23-2016 05:49 PM
Agent-Orange wrote:
Hi Guys
Since this Monday, I have also a problem with the AMDA00 Driver. The system crashes and after a Reboot there is a yellow exclamation mark
on the AMDA00 interface in the device manager, with Code 37 (cannon find the object name). The only thing I can do, is a system restore.
When I try to delete the driver, the "delete window" appears but I cant delete it and I cannot close the window. I can close it when I kill the console with the task manager.
Same situation when I try to deactivate it. The other problem is now, that some services cannot start probably and I cannot restart the system, it get a blue screen after 5-10min after I pressed restart.
A friend of mine has the same board and dont have problems like me. He also has the same driver installed to that device. The only thing I realized, that Windows installed 2 new updates on Monday, but that were only some flash updates for Internet Explorer.
So far I know its the ASUS PC Sense Driver.
Any advice?
07-18-2017 10:34 AM
09-02-2017 05:40 AM
11-14-2016 07:50 PM
maddick wrote:
So I ran into an issue I've seen posted about across the internet where the AMDA00 device (the temperature sensor) would not properly install but instead show up in the device manager as Unknown Device (hardware id ACPI\PNP0A0A
). I battled with my system for a bit then landed on a solution that worked twice (I ended up needing to re-install my OS). Here is the solution I found.
- Open the folder installed by the Asus driver package under Program Files on your system and locate the atkexComSvc.exe file. It was found under "Program Files\ASUS\AMDA\AXSP" on my system
- Double-click and execute atkecComSvc.exe or if you have UAC enabled, right-click it and select "Run as administrator".
- This should generate the file "PEbiosinterface32.dll" in that folder. I would wager this also starts a communication service on your machine.
- Now go into your device manager and right-click the unknown device and uninstall it.
- Restart your machine.
- Magic happens
This solution worked twice for me. I hope it works for others as well. I know how very irritating these issues can be.