Acpi pnp0a0a 2 daba3ff 0 windows 10 asus

1. 06-27-2015 06:49 PM

   
   

   #1

   

   
   New ROGer
   

   Array
   maddick PC Specs

   maddick PC Specs
   Motherboard	x99 Deluxe
   Processor	Intel i7 5930K @4.0ghz
   Memory (part number)	Ripjaws 4 Series 16GB (4 x 4GB) DDR4 2400
   Graphics Card #1	Strix GTX 1080 Ti
   Storage #1	Samsung 850 EVO 250GB
   CPU Cooler	Corsair Hydro H110
   Case	Thermaltake Core v71
   Power Supply	Corsair AX1500i
   Keyboard	Logitech G810
   Mouse	Logitech G800
   Headset	SteelSeries Arctis 3
   OS	Windows 10 Pro

   

   ---

   AMDA00 Fix for x99 boards — Unknown Device ACPIPNP0A0A
   

   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 ACPIPNP0A0A
   ). 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.

   1. 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 FilesASUSAMDAAXSP» on my system
      
   2. Double-click and execute atkecComSvc.exe or if you have UAC enabled, right-click it and select «Run as administrator».
   3. This should generate the file «PEbiosinterface32.dll» in that folder. I would wager this also starts a communication service on your machine.
      
   4. Now go into your device manager and right-click the unknown device and uninstall it.
   5. Restart your machine.
   6. 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.

   ---

2. 06-28-2015 12:15 AM

   
   

   #2

   

   
   ROG Guru: Black Belt
   

   Array
   Korth PC Specs

   Korth PC Specs
   Motherboard	ASUS X99 R5E (BIOS2101/1902)
   Processor	Haswell-EP E5-1680-3 SR20H/R2 (4.4GHz)
   Memory (part number)	Vengeance LPX 4x8GB SS DDR4-3000 (CMK32GX4M4C3000C15)
   Graphics Card #1	NVIDIA Quadro GP100GL/16GB, 16xPCIe3, NVLink1 (SLI-HB)
   Graphics Card #2	NVIDIA Quadro GP100GL/16GB, 16xPCIe3, NVLink1 (SLI-HB)
   Sound Card	JDS Labs O2+ODAC (RevB), USB2 UAC1
   Monitor	ASUS PG278Q
   Storage #1	Samsung 850 PRO 512GB SSDs, 4xSATA3 RAID0
   Storage #2	Comay BladeDrive E28 3200GB SSD, 8xPCIe2
   CPU Cooler	Raijintek NEMESIS/TISIS, AS5, 2xNH-A14
   Case	Obsidian 750D (original), 6xNH-A14
   Power Supply	Zalman/FSP ZM1250 Platinum
   Headset	Pilot P51 PTT *modded*
   OS	Arch, Gentoo, Win7x64, Win10x64
   Network Router	Actiontec T3200M VDSL2 Gateway
   Accessory #1	TP-Link AC1900 Archer T9E, 1xPCIe
   Accessory #2	ASUS/Infineon SLB9635 TPM (TT1.2/FW3.19)
   Accessory #3	ASUS OC Panel I (FW0501)

   

   ---

   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.

   ---

3. 06-28-2015 01:52 AM

   
   

   #3

   

   
   ROG Member
   

   Array

   ---

   ---

4. 06-28-2015 02:09 AM

   
   

   #4

   

   
   ROG Guru: Black Belt
   

   Array
   Hopper64 PC Specs

   Hopper64 PC Specs
   Motherboard	Asus MZ790E Bios 0813
   Processor	i9 13900KS
   Memory (part number)	F5-7600J3646G16GX2-TZ5RK
   Graphics Card #1	Asus 4090 Strix
   Sound Card	Creative SB X4
   Monitor	Asus ROG XG349C
   Storage #1	Samsung 990 Pro
   CPU Cooler	Quantum Kinetic TBE 300 D5 with XTOP DDC 4.2
   Case	Phanteks Enthoo Elite
   Power Supply	Corsair AX1600i
   Keyboard	Asus ROG Claymore 2
   Mouse	Asus ROG Gladius III
   OS	Windows 11 64

   

   ---

   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.

   ---

5. 06-28-2015 04:10 AM

   
   

   #5

   

   
   ROG Guru: Grand Master
   

   Array

   ---

   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 BinAMDA00 folder.

   ---

