SSD is working with my laptop. However, the file explorer is not responding from time to time and i have to restart it, lol
This happened to me exactly once till I restarted the machine and it never happened again. I honestly don’t know what happened that caused that but I recommend you reseat your SSD
Problem solved. The WD nvme SSD was failing, took awhile to figure out what was going on. Replaced it with a Kingston one. All good now.
1 Like
Just a final note… my WD failed, causing the problems on my Framework 13 12 gen laptop. I purchased a Kingston nvme SSD and have a sneaking suspicion that WD was not the best choice when first I bought my old Farmework 13 11 Gen. Will see over time, but the failure of the WD was earlier than I expected for an SSD.
I have a take that WD is never the best choice. It’s not a coincidence that WD’s drives are always a bit cheaper. The history is full of instances where WD has cut too many corners. I don’t trust the brand at all at this point.
Yes, my bad. I had the original Framework 13 11gen, along with all their firmware. Short list: bad motherboard, replaced, bad 16 stick ram, replaced. Bought another 16 to get to 32. WDS500G3X0C-00SJG0 500.11 GB. Much fun soldering the battery issue!
The motherboard from the 11gen went bad too. I bought the motherboard for Framework 13 12th Gen Intel(R) Core™ i7-1260P, Rev. 39427 and hoped all would be good, but that was when booting up became a game of musical chairs. Finally with support help we decided it was the nvme SSD from WD that was bad and so it was after clearing away all the other possible defects that could have caused my blue screen of death experience.
When it was failing CrystalDisk said the WD was 95% good. As I read from other posts, that is bad with WD. My new SSD is from Kingston. Smaller (as I was strapped for bigger) and 100% good and so far, much happier.