Continued BSOD saga

tns1 · 17 Nov 2022

cwsink said:

Those types of logs are not something I've spent time investigating but a file going missing could also be a symptom of a drive intermittently going offline.

I was able to find the files in that error event report. tiworker.exe and the dll components are present and not corrupted, and is suggestive of a power or connection issue. OTOH I'd expect a more random set of error events than I see.

My existing servicing stack components including 5 versions of tiworker, were updated every couple of months via MS Updates in 2022. During that time the error events for tiworker have occurred pretty much every 30 days like clockwork, and not correlated with the update of those particular files. Whatever was going on with tiworker, it doesn't seem random enough to be explained by HW error.

ubuysa · 19 Nov 2022

It's risky making judgements based on only one dump (if you can get more dumps then please upload them) but the one you have is pointing at the NVMe drive as the source of the BSOD. The call stack looks as follows (read it from bottom up)...

[code=rich]
0: kd> knL
# Child-SP RetAddr Call Site
00 fffffb0a`fb498388 fffff807`2c7b667c nt!KeBugCheckEx
01 fffffb0a`fb498390 fffff807`2c7b71d9 nt!WheaReportHwError+0x3ec
02 fffffb0a`fb498470 fffff807`2c7b72f5 nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
03 fffffb0a`fb4984a0 fffff807`30493981 nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
04 fffffb0a`fb498500 fffff807`3048cd50 storport!StorpWheaReportError+0x9d
05 fffffb0a`fb498590 fffff807`3045f0fc storport!StorpMarkDeviceFailed+0x358
06 fffffb0a`fb498820 fffff807`3051edb6 storport!StorPortNotification+0x91c
07 fffffb0a`fb4988f0 fffff807`3051f574 stornvme!NVMeControllerInitPart2+0x226
08 fffffb0a`fb498970 fffff807`3051e4af stornvme!NVMeControllerReset+0x124
09 fffffb0a`fb4989a0 fffff807`3048a446 stornvme!NVMeControllerAsyncResetWorker+0x3f
0a fffffb0a`fb4989d0 fffff807`2c499645 storport!StorPortWorkItemRoutine+0x46
0b fffffb0a`fb498a00 fffff807`2c452b65 nt!IopProcessWorkItem+0x135
0c fffffb0a`fb498a70 fffff807`2c471d25 nt!ExpWorkerThread+0x105
0d fffffb0a`fb498b10 fffff807`2c600778 nt!PspSystemThreadStartup+0x55
0e fffffb0a`fb498b60 00000000`00000000 nt!KiStartSystemThread+0x28
[/code]

The storport.sys driver is the Microsoft high-level storage driver. In the call stack you can see the stornvme!NVMeControllerReset function call, indicating an issue with the NVMe controller, and later you can see the storport!StorpMarkDeviceFailed which is the NVMe I/O failing. That leads to the WHEA (Windows Hardware Error Architecture) function calls and the bugcheck.

I've seen many niggly issues caused by a poorly seated M.2 drive, so I'd suggest you remove and reseat that drive and see whether that stops the BSODs. If not then I'd look for a diagnostic tool for the M.2 NVMe SSD and check the drive out.

tns1 · 21 Nov 2022

OK, so I got another BSOD again without a dmp file or wer file. This time running sfc /scannow did say it fixed something. I was able to reseat the m.2 fairly easily by first removing the gpu card.

After that I reran all the usual scans; sfc, dism, chkdsk, ssd full diagnostics - all clean. It will need to last a month or two without faulting before I celebrate.

I noticed in the CBS log that tiworker and trusted installer seem to be involved for every bootup, so these get a lot of use. If the 'every 30 days' fault is still present I'd expect it again early december.

I took a look at two other W10 PCs using appcrashview. These systems had no obvious problems, yet had lots of recorded error events including tiworker. My guess is that every time any system stack component is updated, it generates an error. It appears to be pretty normal for W10.

ubuysa · 23 Nov 2022

TiWorker is the Trusted Installer program, part of Windows Update, so it might be worth running the Update troubleshooter. Go to Settings > Update & Security > Troubleshoot > Additional Troubleshooters > Windows Update and run that troubleshooter.

It might also be worth resetting the update system using the script here: Reset Windows Update in Windows 10

moriya · 25 Nov 2022

wow, same problem here. My dump file is almost same as yours. Im using a dell laptop.

Last year it was just game crashed and "Hardware D: Access denied error" popped when I try to access the game directory.
Sometimes a reboot could solve it, sometimes not then i reseated the ssd, ram.
And it seemed be solved since I swapped my two ssd location maybe, I don't remember.

In the past months this WHEA bsod became more and more frequent. And now it crashes everyday.
It's surprising that it seems crash only 1 time each day. After reboot everything goes well again.
I don't think the reason is overheat because today it crashed again when I was only browsing.

- - - Updated - - -

btw the boot order sometimes will be changed after bsod. It will try to boot from network first

- - - Updated - - -

I try to use Smartmontool to diagnostic my two samsung nvme ssd but it only shows "NVMe successfully opened", seems like they don't support self test.
the Samsung Magician tool can't diagnostic them, either.

ubuysa · 25 Nov 2022

moriya said:

wow, same problem here. My dump file is almost same as yours. Im using a dell laptop.

Last year it was just game crashed and "Hardware D: Access denied error" popped when I try to access the game directory.
Sometimes a reboot could solve it, sometimes not then i reseated the ssd, ram.
And it seemed be solved since I swapped my two ssd location maybe, I don't remember.

In the past months this WHEA bsod became more and more frequent. And now it crashes everyday.
It's surprising that it seems crash only 1 time each day. After reboot everything goes well again.
I don't think the reason is overheat because today it crashed again when I was only browsing.

- - - Updated - - -

btw the boot order sometimes will be changed after bsod. It will try to boot from network first

- - - Updated - - -

I try to use Smartmontool to diagnostic my two samsung nvme ssd but it only shows "NVMe successfully opened", seems like they don't support self test.
the Samsung Magician tool can't diagnostic them, either.

It's not polite to hijack someone else's thread, plus it makes determining who we're responding to tricky. Please start your own thread and add a link to this one so we know you have the same issue.

moriya · 25 Nov 2022

ubuysa said:

It's not polite to hijack someone else's thread, plus it makes determining who we're responding to tricky. Please start your own thread and add a link to this one so we know you have the same issue.

I didn't mean to hijack thread and it's not hijack because I'm posting related contents.
I think it's addtional info and might be useful for someone want to help.

ubuysa · 25 Nov 2022

moriya said:

I didn't mean to hijack thread and it's not hijack because I'm posting related contents.
I think it's addtional info and might be useful for someone want to help.

Apologies if I misunderstood, I thought you were reporting a similar problem.

moriya · 02 Dec 2022

I reseated my ssd and dram meticulously last week and the bsod never happened again.
I suggest you do it too.

tns1 · 28 Dec 2022

So it has been over a month since reseating the SSD card and no new BSODs! I am not breaking out in celebration just yet, but I am chilling the champagne.

Update: Just shy of two months trouble free operation, so re-seating the NVM is indeed the solution.