尝试过很多次更新，均以绿屏DPC_WATCHDOG_VIOLATION结束，一直被困在了Build22494这次尝试用SetupDiag抓取了一些日志（见附件：Logs.zip）使用WinDbg分析 "C:\$WINDOWS.~BT\Sources\Rollback\setupmem.dmp" 得到了以下内容Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\jiera\AppData\Local\Temp\BNZ.61fbb660140bd6\setupmem.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 22543 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22543.1000.amd64fre.rs_prerelease.220122-2315 Machine Name: Kernel base = 0xfffff806`06600000 PsLoadedModuleList = 0xfffff806`0723e230 Debug session time: Thu Feb 3 18:34:21.185 2022 (UTC 8:00) System Uptime: 0 days 0:02:05.278 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Loading unloaded module list ...... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff806`06a2db00 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:fffff806`0b46ac10=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. The offending component can usually be identified with a stack trace. Arg2: 0000000000001e00, The watchdog period. Arg3: fffff8060731c338, 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: 4265 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 4315 Key : Analysis.Init.CPU.mSec Value: 452 Key : Analysis.Init.Elapsed.mSec Value: 17138 Key : Analysis.Memory.CommitPeak.Mb Value: 77 Key : WER.OS.Branch Value: rs_prerelease Key : WER.OS.Timestamp Value: 2022-01-22T23:15:00Z Key : WER.OS.Version Value: 10.0.22543.1000 FILE_IN_CAB: setupmem.dmp BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff8060731c338 BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: fffff8060b463640 -- (.trap 0xfffff8060b463640) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000120003 rbx=0000000000000000 rcx=ffffe680063e8800 rdx=ffffe680063e5800 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80606a361fa rsp=fffff8060b4637d0 rbp=ffffe680063e9700 r8=ffffe680063e5800 r9=ffffe9800000dc90 r10=ffffe9800000b800 r11=ffffe680063e8800 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!ExpInterlockedPushEntrySList 0x2a: fffff806`06a361fa 75e8 jne nt!ExpInterlockedPushEntrySList 0x14 (fffff806`06a361e4) [br=0] Resetting default scope BLACKBOXNTFS: 1 (!blackboxntfs) PROCESS_NAME: System STACK_TEXT: fffff806`0b46ac08 fffff806`06845bcc : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`0731c338 : nt!KeBugCheckEx fffff806`0b46ac10 fffff806`06843f06 : 0000003d`98be276c 00000000`00000176 fffff806`0217c180 00000000`00000000 : nt!KeAccumulateTicks 0x22c fffff806`0b46ac80 fffff806`0682d19b : ffffb080`3b202000 fffff806`0720b7d0 fffff7e5`0001cd00 00000000`00000008 : nt!KiUpdateRunTime 0x66 fffff806`0b46ace0 fffff806`06843cb5 : fffff806`07240728 00000000`00000000 fffff806`0217c180 00000000`00000000 : nt!KiUpdateTime 0x60b fffff806`0b46aea0 fffff806`0682ab7a : fffff806`0725f7a8 fffff806`073095b0 fffff806`073095b0 00000000`00000002 : nt!KeClockInterruptNotify 0x235 fffff806`0b46af40 fffff806`06912c7b : 00000000`4aaef7ec fffff806`07309500 00000000`00000001 fffff806`06a2f4cb : nt!HalpTimerClockInterrupt 0x10a fffff806`0b46af70 fffff806`06a2f72a : fffff806`0b4636c0 fffff806`07309500 00000000`00000192 ffffe980`0000dc90 : nt!KiCallInterruptServiceRoutine 0x18b fffff806`0b46afb0 fffff806`06a2fcf7 : 00000000`00000000 fffff806`06a2ef34 00000000`000ccccd ffffd409`3fc02840 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa fffff806`0b463640 fffff806`06a361fa : 00000000`00000000 fffff806`068abffd 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw 0x37 fffff806`0b4637d0 fffff806`068abffd : 00000000`00000000 00000000`00000000 ffffe680`063e9700 00000000`00000001 : nt!ExpInterlockedPushEntrySList 0x2a fffff806`0b4637e0 fffff806`068eaab0 : 00000000`00214d80 fffff806`069b6296 00000000`00000000 00000000`00000080 : nt!MiInsertPageInFreeOrZeroedList 0xc0d fffff806`0b463930 fffff806`069b62a9 : ffffe680`063e8818 ffffe680`063e9700 00000000`000001d0 00000000`000000a0 : nt!MiReturnFreeZeroPage 0xa0 fffff806`0b463960 fffff806`069b570f : fffff806`0726a440 ffffe980`00000000 ffffd409`00000010 fffff806`00000000 : nt!MiDemoteSlabEntry 0x25d fffff806`0b4639f0 fffff806`06947615 : fffff806`0731fa00 00000038`0bb9f9f4 ffffd409`405fce38 ffffd409`406a88c0 : nt!MiDemoteSlabEntriesDpc 0x14f fffff806`0b463a90 fffff806`069b080e : 00000000`00000008 00000000`00000000 00000008`80000001 00000000`00000001 : nt!KiInitiateGenericCallDpc 0x89 fffff806`0b463ae0 fffff806`0686a118 : 00000000`00000001 fffff806`0b463e10 00000000`00000000 fffff806`00000002 : nt!KiGenericCallDpcInitiatorDpc 0x2e fffff806`0b463b10 fffff806`068691bf : 00000000`00000022 fffff806`0217c180 00000000`00000026 fffff806`0217c180 : nt!KiExecuteAllDpcs 0x408 fffff806`0b463d10 fffff806`06a35765 : 00000000`00000000 fffff806`0217c180 00000000`00000000 ffffd409`402b2040 : nt!KiRetireDpcList 0x1af fffff806`0b463fb0 fffff806`06a3570f : ffffe48d`2fa74619 fffff806`0686baf8 00000000`00000000 00000000`00000000 : nt!KxSwapStacksAndRetireDpcList 0x5 ffffe48d`2fa74590 fffff806`0686baf8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPlatformSwapStacksAndCallReturn ffffe48d`2fa745a0 fffff806`06a34e24 : fffff806`0217c180 00000000`00000000 00000000`00040202 fffff806`0687382d : nt!KiDispatchInterrupt 0x98 ffffe48d`2fa74680 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt 0x344 SYMBOL_NAME: nt!KeAccumulateTicks 22c MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22543.1000 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 22c FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks OS_VERSION: 10.0.22543.1000 BUILDLAB_STR: rs_prerelease OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06} Followup: MachineOwner ---------以下为尝试过无用的方法：更新显卡驱动到最新可选版降级显卡驱动到最新稳定版sfc /scannow 那一套附件：Logs.zip
您好，A&K，前来提供帮助。您的dump文件显示了系统内核的问题，由驱动程序导致，但dump文件没有记录具体的驱动程序名称。建议先尝试卸载所有主要设备驱动程序（GPU、芯片组等），然后前往设备制造商官网下载最新版本并重新安装。由于您的问题有关Windows预览版，不在本本站支持范围内，可能无法为您提供专业的支持，如想得到进一步的支持，请前往Windows预览体验板块：https://answers.microsoft.com/insider/forum进行提问以获得专业支持。
