BSOD while browsing, error 0x000000d1

Hi Catfish666.

Your Asmedia XHCI (USB3) controller driver is old.

Code:

fffff880`05d0e000 fffff880`05d72000   asmtxhci   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\asmtxhci.sys
    Image name: asmtxhci.sys
    Timestamp:        Thu Nov 03 08:30:22 2011 (4EB203C6)
    CheckSum:         0006C541
    ImageSize:        00064000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Station-Drivers - Asmedia drivers & firmwares.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.
________________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {66725045, 2, 1, fffffa80095b21a0}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+162 )

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

0: 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: 0000000066725045, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffffa80095b21a0, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f01100
GetUlongFromAddress: unable to read from fffff80002f011c0
 0000000066725045 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
+0
fffffa80`095b21a0 48              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

TRAP_FRAME:  fffff80000b9c940 -- (.trap 0xfffff80000b9c940)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000fefa4602 rbx=0000000000000000 rcx=fffffa8006ca9a40
rdx=0000000066725045 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa80095b21a0 rsp=fffff80000b9cad8 rbp=fffffa80095b21a0
 r8=0000000066725045  r9=fffff880041ef200 r10=00000000ffffffff
r11=fffffa80095b21a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe nc
fffffa80`095b21a0 48              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cc9169 to fffff80002cc9bc0

STACK_TEXT:  
fffff800`00b9c7f8 fffff800`02cc9169 : 00000000`0000000a 00000000`66725045 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c800 fffff800`02cc7de0 : 00000000`00000001 00000000`00000004 fffff880`041ef200 fffffa80`06ca9a40 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c940 fffffa80`095b21a0 : fffffa80`095b2a18 fffffa80`0d695c00 fffffa80`095b21a0 fffffa80`095b2050 : nt!KiPageFault+0x260
fffff800`00b9cad8 fffffa80`095b2a18 : fffffa80`0d695c00 fffffa80`095b21a0 fffffa80`095b2050 fffff880`04812016 : 0xfffffa80`095b21a0
fffff800`00b9cae0 fffffa80`0d695c00 : fffffa80`095b21a0 fffffa80`095b2050 fffff880`04812016 fffffa80`095b2050 : 0xfffffa80`095b2a18
fffff800`00b9cae8 fffffa80`095b21a0 : fffffa80`095b2050 fffff880`04812016 fffffa80`095b2050 fffffa80`0e2f8380 : 0xfffffa80`0d695c00
fffff800`00b9caf0 fffffa80`095b2050 : fffff880`04812016 fffffa80`095b2050 fffffa80`0e2f8380 fffffa80`0b241560 : 0xfffffa80`095b21a0
fffff800`00b9caf8 fffff880`04812016 : fffffa80`095b2050 fffffa80`0e2f8380 fffffa80`0b241560 00000000`00000000 : 0xfffffa80`095b2050
fffff800`00b9cb00 fffff880`04802f89 : fffffa80`095b2050 00000000`00000000 fffffa80`095b2a02 fffffa80`095b2a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x162
fffff800`00b9cb60 fffff800`02cd430c : fffff800`02e44e80 fffffa80`095b2a18 fffffa80`095b2a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00b9cb90 fffff800`02cc18ca : fffff800`02e44e80 fffff800`02e52cc0 00000000`00000000 fffff880`04802db0 : nt!KiRetireDpcList+0x1bc
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+162
fffff880`04812016 4c8b4340        mov     r8,qword ptr [rbx+40h]

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+162

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  52272387

FAILURE_BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+162

BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+162

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

ASUS doesn't have the latest drivers listed. And it is difficult to search for drivers in Asmedia. As the driver is not developed by Asus, it is not a must to get from them.