Windows 10 May 2019 Update Breaks Nvme Ssds For Many

Many Windows 10 users revealed that Samsung NVME SSDs are subject to WHEA errors on Ryzen 3000 / X570 chipset.

Users described this problem as follows:

Basically, users never got notified whenever their Samsung NVME SSDs encountered errors and corruptions. More so, they could only find that out if they manually checked for errors, or when their systems crashed altogether.

I’ve found out about these WHEA warnings in the event log by chance while browsing this subreddit. […] I checked my event log and there were 87(!) WHEA event 17 log entries. Afterwards I commenced a system file integrity check using the “sfc /scannow” in an elevated command prompt and it spewed out a list of more than 3000 corrupted system files and registry entries

Initially, it was thought that the cause of the problem was related to driver issues:

Further investigations eventually revealed that wasn’t the case at all. The problem is nothing more but an interference caused by Windows 10 May 2019 Update issues.

The root cause of this strange ordeal seem to be current drivers for devices that stress the motherboards PCI-E interface (like graphics cards and nvme ssds). These drivers seem to not have taken some obscure difference in operating mode (or perhaps simply a bug) for when these, normally PCI-E 3.0 devices are plugged into a PCI-E 4.0 capable motherboard.

As far as users are concerned, some stated that one solution might be to run DISM:

Can confirm that I have this after a Windows update to defender. DISM and sfc fixed it. The WHEA errors are unrelated to it though.

Windows 10 v1903 causes high disk usage on SSD systems
Windows 10 Task Manager now displays HDDs and SSDs separately

If the advices above haven’t solved your issue, your PC may experience deeper Windows problems. We recommend downloading this PC Repair tool (rated Great on TrustPilot.com) to easily address them. After installation, simply click the Start Scan button and then press on Repair All.

Still having issues? Fix them with this tool: