Mini Dump file, can someone work out what's going on here ?

[The Matrix]

Ive had a few bluescreens of late, the culprit maybe My TP-Link WN822N Wireless USB adapter as quite a few people have reported the same issue who are using Windows 7 64 bit. TP-Link havn't updated the drivers for around 2 years and don't seem that bothered about it.

Here are the details, hope ive done it right.


Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
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`03056000 PsLoadedModuleList = 0xfffff800`03299890
Debug session time: Sun Dec 7 10:19:02.402 2014 (UTC - 5:00)
System Uptime: 0 days 0:05:00.354
*******************************************************************************
* *
* 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: fffff88007c17e26, The address that the exception occurred at
Arg3: fffff8800a206808, Exception Record Address
Arg4: fffff8800a206060, Context Record Address

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

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`07c17e26 488b8098260000 mov rax,qword ptr [rax+2698h]

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

CONTEXT: fffff8800a206060 -- (.cxr 0xfffff8800a206060)
rax=0000000000000000 rbx=fffffa800dc56050 rcx=fffffa800dc79030
rdx=0000000000000004 rsi=fffffa800e960040 rdi=fffffa800836a5a0
rip=fffff88007c17e26 rsp=fffff8800a206a40 rbp=fffff80003271280
r8=fffffa80069ee918 r9=0000000000000000 r10=ffffffffffffffbf
r11=0000000000000000 r12=fffffa800836a5a0 r13=0000000000000001
r14=fffff8800a206ba8 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010282
athurx+0x8e26:
fffff880`07c17e26 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 fffff80003303100
GetUlongFromAddress: unable to read from fffff800033031c0
0000000000002698 Nonpaged pool

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

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffffa800dc56050 to fffff88007c17e26

STACK_TEXT:
fffff880`0a206a40 fffffa80`0dc56050 : fffff880`07c17dc5 fffff880`07d5b740 fffff880`07d5b6f0 00000000`000015d7 : athurx+0x8e26
fffff880`0a206a48 fffff880`07c17dc5 : fffff880`07d5b740 fffff880`07d5b6f0 00000000`000015d7 00000000`00000004 : 0xfffffa80`0dc56050
fffff880`0a206a50 fffff880`07d5b740 : fffff880`07d5b6f0 00000000`000015d7 00000000`00000004 00000000`00000000 : athurx+0x8dc5
fffff880`0a206a58 fffff880`07d5b6f0 : 00000000`000015d7 00000000`00000004 00000000`00000000 fffff880`c0000184 : athurx+0x14c740
fffff880`0a206a60 00000000`000015d7 : 00000000`00000004 00000000`00000000 fffff880`c0000184 00000000`00000000 : athurx+0x14c6f0
fffff880`0a206a68 00000000`00000004 : 00000000`00000000 fffff880`c0000184 00000000`00000000 0000057f`00000000 : 0x15d7
fffff880`0a206a70 00000000`00000000 : fffff880`c0000184 00000000`00000000 0000057f`00000000 fffffa80`0dc79af8 : 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 0xfffff8800a206060 ; kb

FAILURE_BUCKET_ID: X64_0x7E_athurx+8e26

BUCKET_ID: X64_0x7E_athurx+8e26

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

 

[Pho]

athurx.sys was the driver which caused the crash which appears to be an Atheros one. Atheros make various ethernet/wifi chips so chances are it is the driver for your TP-Link card which is causing the problem!

 

[The Matrix]

Could i possibly disable the Atheros side of things as a temp solution, is it the Atheros driver that's in conflict with the TP - Link wireless adapter driver ?

 

[zakblood]

as tplink stuff is as cheap as chips, buy a different one, job done, if it was mega money then maybe scratch your head a bit, but as it's not, when in doubt chuck it out

 

[Pho]

Yep, it's probably easier to ditch the card and get a new one.

Try older versions of the driver if you can, but chances are it may still use the athurx.sys driver - an old one may not have this issue though.