The driver \Driver\WUDFRd failed to load for the device error

[bftdsh]

Hi
i have a couple of weeks ago installed windows and i just got bsod crash and this was the only error in the event viewer
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC&PROD_USB_CF_READER&REV_1. 01#18E3312D81B&1#.

after looking at the minidump i thought it was due to a usb vidio/audio capture device so i tried updating the drivers and windows update couldnt find any and i cant find any online.

could some one help me and check my dump file to see if im right.
thanks

 

[Arc]

Hi bftdsh.

A stray crash dump is not enough. Click on the button below ....



It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[bftdsh]

Thanks for the reply arc
sorry about that i have attatched the zip

 

[Arc]

I see you are having a OEM license with a retail motherboard. Is it a system builder license? Asking because of the fact ....

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Also, Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know how it runs. Post for any further BSOD. Will wait for seeing one more crash dump because a single one may not lead to a proper way.

 

[bftdsh]

Thanks for the reply
not sure what it is as i had this custom built
I'll do as you have suggested and wait and see what happens
Thanks again

 

[bftdsh]

Hi
Just had another BSOD seems like the cause is different than last time
ive attached the new zip from the DM log collector

 

[bftdsh]

also i have run driver verifier and got got bsod's on two attempts to startup and both have gdrv as the driver

 

[Arc]

Driver verifier blames some gigabyte bloatware.

BugCheck C4, {f6, 140, fffffa8013a5cb30, fffff88009801809}

*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
[COLOR=Red]Probably caused by : gdrv.sys[/COLOR] ( gdrv+1809 )

Followup: MachineOwner
---------

I'd recommend you to http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

 

[bftdsh]

hi
the gigabyte stuff is gone and now I get another BSOD

 

[Arc]

hi
the gigabyte stuff is gone and now I get another BSOD

Another Gigabyte stuff ..... Gigabyte 3TB+ Unlock Bus Enumerator.

18/09/2014 12:27    Windows Error Reporting    Fault bucket X64_[COLOR=Red][B]0xD1[/B][/COLOR]_[B][COLOR=Red]VirtDiskBus64[/COLOR][/B]+3ea5, type 0
[COLOR=Red][B]Event Name: BlueScreen[/B][/COLOR]
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=8388&Bucket=X64_0xD1_VirtDiskBus64+3ea5&ID=959ad781-7d67-450e-ae49-21fa794a43bc

[COLOR=Red]BugCheck D1[/COLOR], {fffff8a00ee8c0c0, 2, 0, fffff8800462dea5}

*** WARNING: Unable to verify timestamp for VirtDiskBus64.sys
*** ERROR: Module load completed but symbols could not be loaded for VirtDiskBus64.sys
[COLOR=Red]Probably caused by : VirtDiskBus64.sys[/COLOR] ( VirtDiskBus64+3ea5 )

Followup: MachineOwner
---------

Read post #8 again .... there is a special reference. I posted it for you, because it was needed.
Now it appears that this is your option to clean up gigabyte bloatware.

Otherwise, the BSODs will continue to strike back.