Windows 10 TL-WN881ND v2 crash with debug info
It passed a few months since the BSOD persist.. so I decided to ask for help in order to leave this problem forever. My wifi adapter is TP-Link Wireless N PCI Express (TL-WN881ND) 300 mbps.
Minidump info:
Microsoft (R) Windows Debugger Version 10.0.17763.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\043020-14234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`08a00000 PsLoadedModuleList = 0xfffff802`08e48150
Debug session time: Thu Apr 30 11:00:44.333 2020 (UTC + 2:00)
System Uptime: 1 days 14:43:27.078
Loading Kernel Symbols
...............................................................
................................................................
................................................................
Loading User Symbols
Loading unloaded module list
......................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffff80000003, fffff80208a5a1c8, ffffc90c5dd1e3d8, ffffc90c5dd1dc20}
*** WARNING: Unable to verify timestamp for rtwlane02.sys
*** ERROR: Module load completed but symbols could not be loaded for rtwlane02.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : rtwlane02.sys ( rtwlane02+36b4d6 )
Followup: MachineOwner
---------
0: 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: ffffffff80000003, The exception code that was not handled
Arg2: fffff80208a5a1c8, The address that the exception occurred at
Arg3: ffffc90c5dd1e3d8, Exception Record Address
Arg4: ffffc90c5dd1dc20, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202
DUMP_TYPE: 2
BUGCHECK_P1: ffffffff80000003
BUGCHECK_P2: fffff80208a5a1c8
BUGCHECK_P3: ffffc90c5dd1e3d8
BUGCHECK_P4: ffffc90c5dd1dc20
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Uno o pi argomenti non validi.
FAULTING_IP:
nt!KeCheckStackAndTargetAddress+48
fffff802`08a5a1c8 cc int 3
EXCEPTION_RECORD: ffffe2064d000000 -- (.exr 0xffffe2064d000000)
ExceptionAddress: f25cdae9e16472ed
ExceptionCode: 4d100000
ExceptionFlags: ffffe206
NumberParameters: 0
CONTEXT: ffffc90c5dd1dc20 -- (.cxr 0xffffc90c5dd1dc20)
rax=ffffc90c5dd1e638 rbx=ffffc90c5dd1f858 rcx=00000000f1000000
rdx=ffffc90c5dd1f858 rsi=ffffc90c5dd1ee60 rdi=00000000f1000000
rip=fffff80208a5a1c8 rsp=ffffc90c5dd1e610 rbp=ffffc90c5dd1ec20
r8=ffffc90c5dd1ee60 r9=ffffc90c5dd1eca0 r10=00007ffffffeffff
r11=ffffc90c5dd1e6a8 r12=ffffc90c5dd1fb10 r13=ffffc90c5dd1f618
r14=ffffc90c5dd1eca0 r15=fffff80208f16d84
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00040206
nt!KeCheckStackAndTargetAddress+0x48:
fffff802`08a5a1c8 cc int 3
Resetting default scope
CPU_COUNT: 4
CPU_MHZ: e10
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: b
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0x80000003 - {ERRORE DI EXCEPTION} Breakpoint stato raggiunto un breakpoint.
EXCEPTION_CODE_STR: 80000003
EXCEPTION_PARAMETER1: 0000000000000000
ANALYSIS_SESSION_HOST: DESKTOP-LSADSVS
ANALYSIS_SESSION_TIME: 04-30-2020 11:09:42.0427
ANALYSIS_VERSION: 10.0.17763.1 amd64fre
TRAP_FRAME: ffffe2064d560000 -- (.trap 0xffffe2064d560000)
Unable to read trap frame at ffffe206`4d560000
LAST_CONTROL_TRANSFER: from fffff80208b9d315 to fffff80208a5a1c8
STACK_TEXT:
ffffc90c`5dd1e610 fffff802`08b9d315 : 00000000`00000000 ffffc90c`5dd1fb10 fffff802`225ebd98 ffffc90c`5dd1ec30 : nt!KeCheckStackAndTargetAddress+0x48
ffffc90c`5dd1e640 fffff802`08bcb17f : ffffc90c`5dd1fb10 ffffc90c`5dd1ec20 00000000`00000000 00000000`0010001f : nt!_C_specific_handler+0x45
ffffc90c`5dd1e6b0 fffff802`08afa2c5 : 00000000`00000000 00000000`00000000 ffffc90c`5dd1ec20 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0xf
ffffc90c`5dd1e6e0 fffff802`08afe85e : ffffc90c`5dd1f618 ffffc90c`5dd1f360 ffffc90c`5dd1f618 ffffa20c`4bdb9678 : nt!RtlDispatchException+0x4a5
ffffc90c`5dd1ee30 fffff802`08bd431d : ffffc8e4`72391000 ffffc90c`5dd1f6c0 ffff8000`00000000 00000000`f1000000 : nt!KiDispatchException+0x16e
ffffc90c`5dd1f4e0 fffff802`08bd0503 : 00000000`00000000 00000000`00000000 00000000`00000900 00000000`00000000 : nt!KiExceptionDispatch+0x11d
ffffc90c`5dd1f6c0 00000000`f1000000 : fffff802`220bb4d6 ffffa20c`46db7ba8 ffffa20c`46640002 fffff802`22173e00 : nt!KiPageFault+0x443
ffffc90c`5dd1f858 fffff802`220bb4d6 : ffffa20c`46db7ba8 ffffa20c`46640002 fffff802`22173e00 ffffa20c`4bdb9678 : 0xf1000000
ffffc90c`5dd1f860 ffffa20c`46db7ba8 : ffffa20c`46640002 fffff802`22173e00 ffffa20c`4bdb9678 fffff802`00000002 : rtwlane02+0x36b4d6
ffffc90c`5dd1f868 ffffa20c`46640002 : fffff802`22173e00 ffffa20c`4bdb9678 fffff802`00000002 00000000`00002000 : 0xffffa20c`46db7ba8
ffffc90c`5dd1f870 fffff802`22173e00 : ffffa20c`4bdb9678 fffff802`00000002 00000000`00002000 fffff802`22152b30 : 0xffffa20c`46640002
ffffc90c`5dd1f878 ffffa20c`4bdb9678 : fffff802`00000002 00000000`00002000 fffff802`22152b30 00000000`00000000 : rtwlane02+0x423e00
ffffc90c`5dd1f880 fffff802`00000002 : 00000000`00002000 fffff802`22152b30 00000000`00000000 fffff802`221d3000 : 0xffffa20c`4bdb9678
ffffc90c`5dd1f888 00000000`00002000 : fffff802`22152b30 00000000`00000000 fffff802`221d3000 fffff802`22174378 : 0xfffff802`00000002
ffffc90c`5dd1f890 fffff802`22152b30 : 00000000`00000000 fffff802`221d3000 fffff802`22174378 fffff802`221d3000 : 0x2000
ffffc90c`5dd1f898 00000000`00000000 : fffff802`221d3000 fffff802`22174378 fffff802`221d3000 fffff802`220bb33e : rtwlane02+0x402b30
THREAD_SHA1_HASH_MOD_FUNC: 04f0a0a88884a10543eed6c236ed99b67287bc90
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: a4fe3cb17f13765cf7d5dc37211d20e6f7cd886d
THREAD_SHA1_HASH_MOD: b568e3970b785698687d5305ad786ae4b24e54bd
FOLLOWUP_IP:
rtwlane02+36b4d6
fffff802`220bb4d6 837b5401 cmp dword ptr [rbx+54h],1
FAULT_INSTR_CODE: 1547b83
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: rtwlane02+36b4d6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: rtwlane02
IMAGE_NAME: rtwlane02.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5c94890c
STACK_COMMAND: .cxr 0xffffc90c5dd1dc20 ; kb
BUCKET_ID_FUNC_OFFSET: 36b4d6
FAILURE_BUCKET_ID: AV_rtwlane02!unknown_function
BUCKET_ID: AV_rtwlane02!unknown_function
PRIMARY_PROBLEM_CLASS: AV_rtwlane02!unknown_function
TARGET_TIME: 2020-04-30T09:00:44.000Z
OSBUILD: 18362
OSSERVICEPACK: 778
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2015-10-23 08:39:54
BUILDDATESTAMP_STR: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: cba6
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_rtwlane02!unknown_function
FAILURE_ID_HASH: {74f1dee3-966d-8467-64f2-d1bcdf59b8b3}
Followup: MachineOwner
---------