- Jun 30, 2004
- 15,722
- 1,455
- 126
Here's a link to a fairly recent thread over in "Operating Systems" forum:
Event Log Errors
There is a history of peculiar Windows 10 (and Windows 8.1!) Event ID 219 warnings at boot-time. Some involve USB devices; others suggest SATA devices. The source is "Kernel PnP." The message thrown is "The driver \Driver\WudfRd failed to load for the device . . . . . . . { . . . [key] . . . } . . . . "
This and Distributed COM errors which require changing Permissions for the indicated registry keys seem common to folks using Windows 10, and the 219 warnings have caused frustration to people tracing back to Windows 8. So we attempt to clean up -- or at least identify -- the causes.
The Event 219 "WudfRd" errors seem benign. For me, they pointed to two identical HGST TravelStar drives I have for media recording/storage, and image backup. So that one went on the back-burner for a while, and I may just leave it alone unless I can discover the proper tweaks. And for my indications, it seems to show a timing problem loading the drives' driver at boot-time. After boot-up, the drives test out just fine in every respect.
But I stumbled onto something else.
I had initially "experimented" with a 960 EVO 250GB NVMe M.2 PCIEx4 drive and configuration. It was solely intended for caching regular spinner drives, and the "experiment" mostly worked -- at least for one OS at a time in my dual-boot system.
The NVMe driver for the 960 EVO and PRO from Samsung (version 2.1?) is exactly the same as far as I can tell. But I'd decided to swap in a 960 PRO drive after removing the EVO -- removed for the time being, anyway.
So this morning, in the course of reviewing other indications, I happened to look at my Device Manager tree under "Disk Drives." With the PRO drive running in the system for more than a week or so, I discover that it is indicated as "Samsung 960 EVO 250GB."
I had also noticed that CrystalDiskMark results fell significantly short by 500+ MB/s on the Pro. I would be lucky to get a sequential read score of 2,900 or just under 3,050.
I had also suspected my PRO drive performance was under par. After I "uninstalled" the entry for the EVO 250GB and rebooted as required, of course I would expect that the PRO drive would be properly recognized when Windows reloads the driver. And it did just that.
And now CrystalDiskMark offers up a sequential read score within 100 MB/s of spec.
Meanwhile, the key-code for one of my 219 warnings has changed, while the other one remains the same. These keys -- searched in Regedit -- point to the two spinners I mentioned.
The plot thickens! Before I can sort out anything else of particulars about this matter of the EVO "ghost" drive, I can only suggest to people that swapping these 960 drives in and out should merit some attention to how they show up in Device Manager. Can I say exactly why? Not yet. Not yet.
But I'd suggest uninstalling from Device Manager the drive chosen for removal before you swap in the replacement. This may be an issue specific to the 960 PRO and EVO, I can't say.
Event Log Errors
There is a history of peculiar Windows 10 (and Windows 8.1!) Event ID 219 warnings at boot-time. Some involve USB devices; others suggest SATA devices. The source is "Kernel PnP." The message thrown is "The driver \Driver\WudfRd failed to load for the device . . . . . . . { . . . [key] . . . } . . . . "
This and Distributed COM errors which require changing Permissions for the indicated registry keys seem common to folks using Windows 10, and the 219 warnings have caused frustration to people tracing back to Windows 8. So we attempt to clean up -- or at least identify -- the causes.
The Event 219 "WudfRd" errors seem benign. For me, they pointed to two identical HGST TravelStar drives I have for media recording/storage, and image backup. So that one went on the back-burner for a while, and I may just leave it alone unless I can discover the proper tweaks. And for my indications, it seems to show a timing problem loading the drives' driver at boot-time. After boot-up, the drives test out just fine in every respect.
But I stumbled onto something else.
I had initially "experimented" with a 960 EVO 250GB NVMe M.2 PCIEx4 drive and configuration. It was solely intended for caching regular spinner drives, and the "experiment" mostly worked -- at least for one OS at a time in my dual-boot system.
The NVMe driver for the 960 EVO and PRO from Samsung (version 2.1?) is exactly the same as far as I can tell. But I'd decided to swap in a 960 PRO drive after removing the EVO -- removed for the time being, anyway.
So this morning, in the course of reviewing other indications, I happened to look at my Device Manager tree under "Disk Drives." With the PRO drive running in the system for more than a week or so, I discover that it is indicated as "Samsung 960 EVO 250GB."
I had also noticed that CrystalDiskMark results fell significantly short by 500+ MB/s on the Pro. I would be lucky to get a sequential read score of 2,900 or just under 3,050.
I had also suspected my PRO drive performance was under par. After I "uninstalled" the entry for the EVO 250GB and rebooted as required, of course I would expect that the PRO drive would be properly recognized when Windows reloads the driver. And it did just that.
And now CrystalDiskMark offers up a sequential read score within 100 MB/s of spec.
Meanwhile, the key-code for one of my 219 warnings has changed, while the other one remains the same. These keys -- searched in Regedit -- point to the two spinners I mentioned.
The plot thickens! Before I can sort out anything else of particulars about this matter of the EVO "ghost" drive, I can only suggest to people that swapping these 960 drives in and out should merit some attention to how they show up in Device Manager. Can I say exactly why? Not yet. Not yet.
But I'd suggest uninstalling from Device Manager the drive chosen for removal before you swap in the replacement. This may be an issue specific to the 960 PRO and EVO, I can't say.
Last edited: