Continued BSOD saga

I have been getting random BSODs over the last few months ranging from once every few weeks to daily. Every time I think I have fixed the issue, it will pop up again after a week or so. Other than a couple of gaming app crashes, the BSODs happen during a light load, maybe just the browse at most. At its worst I was getting a BSOD shortly after boot before any activity.

As a diagnostic I have repeatedly run:
mbam, eset antivirus - all clean.
sfc, dism, chkdsk - all clean.
memtest86 - no errors.
SSD full scan - clean.

I have cleaned the PC fans/interior & reseated DRAM, GPU, connectors, replaced the CMOS battery.
Updated Nvidia driver to the latest.
Audio drivers appear to be the latest offered from Gigabyte.
Ran the Furmark test for > 10min, no issues. GTX 970 ran 99% load 70fps 75C max. All fans working.

Each BSOD will typically just hang without collecting data even though I have enabled the minidump feature.
I have used the V2 log collector each time but only once was it able to capture a dmp file.

Recent:

Ran HWmonitor - no unusual CPU temps (typ < 30C, never > 40C).
Removed unused hidden devices in device manager.
Using AppCrashViewer I am able to view some of my error events such as:
hardware error related to watchdog,
unexpected shutdown,
windowsservicingfailure,
appcrashes

Hard to tell which of these is relevant. Even though most of these error events list a dmp file, no such files exist. It seems these files are never created or automatically deleted after a short time.

Updated links:
https://www.dropbox.com/s/s4slm02v11...18-01.dmp?dl=0
https://www.dropbox.com/s/6u6jea06d1...21%29.zip?dl=0
https://www.dropbox.com/s/66d5urdmt7...peccy.txt?dl=0

This one dmp file seemed to be related to this error event:

Event[3027]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2022-10-18T17:46:29.1050000Z
Event ID: 1001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: DESKTOP-GAZ170
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000010, 0xffffdc8f2bcbd028,
0xffffdc8f2077293c, 0xffffdc8f226501a0). A dump was saved in: C:\Windows\Minidump\101822-4218-01.dmp. Report Id:
603dbf16-4020-44bc-9cda-f4385a3b685b.

What can you tell me?

Malneb said:

0x00000124

means hardware failure but these are a grain of salt tbh because you passed memtest, if you have overclocked anything then this could be from not enough voltage.

- - - Updated - - -

Also could not download the Dropbox file for some reason

No overclocking, and I would have thought that Furmark and memtest would reveal any heat or voltage issues.
I have re-created the links so downloads should work now.

cwsink said:

I've seen numerous cases where a m.2 drive would intermittently reset and the system would then attempt to add the drive back. That doesn't seem to be something any tool I'm aware of can detect. Reseating is often enough to stop the crashes in such cases. I've always assumed it was caused by heat expansion/contraction with an iffy connection since m.2 drives are usually so close to the GPU and CPU.

Please let us know how it goes.

Almost a month since that bugcheck so I can always hope my cleanup efforts and the various updates took care of it. I'm unwilling to reseat the m.2 nvm unless I have more problems since it is tricky to get at without removing the heat sink.

- - - Updated - - -

Using the AppCrashViewer utility I see I had several recent TiWorker.exe error events. There are 14 instances of TiWorker.exe on my PC, and each error event cites a different instance and claims a different missing component. I never looked at these reports before. Looking further, it seems TiWorker.exe along with its parent process trustedinstaller.exe are key components of windows updates, which I've had no problem with. I found that the certificate for c:\windows\servicing\trustedinstaller.exe has expired. Is this something to be fixed or left alone?

Latest event:
-------------------------------------------------
Version=1
EventType=WindowsServicingFailureInfo
EventTime=133124433470122486
ReportType=1
Consent=1
UploadTime=133124433472011949
ReportStatus=268435456
ReportIdentifier=f98ac71c-fdb7-4911-9ef6-cf3de9ee444d
Wow64Host=34404
OriginalFilename=TiWorker.exe
AppSessionGuid=00000ccc-0000-00b9-1526-f802f7f3d801
TargetAppId=W:000660b616f904ae05c215ab9ded5bcc9eda00000904!0000002dfcdd72ea63a4337f0d5bc79a683300189 9dd!TiWorker.exe
TargetAppVer=2041//03//18:07:02:22!429ab!TiWorker.exe
BootId=4294967295
TargetAsId=572
IsFatal=4294967295
EtwNonCollectReason=1
Response.BucketId=INVALID_REQUEST
Response.type=4
Sig[0].Name=OsVersion
Sig[0].Value=10.0.19041.2180:1
Sig[1].Name=Message
Sig[1].Value=0x800F0984 0x800F0984 Matching binary: LxssManager.dll missing for component: amd64_microsoft-windows-lxss-manager_31bf3856ad364e35_10.0.19041.2251_none_f32397a67ff1fe9e
Sig[2].Name=Callsite
Sig[2].Value=楆敬›瑳牯汥祡畯⹴灣⡰㘱㐹
*潃灭湯湥却潴敲㨺剃睡瑓牯䱥祡畯㩴䠺摹慲整楆敬獕湩䙧牯慷摲湁剤癥牥敳敄瑬獡
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.19043.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=19043
OsInfo[3].Key=ubr
OsInfo[3].Value=2130
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=221871279
OsInfo[15].Key=osinsty
OsInfo[15].Value=2
OsInfo[16].Key=iever
OsInfo[16].Value=11.789.19041.0-11.0.1000
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16342
OsInfo[19].Key=svolsz
OsInfo[19].Value=953
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=191206
OsInfo[22].Key=bldtm
OsInfo[22].Value=1406
OsInfo[23].Key=bldbrch
OsInfo[23].Value=vb_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.19041.2130.amd64fre.vb_release.191206-1406
OsInfo[30].Key=buildflightid
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[34].Key=fconid
OsInfo[35].Key=containerid
OsInfo[36].Key=containertype
OsInfo[37].Key=edu
OsInfo[37].Value=0
FriendlyEventName=WindowsServicingFailureInfo
ConsentKey=WindowsServicingFailureInfo
AppName=Windows Modules Installer Worker
AppPath=C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.2180_none_7e328fe47c714aab\TiWorker.exe
ApplicationIdentity=00000000000000000000000000000000
MetadataHash=-1459974649

Older events summary:
-----------------------------------------------
AppPath=C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1940_none_7dd80d767cb5c7b0\TiWorker.exe
Sig[1].Value=0x800F0984 0x800F0984 Matching binary: TSMSISrv.dll missing for component: amd64_microsoft-windows-t..-tsappsrv-component_31bf3856ad364e35_10.0.19041.2075_none_e3b0fcc6a79fa1ca

AppPath=C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1940_none_7dd80d767cb5c7b0\TiWorker.exe
Sig[1].Value=0x800F0984 0x800F0984 Matching binary: LxssManager.dll missing for component: amd64_microsoft-windows-lxss-manager_31bf3856ad364e35_10.0.19041.2006_none_f333c4247fe6c82e
AppView error events 20221113

AppPath=C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1790_none_7df2aec07ca10e81\TiWorker.exe
Sig[1].Value=0x800F0984 0x800F0984 Matching binary: wstorvsp.inf missing for component: amd64_dual_wstorvsp.inf_31bf3856ad364e35_10.0.19041.1806_none_3575bd8c71b3eb91

AppPath=C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\TiWorker.exe
Sig[1].Value=0x800F0984 0x800F0984 Matching binary: wvmbusr.inf missing for component: amd64_dual_wvmbusr.inf_31bf3856ad364e35_10.0.19041.1466_none_67a229cdb53fa195

AppPath=C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1371_none_7e1bd7147c8285b0\TiWorker.exe