Summary: It's generally harmless, the driver does load, it just doesn't do so the first time it tries.Īt 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. I've tried like hell to find a solution, but this is the best answer I've managed to find. The second issue is that once the device is recognized, you get an error about the driver failing upon every reboot. 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 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.Īny other idea on how to better fix this problem ? Join Date Mar 2015 Reputation 152 Posts 2,719 Samsung 850 PRO 512GB SSDs, 4xSATA3 RAID0 NVIDIA Quadro GP100GL/16GB, 16xPCIe3, NVLink1 (SLI-HB) I know how very irritating these issues can be. Now go into your device manager and right-click the unknown device and uninstall it.I would wager this also starts a communication service on your machine. This should generate the file "PEbiosinterface32.dll" in that folder.Double-click and execute atkecComSvc.exe or if you have UAC enabled, right-click it and select "Run as administrator".It was found under "Program Files\ASUS\AMDA\AXSP" on my system Open the folder installed by the Asus driver package under Program Files on your system and locate the atkexComSvc.exe file.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). 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
0 kommentar(er)
