通过以太网连接到互联网时出现 BSOD

2024-10-27 • tag-icon

问题定义

我在联想笔记本电脑上使用 Windows 10，配有 Realtek 网卡。网卡在设备管理器中显示为“Realtek PCIe GbE 系列控制器”，我通常使用以太网连接到互联网。这 3/4 年一直运行良好。几天以来，通过以太网连接到互联网 30 到 90 秒后，我收到 BSOD 并且 PC 重新启动。

我做了什么（并没有解决问题）

我确信这是一个 IP 地址冲突问题。我有静态 IP 地址，但可以更改为动态。我这样做了，但在典型的 30 到 90 秒后，PC 出现了 BSOD 并重新启动。
我从供应商网站下载了最新的驱动程序。我现在拥有 2022 年 8 月 24 日的驱动程序版本 10.62.824.2022。
根据建议莫伊舍·皮皮克博士，我用了Windows DISM 和 SFC 实用程序检查系统文件问题。DISM 没有发现任何问题。SFC 发现并修复了一些问题，但这并不能解决 BSOD 问题。
根据建议猎羊犬，我更新到了 Windows 10 22H2。之后，我插上了以太网线。几分钟后……再次出现 BSOD。
根据建议丹尼尔B我在连接以太网时禁用了 Wi-Fi 卡（Intel 双频 Wireless-AC 3160）。几分钟后……情况还是一样。（您可能注意到，我们现在讨论的是分钟，而不是 30 秒到 90 秒。
根据建议思凯利我开始更新一些驱动程序。由于我已经更新了以太网卡驱动程序，因此，考虑到丹尼尔B问题可能是由 Wi-Fi 引起的，我决定先更新 Wi-Fi 驱动程序。现在的版本是 2019 年 4 月 29 日的 18.33.17.1，取代了 2016 年的版本。几分钟后... BSOD。
根据建议约翰，我禁用了以太网卡并通过 USB LAN 网卡连接。同样的故事。

我提取的信息

我执行了 WinDbg（只是因为我读到它很有用）希望有人明白发生了什么：

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`37200000 PsLoadedModuleList = 0xfffff803`37e2a2b0
Debug session time: Wed Nov 23 13:40:22.028 2022 (UTC + 1:00)
System Uptime: 0 days 4:56:48.766
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols

