uu加速器加速后电脑会蓝屏蓝屏显示NDIS.sys,一下是使用windbg分析dump文件的结果Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Mr\Desktop\111122-12468-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22000 MP (20 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff801`4d000000 PsLoadedModuleList = 0xfffff801`4dc29a40 Debug session time: Fri Nov 11 09:02:57.687 2022 (UTC 8:00) System Uptime: 1 days 17:32:33.428 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 .............................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff801`4d41af80 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:fffff68e`40a05ae0=000000000000003b 10: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the BugCheck Arg2: fffff80150343989, Address of the instruction which caused the BugCheck Arg3: fffff68e40a06420, Address of the context record for the exception that caused the BugCheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1342 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 14385 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 328 Key : Analysis.Init.Elapsed.mSec Value: 144471 Key : Analysis.Memory.CommitPeak.Mb Value: 97 Key : Bugcheck.Code.DumpHeader Value: 0x3b Key : Bugcheck.Code.Register Value: 0x3b Key : Dump.Attributes.AsUlong Value: 1808 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 FILE_IN_CAB: 111122-12468-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump BUGCHECK_CODE: 3b BUGCHECK_P1: c0000005 BUGCHECK_P2: fffff80150343989 BUGCHECK_P3: fffff68e40a06420 BUGCHECK_P4: 0 CONTEXT: fffff68e40a06420 -- (.cxr 0xfffff68e40a06420) rax=0000000000000000 rbx=0000000000000020 rcx=00450008c7e4f7f3 rdx=ffffe6851564fca1 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80150343989 rsp=fffff68e40a06e40 rbp=fffff68e40a06f00 r8=0000000000000020 r9=fffff8015042b050 r10=0000000000000088 r11=ff00c7e4f7f2ff45 r12=00000000ffffff00 r13=0000000000000000 r14=00450008c7e4f7f3 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206 ndis!ndisNblTrackerTransferOwnershipInternal 0x99: fffff801`50343989 498bbe68010000 mov rdi,qword ptr [r14 168h] ds:002b:00450008`c7e4f95b=???????????????? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: uu.exe STACK_TEXT: fffff68e`40a06e40 fffff801`5037b963 : 00000000`00000000 ffffe685`1564fca1 00000000`00000020 00000000`00000000 : ndis!ndisNblTrackerTransferOwnershipInternal 0x99 fffff68e`40a06ec0 fffff801`50342779 : ffffe685`15791ba0 00000000`00000000 00000000`00000000 00000000`00000001 : ndis!ndisMIndicateNetBufferListsToOpen 0x38d53 fffff68e`40a06fa0 fffff801`503748dc : ffffe685`002e41a0 00000000`00000000 ffffe685`002e41a0 fffff801`4d2a4001 : ndis!ndisMTopReceiveNetBufferLists 0x1c9 fffff68e`40a07080 fffff801`50376da9 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff801`5034648b : ndis!ndisInvokeNextReceiveHandler 0x54 fffff68e`40a070e0 fffff801`65db5b78 : 00000000`00000000 ffffe685`186bb0b0 00000000`00000000 00000000`00000001 : ndis!NdisFIndicateReceiveNetBufferLists 0x305b9 fffff68e`40a07190 00000000`00000000 : ffffe685`186bb0b0 00000000`00000000 00000000`00000001 ffffe685`00000000 : npcap 0x5b78 SYMBOL_NAME: npcap 5b78 MODULE_NAME: npcap IMAGE_NAME: npcap.sys STACK_COMMAND: .cxr 0xfffff68e40a06420 ; kb BUCKET_ID_FUNC_OFFSET: 5b78 FAILURE_BUCKET_ID: AV_npcap!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {75627e3d-b2d1-3073-f887-d35f6796fe71} Followup: MachineOwner --------- 好像是npcap.sys出了问题,但我不知道该怎么办

欢迎访问本站!。显示网络相关的异常。可能是Npcap导致UU加速器出现异常。建议卸载UU加速器,或卸载Npcap(可以鼠标右击开始菜单


点赞(19) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部