Dell G3 3500 crashing randomly

Question

dell laptop suddenly crashing randomly, without overheating, v2 logs are here: https://drive.google.com/drive/folders/13WERrelR9dwJJnCakNXTw9gMx8YkW3Qg?usp=sharing

the only error and warning logs before the crash are:

Activation context generation failed for "C:\Program Files (x86)\Dell\UpdateService\ServiceShell.exe".Error in manifest or policy file "C:\Program Files (x86)\Dell\UpdateService\ServiceShell.exe.Config" on line 0. Invalid Xml syntax.

The description for Event ID 4096 from source Autodesk ComputeQueue cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

A provider, IntelMEProv, has been registered in the Windows Management Instrumentation namespace root\Intel_ME to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

Answer 1

Some of the log findings were:

a) Drive file system corruption

b) Registry database corruption

c) three unexpected shutdowns and restarts without reported BSOD

Plan: (make sure that these tests are run in sequence)

1)Test all of the drives:

a) Sea Tools for Windows Long Generic test

b) HD Tune Full Error scan

c) HD Sentinel Overview, Temperature, SMART

d) Chkdsk /b /v C: (run overnight while sleeping)

If the drive fails any of the above tests then backup files and replace the drive

2)If the drive passes all of the above tests then open a new thread to troubleshoot:

The configuration registry database is corrupt.

Event[48527] Log Name: System Source: Service Control Manager Date: 2024-05-21T22:38:00.7470000Z Event ID: 7005 Task: N/A Level: Error Opcode: N/A Keyword: Classic, User: N/A User Name: N/A Computer: DESKTOP-LSDE8HB Description: The LoadUserProfile call failed with the following error: The configuration registry database is corrupt.

Stage 1: Examining basic file system structure ... Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x13088f is already in use. Deleting corrupt attribute record (0x80, "") from file record segment 0x13088F.

Stage 2: Examining file name linkage ... Unable to locate the file name attribute of index entry 000000000003CA62 of index $I30 with parent 0x1f in file 0x44228. Deleting index entry 000000000003CA62 in index $I30 of file 1F. CHKDSK is scanning unindexed files for reconnect to their original directory. Recovering orphaned file wow64_microsoft-windows-userpowermanagement_31bf3856ad364e35_10.0.22621.2506_none_8d48ae4aacd8a96d_powrprof.dll_480be757 (44228) into directory file 1A1695. Recovering orphaned file wow64_microsoft-windows-userpowermanagement_31bf3856ad364e35_10.0.22621.2506_none_8d48ae4aacd8a96d_powrprof.dll_480be757 (44228) into directory file 1A1695. 2 unindexed files recovered to original directory. CHKDSK is recovering remaining unindexed files. Lost and found is located at \found.000

Drive: C: Free Space: 212.9 GB Total Space: 956.4 GB File System: NTFS Model: NX-1TB 2230

Drive: E: Model: PC SN530 NVMe WDC 512GB

Drive: G: Free Space: 202.2 GB Total Space: 956.4 GB File System: FAT32 Model: n/a

Answer 2

Hello,

According to your description, I suggest that you perform a clean boot to avoid third party software and service effect to check.

How to perform a clean boot in Windows - Microsoft Supports

Also check system event logs about event id 41 and 6008 to find detailed information if could be recorded.

Just like the bug check code.
Best Regards,Hania Lian============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.