Driver verifier BSOD

[ClintonK]

System will randomly lockup. It is very sporadic and I have tested vga, ram, and cpu using prime95, memtest as well as memtest86, furmark used for vga. 7hrs and 7 full runs of memtest 86, 0 errors. I feel hardware is solid.

Upon enabling driver verifier the system bluescreens before even getting into windows. Startup repair runs but does nothing.

Please help,

CK

win 7 64bit

 

[zigzag3143]

System will randomly lockup. It is very sporadic and I have tested vga, ram, and cpu using prime95, memtest as well as memtest86, furmark used for vga. 7hrs and 7 full runs of memtest 86, 0 errors. I feel hardware is solid.

Upon enabling driver verifier the system bluescreens before even getting into windows. Startup repair runs but does nothing.

Please help,

CK

win 7 64bit

This was caused bby USBfilter.sys. USBFILTER.sys is a USB upper class filter driver for AMD SB700 chipsets. It detects arrival and removal of USB 1.0/1.1 audio devices. ...

I would update and re-install it

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\110710-21621-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e56000 PsLoadedModuleList = 0xfffff800`03093e50
Debug session time: Sun Nov  7 14:36:21.524 2010 (GMT-5)
System Uptime: 0 days 0:00:15.147
Loading Kernel Symbols
...............................................................
................................................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff980063cce40, 0, fffff88003e5a1aa, 0}

Unable to load image \SystemRoot\system32\DRIVERS\usbfilter.sys, Win32 error 0n2
*** 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
Probably caused by : usbfilter.sys ( usbfilter+41aa )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff980063cce40, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff88003e5a1aa, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fe0e0
 fffff980063cce40 

FAULTING_IP: 
usbfilter+41aa
fffff880`03e5a1aa 8b4230          mov     eax,dword ptr [rdx+30h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD5

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002f62280 -- (.trap 0xfffff88002f62280)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88002f62478
rdx=fffff980063cce10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003e5a1aa rsp=fffff88002f62410 rbp=0000000000000002
 r8=0000000000000000  r9=fffff88003e5a1a5 r10=0000000000000000
r11=fffff80003040e80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
usbfilter+0x41aa:
fffff880`03e5a1aa 8b4230          mov     eax,dword ptr [rdx+30h] ds:0e80:fffff980`063cce40=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f46f14 to fffff80002ec6740

STACK_TEXT:  
fffff880`02f62118 fffff800`02f46f14 : 00000000`00000050 fffff980`063cce40 00000000`00000000 fffff880`02f62280 : nt!KeBugCheckEx
fffff880`02f62120 fffff800`02ec482e : 00000000`00000000 fffff980`063e0d80 fffffa80`05fff000 fffff800`02ef933f : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`02f62280 fffff880`03e5a1aa : fffff880`02f62478 00000000`00000000 fffff980`063e0d80 fffffa80`0613cbe0 : nt!KiPageFault+0x16e
fffff880`02f62410 fffff880`02f62478 : 00000000`00000000 fffff980`063e0d80 fffffa80`0613cbe0 00000000`00000000 : usbfilter+0x41aa
fffff880`02f62418 00000000`00000000 : fffff980`063e0d80 fffffa80`0613cbe0 00000000`00000000 fffff880`02f62478 : 0xfffff880`02f62478


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbfilter+41aa
fffff880`03e5a1aa 8b4230          mov     eax,dword ptr [rdx+30h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbfilter+41aa

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbfilter

IMAGE_NAME:  usbfilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b3082ae

FAILURE_BUCKET_ID:  X64_0xD5_VRF_usbfilter+41aa

BUCKET_ID:  X64_0xD5_VRF_usbfilter+41aa

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

 

[ClintonK]

I have installed driver and will now reactivate driver verifier

 

[ClintonK]

Ok updated and reinstalled the driver for AMD usb filter.

Upon re-activating driver verifier, the system again bsod before booting into windows.

new minidump attached.

Thanks

 

[ClintonK]

Did clean win install. System still hangs.

Driver verifier still bsod before booting into win

PLEASE HELP!!!

win7 64

attached jcgrif and minidump.

 

[ClintonK]

Hey guys. I installed most up to date drivers from mobo manufacturer, and vid drivers, I really need assistance. If I knew how to analyze minidumps I would. I just need someone to pinpoint the problem and maybe give some insight into how to fix or where to find specific drivers.

 

[ClintonK]

Seriously, why do I feel like this post is being ignored.


I need assistance

 

[wish]

Your latest dump still point to usbfilter.sys as the cause.
Try to download or reinstall your chipset driver --> AMD.com | Support & Downloads

Or if it doesn't work, you may uninstall AMD USB Filter Driver from Program and Features.

BugCheck D5, {fffff98001d84e40, 0, fffff880046041aa, 0}
Unable to load image \SystemRoot\system32\DRIVERS\usbfilter.sys, Win32 error 0n2
*** 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
Probably caused by : usbfilter.sys ( usbfilter+41aa )

 

[ClintonK]

Just bsod'd again. Can anyone confirm that it is still the usb filter? I just updated it, but i suspect these asrock drivers suck. I am going to uninstall the driver completely and see what happens.

Thanks
CK

 

[ClintonK]

So I have removed the offending driver and the system will now boot into windows with driver verifier on. However it still freezes completely at random times. I am at a loss as to what diagnostics to use to determine problem. Any Ideas???

Thanks for any input,

CK

 

[wish]

Yes, the latest dump still blame on usbfilter.sys.

BugCheck D5, {fffff98001c50ed0, 0, fffff88003e5a1aa, 0}
Probably caused by : usbfilter.sys ( usbfilter+41aa )

It's good you have removed that driver, but if you still got freeze maybe there is another culprit.
Just curious your windows was freezing or Bluescreening?
Try to boot in safe mode and see if the problem still occurs.

 

[ClintonK]

update

In response to wish: the system never blue screened before i enabled driver verifier. I have booted into safe mode to upload minidumps and turn driver verifier off. All this was done to deal with the usb filter driver issue. Honestly i was never in safemode for a super long amount of time. I suppose i could stress test the system in safemode, i will do thaty if current batch of testing fails. Thanks

Ran memtest (the one which runs within windows, not the bootdisk) to 900% with no errors, driver verifier still enabled. This result along with the prior run of memtest86+ for 7.5 hrs with no errors basically eliminates ram. Driver verifier is still enabled and I am running furmark, doing this to stress video drivers and determine if that is where the problem lies.

Any other input is welcome.

CK