BSOD, unable to determine exact cause

camphlps · 30 Jun 2013

Been receiving numerous BSOD for months. I never was able to determine the exact cause the first time. Most of the time the error occurs during a game such as Skyrim, Diablo 3. However, sometimes the error happened when watching videos on YouTube or even while idle.

Every time I thought I fixed it, I get a new one. Most of the time it was IRQ less than or equal. I swapped to an older card and it was less frequent, but still got them. Im back to the original card and still get the errors. Sometimes going days without errors, sometimes cant even go 20 minutes without one.

Im a bit lost in the dark on this one, documentation on the web point every direction, blaming video drivers, windows programs and even wireless adapters.

Arc · 30 Jun 2013

The TP link network adapter is old.

Code:

fffff880`05e09000 fffff880`05fe7000   athurx     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys
    Timestamp:        Wed Apr 20 15:37:45 2011 (4DAEB071)
    CheckSum:         001E1C78
    ImageSize:        001DE000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Download - Welcome to TP-LINK , by matching your device number.

And, Disable USB Selective Suspensd too.
USB Selective Suspend - Turn On or Off

Let us know the results.
______________________________________________________________________________

Code:

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {74, 2, 1, fffff88005672cec}

Probably caused by : usbohci.sys ( usbohci!OHCI_ProcessDoneIsoTd+30 )

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

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af100
GetUlongFromAddress: unable to read from fffff800030af1c0
 0000000000000074 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
usbohci!OHCI_ProcessDoneIsoTd+30
fffff880`05672cec 014674          add     dword ptr [rsi+74h],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF880030B7FB0

TRAP_FRAME:  fffff880030b0930 -- (.trap 0xfffff880030b0930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=fffffa8006aeb6a0
rdx=fffff88008678280 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005672cec rsp=fffff880030b0ac0 rbp=fffffa8007822f06
 r8=000000004f444601  r9=fffff88008678280 r10=00000000ffffffff
r11=fffff880030b0b28 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
usbohci!OHCI_ProcessDoneIsoTd+0x30:
fffff880`05672cec 014674          add     dword ptr [rsi+74h],eax ds:00000000`00000074=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e771a9 to fffff80002e77c00

STACK_TEXT:  
fffff880`030b07e8 fffff800`02e771a9 : 00000000`0000000a 00000000`00000074 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`030b07f0 fffff800`02e75e20 : fffffa80`06a7a1a0 fffffa80`06a7a101 fffffa80`0708da00 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`030b0930 fffff880`05672cec : fffffa80`0529d840 00000000`00000001 fffffa80`06a7a101 fffff880`053bdea0 : nt!KiPageFault+0x260
fffff880`030b0ac0 fffff880`05672f7d : 00000000`00000004 fffff880`08678080 fffffa80`06aea101 fffffa80`056fa648 : usbohci!OHCI_ProcessDoneIsoTd+0x30
fffff880`030b0b30 fffff880`05675744 : fffffa80`056fa648 fffffa80`056fa400 fffffa80`06aea1a0 00000000`ffffff02 : usbohci!OHCI_PollIsoEndpoint+0x101
fffff880`030b0b80 fffff880`05391e8b : 00000000`00000002 fffffa80`056fa400 fffffa80`06aea1a0 00000000`00000000 : usbohci!OHCI_PollEndpoint+0x4c
fffff880`030b0bb0 fffff880`053969d1 : 00000000`00000040 00000000`00000004 fffffa80`056fa400 fffffa80`06aea050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`030b0be0 fffff880`053a2077 : fffffa80`06aea1a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`030b0c40 fffff880`05392f89 : fffffa80`06aea050 00000000`00000000 fffffa80`06aeaa02 fffffa80`06aeaa18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`030b0ca0 fffff800`02e822fc : fffff880`03088180 fffffa80`06aeaa18 fffffa80`06aeaa30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`030b0cd0 fffff800`02e6f90a : fffff880`03088180 fffff880`03093040 00000000`00000000 fffff880`05392db0 : nt!KiRetireDpcList+0x1bc
fffff880`030b0d80 00000000`00000000 : fffff880`030b1000 fffff880`030ab000 fffff880`030b0d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbohci!OHCI_ProcessDoneIsoTd+30
fffff880`05672cec 014674          add     dword ptr [rsi+74h],eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbohci!OHCI_ProcessDoneIsoTd+30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbohci

IMAGE_NAME:  usbohci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0bff

FAILURE_BUCKET_ID:  X64_0xD1_usbohci!OHCI_ProcessDoneIsoTd+30

BUCKET_ID:  X64_0xD1_usbohci!OHCI_ProcessDoneIsoTd+30

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

5: kd> lmvm usbohci
start             end                 module name
fffff880`05671000 fffff880`0567c000   usbohci    (pdb symbols)          c:\symbols\usbohci.pdb\45ADE9C11E264B08BFCF9E0A1B4D27C01\usbohci.pdb
    Loaded symbol image file: usbohci.sys
    Mapped memory image file: c:\symbols\usbohci.sys\4D8C0BFFb000\usbohci.sys
    Image path: \SystemRoot\system32\DRIVERS\usbohci.sys
    Image name: usbohci.sys
    Timestamp:        Fri Mar 25 08:59:03 2011 (4D8C0BFF)
    CheckSum:         00008443
    ImageSize:        0000B000
    File version:     6.1.7601.17586
    Product version:  6.1.7601.17586
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     USBOHCI.sys
    OriginalFilename: USBOHCI.sys
    ProductVersion:   6.1.7601.17586
    FileVersion:      6.1.7601.17586 (win7sp1_gdr.110324-1501)
    FileDescription:  OHCI USB Miniport Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

camphlps · 04 Jul 2013

No new drivers avail for tp link, I just got in my new adapter today and installed. So I will post back if BSOD happens again

Arc · 04 Jul 2013

Good luck :)
Let us know how the computer is working with the new adapter?

camphlps · 17 Aug 2013

Tried 2 new devices for up to 300mbs. I cant seem to find one that has any driver update since 2011.

The latest one doesn't crash as often and connection strength is great. My only alternative I can think of is to switched to a wired connection, but I cant at the moment.

Arc · 18 Aug 2013

I think you are right.

The driver is developed by Atheros, but the device is sold by TP Link. So nobody have the updates.
One more thing you may do ... to get a new adapter, which is made and marketed by the same vendor and so updates will be available over a reasonably long time.

camphlps · 06 Sep 2013

Went completely away from wireless this time, even to the point of disabling window's application for controlling the device.
I went to a wired connection and no bsod for about a week. Just last night got 2 more of the same crash. uploaded my updated logs including the two new crashes.

Arc · 06 Sep 2013

Some problem with the USB drivers. Upload the list of all the third party drivers Using NirSoft DriverView :

Download and execute Driverview
View > Hide Microsoft Drivers
Edit > Select all
File > Save Selected Items
In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
Zip the .txt file and upload it.

camphlps · 07 Sep 2013

ok here it is

Arc · 07 Sep 2013

Update the AMD chipset driver for Windows 7. AMD Chipset Drivers

Description:
This package is for motherboards with 700 series or newer AMD chipsets, and includes:
AMD Chipset Drivers
AMD AHCI Driver
AMD USB 3.0 Driver