Well, we all know that when a library method crashes, we blame the caller. It can't be the library's fault, the user simply called it the wrong way. So, simil

Well, we all know that when a library method crashes, we blame the caller. It can't be the library's fault, the user simply called it the wrong way. So, similarly, it is Windows fault that it sent some series of commands that caused the poor innocent SSDs to be invisible to BIOS until power cycle. Absolutely no fault of the SSD. None.