Solved BSOD happening all over the place

[Arc]

AMD USB Filter Driver (likely part of the chipset drivers)

BugCheck D5, {fffff980041d6ed0, 0, fffff880044371aa, 0}

*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys

Could not read faulting driver name
[COLOR=Red]Probably caused by : usbfilter.sys[/COLOR] ( usbfilter+41aa )

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

And it is very old.

lmvm usbfilter
start             end                 module name
fffff880`04433000 fffff880`04440000   usbfilter T (no symbols)           
    Loaded symbol image file: usbfilter.sys
    Image path: \SystemRoot\system32\DRIVERS\usbfilter.sys
    [COLOR=Red]Image name: usbfilter.sys
    Timestamp:        Tue Dec 22 13:56:22 2009[/COLOR] (4B3082AE)
    CheckSum:         0000DFD8
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from AMD Support & Drivers.

Let us know the results.

 

[XshinysuicuneX]

AMD USB Filter Driver (likely part of the chipset drivers)

BugCheck D5, {fffff980041d6ed0, 0, fffff880044371aa, 0}

*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys

Could not read faulting driver name
[COLOR=Red]Probably caused by : usbfilter.sys[/COLOR] ( usbfilter+41aa )

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

And it is very old.

lmvm usbfilter
start             end                 module name
fffff880`04433000 fffff880`04440000   usbfilter T (no symbols)           
    Loaded symbol image file: usbfilter.sys
    Image path: \SystemRoot\system32\DRIVERS\usbfilter.sys
    [COLOR=Red]Image name: usbfilter.sys
    Timestamp:        Tue Dec 22 13:56:22 2009[/COLOR] (4B3082AE)
    CheckSum:         0000DFD8
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from AMD Support & Drivers.

Let us know the results.

Couldn't find an update on AMD's website(and after googleing found there are lots of people having problems with this, I just un-installed it entirely(as was suggested as a fix on one of the threads I found) Then I re-enabled Verifier and have had no crashes since..... It hasn't been a full 24 hours yet, but I have a feeling that driver was the root of the BSODs

 

[Arc]

As I stated earlier, it is a part of the chipset driver.

As you have uninstalled it, the generic windows driver loaded rightly at the next startup, and it will not cause any more problem I guess.

 

[XshinysuicuneX]

Okay, I've had Verifier running for about 48 hours now and no more BSOD's! THANK YOU SOOOOOO MUCH for your help Arc!

 

[Arc]

Good to know. Now disable verifier, as it is not crashing anymore.