6 Posts
1
7297
Aurora R10, AWCC.exe stopped working
When checking the reliability history on my system I see repeated "AWCC.exe stopped working" errors. This error shows up nearly every day, sometimes many times in a day. This has been ongoing since I got my PC. It also happens on my non-Alienware PC that only has AWCC installed because it auto installs when I plug in my Alienware headphones.
The error details info looks like this:
Description
Faulting application name: AWCC.exe, version: 5.4.9.0, time stamp: 0x619e4e2c
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1387, time stamp: 0x0b9a844a
Exception code: 0xc000027b
Fault offset: 0x000000000010b302
Faulting process id: 0x200c
Faulting application start time: 0x01d7f1e53d39cb35
Faulting application path: C:\Program Files\WindowsApps\DellInc.AlienwareCommandCenter_5.4.9.0_x64__htrsf667h5kn2\AWCC.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 2062568f-4aef-459e-bc41-9dab44052e5a
Faulting package full name: DellInc.AlienwareCommandCenter_5.4.9.0_x64__htrsf667h5kn2
Faulting package-relative application ID: App
Does anyone know a fix for this? Thanks!
slackeratwork
6 Posts
2
December 16th, 2021 11:00
I got a response from Dell on this issue. Here is the explanation they sent me:
In regard to the error on reliability history, this may sound a little odd but you can disregard this message since it is normal. This error comes up in all of our systems that use AWCC. The error is not an actual error, but a small communication gap between Alienware Command Center and the Microsoft Store. As you have seen, the app's add-ons like FX and Sound are downloaded by the app automatically from the Microsoft Store. When you start up the computer, there is a small waiting time where the AWCC needs to reconfigure the add-ons to work with it. To do this, the AWCC app stops for a moment to set them up and goes back to normal operation.
You would usually do not see this process occurring since it is all happening on the background, but that small stop that the AWCC does is what causes the alert. This will happen every time you turn the computer on. I hope this explanation is helpful for you to not worry about the alert.
sm56
163 Posts
0
December 15th, 2021 11:00
That's normal (for Dell Alienware I mean)... It has always error-ed out in the event log like that (at least since 2020 when I bought my R10)... Good luck!
Sparky1964
101 Posts
0
December 15th, 2021 12:00
Yep, when I tested AWCC on my system I kept having this too so I uninstalled it. I really don't need it, and I think I have less issues than others with it. I've got the R11.
speedstep
9 Legend
9 Legend
•
47K Posts
0
December 15th, 2021 12:00
@slackeratwork Please press the blue Accept as Solution button below if the post answers your question.
Feature and Version updates Break AWCC
Not all versions fit all models.
You need to install Microsoft .NET Framework 2.0 3.5 Service Pack 1 first, then re-run the Alienware Command Center installation.
https://docs.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows-10
AWCC_5.4.7.0
OC controls
System
Version
Doghouse Reilly
2 Intern
2 Intern
•
395 Posts
0
December 15th, 2021 12:00
That's business as usual. My R9 has had versions of AWCC that couldn't tell it was on a Alienware computer! I only use it for the light color control, and right now that works fine so I am content.
I keep hoping they (Dell) will fix the program to be fully funtional, but in the meantime as far as I know; there is nothing that you can do.
Doghouse Reilly
2 Intern
2 Intern
•
395 Posts
0
December 16th, 2021 11:00
I see, so that explains why in days of old there was no error since there was no connection to the Microsoft Store. Why am I not surprised that Microsoft was involved in an constant error code.
Glad you actually got a odd but reasonable response from Dell and thank you for sharing.
Sparky1964
101 Posts
0
December 16th, 2021 17:00
Interesting. I appreciate this info.
pbug56
13 Posts
0
May 10th, 2023 12:00
What bothers me about this is that 20 minutes later the system bsod. Makes me wonder if there's not more to this.