View Single Post
14 Jan 2011  

Win 8 Release candidate 8400

Quote   Quote: Originally Posted by KennethHoegh View Post
I have just installed x64 yesterday on my computer, i did also have BSOD's on my X86, but though it was because it was x86 with 8GB ram, so i did a format and installed x64.

But i still giving my BSOD's , can you guys help me?

These crashes were caused by your USBFilter.sys driver
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. ...

It needs to be updated and re-installed.

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

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

Symbol search path is: SRV*C:\SymCache*;srv*e:\symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e17000 PsLoadedModuleList = 0xfffff800`03054e50
Debug session time: Fri Jan 14 05:00:01.876 2011 (GMT-5)
System Uptime: 0 days 0:50:53.219
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck FC, {fffff88002f7d120, 8000000003c35963, fffff88002eb04f0, 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
Probably caused by : usbfilter.sys ( usbfilter+1acb )

Followup: MachineOwner

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

An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arg1: fffff88002f7d120, Virtual address for the attempted execute.
Arg2: 8000000003c35963, PTE contents.
Arg3: fffff88002eb04f0, (reserved)
Arg4: 0000000000000000, (reserved)

Debugging Details:






TRAP_FRAME:  fffff88002eb04f0 -- (.trap 0xfffff88002eb04f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002f7d060 rbx=0000000000000000 rcx=fffff8a009130bac
rdx=000000000000001f rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002f7d120 rsp=fffff88002eb0688 rbp=fffffa8007258e30
 r8=0000000000000065  r9=0000000000000000 r10=0000000000000000
r11=fffff88002eb02b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff880`02f7d120 c015410780faff  rcl     byte ptr [fffff87f`fd77d868],0FFh ds:fffff87f`fd77d868=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f064b1 to fffff80002e87740

fffff880`02eb0388 fffff800`02f064b1 : 00000000`000000fc fffff880`02f7d120 80000000`03c35963 fffff880`02eb04f0 : nt!KeBugCheckEx
fffff880`02eb0390 fffff800`02e8582e : fffffa80`082cb000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40a25
fffff880`02eb04f0 fffff880`02f7d120 : fffff880`054b8acb fffffa80`07aa4530 fffffa80`08197760 fffff880`054bca60 : nt!KiPageFault+0x16e
fffff880`02eb0688 fffff880`054b8acb : fffffa80`07aa4530 fffffa80`08197760 fffff880`054bca60 00000000`00000913 : 0xfffff880`02f7d120
fffff880`02eb0690 fffffa80`07aa4530 : fffffa80`08197760 fffff880`054bca60 00000000`00000913 fffffa80`07aa4680 : usbfilter+0x1acb
fffff880`02eb0698 fffffa80`08197760 : fffff880`054bca60 00000000`00000913 fffffa80`07aa4680 00000000`00000700 : 0xfffffa80`07aa4530
fffff880`02eb06a0 fffff880`054bca60 : 00000000`00000913 fffffa80`07aa4680 00000000`00000700 fffffa80`076a9e48 : 0xfffffa80`08197760
fffff880`02eb06a8 00000000`00000913 : fffffa80`07aa4680 00000000`00000700 fffffa80`076a9e48 fffff880`054b85cb : usbfilter+0x5a60
fffff880`02eb06b0 fffffa80`07aa4680 : 00000000`00000700 fffffa80`076a9e48 fffff880`054b85cb fffffa80`08197760 : 0x913
fffff880`02eb06b8 00000000`00000700 : fffffa80`076a9e48 fffff880`054b85cb fffffa80`08197760 ffffffff`fff0bdc0 : 0xfffffa80`07aa4680
fffff880`02eb06c0 fffffa80`076a9e48 : fffff880`054b85cb fffffa80`08197760 ffffffff`fff0bdc0 fffffa80`00000000 : 0x700
fffff880`02eb06c8 fffff880`054b85cb : fffffa80`08197760 ffffffff`fff0bdc0 fffffa80`00000000 fffffa80`07b27d30 : 0xfffffa80`076a9e48
fffff880`02eb06d0 fffffa80`08197760 : ffffffff`fff0bdc0 fffffa80`00000000 fffffa80`07b27d30 00000100`00000600 : usbfilter+0x15cb
fffff880`02eb06d8 ffffffff`fff0bdc0 : fffffa80`00000000 fffffa80`07b27d30 00000100`00000600 fffffa80`076a9e00 : 0xfffffa80`08197760
fffff880`02eb06e0 fffffa80`00000000 : fffffa80`07b27d30 00000100`00000600 fffffa80`076a9e00 00000000`00000000 : 0xffffffff`fff0bdc0
fffff880`02eb06e8 fffffa80`07b27d30 : 00000100`00000600 fffffa80`076a9e00 00000000`00000000 00000001`00000000 : 0xfffffa80`00000000
fffff880`02eb06f0 00000100`00000600 : fffffa80`076a9e00 00000000`00000000 00000001`00000000 00000000`00000000 : 0xfffffa80`07b27d30
fffff880`02eb06f8 fffffa80`076a9e00 : 00000000`00000000 00000001`00000000 00000000`00000000 fffff880`054b84f5 : 0x100`00000600
fffff880`02eb0700 00000000`00000000 : 00000001`00000000 00000000`00000000 fffff880`054b84f5 fffffa80`07aa4530 : 0xfffffa80`076a9e00


fffff880`054b8acb ??              ???


SYMBOL_NAME:  usbfilter+1acb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbfilter

IMAGE_NAME:  usbfilter.sys


FAILURE_BUCKET_ID:  X64_0xFC_usbfilter+1acb

BUCKET_ID:  X64_0xFC_usbfilter+1acb

Followup: MachineOwner
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Ken J
My System SpecsSystem Spec