Armoury crate v3.3.7.0 [report here if any issues]

[MasterC]

Suggest to uninstall Aura Sync software if already installed.

Release Notes:
Core services updates:
Armoury Crate Service v3.3.7
Armoury Crate Lite Service v3.3.7
ROG Live Service v1.1.16.0
Lighting Service v3.04.32
ASUS Framework v2.0.2.2
AURA Lighting Effect add-on v0.0.14
(Please ensure these updates are installed before reporting issues)

New features:
-New AURA Performance Mode - For those with a masssive collection of ROG gear, this mode will make the lighting effect smoother.
-Motherboard:
*Addressable strip & devices (ARGB Gen2)
*Added AI MIC two-way noise canceling
*Added Hydrannode feature
-Laptop:
*Support single-color device lighting control
*Support Whisper mode for eGPU
*Win key lock & Armoury Crate key update
*Support for Multiwheel
-Peripherals:
*Support for "Configurable device settings when in AURA Sync mode" (selected models)
*Added "Power Consumption Notice"
*Added "Power management" feature for wireless devices
*[Mobile - Android] Added headset mobile remote configuration
**Realistic virtual surround sound effects
**Personalize the EQ profile settings
**Apply ROG preset audio profiles
**Monitor battery status of headsets

Support for new products:
[Keyboards] ROG Falchion
[Mice] ROG Keris
[Headsets] TUF H3 WIRELESS, ROG Cetra RGB, ROG Clavis
[Motherboards] Z590 series,*B560 series,*ROG Fan Controller for Z590 series
[Graphics cards] 3090 series, 3080 series, 3070 series, 3060 series
[Displays] ROG STRIX XG27AQ,*ROG SWIFT PG259QN,*ROG SWIFT PG259QNR,*ROG SWIFT PG32UQX,*ROG SWIFT PG279QM

Bug fixes:
Fixed App crash*issue*
Fixed device page "Page error" issue*
Fixed device bugs
Optimized device page loading performance
Optimized graphic asset & usage*
Enhanced the AURA Sync effect - Strobing*
Enhanced GUI*layout and UI interactive behavior
Updated device HAL & kits

---------------------------------------------------------------------------------------------------------------------------
To update to the latest version of Armoury Crate, reboot and the update will run in the background automatically (do not open Armoury Crate for 10-15 minutes, and plug in the power for notebooks).

Before reporting issues, please make sure you have the latest software and firmware.
Be clear about the key issue. Mark/edit posts which are no longer relevant, tracking multiple posts in several pages not only takes time but the issue becomes unclear.

Include the following info:
1. PC / Laptop
2. Aura Sync products
3. 3rd-party peripheral, audio, or lighting software
4. Wired / wireless connection
5. Reinstalled Windows?
6. Windows version & build
7. Previous version of firmware or software that worked as expected
8. Clear description of your issue
9. Any screenshots of the issue
10. Use our new log collection function: Settings=>About=>App diagnostics
Please provide a log, it's much easier to provide fixes if we can replicate as accurately as possible.

Log Collection Tool - Instructions
First, check the Record log box
Agree to the disclaimer
Replicate the issue you are having
Click on the Generate log data button
Save the log file to a location of your choice.
Stop the recording

Even though the log file is encrypted, share the log file with me by PM (provide link to file in cloud).

[Samurai_dk]

GodZill4 wrote:
When you delete Armoury Crate - use "Armoury Crate Uninstall Tool" and then install "Aura Sync". I don't have this problem anymore

OK did that and everything appears to be working fine using Aura Sync standalone

[TSportM]

let the bugs begin

cant update the latest hal for rampage extreme Vi

Gives a error to restart to try and update, of course nothing happens even if you restart

[Foxseiz]

This update didn't do anything, to be honest, my GPU (RTX 3090) and RAM (G.Skill Trident Z RGB) are still not available to be controlled. You can see it in the device list but not in AURA Sync...



I paid $2k+ CAD for a GPU that you can't even control the lighting... tsk tsk.

[JeffLo]

every few days i have to uninstall amoury crate and reinstall again, or do a bunch of things to make it work again to control argb, its really annoying

[cindernat]

Why is there not a sticky for the latest version of A.C.?

