Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: BSOD after corrupt World of Warcraft patch, 2nd BSOD days later

24 May 2013   #1

Windows 7 Home 64 bit
 
 
BSOD after corrupt World of Warcraft patch, 2nd BSOD days later

Corrupted WoW patch 5.3 caused my game client and eventually entire computer to lock up upon loading into game, resulting in a BSOD.

I redownloaded and installed the entire game client and it solved the problem of the game locking up.

Everything seemed fine until this morning when I woke up to another BSOD. So I thought I would post the dumps and see if anyone had any idea what caused this one and/or the first one.

Thanks in advanced!

My System SpecsSystem Spec
.

24 May 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
 
 

It appears that your Asmedia USB 3.0 driver caused the BSOD:

Code:
*** WARNING: Unable to verify timestamp for asmtxhci.sys
*** ERROR: Module load completed but symbols could not be loaded for asmtxhci.sys
ERROR: FindPlugIns 80070005
ERROR: Some plugins may not be available [80070005]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800721b716, fffff88002923708, fffff88002922f60}

Probably caused by : asmtxhci.sys ( asmtxhci+1b716 )

Followup: MachineOwner
---------
Driver Reference Table - asmtxhci.sys

Looking at the driver we can see it is rather old:

Code:
kd> lmvm asmtxhci
start             end                 module name
fffff880`07200000 fffff880`07264000   asmtxhci T (no symbols)           
    Loaded symbol image file: asmtxhci.sys
    Image path: \SystemRoot\system32\DRIVERS\asmtxhci.sys
    Image name: asmtxhci.sys
    Timestamp:        Wed Sep 14 03:36:09 2011 (4E705969)
    CheckSum:         0006E608
    ImageSize:        00064000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Please update the driver from here: ASMedia Technology Inc. ????

Other things to consider:

Removing Daemon tools, as it is a known causer of BSODs:

Code:
Start Menu\Programs\DAEMON Tools Lite
If you remove Daemon tools be sure to download and run this tool aswell:

DuplexSecure - Downloads

when the tool runs if the uninstall button is grayed out you are done and can close out of the windows if not click it and allow the tool to do its job. DO NOT click the install button it will install a driver known to cause BSODs onto your system.


You may want to think about preforming a clean start up there are many items in your start up which could be slowing your PC down during boot:

Troubleshoot Application Conflicts by Performing a Clean Startup
My System SpecsSystem Spec
24 May 2013   #3

Windows 7 Home 64 bit
 
 

I updated the drivers on the USB 3.0 to the newest I could find, which are not much newer, only by a month or so. We will see if it works out. Daemon tools will go away soon as well, just need to keep it until I finish with a build project I am working on. Otherwise I have no use for it.
My System SpecsSystem Spec
.


24 May 2013   #4

Microsoft Community Contributor Award Recipient

Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
 
 

Quote:
I updated the drivers on the USB 3.0 to the newest I could find, which are not much newer, only by a month or so. We will see if it works out.
Some times updates just don't play nice with older drivers, and even if the version is only slightly newer it may still solve the problem.

Quote:
Daemon tools will go away soon as well, just need to keep it until I finish with a build project I am working on. Otherwise I have no use for it.
That's Fine as I said it is known to cause BSODs but it didn't seem to be causing troubles in this case.
My System SpecsSystem Spec
Reply

 BSOD after corrupt World of Warcraft patch, 2nd BSOD days later





Thread Tools



Similar help and support threads for2: BSOD after corrupt World of Warcraft patch, 2nd BSOD days later
Thread Forum
BSOD installing World of Warcraft BSOD Help and Support
BSOD while playing World of Warcraft BSOD Help and Support
Solved BSOD playing World of Warcraft BSOD Help and Support
BSOD while playing world of warcraft BSOD Help and Support
Rage of the Firelands, Patch 4.2 for World of Warcraft Gaming
BSOD When Only Playing World Of Warcraft BSOD Help and Support
BSOD on World of Warcraft BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:19 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33