BSOD (0x0xc000007e windows 7) When i unplugged Wireless Adapter

Hey guys new here.

So this problem is driving me crazy. I'm usually quite good with dealing with computer problems but this has left me completely lost.

The computer im using is a new build. (around 1.5 months ago)

CPU: i7 4790k
GPU: MSI GTX 980
Mobo: ASUS maximus hero VI
RAM: Corsair Vengence 8gb
OS: Windows 7 Service pack 1
Wirless usb adapter: TP-Link TL-WN822N

So as recently i started to get lag and sometimes would spike up to 600ms making the game completely unplayable and making me very ragey. So i thought it was just the wireless adapter over heating or something like that. I unplugged it and boom BSOD (0x0xc000007e).

So my first instinct was to google the issue thinking there would be a nice and easy fix. "This issue occurs because of a race condition in the USB Video driver when a USB video device is unloaded." That was the cause microsoft support was giving. After reading it, it sounded like what was happening to me.

Before i downloaded anything i done abit of testing. I disconnected other usb devices from the back of the computer. They didn't cause a BSOD. so i swapped the wireless adapter and plugged it in, then out. That still caused the BSOD. So i know for a certain it's causing the issue.

Now..... This is where i went down a massive rabbit hole.

First thing i tried:
Unistalled Avast as some people were claiming on a youtube comments section that was causing the issue (i know... im sorry). The BSOD still happened.

Second thing:

I downloaded the windows "hotfix". This is were i gets messy. I tried to run the .msu file but i got another message "this update is not applicable with your computer". Thinking, if i got this working it would then in turn stop the BSOD. So i proceeded to google that message. I read on some forum that i was missing some security windows updates. So i downloaded other "needed" updates (all those installed today). Some where installed using the windows update and others being a .msu standalone update. Then.. of course. It still doesn't install the hotfix for the BSOD error.

So this leaves me here, going crazy. Desperate for help . If anyone has had a similar problem and can offer ANY help id greatly appreciate it.

koolkat77 said:

Welcome.

Have you tried updating this driver?

Code:

Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\GARY-PC-06_01_2015__45707_23\010615-21387-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e4f890
Debug session time: Tue Jan  6 06:10:15.998 2015 (UTC + 6:00)
System Uptime: 0 days 0:01:59.810
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88006e0fe26, fffff88003738808, fffff88003738060}

Probably caused by : athurx.sys ( athurx+8e26 )

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

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006e0fe26, The address that the exception occurred at
Arg3: fffff88003738808, Exception Record Address
Arg4: fffff88003738060, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
athurx+8e26
fffff880`06e0fe26 488b8098260000  mov     rax,qword ptr [rax+2698h]

EXCEPTION_RECORD:  fffff88003738808 -- (.exr 0xfffff88003738808)
ExceptionAddress: fffff88006e0fe26 (athurx+0x0000000000008e26)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000002698
Attempt to read from address 0000000000002698

CONTEXT:  fffff88003738060 -- (.cxr 0xfffff88003738060;r)
rax=0000000000000000 rbx=fffffa800a3aa050 rcx=fffffa800a5d4030
rdx=0000000000000004 rsi=fffffa8006770b50 rdi=fffffa800a2144c0
rip=fffff88006e0fe26 rsp=fffff88003738a40 rbp=fffff80002e27280
 r8=0000000000000000  r9=0000000000000f44 r10=fffff80002c0c000
r11=0000000000000000 r12=fffffa800a2144c0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
athurx+0x8e26:
fffff880`06e0fe26 488b8098260000  mov     rax,qword ptr [rax+2698h] ds:002b:00000000`00002698=????????????????
Last set context:
rax=0000000000000000 rbx=fffffa800a3aa050 rcx=fffffa800a5d4030
rdx=0000000000000004 rsi=fffffa8006770b50 rdi=fffffa800a2144c0
rip=fffff88006e0fe26 rsp=fffff88003738a40 rbp=fffff80002e27280
 r8=0000000000000000  r9=0000000000000f44 r10=fffff80002c0c000
r11=0000000000000000 r12=fffffa800a2144c0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
athurx+0x8e26:
fffff880`06e0fe26 488b8098260000  mov     rax,qword ptr [rax+2698h] ds:002b:00000000`00002698=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000002698

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb9100
GetUlongFromAddress: unable to read from fffff80002eb91c0
 0000000000002698 Nonpaged pool

FOLLOWUP_IP: 
athurx+8e26
fffff880`06e0fe26 488b8098260000  mov     rax,qword ptr [rax+2698h]

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from fffffa800a3aa050 to fffff88006e0fe26

