Blue screen error with nomally using.

Visitor

I've used WinDbg for its analysis. And answer is the error of 'rtwlane'. All from Internet searching tell me that my WLAN should be updated, which I've done when last blue screen error happened and then I used my 'fixed' computer for about 10 days till now. But when the error occured firstly, we started to use a new WIFI6-support router for serveral days.

The WinDbg analysis follows:

 

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

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff80153971358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding this single DPC timeout

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

*** WARNING: Unable to verify timestamp for rtwlane.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3593

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 11283

    Key  : Analysis.Init.CPU.mSec
    Value: 936

    Key  : Analysis.Init.Elapsed.mSec
    Value: 9794

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 84

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  092222-6578-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80153971358

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff801`58b5cb08 fffff801`535f4b97     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff801`58b5cb10 fffff801`53435107     : 0000001c`f42394a0 fffff801`4feb9180 00000000`00000286 fffff801`58b553a0 : nt!KeAccumulateTicks+0x1c1837
fffff801`58b5cb70 fffff801`5335f291     : ffff900e`82000000 fffff801`533cc000 fffff801`58b55420 fffff801`533cc0b0 : nt!KeClockInterruptNotify+0xc07
fffff801`58b5cf30 fffff801`534fdaa5     : fffff801`533cc000 00000000`00000010 ffff4146`4a944d15 ffff900e`820000f8 : hal!HalpTimerClockIpiRoutine+0x21
fffff801`58b5cf60 fffff801`535c55aa     : fffff801`58b55420 fffff801`533cc000 ffff900e`82001400 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`58b5cfb0 fffff801`535c5b17     : ffff900e`8200b83c 00000000`00000100 fffff801`70873000 ffff900e`82000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff801`58b553a0 fffff801`534089a0     : ffff900e`82000000 fffff801`7077207c ffff900e`80f5fb18 fffff801`58b55580 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`58b55530 fffff801`53408587     : ffff900e`820000f8 fffff801`4feb9180 fffff801`707d9df0 fffff801`00000001 : nt!KxWaitForSpinLockAndAcquire+0x30
fffff801`58b55560 fffff801`707cbc38     : ffff900e`80f60df0 ffff900e`82000000 ffff900e`820014ff fffff801`70771964 : nt!KeAcquireSpinLockRaiseToDpc+0x87
fffff801`58b55590 ffff900e`80f60df0     : ffff900e`82000000 ffff900e`820014ff fffff801`70771964 ffffde81`a2f14020 : rtwlane+0x3cbc38
fffff801`58b55598 ffff900e`82000000     : ffff900e`820014ff fffff801`70771964 ffffde81`a2f14020 fffff801`7052c50e : 0xffff900e`80f60df0
fffff801`58b555a0 ffff900e`820014ff     : fffff801`70771964 ffffde81`a2f14020 fffff801`7052c50e 00000000`00000000 : 0xffff900e`82000000
fffff801`58b555a8 fffff801`70771964     : ffffde81`a2f14020 fffff801`7052c50e 00000000`00000000 ffff900e`825bf610 : 0xffff900e`820014ff
fffff801`58b555b0 ffffde81`a2f14020     : fffff801`7052c50e 00000000`00000000 ffff900e`825bf610 00000000`00000000 : rtwlane+0x371964
fffff801`58b555b8 fffff801`7052c50e     : 00000000`00000000 ffff900e`825bf610 00000000`00000000 00000000`00000000 : 0xffffde81`a2f14020
fffff801`58b555c0 00000000`00000000     : ffff900e`825bf610 00000000`00000000 00000000`00000000 ffffffff`ffffffff : rtwlane+0x12c50e


SYMBOL_NAME:  rtwlane+3cbc38

MODULE_NAME: rtwlane

IMAGE_NAME:  rtwlane.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  3cbc38

FAILURE_BUCKET_ID:  0x133_DPC_rtwlane!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {59e49550-247c-b883-d51a-d0d9f839f43f}

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

 

0 Replies