netrtp.sys 导致的电脑蓝屏 ---求助
************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : false AllowNugetExeUpdate : false AllowNugetMSCredentialProviderInstall : false AllowParallelInitializationOfLocalRepositories : true -- 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: 36Microsoft (R) Windows Debugger Version 10.0.25877.1004 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 SingleUserTSEdition build lab: 22621.1.amd64fre.ni_release.220506-1250Kernel base = 0xfffff800`29200000 PsLoadedModuleList = 0xfffff800`29e134b0Debug session time: Tue Jun 27 14:53:56.526 2023 (UTC + 8:00)System Uptime: 0 days 5:57:35.297Loading Kernel Symbols.................................................................................................................................................................................................................................................Loading User SymbolsPEB is paged out (Peb.Ldr = 000000e1`2e74b018).Type ".hh dbgerr001" for detailsLoading unloaded module list...................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`2962c280 48894c2408 mov qword ptr ,rcx ss:0018:fffff800`2524dcd0=00000000000001330: 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: fffff80029f1c340, 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: 2030 Key: Analysis.Elapsed.mSec Value: 14669 Key: Analysis.IO.Other.Mb Value: 10 Key: Analysis.IO.Read.Mb Value: 0 Key: Analysis.IO.Write.Mb Value: 31 Key: Analysis.Init.CPU.mSec Value: 499 Key: Analysis.Init.Elapsed.mSec Value: 236464 Key: Analysis.Memory.CommitPeak.Mb Value: 101 Key: Bugcheck.Code.LegacyAPI Value: 0x133 Key: Failure.Bucket Value: 0x133_ISR_netrtp!unknown_function Key: Failure.Hash Value: {d1a52398-623d-e4a5-5951-02cd99e33301} Key: Hypervisor.Enlightenments.ValueHex Value: 1417df84 Key: Hypervisor.Flags.AnyHypervisorPresent Value: 1 Key: Hypervisor.Flags.ApicEnlightened Value: 0 Key: Hypervisor.Flags.ApicVirtualizationAvailable Value: 1 Key: Hypervisor.Flags.AsyncMemoryHint Value: 0 Key: Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key: Hypervisor.Flags.CpuManager Value: 1 Key: Hypervisor.Flags.DeprecateAutoEoi Value: 1 Key: Hypervisor.Flags.DynamicCpuDisabled Value: 1 Key: Hypervisor.Flags.Epf Value: 0 Key: Hypervisor.Flags.ExtendedProcessorMasks Value: 1 Key: Hypervisor.Flags.HardwareMbecAvailable Value: 1 Key: Hypervisor.Flags.MaxBankNumber Value: 0 Key: Hypervisor.Flags.MemoryZeroingControl Value: 0 Key: Hypervisor.Flags.NoExtendedRangeFlush Value: 0 Key: Hypervisor.Flags.NoNonArchCoreSharing Value: 1 Key: Hypervisor.Flags.Phase0InitDone Value: 1 Key: Hypervisor.Flags.PowerSchedulerQos Value: 0 Key: Hypervisor.Flags.RootScheduler Value: 0 Key: Hypervisor.Flags.SynicAvailable Value: 1 Key: Hypervisor.Flags.UseQpcBias Value: 0 Key: Hypervisor.Flags.Value Value: 21631230 Key: Hypervisor.Flags.ValueHex Value: 14a10fe Key: Hypervisor.Flags.VpAssistPage Value: 1 Key: Hypervisor.Flags.VsmAvailable Value: 1 Key: Hypervisor.RootFlags.AccessStats Value: 1 Key: Hypervisor.RootFlags.CrashdumpEnlightened Value: 1 Key: Hypervisor.RootFlags.CreateVirtualProcessor Value: 1 Key: Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key: Hypervisor.RootFlags.HostTimelineSync Value: 1 Key: Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key: Hypervisor.RootFlags.IsHyperV Value: 1 Key: Hypervisor.RootFlags.LivedumpEnlightened Value: 1 Key: Hypervisor.RootFlags.MapDeviceInterrupt Value: 1 Key: Hypervisor.RootFlags.MceEnlightened Value: 1 Key: Hypervisor.RootFlags.Nested Value: 0 Key: Hypervisor.RootFlags.StartLogicalProcessor Value: 1 Key: Hypervisor.RootFlags.Value Value: 1015 Key: Hypervisor.RootFlags.ValueHex Value: 3f7 Key: WER.OS.Branch Value: ni_release Key: WER.OS.Version Value: 10.0.22621.1BUGCHECK_CODE:133BUGCHECK_P1: 1BUGCHECK_P2: 1e00BUGCHECK_P3: fffff80029f1c340BUGCHECK_P4: 0FILE_IN_CAB:062723-10265-01.dmpDPC_TIMEOUT_TYPE:DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDEDTRAP_FRAME:fffffb8af01dda60 -- (.trap 0xfffffb8af01dda60)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000001rdx=fffffb8af01de0c4 rsi=0000000000000000 rdi=0000000000000000rip=fffff8005edb6b3a rsp=fffffb8af01ddbf8 rbp=fffff8005edb5938 r8=0000000000000067r9=ffffea82142f8c4c r10=0000000000000043r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz ac pe cynetrtp+0x6b3a:fffff800`5edb6b3a 664183c220 add r10w,20hResetting default scopeBLACKBOXBSD: 1 (!blackboxbsd)BLACKBOXNTFS: 1 (!blackboxntfs)BLACKBOXPNP: 1 (!blackboxpnp)BLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT:1PROCESS_NAME:runnerw.exeSTACK_TEXT:fffff800`2524dcc8 fffff800`294deed1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`29f1c340 : nt!KeBugCheckExfffff800`2524dcd0 fffff800`294de74c : 000038f6`4e069663 fffff800`24e73180 00000000`0014f3d2 00000000`00000202 : nt!KeAccumulateTicks+0x231fffff800`2524dd30 fffff800`294dc801 : 00000000`00000000 00000000`00000000 fffff800`24e73180 00000000`00000000 : nt!KiUpdateRunTime+0xccfffff800`2524dea0 fffff800`294dc219 : fffff800`29e5fe78 00000000`00000001 00000000`00000001 00000000`00000002 : nt!KeClockInterruptNotify+0xc1fffff800`2524df40 fffff800`2951757c : 00000031`f45d95cb fffff800`29f0d0f0 fffff800`29f0d1a0 00000000`00000000 : nt!HalpTimerClockInterrupt+0x109fffff800`2524df70 fffff800`2962e3da : fffffb8a`f01ddae0 fffff800`29f0d0f0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9cfffff800`2524dfb0 fffff800`2962ec47 : 00000000`00000000 fffff800`29f0d0f0 00000000`00000000 fffff800`29f0d0f0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfafffffb8a`f01dda60 fffff800`5edb6b3a : fffff800`5edb5953 00000000`00000000 fffff800`5edb585c 00000000`00000010 : nt!KiInterruptDispatchNoLockNoEtw+0x37fffffb8a`f01ddbf8 fffff800`5edb5953 : 00000000`00000000 fffff800`5edb585c 00000000`00000010 00000000`00040246 : netrtp+0x6b3afffffb8a`f01ddc00 00000000`00000000 : fffff800`5edb585c 00000000`00000010 00000000`00040246 ffffe60d`044d6cf0 : netrtp+0x5953SYMBOL_NAME:netrtp+6b3aMODULE_NAME: netrtpIMAGE_NAME:netrtp.sysSTACK_COMMAND:.cxr; .ecxr ; kbBUCKET_ID_FUNC_OFFSET:6b3aFAILURE_BUCKET_ID:0x133_ISR_netrtp!unknown_functionOS_VERSION:10.0.22621.1BUILDLAB_STR:ni_releaseOSPLATFORM_TYPE:x64OSNAME:Windows 10FAILURE_ID_HASH:{d1a52398-623d-e4a5-5951-02cd99e33301}Followup: MachineOwner---------您好，该问题管家已经在5.0.100.5232版本解决，建议您升级管家版本到5.0.100.5232，然后在观察一段时间看netrtp.sys 导致的电脑蓝屏问题是否还会出现。
页:
[1]