6. 06-28-2015 07:53 AM

   
   

   #6

   

   
   New ROGer
   

   Array
   maddick PC Specs

   maddick PC Specs
   Motherboard	x99 Deluxe
   Processor	Intel i7 5930K @4.0ghz
   Memory (part number)	Ripjaws 4 Series 16GB (4 x 4GB) DDR4 2400
   Graphics Card #1	Strix GTX 1080 Ti
   Storage #1	Samsung 850 EVO 250GB
   CPU Cooler	Corsair Hydro H110
   Case	Thermaltake Core v71
   Power Supply	Corsair AX1500i
   Keyboard	Logitech G810
   Mouse	Logitech G800
   Headset	SteelSeries Arctis 3
   OS	Windows 10 Pro

   

   ---

   Originally Posted by Hopper64
   

   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.

   Yes. This refers to the temperature sensor.

   Originally Posted by Korth
   

   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.

   Running the following as hardware:
   • x99 Deluxe
   • two nVidia 970 gtx in sli

   Originally Posted by foo-adrian-3
   

   Yes is workable. Thanks

   Glad to hear this fix has help someone else out there.

   Originally Posted by Chino
   

   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 BinAMDA00 folder.

   The installer, both from the CD and downloaded via Asus site did not provide a fully working sensor for me. In either case I needed to manually kick off the service which in turn generates what I imagine to be a necessary dll file as well. I will note that others have good success turning to their CD though. This might be worth noting if someone is facing issues with this device.

   Last edited by maddick; 06-28-2015 at 07:57 AM.

   ---

7. 01-01-2016 07:48 PM

   
   

   #7

   

   
   New ROGer
   

   Array

   ---

   I tried the solution but the problem reoccurs
   

   Hello,
   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

   Originally Posted by maddick
   

   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 ACPIPNP0A0A
   ). 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.

   1. 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 FilesASUSAMDAAXSP» on my system
      
   2. Double-click and execute atkecComSvc.exe or if you have UAC enabled, right-click it and select «Run as administrator».
   3. This should generate the file «PEbiosinterface32.dll» in that folder. I would wager this also starts a communication service on your machine.
      
   4. Now go into your device manager and right-click the unknown device and uninstall it.
   5. Restart your machine.
   6. 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.

   ---

8. 01-01-2016 08:32 PM

   
   

   #8

   

   
   ROG Guru: Green Belt
   

   Array
   Qwinn PC Specs

   Qwinn PC Specs
   Motherboard	Crosshair x670e Extreme
   Processor	AMD 7950x
   Memory (part number)	128GB Corsair Dominator Platinum ARGB (CMT64GX5M2B5200Z40 — 2 kits)
   Graphics Card #1	EVGA Hybrid 1080TI FTW3
   Monitor	ROG Swift PG278Q
   Storage #1	Kingston SKC3000D/4096G M.2 NVME
   CPU Cooler	ROG Ryujin II 360 ARGB Eva Edition
   Case	Fractal Define 7 XL
   Power Supply	Rosewill SMG1200
   Keyboard	Corsair K100 RGB
   Mouse	Razer Basilisk V3
   OS	Windows 10 Professional 64 bit

   ---

   Originally Posted by francesco.bruno
   

   Hello,
   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

   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.

   https://rog.asus.com/forum/showthrea…-Errors/page17

   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.

   ---

9. 01-02-2016 11:52 AM

   
   

   #9

   

   
   New ROGer
   

   Array

   ---

   Collateral effect of Driverfailing to load for the device ACPIPNP0A0A2&daba3ff&2
   

   Originally Posted by Qwinn
   

   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.

   https://rog.asus.com/forum/showthrea…-Errors/page17

   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.

   Thanks a lot for your reply.

   Oftnen when I get the event :
   Source: Kernel-PnP
   Event ID: 219
   Task Category: (212)
   The driver DriverWUDFRd failed to load for the device ACPIPNP0A0A2&daba3ff&2.

   one or two seconds later I have:
   Source: Eventlog
   Event ID: 6008
   Task Category: None
   The previous system shutdown at time on date was unexpected.

   And when this other correlated event occurs, the boot process gets locked and I am forced to switch off and on my PC. This fact occurs about every other day.

   Anyone else experiencing this same problem. Any idea on how to prevent the boot process from locking up.

   Thanks a lot in advance

   ---

10. 01-02-2016 02:13 PM

    
    

    #10

    

    
    ROG Guru: Green Belt
    

    Array
    Qwinn PC Specs

    Qwinn PC Specs
    Motherboard	Crosshair x670e Extreme
    Processor	AMD 7950x
    Memory (part number)	128GB Corsair Dominator Platinum ARGB (CMT64GX5M2B5200Z40 — 2 kits)
    Graphics Card #1	EVGA Hybrid 1080TI FTW3
    Monitor	ROG Swift PG278Q
    Storage #1	Kingston SKC3000D/4096G M.2 NVME
    CPU Cooler	ROG Ryujin II 360 ARGB Eva Edition
    Case	Fractal Define 7 XL
    Power Supply	Rosewill SMG1200
    Keyboard	Corsair K100 RGB
    Mouse	Razer Basilisk V3
    OS	Windows 10 Professional 64 bit

    ---

    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.

    ---

Tags for this Thread

In Internet Explorer, click Tools, and then click Internet Options.

On the Security tab, click the Trusted Sites icon.

Click Sites and then add these website addresses one at a time to the list:
You can only add one address at a time and you must click Add after each one:

http://*.update.microsoft.com

https://*.update.microsoft.com

http://download.windowsupdate.com