I recently updated my system to KB5063878, which apparently has been linked to SSD failures, but I wasn't aware of this at the time. During this update, I transferred two 50GB files from my phone to my WD Blue SN5000 NVMe drive (which isn't my OS drive) and also installed a 120GB game without any issues. Just to be safe, I later reverted back to KB5062553. However, after copying nearly 100GB of files to the drive today and verifying a game on Epic Games, my cursor started lagging, and I ended up with a BSOD that restarted my PC so quickly I couldn't catch the error code. When my system booted up, it went directly to the boot menu, and my OS drive, a Lexar NM620 250GB, was missing from the list. I tried exiting the menu but couldn't get past it, so I powered off the PSU and restarted, which thankfully brought me back to Windows. The Event Logger noted an unexpected reboot happened at 8:34, but there's no log entry from that time, making it hard to diagnose the problem. Could this issue be a side effect of the KB5063878 update, possibly corrupting the SSD controller even after reverting to the earlier update?
2 Answers
It seems like you've hit a known issue related to that KB5063878 update, especially with NVMe drives. The BSOD and the temporary disappearance of your OS drive likely stem from some corruption that could have been introduced while that update was active. The good news is you might be able to resolve this, but first, I’d recommend backing up your data on the WD Blue SN5000, as it’s showing signs of instability. Make sure to also check for any firmware updates for the NVMe SSD; they can be crucial in preventing further issues. Until you're sure everything's stable, avoid heavy file transfers. You could think about reinstalling the KB5063878 update if your system needs it, just make sure to back up your data before proceeding.
I’d second what DataDiver12 said! It's possible that controller-level issues were introduced with the update, and reverting doesn’t always fix those. As for dump files, if you can get into Windows, try to locate any crash logs in the C:WindowsMinidump folder. Those dump files could provide valuable insight into what went wrong. If you find any, zip them up and consider sharing them for more tailored help! If not, you might need to adjust the dump settings to ensure more are created in the future.
Related Questions
Lenovo Thinkpad Stuck In Update Loop Install FilterDriverU2_Reload