Narrowed down BSOD to USB (maybe). Could someone confirm?

Hi guys. Running Windows 7 Ult. x64 on a new build. Nothing OCed and temps are excellent. System has been built only a month now but I have only received 3 bsod since then so not exactly often. I have ran burn in tests, stability tests, memtest, windows mem diagnostic all come out fine. It is free of viruses, spyware, etc. The only thing I have not done is re-install drivers, which I believe to be where the problem is coming from. I used Blue Screen View to analyze my dump file and it seems to say USBPORT.SYS driver caused it. It highlights this and ntoskrnl.exe in red, which I am not sure what that is. Am I reading this correctly? All help is greatly appreciated!

I attached my zip file below.

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\jta98z\011312-16660-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e4d000 PsLoadedModuleList = 0xfffff800`03092670
Debug session time: Fri Jan 13 09:55:57.818 2012 (UTC - 7:00)
System Uptime: 0 days 0:15:53.004
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpDistributeInterruptReport+130 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3234316264613239
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  bf3.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000ba2448 -- (.exr 0xfffff80000ba2448)
ExceptionAddress: fffff88000ead8fd (Wdf01000!FxTagTracker::UpdateTagHistory+0x0000000000000019)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000ba24f0 -- (.trap 0xfffff80000ba24f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88000ed7201 rbx=0000000000000000 rcx=6469484c021b000b
rdx=fffffa8009ab33a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000ead8fd rsp=fffff80000ba2680 rbp=fffffa8009ab33b0
 r8=000000000000017a  r9=fffff88000ed7570 r10=fffffa8009a7fe70
r11=fffff80000ba26c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
Wdf01000!FxTagTracker::UpdateTagHistory+0x19:
fffff880`00ead8fd 488b31          mov     rsi,qword ptr [rcx] ds:6469484c`021b000b=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec15fe to fffff80002ec9c10

STACK_TEXT:  
fffff800`00ba1528 fffff800`02ec15fe : fffff800`0312b000 fffff800`03198000 fffff800`00ba1ca0 fffff800`02ef5830 : nt!KeBugCheck
fffff800`00ba1530 fffff800`02ef54fd : fffff800`030d371c fffff800`03010c30 fffff800`02e4d000 fffff800`00ba2448 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba1560 fffff800`02ef42d5 : fffff800`03014028 fffff800`00ba15d8 fffff800`00ba2448 fffff800`02e4d000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba1590 fffff800`02f05361 : fffff800`00ba2448 fffff800`00ba1ca0 fffff800`00000000 fffffa80`096b8370 : nt!RtlDispatchException+0x415
fffff800`00ba1c70 fffff800`02ec92c2 : fffff800`00ba2448 fffffa80`096b8370 fffff800`00ba24f0 fffff980`062f6700 : nt!KiDispatchException+0x135
fffff800`00ba2310 fffff800`02ec7bca : 00000000`00000004 fffff980`0e584f90 fffff980`02cf6670 fffffa80`0adf6b90 : nt!KiExceptionDispatch+0xc2
fffff800`00ba24f0 fffff880`00ead8fd : fffff880`05c0c010 fffff880`00e862a7 00000000`00000000 0000057f`f654cc58 : nt!KiGeneralProtectionFault+0x10a
fffff800`00ba2680 fffff880`00e82e75 : fffffa80`096b8370 fffffa80`09ab33b0 fffff980`062f6700 fffffa80`096b8370 : Wdf01000!FxTagTracker::UpdateTagHistory+0x19
fffff800`00ba26d0 fffff880`00e5cc9b : fffffa80`09ab33a0 fffff980`062f6701 fffffa80`09ab33b0 fffff980`062f6701 : Wdf01000!FxRequest::Release+0x3d
fffff800`00ba2710 fffff880`00e5cdc4 : fffff800`02eb6402 fffff980`062f6f20 00000000`00000000 fffffa80`0adf6b90 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff800`00ba2780 fffff800`02eb6485 : fffff980`062f6f20 fffffa80`090401c0 fffff800`02eb6430 fffff980`062f6f20 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff800`00ba27b0 fffff800`033715d6 : fffff980`062f6f20 fffffa80`08096b70 fffff800`00ba2990 fffff980`062f6700 : nt!IopUnloadSafeCompletion+0x55
fffff800`00ba27f0 fffff800`02ecd021 : fffff980`062f6f23 00000000`00000000 00000000`00000000 fffff800`02f86803 : nt!IovpLocalCompletionRoutine+0x166
fffff800`00ba2850 fffff800`0336919f : fffff980`062f6700 fffffa80`099fec06 fffffa80`09a81706 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`00ba2940 fffff880`05fd59c4 : fffffa80`09a81760 fffffa80`09a81750 fffffa80`09a81760 fffffa80`09a81750 : nt!IovCompleteRequest+0x19f
fffff800`00ba2a10 fffff880`05fd5c2d : fffffa80`09a81302 fffffa80`09a81390 fffffa80`099feca0 00000000`00000008 : HIDCLASS!HidpDistributeInterruptReport+0x130
fffff800`00ba2aa0 fffff800`033715d6 : fffff980`02cc8fb0 fffffa80`099feca0 fffff800`00ba2c01 fffff980`02cc88b0 : HIDCLASS!HidpInterruptReadComplete+0x235
fffff800`00ba2b30 fffff800`02ecd021 : fffff980`02cc8fb3 00000000`00000001 00000000`00000000 fffff800`02f86803 : nt!IovpLocalCompletionRoutine+0x166
fffff800`00ba2b90 fffff800`0336919f : fffff980`02cc88b0 fffffa80`0c26f300 fffffa80`091ce000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`00ba2c80 fffff880`0533a631 : fffffa80`091ce050 fffffa80`08414e02 00000000`00000002 fffffa80`091ce050 : nt!IovCompleteRequest+0x19f
fffff800`00ba2d50 fffff880`0533ab0f : fffffa80`0c603c02 fffff980`02cc88b0 00000000`ffffffff fffffa80`091ceeb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`00ba2e30 fffff880`0533866f : fffffa80`091ceeb0 fffffa80`091ce1a0 fffffa80`091cf050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`00ba2e90 fffff880`05329f89 : fffffa80`091ce050 00000000`00000000 fffffa80`091cee02 fffffa80`091ceeb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`00ba2ed0 fffff800`02ed50ac : fffff800`0303fe80 fffffa80`091ceeb0 fffffa80`091ceec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00ba2f00 fffff800`02ecc765 : 00000000`00000000 fffffa80`08063b60 00000000`00000000 fffff880`05329db0 : nt!KiRetireDpcList+0x1bc
fffff800`00ba2fb0 fffff800`02ecc57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`0c469aa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
HIDCLASS!HidpDistributeInterruptReport+130
fffff880`05fd59c4 488b4c2448      mov     rcx,qword ptr [rsp+48h]

