cthombor

Thanks for the kind offer to analyse my memory dump. I'm now trying to figure out why I didn't get a memory dump from my latest crash (last night) -- even though after reading your response I had adjusted the pagefile size greatly upwards from its system-managed (and strangely low) value of about 1.6 GB. One possibility for the missing fulldump last night is that there wasn't enough battery left to create it. (I had left my laptop sleeping while I slept, but not plugged in, and it had a dirty shutdown sometime before I got up.) However... I didn't see any minidump either, so *maybe* there's some problem with my SSD firmware (as darkly suggested in the checklist at https://answers.microsoft.com/en-us/windows/forum/windows_10-update/bsod-finding-and-fixing-them/1939df35-283f-4830-a4dd-e95ee5d8669d. However... my laptop's mfr Lenovo isn't suggesting any SSD firmware update to what they shipped with my ThinkPad 13 2nd Gen. Well it's crashing only about once a week, and only when I let it sleep, so it's not too hard to avoid -- I have other things to do in my life than diagnose this BSOD! When I get a chance: I'll dig out the make & model # for the SSD in my laptop, to see if its manufacturer is offering new firmware. <flame>There are always so many unrelated errors and warnings to investigate, whenever a Win10 box is misbehaving! I'm *pretty* sure my BSOD crashes are not related to the 1460 errors (code 10016) thrown since 27 July 2018 by RuntimeBroker.exe, as my googling suggests these are sort-of-normal for any Win10 box, are a real nuisance to trace, and would require regedit brainsurgery to avoid. My best guess is that my chatty HP printer is periodically asking my laptop to do something that causes these errors. Grumble!</flame>

I have been having BSOD issues for weeks... just saw this warning on my Chrome after my latest restart. I had been suspecting Cisco AnyConnect VPN (which throws many error messages during system boot, due to a carelessly-configured .msi from my enterprise that isn't suitable for my laptop when it is started away from work); but I'm now adding Chrome+ESET to my suspect-list. Never a dull moment with Windows. Strange to read that Google had been working with ESET on this security feature for its Chrome browser, according to https://www.eset.com/int/about/newsroom/press-releases/products/eset-works-with-google-to-halt-dangerous-malware/.

I have been having BSOD issues for weeks... just saw this warning on my Chrome after my latest restart. I had been suspecting Cisco AnyConnect VPN (which throws many error messages during system boot, due to a carelessly-configured .msi from my enterprise that isn't suitable for my laptop when it is started away from work); but I'm now adding Chrome+ESET to my suspect-list. Never a dull moment with Windows.