02-16-2025 06:07 AM
Faulting application name: ArmourySocketServer.exe, version: 0.1.20.18, time stamp: 0x6721a440
Faulting module name: ArmourySocketServer.exe, version: 0.1.20.18, time stamp: 0x6721a440
Exception code: 0xc0000409
Fault offset: 0x00000000001201d1
Faulting process id: 0x0x228C
Faulting application start time: 0x0x1DB8079BA78AC78
Faulting application path: C:\Program Files (x86)\ASUS\ArmouryDevice\dll\ArmourySocketServer\ArmourySocketServer.exe
Faulting module path: C:\Program Files (x86)\ASUS\ArmouryDevice\dll\ArmourySocketServer\ArmourySocketServer.exe
Report Id: 5daaa69a-0f1b-4802-b668-b97f965a7243
Faulting package full name:
Faulting package-relative application ID:
I9-14900KS
Asus Rog Strix Z790-E
Corsair Dominator Titanium 4x24Gb 96GB
Gigabyte RTX 4080 Super Master
Crucial T700 4Tb
Thermaltake GF3 1200W
02-16-2025 06:26 AM
Hello Lexxguard
In Task Manager, try End Task for ArmourySocketServer.
Open Armoury Crate, it will restart the ArmourySocketServer.
If that doesn't help, a quick reinstall of Armoury Crate should fix the issue.
1) Uninstall Armoury Crate from Windows.
2) Reboot your pc.
3) Install Armoury Crate version 3.2.11.2. - Armoury Crate - Support
Does this get Armoury Crate back to normal?
4 weeks ago
This is a known bug (firstly appeared all of a sudden I think in Oct-Nov 2024) and none of the above workaround fixes the problem till now..it is clearly an Armoury bug and since February 2025 it is shown at every PC shutdown...none of the Armoury crate's employees seem to do something to fix it...at last..are you a serious company?
2 weeks ago
You can try reinstalling Armoury Crate or updating drivers to fix crashes.
2 weeks ago - last edited 2 weeks ago
Reinstalling of ArmouryCrate does NOT fix the error.
I've already tested it several times since this error occurred.
That's why I opened a separate thread about it.
A new installation of ArmouryCrate does NOT fix the error.
I have already tested this several times since this error occurred.
Even a new installation of Windows does NOTHING.
That is why I opened a separate thread about it.
In addition, new error entries have been added with the current version 6 of ArmouryCrate.
It is a bug in ArmouryCrate in connection with Windows and only Asus can fix it.
Sufficient logs have been submitted by users but so far nothing has been done.
As long as ArmouryCrate is obviously running without error messages in the program, all we can do is ignore these error entries in the reliability history and event log.
2 weeks ago
It doesn't fix the problem. Already tested 2 times
2 weeks ago
What kind of device or hardware are you using?
Have you restarted the device yet?
2 weeks ago
Asus tuf 16 gamings radeon 9 ...