bluetooth headset x64

[jamieman]

ok well ive had no luck troubleshooting it in other sections in the forum

ive got a bluetooth headset. ive had it working once. but its a hit and miss sometimes it will BSOD. anyway i realised it was the software and hardware with the bluetooth dongle. ive now swapped over to an asus usb-bt21 and it detects everything hard to connect sometimes.


ive been having really horrible and upsetting constant BSOD trouble with this.
please help me to see what this is

 

[richc46]

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL Usual causes: Device driver

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2MINIDUMPINFO[1].zip\Windows_NT6_BSOD_jcgriff2\Mini082810-02.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
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0xfffff800`0204b000 PsLoadedModuleList = 0xfffff800`0220fdd0
Debug session time: Sat Aug 28 00:34:05.429 2010 (GMT-4)
System Uptime: 0 days 0:09:27.947
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 8, 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                                    *
*                                                                             *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory
Debugging Details:
------------------
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002272080
 0000000000000000 
CURRENT_IRQL:  2
FAULTING_IP: 
+0
00000000`00000000 ??              ???
PROCESS_NAME:  System
CUSTOMER_CRASH_COUNT:  2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
TRAP_FRAME:  fffffa600a7d47b0 -- (.trap 0xfffffa600a7d47b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa6001981aa0 rbx=0000000000000000 rcx=fffff800021be680
rdx=000000000000001f rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffffa600a7d4948 rbp=0000000000000002
 r8=0000000000000065  r9=0000000000000000 r10=0000000000000000
r11=fffffa600a7d4580 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
00000000`00000000 ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800020a526e to fffff800020a54d0
FAILED_INSTRUCTION_ADDRESS: 
+0
00000000`00000000 ??              ???
STACK_TEXT:  
fffffa60`0a7d4948 fffffa60`023f1acb : fffffa80`09d8b348 00000000`00000002 fffffa60`023f5a60 00000000`000006b7 : 0x0
fffffa60`0a7d4950 fffffa80`09d8b348 : 00000000`00000002 fffffa60`023f5a60 00000000`000006b7 fffffa80`09d94d40 : usbfilter+0x1acb
fffffa60`0a7d4958 00000000`00000002 : fffffa60`023f5a60 00000000`000006b7 fffffa80`09d94d40 fffffa80`08695700 : 0xfffffa80`09d8b348
fffffa60`0a7d4960 fffffa60`023f5a60 : 00000000`000006b7 fffffa80`09d94d40 fffffa80`08695700 fffffa80`0809b788 : 0x2
fffffa60`0a7d4968 00000000`000006b7 : fffffa80`09d94d40 fffffa80`08695700 fffffa80`0809b788 fffffa60`023f15cb : usbfilter+0x5a60
fffffa60`0a7d4970 fffffa80`09d94d40 : fffffa80`08695700 fffffa80`0809b788 fffffa60`023f15cb fffffa80`09649020 : 0x6b7
fffffa60`0a7d4978 fffffa80`08695700 : fffffa80`0809b788 fffffa60`023f15cb fffffa80`09649020 ffffffff`fff0bdc0 : 0xfffffa80`09d94d40
fffffa60`0a7d4980 fffffa80`0809b788 : fffffa60`023f15cb fffffa80`09649020 ffffffff`fff0bdc0 00000000`00000000 : 0xfffffa80`08695700
fffffa60`0a7d4988 fffffa60`023f15cb : fffffa80`09649020 ffffffff`fff0bdc0 00000000`00000000 fffffa80`0809b870 : 0xfffffa80`0809b788
fffffa60`0a7d4990 fffffa80`09649020 : ffffffff`fff0bdc0 00000000`00000000 fffffa80`0809b870 00000100`00000600 : usbfilter+0x15cb
fffffa60`0a7d4998 ffffffff`fff0bdc0 : 00000000`00000000 fffffa80`0809b870 00000100`00000600 fffffa80`0809b701 : 0xfffffa80`09649020
fffffa60`0a7d49a0 00000000`00000000 : fffffa80`0809b870 00000100`00000600 fffffa80`0809b701 00000000`00000000 : 0xffffffff`fff0bdc0
 
STACK_COMMAND:  .trap 0xfffffa600a7d47b0 ; kb
FOLLOWUP_IP: 
usbfilter+1acb
fffffa60`023f1acb ??              ???
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  usbfilter+1acb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: usbfilter
IMAGE_NAME:  usbfilter.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4acc46c8
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_usbfilter+1acb
BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_usbfilter+1acb
Followup: MachineOwner
---------

Usbfilter.sys file description
Productname: AMD USB Filter Driver
Description: AMD USB Filter Driver
Company: Advanced Micro Devices Inc

Go to the company website and replace driver. Report back, telling us that it is solved or a new BSOD.
Good luck

 

[jamieman]

what does that mean sorry?

 

[richc46]

Bottom line, you have a bad usb driver and it must be replaced.

 