SYMBOL_STACK_INDEX:  f

SYMBOL_NAME:  HIDCLASS!HidpDistributeInterruptReport+130

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME:  HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

FAILURE_BUCKET_ID:  X64_0x1E_0_HIDCLASS!HidpDistributeInterruptReport+130

BUCKET_ID:  X64_0x1E_0_HIDCLASS!HidpDistributeInterruptReport+130

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

HIDCLASS.SYS is usually blamed due to USB, Human Interface Devices, or Bluetooth devices. Proceed through the steps in USB Driver - General Fix for Problems to troubleshoot USB devices. Update all drivers for your Human Inteface Devices and Bluetooth devices following the steps in Installing and updating drivers in 7.

so are you saying it was caused by HIDCLASS? I don't question your knowledge I'm just a little confused at how to interpret these messages. Blue Screen View said usbport.sys caused the crash?

jta98z said:

so are you saying it was caused by HIDCLASS? I don't question your knowledge I'm just a little confused at how to interpret these messages. Blue Screen View said usbport.sys caused the crash?

USBPORT was also within the memory stack, so I can see why it may have been blamed. HIDCLASS is more general to Human Interface Devices that can include USB, game controllers/joysticks, bluetooth devices as I outlined in my previous post.

Code:

STACK_TEXT:  
fffff800`00ba1528 fffff800`02ec15fe : fffff800`0312b000 fffff800`03198000 fffff800`00ba1ca0 fffff800`02ef5830 : nt!KeBugCheck
fffff800`00ba1530 fffff800`02ef54fd : fffff800`030d371c fffff800`03010c30 fffff800`02e4d000 fffff800`00ba2448 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba1560 fffff800`02ef42d5 : fffff800`03014028 fffff800`00ba15d8 fffff800`00ba2448 fffff800`02e4d000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba1590 fffff800`02f05361 : fffff800`00ba2448 fffff800`00ba1ca0 fffff800`00000000 fffffa80`096b8370 : nt!RtlDispatchException+0x415
fffff800`00ba1c70 fffff800`02ec92c2 : fffff800`00ba2448 fffffa80`096b8370 fffff800`00ba24f0 fffff980`062f6700 : nt!KiDispatchException+0x135
fffff800`00ba2310 fffff800`02ec7bca : 00000000`00000004 fffff980`0e584f90 fffff980`02cf6670 fffffa80`0adf6b90 : nt!KiExceptionDispatch+0xc2
fffff800`00ba24f0 fffff880`00ead8fd : fffff880`05c0c010 fffff880`00e862a7 00000000`00000000 0000057f`f654cc58 : nt!KiGeneralProtectionFault+0x10a
fffff800`00ba2680 fffff880`00e82e75 : fffffa80`096b8370 fffffa80`09ab33b0 fffff980`062f6700 fffffa80`096b8370 : Wdf01000!FxTagTracker::UpdateTagHistory+0x19
fffff800`00ba26d0 fffff880`00e5cc9b : fffffa80`09ab33a0 fffff980`062f6701 fffffa80`09ab33b0 fffff980`062f6701 : Wdf01000!FxRequest::Release+0x3d
fffff800`00ba2710 fffff880`00e5cdc4 : fffff800`02eb6402 fffff980`062f6f20 00000000`00000000 fffffa80`0adf6b90 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff800`00ba2780 fffff800`02eb6485 : fffff980`062f6f20 fffffa80`090401c0 fffff800`02eb6430 fffff980`062f6f20 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff800`00ba27b0 fffff800`033715d6 : fffff980`062f6f20 fffffa80`08096b70 fffff800`00ba2990 fffff980`062f6700 : nt!IopUnloadSafeCompletion+0x55
fffff800`00ba27f0 fffff800`02ecd021 : fffff980`062f6f23 00000000`00000000 00000000`00000000 fffff800`02f86803 : nt!IovpLocalCompletionRoutine+0x166
fffff800`00ba2850 fffff800`0336919f : fffff980`062f6700 fffffa80`099fec06 fffffa80`09a81706 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`00ba2940 fffff880`05fd59c4 : fffffa80`09a81760 fffffa80`09a81750 fffffa80`09a81760 fffffa80`09a81750 : nt!IovCompleteRequest+0x19f
fffff800`00ba2a10 fffff880`05fd5c2d : fffffa80`09a81302 fffffa80`09a81390 fffffa80`099feca0 00000000`00000008 : HIDCLASS!HidpDistributeInterruptReport+0x130
fffff800`00ba2aa0 fffff800`033715d6 : fffff980`02cc8fb0 fffffa80`099feca0 fffff800`00ba2c01 fffff980`02cc88b0 : HIDCLASS!HidpInterruptReadComplete+0x235
fffff800`00ba2b30 fffff800`02ecd021 : fffff980`02cc8fb3 00000000`00000001 00000000`00000000 fffff800`02f86803 : nt!IovpLocalCompletionRoutine+0x166
fffff800`00ba2b90 fffff800`0336919f : fffff980`02cc88b0 fffffa80`0c26f300 fffffa80`091ce000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`00ba2c80 fffff880`0533a631 : fffffa80`091ce050 fffffa80`08414e02 00000000`00000002 fffffa80`091ce050 : nt!IovCompleteRequest+0x19f
fffff800`00ba2d50 fffff880`0533ab0f : fffffa80`0c603c02 fffff980`02cc88b0 00000000`ffffffff fffffa80`091ceeb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`00ba2e30 fffff880`0533866f : fffffa80`091ceeb0 fffffa80`091ce1a0 fffffa80`091cf050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`00ba2e90 fffff880`05329f89 : fffffa80`091ce050 00000000`00000000 fffffa80`091cee02 fffffa80`091ceeb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`00ba2ed0 fffff800`02ed50ac : fffff800`0303fe80 fffffa80`091ceeb0 fffffa80`091ceec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00ba2f00 fffff800`02ecc765 : 00000000`00000000 fffffa80`08063b60 00000000`00000000 fffff880`05329db0 : nt!KiRetireDpcList+0x1bc
fffff800`00ba2fb0 fffff800`02ecc57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`0c469aa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue

