netrtp.sys导致电脑频繁蓝屏
2023款拯救者Y7000P win11windbg蓝屏分析日志如下：
************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds************* Waiting for Debugger Extensions Gallery to Initialize **************>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 43Microsoft (R) Windows Debugger Version 10.0.27793.1000 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 22621 MP (20 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalKernel base = 0xfffff800`5ee00000 PsLoadedModuleList = 0xfffff800`5fa134f0Debug session time: Sun Apr 20 14:25:15.136 2025 (UTC + 8:00)System Uptime: 0 days 23:37:27.812Loading Kernel Symbols.......................................................................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list....................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`5f2148b0 48894c2408 mov qword ptr ,rcx ss:0018:ffffba80`2e3abc90=000000000000013310: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION (133)The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor 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: fffff8005fb1c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeoutArg4: 0000000000000000Debugging 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: 359 Key: Analysis.Elapsed.mSec Value: 6823 Key: Analysis.IO.Other.Mb Value: 15 Key: Analysis.IO.Read.Mb Value: 1 Key: Analysis.IO.Write.Mb Value: 25 Key: Analysis.Init.CPU.mSec Value: 171 Key: Analysis.Init.Elapsed.mSec Value: 83683 Key: Analysis.Memory.CommitPeak.Mb Value: 93 Key: Analysis.Version.DbgEng Value: 10.0.27793.1000 Key: Analysis.Version.Description Value: 10.2410.02.02 amd64fre Key: Analysis.Version.Ext Value: 1.2410.2.2 Key: Bugcheck.Code.LegacyAPI Value: 0x133 Key: Bugcheck.Code.TargetModel Value: 0x133 Key: Dump.Attributes.AsUlong Value: 0x1008 Key: Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key: Dump.Attributes.ErrorCode Value: 0x0 Key: Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key: Dump.Attributes.LastLine Value: Dump completed successfully. Key: Dump.Attributes.ProgressPercentage Value: 0 Key: Failure.Bucket Value: 0x133_ISR_netrtp!unknown_function Key: Failure.Hash Value: {d1a52398-623d-e4a5-5951-02cd99e33301} Key: Stack.Pointer Value: ISRBUGCHECK_CODE:133BUGCHECK_P1: 1BUGCHECK_P2: 1e00BUGCHECK_P3: fffff8005fb1c340BUGCHECK_P4: 0FILE_IN_CAB:042025-10421-01.dmpDUMP_FILE_ATTRIBUTES: 0x1008Kernel Generated Triage DumpFAULTING_THREAD:ffffd183ef655080DPC_TIMEOUT_TYPE:DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDEDBLACKBOXBSD: 1 (!blackboxbsd)BLACKBOXNTFS: 1 (!blackboxntfs)BLACKBOXPNP: 1 (!blackboxpnp)BLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT:1PROCESS_NAME:SystemSTACK_TEXT:ffffba80`2e3abc88 fffff800`5f086129 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`5fb1c340 : nt!KeBugCheckExffffba80`2e3abc90 fffff800`5f085991 : 0000844e`a244ad84 ffffba80`2e3abd58 00000000`00530df3 00000000`00000000 : nt!KeAccumulateTicks+0x239ffffba80`2e3abcf0 fffff800`5f083a21 : 00000000`00000000 00000000`00000000 ffffba80`2e391180 00000000`00000000 : nt!KiUpdateRunTime+0xd1ffffba80`2e3abea0 fffff800`5f08344a : fffff800`5fa5ff88 00000000`00000001 00000000`00000001 00000000`00000002 : nt!KeClockInterruptNotify+0xc1ffffba80`2e3abf40 fffff800`5f11d64c : 000000c6`048c8596 ffffd183`d015b500 ffffd183`d015b5b0 00000000`00000000 : nt!HalpTimerClockInterrupt+0x10affffba80`2e3abf70 fffff800`5f216aba : ffffcd8b`3633f9d0 ffffd183`d015b500 00000000`00000000 00000000`00000004 : nt!KiCallInterruptServiceRoutine+0x9cffffba80`2e3abfb0 fffff800`5f217387 : ffffd183`ef655080 00000000`00000002 ffffba80`2e391180 ffffd183`ef655080 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfaffffcd8b`3633f950 fffff800`adfe67fc : fffff800`adfe91e8 00000000`00000000 00000000`00000004 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37ffffcd8b`3633fae0 fffff800`adfe91e8 : 00000000`00000000 00000000`00000004 00000000`00000000 ffffcd8b`40ede490 : netrtp+0x67fcffffcd8b`3633fae8 00000000`00000000 : 00000000`00000004 00000000`00000000 ffffcd8b`40ede490 fffff800`adfe9240 : netrtp+0x91e8SYMBOL_NAME:netrtp+67fcMODULE_NAME: netrtpIMAGE_NAME:netrtp.sysSTACK_COMMAND:.process /r /p 0xffffd183d0153040; .thread 0xffffd183ef655080 ; kbBUCKET_ID_FUNC_OFFSET:67fcFAILURE_BUCKET_ID:0x133_ISR_netrtp!unknown_functionOSPLATFORM_TYPE:x64OSNAME:Windows 10FAILURE_ID_HASH:{d1a52398-623d-e4a5-5951-02cd99e33301}Followup: MachineOwner---------
您好，netrtp.sys 蓝屏通常与网络驱动或硬件相关，卸载当前驱动： 右键点击 开始菜单 → 选择 设备管理器。 展开 网络适配器，找到你的网卡（如 Realtek、Intel 等）。 右键点击网卡 → 选择 卸载设备，勾选 删除驱动程序软件 → 确认。 重启电脑，Windows 会自动安装默认驱动。 联想电脑管家-运营 发表于 2025-4-21 11:27
您好，netrtp.sys 蓝屏通常与网络驱动或硬件相关，卸载当前驱动： 右键点击 开始菜单 → 选择 设备管理器。 ...
你好，我在联想电脑管家里查看了我的网卡驱动，显示与原厂驱动一致，好像并非是网卡的问题导致的
页:
[1]