Solved Constant BSOD after Re-installing Windows

[Chimi]

Hi guys, I've posted on here a couple months ago about BSOD problems I was having and after multiple tests of the hardware, everything was coming back fine. I ended up just re-installing Windows to give a clean install and see if that fixed any issues but it seems like it keeps happening. It's gradually gotten worse which led to me turning on driver verifier which has caused my computer to crash repeatably today.

Here is the upload needed. This has been going on for months and at this point I'm feeling desperate to fix it. I'm not sure if it's relevant, but I have noticed it crashes more frequently while playing World of Warcraft. Especially if I'm doing something with a large group of people. It'll be fine for a couple hours and then BSOD almost at the same time every night.

Anyhow, any help would be appreciated.

 

[Golden]

*** WARNING: Unable to verify timestamp for asmtxhci.sys
*** ERROR: Module load completed but symbols could not be loaded for asmtxhci.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc000001d, fffff880048c0141, fffff88004c29948, fffff88004c291a0}

Probably caused by : asmtxhci.sys ( asmtxhci+24141 )

Followup: MachineOwner
0: kd> lmvm asmtxhci
start             end                 module name
fffff880`0489c000 fffff880`048ff000   asmtxhci T (no symbols)           
    Loaded symbol image file: asmtxhci.sys
    Image path: \SystemRoot\system32\DRIVERS\asmtxhci.sys
    Image name: asmtxhci.sys
    Timestamp:        [B][COLOR="Red"]Fri Mar 04 18:24:59 2011[/COLOR][/B] (4D709AD3)
    CheckSum:         0006C1A9
    ImageSize:        00063000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
---------

Please check for updates for the Asmedia USB3 driver:
ASMedia Technology Inc.

 

[Chimi]

Thanks for the reply. I did update that driver earlier today but after some digging, it appears there is an even newer driver than the one I had previously downloaded. I just installed the newer driver so I'll give it a test drive and update on any new BSOD if they happen.

 

[Chimi]

That didn't last too long. After an hour or two, I got another BSOD.

 

[Golden]

FOLLOWUP_IP: 
USBPORT!USBPORT_Core_iGetNextPriorityTransfer+5f
fffff880`049723b3 83a80000004885  sub     dword ptr [rax+48000000h],0FFFFFF85h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  USBPORT!USBPORT_Core_iGetNextPriorityTransfer+5f

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  6.1.7601.18328

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned

FAILURE_ID_HASH:  {45769616-fd06-8c70-4b8b-74a01eddc0cd}

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

0: kd> lmvm hardware
start             end                 module name
0: kd> !thread
GetPointerFromAddress: unable to read from fffff80002ec9000
THREAD fffffa800c0a1060  Cid 04b4.0e10  Teb: 000007fffffae000 Win32Thread: 0000000000000000 RUNNING on processor 0
IRP List:
    Unable to read nt!_IRP @ fffff980573c4bd0
Not impersonating
GetUlongFromAddress: unable to read from fffff80002e08ba8
Owning Process            fffffa800b34c650       Image:         audiodg.exe

Are there any audio/audio-related devices connected via USB port?

 

[Chimi]

I have some Logitech Headphones connected to USB and a Creative Labs SB1090 sound card. The headphones are brand new, I haven't even had them a week and the problem was going on before those. So maybe the sound card? I've had that sound card for a while.

 

[Chimi]

I tried updating drivers for the sound card and then just ended up removing it all together. I still kept getting BSODs yesterday. Spent most of the day trying to look for fixes and update drivers but still, they kept happening. It seems like every BSOD is something different.

Anyhow, here is another zip file of the stuff. I'm super close to just throwing my computer out the window, haha.

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffda801a4fe267, 2, 1, fffff88005417c0e}

*** WARNING: Unable to verify timestamp for iusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3hub.sys
Probably caused by : hardware ( iusb3hub+17c0e )

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

0: kd> lmvm iusb3hub
start             end                 module name
fffff880`05400000 fffff880`0545d000   iusb3hub T (no symbols)           
    Loaded symbol image file: iusb3hub.sys
    Image path: \SystemRoot\system32\DRIVERS\iusb3hub.sys
    Image name: iusb3hub.sys
    Timestamp:        [COLOR="Red"][B]Wed Sep 18 00:14:18 2013[/B][/COLOR] (52386AC2)
    CheckSum:         0006110E
    ImageSize:        0005D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

See if there is an update for the Intel USB driver here:
https://downloadcenter.intel.com/default.aspx

 

[Chimi]

I updated the USB driver from Intel. Since then however, I've still received a few BSOD. I've tried going through and just updating every driver I could possibly find that might be outdated but the blue screens keep coming. It's getting to the point where it's hard to play with friends because while we're playing WoW or something, I just crash in the middle of stuff.

Thanks for your help so far. Hopefully these new dumps will provide some new info.

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80003088ca8}

Probably caused by : ntkrnlmp.exe ( nt!KiInsertQueue+a8 )

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

0: kd> !thread
GetPointerFromAddress: unable to read from fffff800032ca000
THREAD fffffa800c739190  Cid 09ac.0be4  Teb: 000007fffff06000 Win32Thread: 0000000000000000 RUNNING on processor 0
Not impersonating
GetUlongFromAddress: unable to read from fffff80003209ba8
Owning Process            fffffa800aeef230       Image:         [COLOR="Red"][B]CurseClient.ex[/B][/COLOR]
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data

The only thing I can tell is that CurseClient (the WoW add-on) is running during the crash. The only advice I can give at the moment is to disable it, and see if you avoid BSOD'ing whilst playing WoW.

 

[Chimi]

Alright, I will give that a try and let you know how it goes.

 

[Chimi]

Figured I'd give an update. Since my last post I have disabled Curse and I haven't had a single BSOD since then. Things seem to be running very smoothly now. So thank you for all the help. Very much appreciated.

 

[Golden]