The driver \Driver\WudfRd failed to load

Here we are in July, 2015, and still no response from Microsoft.  

WHAT THE HELL IS THE PROBLEM MICROSOFT?  HOW MANY SCREAMS DO YOU NEED TO HEAR BEFORE YOU FIX THIS???????Here we are again, Microsoft is unresponsive (nothing new there) and unhelpful (equally not new) on an issue that people have been complaining about since the beginning of Windows 8.1 - and nothing.THANK YOU FOR SHOWING YOU DON'T CARE ABOUT YOUR USERS.  AGAIN.

Hi BrimMichael,

-          After upgrading to Windows 8.1, did you update all the drivers on the computer?

Boot the computer in safe mode with networking and update all the drivers to check if this helps.

Windows Startup Settings (including safe mode): http://windows.microsoft.com/en-in/windows-8/windows-startup-settings-including-safe-mode

Drivers are updated occasionally. Ensure to install any pending updates to check if this helps. You may also look for optional updates related to this device and install those updates as well. Windows can update them automatically, or you can install the updated drivers yourself. It's important for you to have confidence in the updated drivers you install. Windows notifies you if it detects a suspicious or unsafe driver you shouldn't install.

Download and install drivers: http://windows.microsoft.com/en-in/windows-8/all-drivers

Reply with the status of the issue and we will be glad to offer our assistance.

Your reply is bloviated. You did not help towards a solution and you are obviously a Microsoft cheerleader. This is an issue that causes millions of people problems because of automatic reboots and BSODs. If you cannot help the situation you should avoid it.

Here is a link that will help - you can sue Microsoft for the wasted time that it causes in your life. Believe me after supporting Microsoft products for over 20 years and seeing the many reboots - incessant BSODs - they owe me about half a million dollars for wasted hours and my time!

https://techlick.com/index.php/tech-news-i/techlick/48-slashdot-1/23108-how-microsoft-lost-in-court-over-windows-10-upgrades

Let me start by saying that I am commenting on this thread using pure speculation, with regard to this event error.  I'm trying to find proof to back my theory written below, but it may take some time. My work day is hectic, and my test lab is usually being pounded with a work related problem.  So please just take this "best guess" of mine with a grain of salt.  But I do think the key to this, and some other strange Win8 behavior, lay within the new Fastboot (Hybrid-Shutdown) feature.

I've been seeing this same error (different hardware ID's of course) since day one of deploying Win8/8.1 on my network. On about 6 or 8 different machines (including my own, custom built PC at home) of various Mfg's and hardware configs. The only "constants" I've noticed between the affected PC's (and possibly all of us seeing this same Event Error) are these following things:

1. Windows 8/8.1
2. USB connected storage
3. The type of "Start Up" (full or Fastboot) which invokes this Error Event.

From what I can gather this problem has something to do with the Fastboot feature in Windows 8.1.  When a Windows 8.1 PC is shutdown (normal situation, no pending or completed updates/hardware installs, or during Restarts) Fastboot is used, and a pagefile is written out of RAM containing driver/hardware/operational states at that time.  This is how Win8.1 starts so quickly most of the time.  Especially on SSD based PC's/Tablets.  When you power on your PC, after a previous "clean Shutdown", that Fastboot pagefile data is injected back into RAM, bring the PC's base "hardware state" in RAM as the Win kernel is loaded also.  This process directly affects Windows boot up time, since less time is spent loading the same, specific driver/hardware data from different points on the physical hard disk every time the PC boots.

I believe, but again I have no viable proof (yet), that this event is directly related to the Fastboot/pagefile data and/or process. (possibly leading to other, odd Win8 behavior)  My theory includes:

a.) the pagefile data possibly getting corrupted for hardware/drivers/WDF service info

b.) the pagefile data is not being loaded into RAM fast enough for the Windows Kernel, which of course is also being loaded into RAM on Startup. Result, possibly... "Driver Failed to Load for Device". 

c.) not using the Fastboot process causes Event Error, which means Windows is not cleanly loading the driver/service on "fresh" startup's.

Take notice of what errors you see when you "Restart" as apposed to "Shutdown", and notice if they are vastly different.  I've gone ahead and disabled Fastboot via Group Policy, while writing this reply.  I want to see which errors are consistent with which Startup type.

Note changes in Error Event Logs:

1.) No event error is logged when a "Fastboot" Startup is used, but event is logged when a full Startup is used?

2.) Event error is logged on full Startup's, but is logged when Fastboot Startup's are used?

3.) No change in Error Event consistency?

One other thing... I've never had this error come up on my Microsoft Surface Pro.  But I've seen it on almost all of my other PC's, custom and big mfg's.

Srimadhwa B said "Reply with the status of the issue and we will be glad to offer our assistance."

(1) Services - Windows Driver Foundation - changing this from Manual to Automatic fixes the Event 219 problem.

(2) Drivers - My wife has the identical computer which came with Windows 7 installed. The driver for the 15-in-1 Multicard read is "Generic" supplied by Microsoft. When I installed Windows 8 it was "Generic" supplied by Microsoft. In both instances there were NO Event ID 11 errors. Under the new, improved Windows 8.1 is still "Generic" driver.

So if Microsoft is the supplier AND I update drivers through Windows Update will Microsoft be providing a fix either to Windows 8.1 or to their driver?

At the risk of being rude I have replied with the status of the issue but this thread appears to have been abandoned.