Anyway I've always had the occasional issue with A.C (not remembering settings, etc) but last week, when I went in to make a change I was force to do some device updates (not sure which, but I have 5 Aura devices). After that, my RGB went to default settings and weren't showing anymore in A.C. I've read tonnes of threads and tried everything, best I can get is 2/5 devices being recognised and controllable in A.C - the rest stuck in rainbow.

Had no response from Asus from my problem ticket and I can't even view it, when I put my email address in, nothing happens. Very frustrating from Asus.

[FlufflePuff1337]

If only cpu usage was fixed already when syncing memory with g skill and g skill memory showing up out of box without having to install g skill own rgb drivers that can only be installed if you remove asus drivers first else you just risk breaking stuff, then i be having no complains.
Also this looks far better then default rainbow effect.
https://imgur.com/2AasLhG

Just change the starting color for each stick to be 2 colors ahead of the next one, i should't need aura creator to do this, if asus wants me to provide exported profile from aura creator i gladly provide if they ask for it, all i do is insist they fix cpu usage and rgb memory intergration for all rgb memory especially g skill cos its clearly broken state i do not remember corsair rgb memory ever showing up in aura creator, but somehow managed fix it my self at cost of 4% cpu usage instead of 2%
You cant just keep saying nothing either asus, you just gonna make me repeat my self over and over again until it gets adressed, you are just ruining armoury crate experience right now its time to fix it.

[Erwin05]

I have a DxDiag file with some error's is this of any use for Asus?

Windows Error Reporting:
+++ WER0 +++:
Foutbucket 1468478466330317310, type 4
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: DtsApo4Service.exe
P2: 1.5.3.0
P3: 5f0d2715
P4: DtsApo4Service.exe
P5: 1.5.3.0
P6: 5f0d2715
P7: c0000005
P8: 000000000000bdc2
P9:
P10:

Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER464D.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER469D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46AD.tmp.xml
\\?\C:\Windows\Temp\WER46AE.tmp.appcompat.txt

Deze bestanden zijn mogelijk hier beschikbaar:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DtsApo4Service.e_6f81724b5e62cebae51294446f972e28d9213bf_4d394567_488f00dd-40d7-4148-bbe6-c3887b0ec6f0

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: aa460e8c-78bc-45be-ae8e-0dc4459e28c4
Rapportstatus: 268435456
Opgedeelde bucket: a4cea38a7f401bffb461156281edd1fe
GUID van CAB-bestand: 0
+++ WER1 +++:
Foutbucket 2271698015751035543, type 1
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: SupportRegedit.exe
P2: 0.0.0.0
P3: 60210b3e
P4: StackHash_ac64
P5: 10.0.19041.964
P6: b7db0838
P7: c0000374
P8: PCH_1C_FROM_ntdll+0x00072F6C
P9:
P10:

Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1923.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1953.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1954.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1963.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1984.tmp.txt

Deze bestanden zijn mogelijk hier beschikbaar:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_SupportRegedit.e_8eca7463fbddc0abdcb89e206a967df558594461_ff94a6e3_931581a1-c5a8-4862-808d-bdd7202b701e

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: bd11946a-f0f5-4ad8-b3c9-55c407930bcf
Rapportstatus: 268435456
Opgedeelde bucket: 0e8f37c12f35013f5f86b14f31ccda97
GUID van CAB-bestand: 0
+++ WER2 +++:
Foutbucket 1611581533685977528, type 5
Naam van gebeurtenis: FaultTolerantHeap
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: SupportRegedit.exe
P2: 0.0.0.0
P3: 60210B3E
P4: ffffbaad
P5:
P6:
P7:
P8:
P9:
P10:

Toegevoegde bestanden:
\\?\C:\Windows\SERVIC~1\LOCALS~1\AppData\Local\Temp\FTH1913.tmp\fthempty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1914.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1925.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1933.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1943.tmp.txt

Deze bestanden zijn mogelijk hier beschikbaar:


Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: f7348748-2b63-4cba-9236-61f29cf7c08b
Rapportstatus: 268435456
Opgedeelde bucket: 64e1c44247492955e65d7cddc9ee91b8
GUID van CAB-bestand: 0
+++ WER3 +++:
Foutbucket 1468478466330317310, type 4
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: DtsApo4Service.exe
P2: 1.5.3.0
P3: 5f0d2715
P4: DtsApo4Service.exe
P5: 1.5.3.0
P6: 5f0d2715
P7: c0000005
P8: 000000000000bdc2
P9:
P10:

Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFC6E.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFCBD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFCBE.tmp.xml
\\?\C:\Windows\Temp\WERFCCF.tmp.appcompat.txt

Deze bestanden zijn mogelijk hier beschikbaar:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DtsApo4Service.e_6f81724b5e62cebae51294446f972e28d9213bf_4d394567_756c7873-6c67-4dd4-a279-d45649a13aa6

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: ba2992f9-6398-4af6-a90b-7385f804bab0
Rapportstatus: 268435456
Opgedeelde bucket: a4cea38a7f401bffb461156281edd1fe
GUID van CAB-bestand: 0
+++ WER4 +++:
Foutbucket 1688910230411814934, type 1
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: Aac3572MbHal_x86.exe
P2: 1.1.7.0
P3: 604b1d5f
P4: combase.dll
P5: 10.0.19041.928
P6: f338dc14
P7: c0000005
P8: 000e2619
P9:
P10:

Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA3E3.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA423.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA433.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA441.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA452.tmp.txt
\\?\C:\Users\erwin\AppData\Local\Temp\WERA464.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Aac3572MbHal_x86_b28fa6351ac711de9e3c938c5dbe213c444f_c4786666_cab_802c65bf-a56a-4788-9c3d-67bc795f2ddd\memory.hdmp

Deze bestanden zijn mogelijk hier beschikbaar:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Aac3572MbHal_x86_b28fa6351ac711de9e3c938c5dbe213c444f_c4786666_802c65bf-a56a-4788-9c3d-67bc795f2ddd

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: 6bd423a8-155e-4152-aaaa-e9c00ea3746d
Rapportstatus: 268435456
Opgedeelde bucket: ed4026daa86d0cf2877036e805382816
GUID van CAB-bestand: 0
+++ WER5 +++:
Foutbucket , type 0
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: Aac3572MbHal_x86.exe
P2: 1.1.7.0
P3: 604b1d5f
P4: combase.dll
P5: 10.0.19041.928
P6: f338dc14
P7: c0000005
P8: 000e2619
P9:
P10:

Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA3E3.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA423.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA433.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA441.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA452.tmp.txt
\\?\C:\Users\erwin\AppData\Local\Temp\WERA464.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Aac3572MbHal_x86_b28fa6351ac711de9e3c938c5dbe213c444f_c4786666_cab_802c65bf-a56a-4788-9c3d-67bc795f2ddd\memory.hdmp

Deze bestanden zijn mogelijk hier beschikbaar:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Aac3572MbHal_x86_b28fa6351ac711de9e3c938c5dbe213c444f_c4786666_cab_802c65bf-a56a-4788-9c3d-67bc795f2ddd

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: 6bd423a8-155e-4152-aaaa-e9c00ea3746d
Rapportstatus: 4
Opgedeelde bucket:
GUID van CAB-bestand: 0
+++ WER6 +++:
Foutbucket 1468478466330317310, type 4
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: DtsApo4Service.exe
P2: 1.5.3.0
P3: 5f0d2715
P4: DtsApo4Service.exe
P5: 1.5.3.0
P6: 5f0d2715
P7: c0000005
P8: 000000000000bdc2
P9:
P10:

Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER77C9.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7808.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7819.tmp.xml
\\?\C:\Windows\Temp\WER781A.tmp.appcompat.txt

Deze bestanden zijn mogelijk hier beschikbaar:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DtsApo4Service.e_6f81724b5e62cebae51294446f972e28d9213bf_4d394567_01922a42-9804-41e0-a213-73bbe4990e2a

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: 93695c20-cb33-46af-a7e3-20db8c0e74a4
Rapportstatus: 268435456
Opgedeelde bucket: a4cea38a7f401bffb461156281edd1fe
GUID van CAB-bestand: 0
+++ WER7 +++:
Foutbucket 1468478466330317310, type 4
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: DtsApo4Service.exe
P2: 1.5.3.0
P3: 5f0d2715
P4: DtsApo4Service.exe
P5: 1.5.3.0
P6: 5f0d2715
P7: c0000005
P8: 000000000000bdc2
P9:
P10:

Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44C.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49D.tmp.xml
\\?\C:\Windows\Temp\WER4AD.tmp.appcompat.txt

