31–33 of 33 posts
Earlier quoted context omitted.
while not root cause, wouldn’t a module having corrupted memory still be an issue with either the OS (for not protecting it) or the module (for not sanitizing input)?
No, because this would be kernel level code, so anything else running in the kernel (other drivers) could stomp on your memory and you couldn't do anything about it. No OS protections here.
On a possibly related issue, is this the same thing that cause the 'USB drive is still in use' message when you try to eject a USB drive even when every application is closed? If so, does anyone know a fix for it?
So there is no fix, because there is nothing to fix. If you remove the device before the OS tells you you can, you risk missing data or corruption.
But they can't be bothered to tell which process is holding it, not even a damn PID. C'mon guys, bare minimum here, and this issue has been there for decades. It's great you added file locksmith to powertoys but that should be a built in OS feature for many, many years now.