Started a few months ago, and has been steadily getting worse. Checking the Reliability History program has revealed an issue with AWCC.exe (alienware command center) being the cause of pretty much every single crash since. Copied from the Reliability History report. Please help, I crashed three times while just writing this report.

Source

AWCC

Summary

Stopped working

Date

‎9/‎7/‎2020 8:56 AM

Status

Report sent

Description

Faulting Application Path: C:\Program Files\WindowsApps\DellInc.AlienwareCommandCenter_5.2.91.0_x64__htrsf667h5kn2\AWCC.exe

Problem signature

Problem Event Name: MoAppCrash

Package Full Name: DellInc.AlienwareCommandCenter_5.2.91.0_x64__htrsf667h5kn2

Application Name: praid:App

Application Version: 5.2.91.0

Application Timestamp: 5f0f0d58

Fault Module Name: combase.dll

Fault Module Version: 10.0.18362.997

Fault Module Timestamp: ec78388d

Exception Code: 80004003

Exception Offset: 000000000006746a

OS Version: 10.0.18362.2.0.0.768.101

Locale ID: 1033

Additional Information 1: 81f3

Additional Information 2: 81f35c835a3f99618d1ebce634c11168

Additional Information 3: ecd3

Additional Information 4: ecd35b49268db814f30485a95d72c342

Extra information about the problem

Bucket ID: c5e06e2949eb5b6b064b6cdc01b04b3c (1606497384264649532)

It was Alienware Command Center, I uninstalled it and now everything is working completely fine. Thank you for the help!

No problem. If it i something you want to reinstall, you can obtain it from the dell website, but I dont see any real use for this utility, especially considering the instability it introduced.

These 2 bugchecks are quite old:

Debug session time: Tue Jul 7 07:29:16.469 2020 (UTC - 4:00) which threw SYSTEM_SERVICE_EXCEPTION (3b). The specific exception was c0000006, which translates to C0000006 (In-page I/O error) and this is usually related to network IO. The system bugchecked performing some registry work (read from the bottom up):

11: kd> k

Child-SP RetAddr Call Site

00 ffffa9857217dab8 fffff8030ddd41e9 nt!KeBugCheckEx

01 ffffa9857217dac0 fffff8030ddd363c nt!KiBugCheckDispatch+0x69

02 ffffa9857217dc00 fffff8030ddcb18f nt!KiSystemServiceHandler+0x7c

03 ffffa9857217dc40 fffff8030dc89855 nt!RtlpExecuteHandlerForException+0xf

04 ffffa9857217dc70 fffff8030dc8ddee nt!RtlDispatchException+0x4a5

05 ffffa9857217e3c0 fffff8030ddd431d nt!KiDispatchException+0x16e

06 ffffa9857217ea70 fffff8030ddd0503 nt!KiExceptionDispatch+0x11d

07 ffffa9857217ec50 fffff8030e280022 nt!KiPageFault+0x443

08 ffffa9857217ede8 fffff8030e22033f nt!HvpGetCellPaged+0xa2

09 ffffa9857217edf0 fffff8030e21ec39 nt!CmpDoCompareKeyName+0x2f

0a ffffa9857217ee40 fffff8030e210b6a nt!CmpWalkOneLevel+0x709

0b ffffa9857217ef50 fffff8030e20dbd4 nt!CmpDoParseKey+0x9fa

0c ffffa9857217f1f0 fffff8030e20babf nt!CmpParseKey+0x274

0d ffffa9857217f410 fffff8030e209f21 nt!ObpLookupObjectName+0x78f

0e ffffa9857217f5d0 fffff8030e21343c nt!ObOpenObjectByNameEx+0x201

0f ffffa9857217f710 fffff8030e2132bd nt!ObOpenObjectByName+0x5c

10 ffffa9857217f760 fffff8030e2152df nt!CmOpenKey+0x29d

11 ffffa9857217f9c0 fffff8030ddd3c15 nt!NtOpenKeyEx+0xf

12 ffffa9857217fa00 00007ffb25d3e3c4 nt!KiSystemServiceCopyEnd+0x25