STACK_TEXT:  
fffff880`03738a40 fffffa80`0a3aa050 : fffff880`06e0fdc5 fffff880`06f53740 fffff880`06f536f0 00000000`000015d7 : athurx+0x8e26
fffff880`03738a48 fffff880`06e0fdc5 : fffff880`06f53740 fffff880`06f536f0 00000000`000015d7 00000000`00000004 : 0xfffffa80`0a3aa050
fffff880`03738a50 fffff880`06f53740 : fffff880`06f536f0 00000000`000015d7 00000000`00000004 00000000`00000000 : athurx+0x8dc5
fffff880`03738a58 fffff880`06f536f0 : 00000000`000015d7 00000000`00000004 00000000`00000000 00000000`c0000184 : athurx+0x14c740
fffff880`03738a60 00000000`000015d7 : 00000000`00000004 00000000`00000000 00000000`c0000184 00000000`00000000 : athurx+0x14c6f0
fffff880`03738a68 00000000`00000004 : 00000000`00000000 00000000`c0000184 00000000`00000000 0000057f`00000000 : 0x15d7
fffff880`03738a70 00000000`00000000 : 00000000`c0000184 00000000`00000000 0000057f`00000000 fffffa80`0a5d4af8 : 0x4


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  athurx+8e26

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athurx

IMAGE_NAME:  athurx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4daeb071

STACK_COMMAND:  .cxr 0xfffff88003738060 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_athurx+8e26

BUCKET_ID:  X64_0x7E_athurx+8e26

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_athurx+8e26

FAILURE_ID_HASH:  {ef04386b-f0b2-3efa-b240-ded80b69a26b}

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

7: kd> lmvm athurx
start             end                 module name
fffff880`06e07000 fffff880`06fe5000   athurx   T (no symbols)           
    Loaded symbol image file: athurx.sys
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys
    Timestamp:        Wed Apr 20 16:07:45 2011 (4DAEB071)
    CheckSum:         001E1C78
    ImageSize:        001DE000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

sorry but what driver do you mean ? Im trying to read that and i can't make out what one. Thanks for the reply

koolkat77 said:

Sorry about that.

The driver in this link :Driver Reference Table

I think i have the latest driver for my wireless adapter.

koolkat77 said:

Sorry about that.

The driver in this link :Driver Reference Table

unless that one will fix it ? sorry im confused, its because that driver you linked isnt the same as the tp link adapter that im using. My one

bump

No help ?

Arc said:

gazareap said:

No help ?

People has other things to do, specially when you are not ready to take suggestions.

gazareap said:

I think i have the latest driver for my wireless adapter.

Dont think, verify.

Your adapter is TP-Link TL-WN822N 300MBPS High Gain Wireless N USB Adapter, as you said. The installed driver is of 2011 ...

Code:

    Image name: athurx.sys
    Timestamp:        Wed Apr 20 15:37:45 2011 (4DAEB071)

The suggested driver is ....

Code:

Version: 10.0.0.297
Release: 2014-07-22   [July '14]

Attachment 345474

Try it, then think.

Im trying this now. Sorry if i came across ignorant. I know people have stuff to do and frankly, helping a random online isn't top of their priorities. So i am honestly very grateful for ANY help offered. I'll report back when i try it.