Armoury Crate not Detecting Motherboard

[DBoone420]

same issue for me, I updated to the latest bios version on my TUF Gaming x570-plus, and now only Strix 5700xt GPU and G.Skill Trident RGB DRAM are being detected. I've tried uninstalling with the uninstallation tool and reinstalling multiple times with no luck.

[frdiasg]

STOP DETECTING MOTHERBORD, STOP DETECTING DDR, STOP DETECTING GPU, WTF ASUS...

It has stop working even asus isuite 3... After last release update, my isuite got an error related with dipawamode... Whatahell asus, FIX THIS!!!

[Jimbo93]

Whether you actually have a problem or not this is stupid. Armoury Crate has had many changes in a year and a half. Start a new thread for pete's sake.

[DBoone420]

Whether you actually have a problem or not this is stupid. Armoury Crate has had many changes in a year and a half. Start a new thread for pete's sake.

Well if they actually addressed these bugs maybe people wouldn't do that.

[Jimbo93]

[QUOTE=DBoone420;865781]Well if they actually addressed these bugs maybe people wouldn't do that.[/QUOT

You mean like the keyboard issue that was fixed in one week after a log was properly sent?

[MaximusZee]

it happened on my Z690 Extreme too...
I tried everything but nothing solved.

the only solution was to restore a macrium backup I had...

I experienced same issue with Crosshair VIII Hero (Wifi) Win 11 22H2 on 6/17. I think this happened after I updated AI Suite 3 from 3.0.69 to 3.01.10 using Armoury Crate. The update completed but the current version is still showing in Armoury Crate as 3.0.69 after reboot. However several problems happened on Armoury Crate.

Symptoms
1. ROG CRosshair VIII Hero (Wifi) and Addressable LED strip devices missing from Aura Sync - Sync Devices screen.
2. Pop up error messages concerning Dipawaymode.exe after log on.
3. 1035 Error in eventviewer 1035 concerning asComSvc not responding. In the service control manager, asComSvc was stopped and could not be restarted.
4. ROG Live Service also had errors and was stopped.
5. AsusFanControl Service also did not start

Trouble shooting effort with reboots as required
1. Uninstall Armoury Crate using Installed apps
2. Uninstall using Armoury Carte uninstall tool
3. Uninstall AI Suite 3
4. Uninstall AI Suite 3 using AI Suite 3 removal tool
5. Tried reinstalling Armoury Crate & AI Suite 3 using old and new versions

Nothing worked but was getting more errors showing up on event viewer.

Restored system to 6/16 using Acronis backup and everything was working was usual again. Retried updating AI Suite 3 again to 3.0.1.10 and then symptoms reoccurred. Attempted more trouble shooting after restoring and reinstalling Armoury Crate components again but nothing worked.

Finally gave up and restored system from 6/16 backup again and it is working properly so will leave it alone for now.

Version Info in Armoury Crate Settings->About

Armoury Crate UWP App 5.1.5.0
ROG Live Service 1.4.10.0
Aura Service (Lighting Service) 3.05.40
Armoury Crate lite service 5.1.4
Aura Wallpaper Service Not installed
ASUS AIOFan HAL 1.1.47.0
ASUS AURA Extension Card HAL 1.1.0.18
ASUS AURA Motherboard HAL 1.3.0.0
AacVGA 0.0.4.3
KingstonDram 1.1.12
AURA DRAM Component 1.1.18
ENE RGB HAL 1.1.39.18
ENE_EHD_M2_HAL 1.0.9.12
PHISON HAL 1.0.9.0
Patriot Viper DRAM RGB 1.0.9.2
Patriot Viper M2 SSD RGB 1.0.6.5
Universal Holtek RGB DRAM 1.0.0.2
WD_BLACK AN1500 1.0.14.0

[modernmyth]

I installed latest armoury crate update and my motherboard not detected. I tried to uninstall with tool and installed after that but problem still occurs. In Aura section my gpu and other components doesn't detected.

[MaximusZee]

Some thoughts for my case...

Armoury Crate and AI Suite 3 is running perfectly under Win 11 Pro 22H2 OS build 22621.105 on Crosshair vIII Hero (Wifi) with latest BIOS 4201.

If I update AI Suite Version using Armoury Crate to 3.01.10 and devices disappear from Armoury Crate Sync devices and AI Suite 3 can't be started. Errors related to ASUS services are recorded in the windows system event log.

I can revert back to working system using backup. There are no other differences between the two states so I can safely assume that AI Suite update from Armoury Crate is causing issues and Windows component, Nvidia, and BIOS can be ruled out.

Perfectly funcitioning version:

AI Suite 3 Version 3.00.69

Item Version
---- -------
Armoury Crate UWP App 5.1.5.0
ROG Live Service 1.4.10.0
Aura Service (Lighting Service) 3.05.40
Armoury Crate lite service 5.1.4
Aura Wallpaper Service Not installed
ASUS AIOFan HAL 1.1.47.0
ASUS AURA Extension Card HAL 1.1.0.18
ASUS AURA Motherboard HAL 1.3.0.0
AacVGA 0.0.4.3
KingstonDram 1.1.12
AURA DRAM Component 1.1.18
ENE RGB HAL 1.1.39.18
ENE_EHD_M2_HAL 1.0.9.12
PHISON HAL 1.0.9.0
Patriot Viper DRAM RGB 1.0.9.2
Patriot Viper M2 SSD RGB 1.0.6.5
Universal Holtek RGB DRAM 1.0.0.2
WD_BLACK AN1500 1.0.14.0

I would pursue further if backup restoration time didn't take 2.5 hours...

[bradbergeron]

I have the exact same problem as all above.. I have tried uninstall and clean up.. I just got home from 3 weeks trip and updated Armoury Crate and now I cant control my Motherboard lights or things connected. Half my PC lights work and others dont... So annoying.... No idea on what to do... I submitted logs.

[MaximusZee]

I shouldn't have but I went through all functions of Armoury Crate, AI Suite 3, Aura and Aura Creator on my working system. Don't know what caused it but I started getting DipAwayMode.exe and asComSvc service errors upon reboot. I did not do any software or driver updates so the issue may be related to software settings. At this point, I copied my working backup from hard disk to SSD for faster restoration. After I restored, I noticed a change in service start settings in HKLM\System\CurrentControlSet\Services.

Working: asComSvc image path is c:\programfiles (x86)\asus\axsp\4.02.12\atkexcomsvc.exe (After restore)
Problem: asComSvc image path is c:\programfiles (x86)\asus\axsp\4.02.06\atkexcomsvc.exe (Issue recurrance after playing around on restored state)

So what caused 4.02.12 change to 4.02.06 where the latter is presumably older version? I am stopping for time being but if the issue recurrs, I will rewrite the service image path in the registry and reboot to see if that corrects the service related errors. If it does then have to identify what is causing this change.