Tweet
would point to the old m.2 SSD by the looks of things.
exactly what/why - heck, that’s anyone’s guess.
I seem to recall many 2.5" SSD’s ago that I had something with the same outcome, weird shite happening, no logical explanation, changed the SSD, all good.
my uneducated guess is it’s related to the NAND cells in the m.2 drive being faulty and Windows not being able to recover from whatever error they were reporting.
any chance you have SMART values for that dodgy drive?
exactly what/why - heck, that’s anyone’s guess.
I seem to recall many 2.5" SSD’s ago that I had something with the same outcome, weird shite happening, no logical explanation, changed the SSD, all good.
my uneducated guess is it’s related to the NAND cells in the m.2 drive being faulty and Windows not being able to recover from whatever error they were reporting.
any chance you have SMART values for that dodgy drive?
Comment