13 000000b1c0e7e038 0000000000000000 0x00007ffb`25d3e3c4

When I see this I usually suspect reg filters for 3rd party antivirus. The other dump eludes to this:

Debug session time: Mon Jun 29 23:39:11.571 2020 (UTC - 4:00) - REGISTRY_FILTER_DRIVER_EXCEPTION (135). The specific exception was also c0000006. In this case, though, I see Windows Defender doing the reg filtering (WdFilter.sys):

7: kd> k

Child-SP RetAddr Call Site

00 ffffcd04e030cdd8 fffff8054da281e4 nt!KeBugCheckEx

01 ffffcd04e030cde0 fffff8054d99c219 nt!CmpCallbackFatalFilter+0x24

02 ffffcd04e030ce20 fffff8054d39d389 nt!CmpCallCallBacksEx$filt$1+0x19

03 ffffcd04e030ce50 fffff8054d3cb18f nt!_C_specific_handler+0xa9

04 ffffcd04e030cec0 fffff8054d289855 nt!RtlpExecuteHandlerForException+0xf

05 ffffcd04e030cef0 fffff8054d28ddee nt!RtlDispatchException+0x4a5

06 ffffcd04e030d640 fffff8054d3d431d nt!KiDispatchException+0x16e

07 ffffcd04e030dcf0 fffff8054d3d0503 nt!KiExceptionDispatch+0x11d

08 ffffcd04e030ded0 fffff8054d880022 nt!KiPageFault+0x443

09 ffffcd04e030e068 fffff8054d82033f nt!HvpGetCellPaged+0xa2

0a ffffcd04e030e070 fffff8054d81ec39 nt!CmpDoCompareKeyName+0x2f

0b ffffcd04e030e0c0 fffff8054d810b6a nt!CmpWalkOneLevel+0x709

0c ffffcd04e030e1d0 fffff8054d80dbd4 nt!CmpDoParseKey+0x9fa

0d ffffcd04e030e470 fffff8054d80babf nt!CmpParseKey+0x274

0e ffffcd04e030e690 fffff8054d809f21 nt!ObpLookupObjectName+0x78f

0f ffffcd04e030e850 fffff8054d81343c nt!ObOpenObjectByNameEx+0x201

10 ffffcd04e030e990 fffff8054d8132bd nt!ObOpenObjectByName+0x5c

11 ffffcd04e030e9e0 fffff8054d895a62 nt!CmOpenKey+0x29d

12 ffffcd04e030ec40 fffff8054d3d3c15 nt!NtOpenKey+0x12

13 ffffcd04e030ec80 fffff8054d3c61c0 nt!KiSystemServiceCopyEnd+0x25

14 ffffcd04e030ee18 fffff80551fc4204 nt!KiServiceLinkage

15 ffffcd04e030ee20 0000000000000000 WdFilter+0x34204

I would start by updating or removing any unnecessary network components/drivers. Among them:

Rivet Networks Driver Suite UWD

1: kd> lmDvmKfeCo10X64

Browse full module list

start end module name

fffff8030b8b0000 fffff8030c9c8000 KfeCo10X64 (deferred)

Image path: \SystemRoot\System32\drivers\RivetNetworks\Killer\KfeCo10X64.sys

Image name: KfeCo10X64.sys

Browse all global symbols  functions  data

Timestamp:        Thu Mar 21 16:31:47 2019 (5C93F4B3)

Qualcomm Atheros Driver

11: kd> lmDvmQcamain10x64

Browse full module list

start end module name

fffff80327c00000 fffff80327e8c000 Qcamain10x64 (deferred)

Image path: \SystemRoot\System32\drivers\Qcamain10x64.sys

Image name: Qcamain10x64.sys

As I noted in my initial reply, it is possible the AiienWare service could be crashing the OS since we are seeing a service type bugcheck in the first dump. Try to uninstall it.

That said, if you have a more recent dump, that would help narrowing down if the cause remains reg functions/network IO.

It is getting worse, and crashing even in Safe Mode. I was lucky to even be able to upload the .dmp files - the computer wont stay stable enough to even let me send the link on it, so i am currently sending it via my Ipad.

https://drive.google.com/file/d/1kf3T-PyBmPU6fDzHCIfSA19yzPemfa7t/view?usp=drivesdk

Hi and thanks for reaching out. My name is William. I'm a Windows technical expert. I'll be happy to help you out today.

Normally, user-mode crashes (that is, program crashes) do not spill into the kernel and cause it to bugcheck, with some exceptions. It just be that you are correlating the system bugchecks with the only thing that is being reported by he Reliability History.

When your system crashes it will create a dump file(s) in C:\Windows\Minidumps. I can analyze those files for the potential cause of the system halting. Can you upload the .dmp file(s) to OneDrive, Google Drive, Dropbox or some other file sharing service and share the link here?