Loading unloaded module list
.......................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`375f92d0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff803`3c67ee20=0000000000000133
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: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff80337efb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: 6936

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 965324

    Key  : Analysis.IO.Other.Mb
    Value: 14

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 23

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80337efb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffff9a84bf4ae1f0 -- (.trap 0xffff9a84bf4ae1f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000001d20c0002 rbx=0000000000000000 rcx=fffff80337e59740
rdx=fffffffffffffff0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80337602907 rsp=ffff9a84bf4ae380 rbp=ffff9a84bf4ae471
 r8=fffffffffffffff0  r9=0000000000000000 r10=fffff80337e59740
r11=ffff8dffc5000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ExpInterlockedPopEntrySListFault:
fffff803`37602907 498b08          mov     rcx,qword ptr [r8] ds:ffffffff`fffffff0=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT:  
fffff803`3c67ee18 fffff803`3765bf02     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`37efb320 : nt!KeBugCheckEx
fffff803`3c67ee20 fffff803`374d2973     : 00002d47`78984ce4 fffff803`33f87180 00000000`00000000 fffff803`33f87180 : nt!KeAccumulateTicks+0x186d32
fffff803`3c67ee80 fffff803`374d245a     : fffff803`37ef3880 ffff9a84`bf4adf00 fffff803`3ca8d800 00000000`0000a201 : nt!KeClockInterruptNotify+0x453
fffff803`3c67ef30 fffff803`37408a45     : fffff803`37ef3880 fffff803`3c67ef40 00000000`00000010 ffff959c`76c911b0 : nt!HalpTimerClockIpiRoutine+0x1a
fffff803`3c67ef60 fffff803`375fb26a     : ffff9a84`bf4adf00 fffff803`37ef3880 00000000`00000200 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`3c67efb0 fffff803`375fba37     : fffff71b`f5e422c0 fffff803`3752300a ffff9a84`00000000 ffffffff`fffffff0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff9a84`bf4ade80 fffff803`3760d3ad     : 00000000`00000000 ffff9a84`bf4ae270 ffffffff`ffffffd2 fffff803`3743962f : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff9a84`bf4ae010 fffff803`37608ebd     : fffff803`37e59740 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x6d
ffff9a84`bf4ae1f0 fffff803`37602907     : fffff803`37e59740 fffff803`37427b0f ffffd607`834c9b20 ffffd607`88b83dc0 : nt!KiPageFault+0x43d
ffff9a84`bf4ae380 fffff803`37427b0f     : ffffd607`834c9b20 ffffd607`88b83dc0 00000000`00000000 ffffd607`8acfb200 : nt!ExpInterlockedPopEntrySListFault
ffff9a84`bf4ae390 fffff803`37bb5094     : 00000000`00000000 ffffd607`8b199a40 00000000`766d6777 00000000`00000000 : nt!ExAllocateHeapPool+0x49f
ffff9a84`bf4ae4d0 fffff803`4f80a9bc     : fffff803`4f89fa00 ffffd607`8ee17010 ffffd607`905c7a10 ffffd607`00000000 : nt!ExAllocatePoolWithTag+0x64
ffff9a84`bf4ae520 fffff803`4f80d7b2     : 00000000`00000000 ffff9a84`bf4ae5b8 ffffd607`8ee17010 00000000`0000000a : nwifi!Dot11AllocateRecvPacket+0x90
ffff9a84`bf4ae560 fffff803`4f80e533     : ffffd607`8a000302 ffffd607`00000030 00000000`00000004 00000000`00000000 : nwifi!Pt6RepackRecvNBL+0xa2
ffff9a84`bf4ae600 fffff803`3bc67ef0     : ffffd607`8f2a3c30 fffff803`4f80e3b0 ffffd607`887d5020 00000000`00000001 : nwifi!Pt6Receive+0x183
ffff9a84`bf4ae660 fffff803`3bc9df58     : ffffd607`8acf8700 ffff9a84`bf4ae731 ffffd607`8acf8530 fffff804`ae77ca8b : ndis!ndisCallReceiveHandler+0x60
ffff9a84`bf4ae6b0 fffff803`3bc64a94     : 00000000`00114631 00000000`00000001 ffffd607`839b71a0 00000000`00000001 : ndis!ndisInvokeNextReceiveHandler+0x148
ffff9a84`bf4ae780 fffff804`ae7b1296     : 00000000`00000000 00000000`00000000 ffffd607`8c224d80 00000000`0000000a : ndis!NdisMIndicateReceiveNetBufferLists+0x104
ffff9a84`bf4ae810 fffff804`ae77d325     : ffffd607`8b8b9118 00000000`00000000 ffff9a84`bf4ae901 ffffd607`8b3c8b10 : Netwbw02!doApiIndicateReceiveNbl+0x92
ffff9a84`bf4ae850 fffff804`ae7c8742     : ffffd607`0000000a 00000029`2f6c5767 ffffd607`90eceb30 00000029`2f6c5767 : Netwbw02!prvRxDataHandlePhyHdrFrames+0x715
ffff9a84`bf4ae8b0 fffff804`ae7c0839     : ffffd607`00000000 ffffd607`8b76b8ff 00000000`00000000 fffff803`374125df : Netwbw02!rfdQueueProcessFragments+0x1e2
ffff9a84`bf4ae950 fffff804`ae7b7598     : 00000000`00000000 ffffd607`8b76b8a0 ffffd607`839b71a0 00000000`00000000 : Netwbw02!isrHandlerRoutine+0x221
ffff9a84`bf4ae9b0 fffff804`ae7a9192     : 00000000`00000000 ffffd607`834a8060 00000000`00000000 ffff9a84`bf4aeaa1 : Netwbw02!alonExInterruptHandlerRoutine+0x1c
ffff9a84`bf4ae9e0 fffff803`3bcc6df8     : 00000000`00000000 ffff9a84`00000000 00000000`00000000 ffffd607`834b5180 : Netwbw02!oscHandleInterrupt+0x12
ffff9a84`bf4aea10 fffff803`3bcc72ec     : ffffd607`8b76bb88 00000000`0000000a 00000000`00000001 00000000`00000000 : ndis!ndisMiniportDpc+0xf0
ffff9a84`bf4aeaa0 fffff803`3bcb7dfb     : ffffd607`834a8040 ffffd607`834a8040 ffff9a84`bf4aeba9 fffff803`3bc97100 : ndis!ndisQueuedMiniportDpcWorkItem+0x11c
ffff9a84`bf4aeb40 fffff803`37471d25     : ffffd607`834b5040 ffffd607`834b5040 fffff803`3bc97130 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x20ccb
ffff9a84`bf4aec10 fffff803`37601f08     : fffff803`33f87180 ffffd607`834b5040 fffff803`37471cd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff9a84`bf4aec60 00000000`00000000     : ffff9a84`bf4af000 ffff9a84`bf4a9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nwifi!Dot11AllocateRecvPacket+90

MODULE_NAME: nwifi

IMAGE_NAME:  nwifi.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  90

FAILURE_BUCKET_ID:  0x133_ISR_nwifi!Dot11AllocateRecvPacket

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {10acb27e-cf1f-e7d3-8b3d-9ec902e8eafb}

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

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: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff80337efb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: 5077

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 5084

    Key  : Analysis.IO.Other.Mb
    Value: 14

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 23

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80337efb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffff9a84bf4ae1f0 -- (.trap 0xffff9a84bf4ae1f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000001d20c0002 rbx=0000000000000000 rcx=fffff80337e59740
rdx=fffffffffffffff0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80337602907 rsp=ffff9a84bf4ae380 rbp=ffff9a84bf4ae471
 r8=fffffffffffffff0  r9=0000000000000000 r10=fffff80337e59740
r11=ffff8dffc5000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ExpInterlockedPopEntrySListFault:
fffff803`37602907 498b08          mov     rcx,qword ptr [r8] ds:ffffffff`fffffff0=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT:  
fffff803`3c67ee18 fffff803`3765bf02     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`37efb320 : nt!KeBugCheckEx
fffff803`3c67ee20 fffff803`374d2973     : 00002d47`78984ce4 fffff803`33f87180 00000000`00000000 fffff803`33f87180 : nt!KeAccumulateTicks+0x186d32
fffff803`3c67ee80 fffff803`374d245a     : fffff803`37ef3880 ffff9a84`bf4adf00 fffff803`3ca8d800 00000000`0000a201 : nt!KeClockInterruptNotify+0x453
fffff803`3c67ef30 fffff803`37408a45     : fffff803`37ef3880 fffff803`3c67ef40 00000000`00000010 ffff959c`76c911b0 : nt!HalpTimerClockIpiRoutine+0x1a
fffff803`3c67ef60 fffff803`375fb26a     : ffff9a84`bf4adf00 fffff803`37ef3880 00000000`00000200 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`3c67efb0 fffff803`375fba37     : fffff71b`f5e422c0 fffff803`3752300a ffff9a84`00000000 ffffffff`fffffff0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff9a84`bf4ade80 fffff803`3760d3ad     : 00000000`00000000 ffff9a84`bf4ae270 ffffffff`ffffffd2 fffff803`3743962f : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff9a84`bf4ae010 fffff803`37608ebd     : fffff803`37e59740 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x6d
ffff9a84`bf4ae1f0 fffff803`37602907     : fffff803`37e59740 fffff803`37427b0f ffffd607`834c9b20 ffffd607`88b83dc0 : nt!KiPageFault+0x43d
ffff9a84`bf4ae380 fffff803`37427b0f     : ffffd607`834c9b20 ffffd607`88b83dc0 00000000`00000000 ffffd607`8acfb200 : nt!ExpInterlockedPopEntrySListFault
ffff9a84`bf4ae390 fffff803`37bb5094     : 00000000`00000000 ffffd607`8b199a40 00000000`766d6777 00000000`00000000 : nt!ExAllocateHeapPool+0x49f
ffff9a84`bf4ae4d0 fffff803`4f80a9bc     : fffff803`4f89fa00 ffffd607`8ee17010 ffffd607`905c7a10 ffffd607`00000000 : nt!ExAllocatePoolWithTag+0x64
ffff9a84`bf4ae520 fffff803`4f80d7b2     : 00000000`00000000 ffff9a84`bf4ae5b8 ffffd607`8ee17010 00000000`0000000a : nwifi!Dot11AllocateRecvPacket+0x90
ffff9a84`bf4ae560 fffff803`4f80e533     : ffffd607`8a000302 ffffd607`00000030 00000000`00000004 00000000`00000000 : nwifi!Pt6RepackRecvNBL+0xa2
ffff9a84`bf4ae600 fffff803`3bc67ef0     : ffffd607`8f2a3c30 fffff803`4f80e3b0 ffffd607`887d5020 00000000`00000001 : nwifi!Pt6Receive+0x183
ffff9a84`bf4ae660 fffff803`3bc9df58     : ffffd607`8acf8700 ffff9a84`bf4ae731 ffffd607`8acf8530 fffff804`ae77ca8b : ndis!ndisCallReceiveHandler+0x60
ffff9a84`bf4ae6b0 fffff803`3bc64a94     : 00000000`00114631 00000000`00000001 ffffd607`839b71a0 00000000`00000001 : ndis!ndisInvokeNextReceiveHandler+0x148
ffff9a84`bf4ae780 fffff804`ae7b1296     : 00000000`00000000 00000000`00000000 ffffd607`8c224d80 00000000`0000000a : ndis!NdisMIndicateReceiveNetBufferLists+0x104
ffff9a84`bf4ae810 fffff804`ae77d325     : ffffd607`8b8b9118 00000000`00000000 ffff9a84`bf4ae901 ffffd607`8b3c8b10 : Netwbw02!doApiIndicateReceiveNbl+0x92
ffff9a84`bf4ae850 fffff804`ae7c8742     : ffffd607`0000000a 00000029`2f6c5767 ffffd607`90eceb30 00000029`2f6c5767 : Netwbw02!prvRxDataHandlePhyHdrFrames+0x715
ffff9a84`bf4ae8b0 fffff804`ae7c0839     : ffffd607`00000000 ffffd607`8b76b8ff 00000000`00000000 fffff803`374125df : Netwbw02!rfdQueueProcessFragments+0x1e2
ffff9a84`bf4ae950 fffff804`ae7b7598     : 00000000`00000000 ffffd607`8b76b8a0 ffffd607`839b71a0 00000000`00000000 : Netwbw02!isrHandlerRoutine+0x221
ffff9a84`bf4ae9b0 fffff804`ae7a9192     : 00000000`00000000 ffffd607`834a8060 00000000`00000000 ffff9a84`bf4aeaa1 : Netwbw02!alonExInterruptHandlerRoutine+0x1c
ffff9a84`bf4ae9e0 fffff803`3bcc6df8     : 00000000`00000000 ffff9a84`00000000 00000000`00000000 ffffd607`834b5180 : Netwbw02!oscHandleInterrupt+0x12
ffff9a84`bf4aea10 fffff803`3bcc72ec     : ffffd607`8b76bb88 00000000`0000000a 00000000`00000001 00000000`00000000 : ndis!ndisMiniportDpc+0xf0
ffff9a84`bf4aeaa0 fffff803`3bcb7dfb     : ffffd607`834a8040 ffffd607`834a8040 ffff9a84`bf4aeba9 fffff803`3bc97100 : ndis!ndisQueuedMiniportDpcWorkItem+0x11c
ffff9a84`bf4aeb40 fffff803`37471d25     : ffffd607`834b5040 ffffd607`834b5040 fffff803`3bc97130 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x20ccb
ffff9a84`bf4aec10 fffff803`37601f08     : fffff803`33f87180 ffffd607`834b5040 fffff803`37471cd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff9a84`bf4aec60 00000000`00000000     : ffff9a84`bf4af000 ffff9a84`bf4a9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nwifi!Dot11AllocateRecvPacket+90

MODULE_NAME: nwifi

IMAGE_NAME:  nwifi.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  90

FAILURE_BUCKET_ID:  0x133_ISR_nwifi!Dot11AllocateRecvPacket

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {10acb27e-cf1f-e7d3-8b3d-9ec902e8eafb}

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

接下来是什么？

好吧，这由你来写。我现在靠 Wi-Fi 生存，它不太稳定。我在双启动机器上，注意到我可以在 Ubuntu 中连接到以太网，所以我可能会切换到 Ubuntu。我喜欢它，但有时当我必须在 Ubuntu 中编辑 word 文档时，我会很恼火。

在调试文件中，我注意到提到了 DPC_Watchdog，因此我在网上查找了如何解决这个问题，并找到了一些建议这里，但在尝试完全随机的事情之前，我想听听是否有人有一些好的建议。

答案1

我解决了这个问题……好吧……或多或少。这意味着我能够让 BSOD 消失，但我不知道到底发生了什么。基本上，在我的工作场所，我们可以使用静态 IP（导致我的 PC 出现 BSOD）、DHCP（导致我的 PC 出现 BSOD）和强制门户。我要求 IT 部门为我激活强制门户的套接字……好吧，我现在通过以太网连接了 2 个小时！我对 IT 了解不够，无法理解原因。我猜导致 BSOD 的问题协议在通过强制门户运行时没有使用。我对这个解决方案很满意（暂时）。如果有人想了解发生了什么，我可以进行一些测试：如果我的 IT 人员没有从我的所有以太网套接字停用 DHCP。

答案1

相关内容