Сбой загрузки драйвера \Driver\WUDFRd для устройства — Решение
При работе ОС Виндовс 10 пользователь может столкнуться с внезапным «вылетом» данной системы, проявляющимся в её зависании или перезагрузке. При анализе логов в событиях выясняется, что причиной ошибки является «Сбой загрузки драйвера \Driver\WUDFRd для устройства XXXXX». Вместо ХХХХХ может стоять любое устройство, но наиболее часто проблемным оказывается какой-либо USB-девайс (к примеру, стандартный флеш-накопитель). Ниже я разберу, что это за дисфункция, и как её можно исправить.
Что значит данная ошибка
Ошибка driver\wudfrd обычно вызвана каким-либо несовместимым (конфликтным) драйвером, установленным в пользовательской системе. При переходе с более ранних ОС на Виндовс 10 система вместо прежнего корректного драйвера может установить свой аналог от Майкрософт, который и будет вызывать конфликт имеющихся в системе устройств.
В других случаях указанная ошибка появляется из-за отключения (проблем с запуском) службы «Windows Driver Foundation», ответственной за работу с системными драйверами.
Также данная ошибка часто связана с ЮСБ-устройствами, подключаемыми к данному ПК (Event ID 219). Драйвер для такого устройства может работает некорректно, и вызывать рассматриваемую мной дисфункцию.
Как исправить данный сбой
Чтобы избавиться от ошибки «Сбой загрузки драйвера \Driver\WUDFRd для устройства XXXXX» выполните следующее:
- Установите все требуемые апдейты для вашей ОС. Без установки необходимых обновлений изложенные далее шаги могут оказаться неэффективными;
- Переустановите все контроллеры ЮСБ. Перейдите в «Диспетчер устройств», для чего нажмите на Win+R, наберите там devmgmt.msc и нажмите ввод. В перечне устройств найдите «Контроллеры USB», дважды кликлите на них для раскрытия ветки, и последовательно удалите здесь каждое устройство ЮСБ с помощью клика на ПКМ и выбора «Удалить устройство».
- Удалите все контроллеры ЮСБ
После удаления всех указанных устройств перезагрузите ваш PC, и понаблюдайте, будет ли проявлять себя данная ошибка. Если да – тогда идём дальше;
Заключение
Рассматриваемая в данной статье ошибка обычно вызвана некорректной работой драйвера одного из устройств, подключаемого через ЮСБ. Среди перечисленных решений наиболее эффективным считается перевод в автоматический режим службы «Windows Driver Foundation». Если же данное решение не помогло (или указанная служба у вас отсутствует) попробуйте другие перечисленные выше способы, позволяющие исправить ошибку «Сбой загрузки драйвера \Driver\WUDFRd для устройства» на вашем PC.
The driver \Driver\WudfRd failed to load
We’ll start with this Event FIRST:
Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 10/26/13 1:03:18 PM
Event ID: 219
Task Category: (212)
Level: Warning
Keywords:
User: SYSTEM
Computer: Michael-HP
Description:
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic&Prod_USB_SD_Reader&Rev_1.00#18E3312D81B&0#<53f56307-b6bf-11d0-94f2-00a0c91efb8b>.
Event Xml:
219
0
3
212
0
0x8000000000000000
42592
System
Michael-HP
124
SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic&Prod_USB_SD_Reader&Rev_1.00#18E3312D81B&0# <53f56307-b6bf-11d0-94f2-00a0c91efb8b>
3221226341
14
\Driver\WudfRd
0
I’m guessing this is related to Event ID 11 (below) which shows up for 4 items DR1 through DR 4. .
Log Name: System
Source: disk
Date: 10/26/13 1:22:46 PM
Event ID: 11
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Michael-HP
Description:
The driver detected a controller error on \Device\Harddisk2\DR2.
Event Xml:
11
2
0
0x80000000000000
42601
System
Michael-HP
\Device\Harddisk2\DR2
0F00800001000000000000000B0004C00301000000000000000000001600000000000000000000000B29010000000000FFFFFFFF06000000580000050000000000000A122809080000000000140000000000000000000000803A110200E0FFFF0000000000000000E053B70100E0FFFF0000000000000000000000000000000035000000000000000000000000000000000000000000000000000000000000000000000000000000
These show up on Device Manager as:
Disk Drives: as Generic USB SD Reader, CF Reader, xD/SM Reader and MS REader
Portable Devices as E:\ through H:\
Device Status shows as Device Working Properly
Before you ask: earlier today I ran
full scan Windows Defender
full scan Malwarebytes
NO new hardware or software since Windows 8.1 upgrade
all Windows Updates
Any help would be appreciated as I slowly go through the MULTIPLE Event Logs caused by my recent UPGRADE to Windows 8.1
Replies (44)
* Please try a lower page number.
* Please enter only numbers.
* Please try a lower page number.
* Please enter only numbers.
— 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.
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.
Reply with the status of the issue and we will be glad to offer our assistance.
7 people were helped by this reply
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
I also went through each instance of the drives and asked to «Update Driver Software» and «Scan for Hardware Changes».
They are Generic Microsoft Drives as they were under Windows 8 and as they still are on an identical Windows 7 machine.
All drives report as «This device is working properly» BUT the error messages are STILL appearing.
Have run the Hardware and Devices Troubleshooting which gives the message: «Hardware changes might not have been detected. Detected. Completed»
N.B. I examine Event Logs on a regular basis there were no issues PRIOR to installing Windows 8.1.
Since installing Windows 8.1 a number of issues are being reported NONE of which have been resolved.
So far as workarounds I’ve had to leave the Homegroup so that the power settings will work and due to Audit Failures am no longer using Internet Explorer 11.
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
Just to update the situation I’m getting this same Event ID 11 regarding DR1 on a second unrelated computer. So HP Desktop Windows 8.1 (64 bit) Acer Iconia W500 Tablet (32 bit) NEITHER of which had this error PRIOR to Windows 8.1 UPGRADE but now BOTH have the error.
Obviously something changed with the upgrade I’d ignore the error BUT am trying to resolve ALL the errors caused by Windows 8.1 and hopefully that will solve the more serious problem of my computer not being able to automatically go to sleep.
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
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.
1 person was helped by this reply
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
On an affected 8.1 machine, the following powershell script will output the Windows Driver Foundation-related Windows Error Report (WER) events into a text file (werUmdfReports.txt):
PS:> get-winevent -providername «Windows Error Reporting» | where-object <$_.Message -like "*wudf*">| format-list | out-file werUmdfReports.txt
Did this solve your problem?
Sorry this didn’t help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
I ran command (PowerShell Admin) unfortunately got an empty text file
As stated above changing Windows Driver Foundation from Manual to Automatic will temporarily «fix» this part of the problem BUT Windows tends to reset this back to Manual.
Also as stated above this occurs on two completely unrelated machines (HP-Desktop & Acer-Tablet) and I doubt that I have two machines with same error.
This is the latest Event log for Event ID 219
Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 11/13/13 1:35:28 PM
Event ID: 219
Task Category: (212)
Level: Warning
Keywords:
User: SYSTEM
Computer: Michael-HP
Description:
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic&Prod_USB_SD_Reader&Rev_1.00#18E3312D81B&0#<53f56307-b6bf-11d0-94f2-00a0c91efb8b>.
Event Xml:
219
0
3
212
0
0x8000000000000000
49464
System
Michael-HP
124
SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic&Prod_USB_SD_Reader&Rev_1.00#18E3312D81B&0# <53f56307-b6bf-11d0-94f2-00a0c91efb8b>
3221226341
14
\Driver\WudfRd
0
Which I imagine is related to Event ID which I get for DR1 to DR4 which are part of the Multicard Reader referenced in 219 above.
Log Name: System
Source: disk
Date: 11/13/13 1:00:35 PM
Event ID: 11
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Michael-HP
Description:
The driver detected a controller error on \Device\Harddisk2\DR2.
Event Xml:
11
2
0
0x80000000000000
49382
System
Michael-HP
\Device\Harddisk2\DR2
0F00800001000000000000000B0004C0030100000000000000000000160000000000000000000000D9FD040000000000FFFFFFFF06000000580000050000000000000612280108000000000073000000000000000000000040D1BA0100E0FFFF0000000000000000B0B4E90100E0FFFF000000000000000000000000000000001B000000010000000000000000000000000000000000000000000000000000000000000000000000
Swd wpdbusenum windows 10
Сообщения: 540
Благодарности: 31
| Конфигурация компьютера | ||||||||||||||||||||||||||||||||||||||||||||
| Материнская плата: MSI MS 7507 Ver:1.0 | ||||||||||||||||||||||||||||||||||||||||||||
| HDD: Western Digital,1.0TB,SATA | ||||||||||||||||||||||||||||||||||||||||||||
| Звук: Realtek | ||||||||||||||||||||||||||||||||||||||||||||
| CD/DVD: Pioneer и LG | ||||||||||||||||||||||||||||||||||||||||||||
| ОС: Windwos 7 SP1 Домашняя базовая x86 | ||||||||||||||||||||||||||||||||||||||||||||
 Профиль | Цитировать
Только что переустановлена Вин 8.1 (прежняя давала бсоды,- повреждение системных файлов). Никаких флешек не установлено. Если же вы забыли свой пароль на форуме, то воспользуйтесь данной ссылкой для восстановления пароля.
Установите тип запуска службы Windows Driver Foundation — Автоматически. ——-
219 118312 System 24 Последний раз редактировалось ministr91, 16-03-2016 в 22:03 .
Как раз ответ в предыдущем сообщении . ——-
|