Deze bestanden zijn mogelijk hier beschikbaar:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DtsApo4Service.e_6f81724b5e62cebae51294446f972e28d9213bf_4d394567_81df3ceb-f462-4406-9b9e-d5ea3e881fa0

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: 911dec68-ec25-4291-96ca-56dbc8898af8
Rapportstatus: 268435456
Opgedeelde bucket: a4cea38a7f401bffb461156281edd1fe
GUID van CAB-bestand: 0
+++ WER8 +++:
Foutbucket 1468478466330317310, type 4
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: DtsApo4Service.exe
P2: 1.5.3.0
P3: 5f0d2715
P4: DtsApo4Service.exe
P5: 1.5.3.0
P6: 5f0d2715
P7: c0000005
P8: 000000000000bdc2
P9:
P10:

Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA0A9.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA0E8.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA0F9.tmp.xml
\\?\C:\Windows\Temp\WERA0FA.tmp.appcompat.txt

Deze bestanden zijn mogelijk hier beschikbaar:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DtsApo4Service.e_6f81724b5e62cebae51294446f972e28d9213bf_4d394567_5187e950-0135-445f-a9ad-ca629c89b8cb

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: 418a8a23-9054-4745-a9b0-e60435a016f7
Rapportstatus: 268435456
Opgedeelde bucket: a4cea38a7f401bffb461156281edd1fe
GUID van CAB-bestand: 0
+++ WER9 +++:
Foutbucket 1468478466330317310, type 4
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: DtsApo4Service.exe
P2: 1.5.3.0
P3: 5f0d2715
P4: DtsApo4Service.exe
P5: 1.5.3.0
P6: 5f0d2715
P7: c0000005
P8: 000000000000bdc2
P9:
P10:

Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBF7F.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBFAF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBFBF.tmp.xml
\\?\C:\Windows\Temp\WERBFC0.tmp.appcompat.txt

Deze bestanden zijn mogelijk hier beschikbaar:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DtsApo4Service.e_6f81724b5e62cebae51294446f972e28d9213bf_4d394567_4691d57b-4a98-4e3d-aafd-017c668a9c64

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: b9ecd79d-7863-45e7-bda8-3323fe64f768
Rapportstatus: 268435456
Opgedeelde bucket: a4cea38a7f401bffb461156281edd1fe
GUID van CAB-bestand: 0

[therealsummoner]

1. PC / Laptop:
PC
2. Aura Sync products:
Prime B450-Plus, TUF-RTX3080-O10G, TUF-RTX3060TI-O8G
3. 3rd-party peripheral, audio, or lighting software:
None
4. Wired / wireless connection:
Wireless
5. Reinstalled Windows?:
More times
6. Windows version & build:
Version 21H1 Build 19043.985
7. Previous version of firmware or software that worked as expected:
None ever
8. Clear description of your issue:
Using a PciE x16-to-x1 converter (riser), both GPU ignores any RGB settings i.e. they always have their default RGB lights on, no matter what one in Armoury Crate changes.
Secondly, logging on to the pc via Microsoft RDP makes Armoury Crate to not seeing the GPUs. Usually only the MB and the 3080 show up in Aura Sync (see screenshot), sometimes after reboot however none of them shows up there. All three devices are however showing up in Devices, always.
9. Any screenshots of the issue

10. Use our new log collection function: Settings=>About=>App diagnostics

[MasterC]

These 2 known limitations unfortunately. I'll provide an update if any progress.

therealsummoner wrote:
1. PC / Laptop:
PC
2. Aura Sync products:
Prime B450-Plus, TUF-RTX3080-O10G, TUF-RTX3060TI-O8G
3. 3rd-party peripheral, audio, or lighting software:
None
4. Wired / wireless connection:
Wireless
5. Reinstalled Windows?:
More times
6. Windows version & build:
Version 21H1 Build 19043.985
7. Previous version of firmware or software that worked as expected:
None ever
8. Clear description of your issue:
Using a PciE x16-to-x1 converter (riser), both GPU ignores any RGB settings i.e. they always have their default RGB lights on, no matter what one in Armoury Crate changes.
Secondly, logging on to the pc via Microsoft RDP makes Armoury Crate to not seeing the GPUs. Usually only the MB and the 3080 show up in Aura Sync (see screenshot), sometimes after reboot however none of them shows up there. All three devices are however showing up in Devices, always.
9. Any screenshots of the issue

10. Use our new log collection function: Settings=>About=>App diagnostics