BSOD with various USB devices

Wasti · 02 Nov 2015

Hello! My freshly installed system

Win7 32Bit
ASrock H81M-DGS R2.0
Celeron G
onboard sound and graphics card
Bluetooth stick
USB keyboard and mouse
USB webcam
USB hub by Belinea monitor integrated
USB mass storage device
USB 2.0 port in front of the case via internal usb 2.0 header

with drivers taken from the manufacturers website ASrock does not work well.
It often crashes which results in restarts, sometimes bluescreens occur and very often one USB device does not respond at all, it can be the WLAN router stick or the USB mouse. When I switch the devices, it usually works again just to create a restart within a few minutes.
I have all USB options in the UEFI enabled, also the legacy option.
Can you tell me what exactly causes the problems?

I used Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.

Show DivPrimary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage | OSR)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18939.x86fre.win7sp1_gdr.150722-0600
Machine Name:
Kernel base = 0x82a51000 PsLoadedModuleList = 0x82b9ce30
Debug session time: Wed Sep 30 07:55:15.570 2015 (UTC - 5:00)
System Uptime: 0 days 0:00:41.710
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 8078b000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82a89ff3, address which referenced memory

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

READ_ADDRESS: GetPointerFromAddress: unable to read from 82bbd84c
Unable to read MiSystemVaType memory at 82b9c780
8078b000

CURRENT_IRQL: 0

FAULTING_IP:
nt!memcpy+33
82a89ff3 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

TRAP_FRAME: 8078a648 -- (.trap 0xffffffff8078a648)
ErrCode = 00000000
eax=00f0a6f5 ebx=8680aa8c ecx=201dfdbd edx=00000001 esi=8078b000 edi=8680b3a8
eip=82a89ff3 esp=8078a6bc ebp=8078a6c4 iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216
nt!memcpy+0x33:
82a89ff3 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

LAST_CONTROL_TRANSFER: from 82a89ff3 to 82a91cbf

STACK_TEXT:
8078a648 82a89ff3 badb0d00 00000001 00000004 nt!KiTrap0E+0x1b3
8078a6c4 ac2d5545 8680aa8c 8078a6e4 80780011 nt!memcpy+0x33
WARNING: Stack unwind information not available. Following frames may be wrong.
8078aa24 ac2d5842 00000000 8658a2a0 8680a9c8 BthAvrcp+0x2545
8078aa64 82ac9933 00000000 8658a2a0 0180a9c8 BthAvrcp+0x2842
8078aaa8 89a0e272 00000000 8078aad0 89a0e2b7 nt!IopfCompleteRequest+0x128
8078aab4 89a0e2b7 861af350 8658a2a0 8658a2a0 bthport!BthCompleteRequestEpilogue+0x38
8078aad0 89a38404 861af350 8658a2a0 00000000 bthport!BthCompleteRequestEx+0x27
8078aafc 89a34c0b 84905ae8 0178abe4 8794d008 bthport!L2Cap_CompleteReadIrpList+0x8c
8078abf0 89a1712a 84905ae8 01d685a0 0094d008 bthport!L2CapInt_ProcessReadBip+0x2b3
8078ac30 89a16c8b 86ad88e0 8653b300 00d68540 bthport!HCI_ProcessAclReadBip+0x45e
8078ac60 89a31cb6 86ad88e0 00000000 00000016 bthport!HCI_ProcessAclRead+0x18d
8078ac84 89a10122 86ad88e0 add5e670 add5e670 bthport!HCI_ProcessMpBip+0x60
8078ac98 899c084a add5e670 82a1d7a0 86af3e68 bthport!BTHPORT_RecvMpBip+0x38
8078acb4 899c5b82 861b0008 addaa000 00000016 BTHUSB!BthUsb_ReadTransferComplete+0x9e
8078ad0c 899c5f85 861af298 8078ad28 866602df BTHUSB!UsbWrapWorkRoutine+0xce
8078ad34 82ac9933 861af298 866601b8 01000003 BTHUSB!UsbWrapInterruptReadComplete+0x11d
8078ad7c 8e6ab1cb 00000400 86af3c48 8078ada0 nt!IopfCompleteRequest+0x128
8078ad8c 8e6ab202 8519e9a8 866601b8 00000000 iusb3xhc+0x661cb
8078ada0 8e69934d 8519e9a8 866601b8 00000000 iusb3xhc+0x66202
8078add8 8e695aae 8519e9a8 866601b8 85201ce0 iusb3xhc+0x5434d
8078adf4 8e67fd9e 00000000 86af3c48 86af3298 iusb3xhc+0x50aae
8078ae1c 8e679daa 8517c000 86af3c48 86af3298 iusb3xhc+0x3ad9e
8078aeb8 8e65d56b 8517c000 86aec510 86ae2c10 iusb3xhc+0x34daa
8078af24 8e65e02c 86ae2eb0 00000000 00000000 iusb3xhc+0x1856b
8078af48 82ac9015 86ae2eb0 8517c000 86ae2c10 iusb3xhc+0x1902c
8078afa4 82ac8e78 82b7de20 876fbd48 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 82ac863c bb9a2c70 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 bb9a2c70 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
82ac863c 00000000 0000001a 00d6850f bb830000 0xbb9a2c70

STACK_COMMAND: kb

FOLLOWUP_IP:
BthAvrcp+2545
ac2d5545 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: BthAvrcp+2545

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: BthAvrcp

IMAGE_NAME: BthAvrcp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a83cd65

FAILURE_BUCKET_ID: 0xA_BthAvrcp+2545

BUCKET_ID: 0xA_BthAvrcp+2545

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

Hacb · 03 Nov 2015

the dump referenced BthAvrcp.sys which is the bluetooth driver, you also mentioned having a bluetooth stick, try removing that and see if the crashes stop.

Wasti · 03 Nov 2015

Thank you. iusb3xhc is also mentioned in this log. Does this mean that USB 3 driver or device causes errors?

**axe0** · 03 Nov 2015

Actually your dump hasn't loaded properly, so the data from the dump could be something else then it should.

This part means you are having symbol errors, could be because you are missing the symbols.
Please try loading the dump again.

Code:

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

Hacb · 03 Nov 2015

no, that happens all the time when I analyse on there, it still gives me the essentials though.

**axe0** · 03 Nov 2015

It means a few things,

symbol problems, usually solved by loading the dump a few times (open, wait until it is loaded, close, open, wait til it is loaded etc.)
hardware problem,
counterfeit installation,
malware
Microsoft server down for downloading the symbols, rare but happens
other un-explained behavior.

Whenever you get this, you get data yes but who says the data is right?

Hacb · 03 Nov 2015

and by the way if the usb driver shows up, then it may well be a usb issue as well, try starting up without all the devices in that list and see if it stops, then try putting the bluetooth back and see if anything changes.

**axe0** · 03 Nov 2015

Wasti, please read BSOD Posting Instructions & How to upload files

**axe0** · 04 Nov 2015

axe0 said:

Actually your dump hasn't loaded properly, so the data from the dump could be something else then it should.

This part means you are having symbol errors, could be because you are missing the symbols.
Please try loading the dump again.

Code:

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

By the way, it literally says the symbol hasn't loaded (properly).