06-27-2015 11:49 AM
06-27-2015 05:15 PM
06-27-2015 06:52 PM
06-27-2015 07:09 PM
06-28-2015 12:53 AM
Korth-I think he's referring to the Asus probe sense driver. It's under utilities in the driver downloads for our board. I don't think this has anything to do with AMD video cards.
Which X99 mobo, AMD card(s), AMD driver version, and Windows version are you using?
I tried out a pair of AMD 7870XT cards on my X99 R5E for a while (and they're surprisingly strong performers, lol). Never saw this "Unknown Device/AMDA00" error with Catalyst 14.10 and Win7, my GPU temp sensors worked just fine (and my Device Manager seemed happy) without any manual configuration.
Yes is workable. Thanks
For future reference the AMDA00 driver is on the driver DVD that comes with the motherboard. If I'm not mistaken, you should find it in the \Bin\AMDA00 folder.
06-27-2015 09:10 PM
01-01-2016 11:48 AM
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.
01-01-2016 12:32 PM
I have tried the solution below. The first time I restart the PC I do not get the error of failing to load the device driver, but all following restart the error re-appear and every now and then the log on process gets locked.
Any other idea on how to better fix this problem ?
Thanks in advance
01-02-2016 03:52 AM
I think there's two different issues. The OP is about an issue which doesn't always occur where the device in question is unrecognized and shows up as an unknown device. The second issue is that once the device is recognized, you get an error about the driver failing upon every reboot. You're talking about the second issue.
I've tried like hell to find a solution, but this is the best answer I've managed to find. Summary: It's generally harmless, the driver does load, it just doesn't do so the first time it tries.
At this point, I've learned to embrace the error as it has the side benefit of recording at what time I've done a reboot in relation to any other errors that might pop up in the event log.
01-02-2016 06:13 AM