[jamieman]

yeh i have updated the latest drivers for the bluetooth. ill try my best looking for latest drivers for related hardware, make sure correct driver etc, still BSOD with the same error 0x000000D1 (0x0000000000000000 0x0000000000000002 0x0000000000000008 0x0000000000000000)

 

[richc46]

Post the dump after all drivers are updated.

 

[richc46]

 secdrv.SYS   Wed Sep 13 09:18:38 2006
peauth.sys   Mon Oct 23 07:57:00 2006
ASACPI.sys   Mon Oct 30 22:09:12 2006
Null.SYS     Thu Nov 02 05:37:15 2006
MSPCLOCK.sys Thu Nov 02 05:37:30 2006
MSPQM.sys    Thu Nov 02 05:37:30 2006
swenum.sys   Thu Nov 02 05:37:33 2006
vbtenum.sys  Mon Mar 05 07:17:00 2007
BTHidMgr.sys Mon Mar 05 07:17:15 2007
VComm.sys    Mon Mar 05 07:17:28 2007
VcommMgr.sys Mon Mar 05 07:17:48 2007
btnetdrv.sys Mon Mar 05 07:18:08 2007
btcusb.sys   Sun Jun 24 09:55:36 2007
modrc.sys    Wed Jul 11 04:07:06 2007
processr.sys Sat Jan 19 00:52:45 2008
Fs_Rec.SYS   Sat Jan 19 00:53:41 2008
cdfs.sys     Sat Jan 19 00:53:45 2008
Msfs.SYS     Sat Jan 19 00:53:55 2008
bowser.sys   Sat Jan 19 00:54:51 2008
luafv.sys    Sat Jan 19 00:59:06 2008
wmiacpi.sys  Sat Jan 19 01:02:42 2008
msisadrv.sys Sat Jan 19 01:02:50 2008
mssmbios.sys Sat Jan 19 01:02:54 2008
fileinfo.sys Sat Jan 19 01:05:23 2008
Dxapi.sys    Sat Jan 19 01:08:00 2008
mountmgr.sys Sat Jan 19 01:28:01 2008
mouclass.sys Sat Jan 19 01:28:05 2008
kbdclass.sys Sat Jan 19 01:28:05 2008
i8042prt.sys Sat Jan 19 01:28:08 2008
mouhid.sys   Sat Jan 19 01:28:10 2008
ksthunk.sys  Sat Jan 19 01:28:14 2008
serenum.sys  Sat Jan 19 01:28:36 2008
serial.sys   Sat Jan 19 01:28:41 2008
SCSIPORT.SYS Sat Jan 19 01:28:52 2008
crcdisk.sys  Sat Jan 19 01:30:12 2008
vga.sys      Sat Jan 19 01:32:21 2008
VIDEOPRT.SYS Sat Jan 19 01:32:25 2008
WDFLDR.SYS   Sat Jan 19 01:32:33 2008
monitor.sys  Sat Jan 19 01:32:34 2008
Wdf01000.sys Sat Jan 19 01:33:27 2008
WMILIB.SYS   Sat Jan 19 01:33:45 2008
HIDPARSE.SYS Sat Jan 19 01:33:51 2008
USBD.SYS     Sat Jan 19 01:33:53 2008
usbccgp.sys  Sat Jan 19 01:34:04 2008
BdaSup.SYS   Sat Jan 19 01:34:06 2008
umbus.sys    Sat Jan 19 01:34:16 2008
mpsdrv.sys   Sat Jan 19 01:35:28 2008
rspndr.sys   Sat Jan 19 01:35:48 2008
lltdio.sys   Sat Jan 19 01:35:48 2008
ndisuio.sys  Sat Jan 19 01:36:29 2008
tunmp.sys    Sat Jan 19 01:36:30 2008
netbios.sys  Sat Jan 19 01:36:35 2008
nsiproxy.sys Sat Jan 19 01:36:45 2008
ndistapi.sys Sat Jan 19 01:37:22 2008
NDProxy.SYS  Sat Jan 19 01:37:26 2008
asyncmac.sys Sat Jan 19 01:37:27 2008
rasacd.sys   Sat Jan 19 01:37:30 2008
RootMdm.sys  Sat Jan 19 01:38:16 2008
modem.sys    Sat Jan 19 01:38:17 2008
rdpencdd.sys Sat Jan 19 01:42:03 2008
RDPCDD.sys   Sat Jan 19 01:42:04 2008
drmk.sys     Sat Jan 19 02:20:04 2008

Here is a complete list of outdated drivers in use during the dump. It is not possible to just update all at this time. If problem continues, just give us the new dump report and I may suggest the driver verifier test.
In the mean time be sure to update ASACPI, above. The 2006 version was known to cause BSOD.
Asacpi.sys is a driver from the Austek Computer Corp. Your driver is very old and is known to cause BSOD's in current Windows versions; it must be updated
http://support.asus.com/download/dow...Language=en-us