So far I've noticed that it has done it in games. Sometimes it may take 5m and other times I play for hours. The only usb device I even have is my mouse.

Lol ok I'm really sorry but could you clarify a little further? I know all the ins and outs of pc hardware but when it comes to these error messages I feel like a 3 year old. I still don't fully understand what you are telling me? I realize it is something to do with a HID but what? Is a driver malfunctioning? Is another process triggering the malfunction? I don't really understand if your telling me there is a driver error, something is wrong with a usb port, or even a device attached to it? I greatly appreciate all your help and patience. I'm sorry for my lack of understanding, I'm just confused.

jta98z said:

Lol ok I'm really sorry but could you clarify a little further? I know all the ins and outs of pc hardware but when it comes to these error messages I feel like a 3 year old. I still don't fully understand what you are telling me? I realize it is something to do with a HID but what? Is a driver malfunctioning? Is another process triggering the malfunction? I don't really understand if your telling me there is a driver error, something is wrong with a usb port, or even a device attached to it? I greatly appreciate all your help and patience. I'm sorry for my lack of understanding, I'm just confused.

It usually is a device attached to your computer that causes these blue screens, or it could be a device that was once attached and no longer is used. That is why you need to follow the steps in the link I gave in my first post USB Driver - General Fix for Problems. Then post back whether the crashes stop. You should also update all drivers I mentioned before: USB devices, drivers for the USB ports themselves, Human Interface Devices, and Bluetooth devices.

Ok I'll try that Monday when I get back. Just a quick question though. I have bluetooth disabled in my BIOS because I do not use any bluetooth devices. SHould I still bother with troubleshooting bluetooth or its drivers?

jta98z said:

Ok I'll try that Monday when I get back. Just a quick question though. I have bluetooth disabled in my BIOS because I do not use any bluetooth devices. SHould I still bother with troubleshooting bluetooth or its drivers?

Since the drivers should not be loading for bluetooth, it should be fine, but if bluetooth ever ran, you may want to look into it anyway. See if it is one of the hidden devices that shows up when you run the the basic USB drivers fix.

Did the USB general driver fix resolve your stability problems?