The driver \Driver\WudfRd failed to load. How do i fix this?

Hello again,

I tried to fix the errors for the component services but adding a user option was grayed out and I was unable to do that. Also 2593F8B9-4EAF-457C-B68A-50F6B8EA6B54 and 15C20B67-12E7-4BB6-92BB-7AFF07997402.Theese ID dont seem to exist in the component services tool and I cant seem to find it anywhere.

The system worked fine for a while then I recently Blue screened again when I tried to play Fifa 23. This time I got a blue screen with the message whea uncorrectable error. A dump file wasnt made because the screen was stuck for roughly 20 minutes like this and the percentage didnt move from 0% so i decided to just hold the power button on the system. Blue screen view is still empty.

I plan to run memtest in the morning.

I also plan to have an electrician check my wall outlet because Ive had issues with this pc nearly every year, so I thought id make sure that my outlet isnt the issue.

Looking at the event viewer after the error. I have:

Event ID 6008: The previous system shutdown at 22:47:34 on ‎08/‎01/‎2024 was unexpected.

Event ID 161: Dump file creation failed due to error during dump creation.

Event ID 41: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event ID 1014: Name resolution for the name wpad timed out after none of the configured DNS servers responded.

Event ID 10016: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 

{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}

 and APPID 

{15C20B67-12E7-4BB6-92BB-7AFF07997402}

 to the user DESKTOP-LRQ3P0V\flaps SID (S-1-5-21-3069406887-25207266-2636239509-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

This warning has been repeated 3 times in the event viewer.

In the time between my last post and this post I have:

1. Installed the latest realtek audio drivers found on my motherboards support page for win 10
2. Installed the latest chipset drivers from AMD using the adrenaline software they have
3. I installed the EA app to play fifa
4. I installed autodesk products and adobe products for my work.
5. Got rid of the hyper X headset that was mentioned in the prior log and bought a new headset that seem to work fine as im not seeing any errors in the event viewer related to it. It also uses the audio ports on my motherboard and not a usb connection.

Hi, thank you for your response. I tried this and here is what happened.

I tried to update drivers and was told me there are no drivers that needed to be updated and that it was up to date.

During this process my computer crashed again and i was put into a boot loop

Because of the boot loop i had to format my m.2 drive and reinstall a fresh copy of windows.

The problem still persisted.

After i reinstalled windows I went to do your other steps and I saw a network adapter had an issue with drivers. I found out this was a Tplink PCIE network adapter. I uninstalled the device and removed it from my system because it wasnt needed anymore because I use ethernet.

After a bit of testing everything seemed to work fine for a bit until i blue screened again.

Then I saw the error again of wudfrd for the device tht was my Hyper X cloud 2 gaming headset. Which I have now uninstalled and unplugged.

I have also ran a windows memory test and my RAM seems fine with no issues.

I also ran sfc/scannow and windows seems to be fine. I have checked crystal disk info, and samsung magician and my drives are reported to be fine.

I have also reseated my GPU and it is fine as well.

Currently I havent BSODed again but I have a couple errors I know want to get checked out.

1 - Name resolution for the name wpad timed out after none of the configured DNS servers responded. Error 1014

2 - The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 

{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}

 and APPID 

{15C20B67-12E7-4BB6-92BB-7AFF07997402}

 to the user DESKTOP-LRQ3P0V\flaps SID (S-1-5-21-3069406887-25207266-2636239509-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Error 10016

3 - The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 

{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}

 and APPID 

{15C20B67-12E7-4BB6-92BB-7AFF07997402}

 to the user DESKTOP-LRQ3P0V\flaps SID (S-1-5-21-3069406887-25207266-2636239509-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Error 10016

Theese are the warning i know get in the event viewer. I understand the Error 10016 is normal but I know need to figure out how to fix the Event ID 1014.

Hi

Welcome to Microsoft community.

The error with the driver \Driver\WudfRd failing to load is associated with the Windows User-Mode Driver Framework (UMDF), which is used by certain drivers to run in user mode. The specific devices mentioned in your error messages seem to be related to input devices, possibly a game controller or HID (Human Interface Device). Here are some steps to troubleshoot and potentially resolve the issue:

1. Update Drivers: Go to the Device Manager and look for the devices listed in the error message. They might be under 'Human Interface Devices' or similar. Right-click on the device and select 'Update driver'. Choose 'Search automatically for updated driver software'.
2. Reinstall Drivers: If updating doesn't work, you can try uninstalling the device from Device Manager and then rebooting your computer. Windows should attempt to reinstall the driver on startup.
3. Check for Conflicts: In Device Manager, check if there are any yellow exclamation marks next to any of the devices, which would indicate a conflict or issue with that device.
4. SFC and DISM: Run the System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools to repair any corrupted system files. Open Command Prompt as an administrator and run the following commands:
   • sfc /scannow
   • DISM /Online /Cleanup-Image /RestoreHealth
5. Check for Hardware Issues: Sometimes, BSODs can be caused by failing hardware. If you suspect a hardware issue, you might want to run a hardware diagnostic. Many manufacturers provide diagnostic tools, or you can use third-party tools.
6. Restore System: If the issue started recently, you could try performing a system restore to revert your computer to a state where everything was working properly.
7. Safe Mode: Boot into Safe Mode to see if the issue persists there. If it doesn't, it's likely a driver or software issue that doesn't load in Safe Mode.
8. View BSOD Information: Tools like BlueScreenView can help analyze BSODs. Since you mentioned it shows nothing, consider using the built-in Windows tool, WinDbg, to analyze the minidump files. We need you to provide the blue screen log files(minidump) to analyze your problem. Finally upload it to your network drive and send the share link in your reply. To find the minidump file in Windows, you can follow these steps:
   1. Open File Explorer by pressing the Windows key + E.
   2. Navigate to the following location: C:\Windows\Minidump (replace C with the drive where Windows is installed if it is different).
   3. If you cannot find the Minidump folder at the specified location, it might be hidden. To show hidden files and folders, click on the "View" tab in the File Explorer, and check the "Hidden items" option.
   4. If the Minidump folder is still not present, it might be because your system is not configured to create Minidump files. To enable this feature, follow these steps:
      • Press the Windows key + X and select "System".
      • Click on "Advanced system settings" on the left-hand side.
      • In the System Properties window, go to the "Advanced" tab and click on the "Settings" button under the "Startup and Recovery" section.
      • In the Startup and Recovery window, make sure that the "Write debugging information" drop-down menu is set to "Small memory dump (256 KB)" or "Kernel memory dump".
      • Click "OK" to save the changes.
      • Restart your computer for the changes to take effect.
   5. Once you have located the Minidump folder, you will find the Minidump files inside it. These files have the .dmp extension and are named with a combination of date and time.
   Note: Minidump files are created when your system encounters a blue screen of death (BSOD) or a crash. If you have not experienced any crashes, the Minidump folder may be empty.

Best regards

Derrick Qian | Microsoft Community Support Specialist

Hi

Thanks for your reply.

It appears that you've taken several steps to troubleshoot the issue, and it's unfortunate that the problem persists. Let's address the remaining concerns:

1. Name Resolution Timeout (Error 1014):

The error indicates a timeout in name resolution for the name "wpad." This issue is often related to DNS (Domain Name System) settings. To address this:

• Check your DNS settings: Ensure that your DNS server settings are correctly configured. You can do this in the Network and Sharing Center or by checking your router settings.
• Flush DNS cache: Open Command Prompt as an administrator and run the following command:

    bashCopy codeipconfig /flushdns
  

2. Application-Specific Permission Errors (Error 10016):

These errors often occur due to permission issues related to COM (Component Object Model) servers. To resolve this:

• Use the Component Services administrative tool:
  • Press  Win + R  to open the Run dialog, type dcomcnfg, and press Enter.
  • In the Component Services window, navigate to  Component Services -> Computers -> My Computer -> DCOM Config
  • Find the CLSID and APPID mentioned in the errors (in your case, {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and {15C20B67-12E7-4BB6-92BB-7AFF07997402}).
  • Right-click on each entry, select  Properties and go to the  Security  tab.
  • Under  Launch and Activation Permissions click  Edit
  • Add the user  DESKTOP-LRQ3P0V\flaps  and grant the necessary permissions.
• After making changes, restart your computer.

3. Further Considerations:

• Ensure that your operating system, drivers, and software are fully updated.
• Monitor your system for any recurring BSODs and note the error messages for analysis.

In order to better assist you, it would be best if you could upload and send me the minidump files through the steps provided in the previous response. I can help you further analyze the issue.