Microsoft should rename Windows’ Reliability Monitor to Unreliability Monitor.
This isn’t too unusual for Windows 10, is it?
I’ve put Oracle Virtualbox and Cyberlink Power2Go back on, because it’s becoming more apparent that Windows 10 is incompatible with my hard drives in certain circumstances. It’s always when a drive (including a phone set up as a drive) is accessed that the system BSODs. It may also be a USB incompatibility. To be on the safe side, I have unplugged one of the two external drives I use.
The Microsoft technician has finally given up and asked I do a clean install. As if I have the time—the last time I did that was on an Imac: it took days to get all the OS X updates and the software up and running again. Bwv848 at Bleeping Computer is, like me, determined. I’ll do a memtest (their latest suggestion) when I get a chance.
Just another day using Windows 10 then.
PS.: Since the post: as my settings window would not come up (another fault of Creators fall), I deleted everything out of C:\Users\[username]\AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe. That was solved. I also went to Intel to download SetupChipset.exe. Not saying these are solutions to the original cause, and I was largely away from the computer for Sunday. However, I have a real suspicion that, because the computer often BSODs when Explorer (or something relying up on it) is open, there are hard-drive drivers that are failing despite, according to Device Manager, being up to date. One of the modules regularly affected is ntdll.dll, something the Reliability Monitor revealed.—JY