我的笔记本电脑是联想拯救者y9000p 2022版，显卡是3070，前段时间到现在玩游戏apex经常玩着玩着突然画面卡死，然后蓝屏重启，有时候不会蓝屏，而是卡死直接重启，蓝屏代码是 clock wat

link管理
链接快照平台
输入网页链接，自动生成快照
标签化管理网页链接
相关文章推荐
腼腆的警车 · 如何通过消费组消费数据_日志服务(SLS)- ...· 8 月前 ·
含蓄的大象 · 【Python】获取文件的创建时间，修改时间 ...· 2 年前 ·
痴情的板凳 · python yaml - 知乎· 2 年前 ·
逆袭的汉堡包 · 用户对问题“GraphQLSchema指定的 ...· 2 年前 ·
想发财的炒粉 · Log4JConverter在日志中插入自定 ...· 2 年前 ·
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Loading Dump File [C:\Windows\Minidump\053023-11718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff807`29000000 PsLoadedModuleList = 0xfffff807`29c134d0
Debug session time: Tue May 30 18:21:43.814 2023 (UTC + 8:00)
System Uptime: 0 days 9:15:54.485
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:
fffff807`2942c0f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8001`b47daa30=0000000000000101
10: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 000000000000000a, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff8001b4931180, The PRCB address of the hung processor.
Arg4: 000000000000000c, The index of the hung processor.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
    Key  : Analysis.CPU.mSec
    Value: 827
    Key  : Analysis.DebugAnalysisManager
    Value: Create
    Key  : Analysis.Elapsed.mSec
    Value: 29111
    Key  : Analysis.IO.Other.Mb
    Value: 10
    Key  : Analysis.IO.Read.Mb
    Value: 0
    Key  : Analysis.IO.Write.Mb
    Value: 32
    Key  : Analysis.Init.CPU.mSec
    Value: 1015
    Key  : Analysis.Init.Elapsed.mSec
    Value: 776988
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 101
    Key  : Bugcheck.Code.DumpHeader
    Value: 0x101
    Key  : Bugcheck.Code.Register
    Value: 0x101
    Key  : Dump.Attributes.AsUlong
    Value: 1008
    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:  053023-11718-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump
BUGCHECK_CODE:  101
BUGCHECK_P1: a
BUGCHECK_P2: 0
BUGCHECK_P3: ffff8001b4931180
BUGCHECK_P4: c
FAULTING_PROCESSOR: c
FAULTING_THREAD:  ffffce8a499a4080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  System
STACK_TEXT:  
ffffa780`d29a71e0 ffffce8a`45c49998     : 00000000`00040246 fffff807`2923d86b 00000000`00000000 ffffce8a`45c49998 : nt!KiSwapContext+0x76
ffffa780`d29a7320 00000000`00040246     : fffff807`2923d86b 00000000`00000000 ffffce8a`45c49998 00000000`00000000 : 0xffffce8a`45c49998
ffffa780`d29a7328 fffff807`2923d86b     : 00000000`00000000 ffffce8a`45c49998 00000000`00000000 fffff807`292e7410 : 0x40246
ffffa780`d29a7330 fffff807`292e94a3     : ffffce8a`00000001 ffffa780`d29a7509 ffffce8a`407ea701 ffffce8a`3d3020c0 : nt!KeSetEvent+0xeb
ffffa780`d29a73c0 ffffa780`d29a75c0     : 00000000`00000001 00000000`0020f300 00000000`00000000 00000000`00000000 : nt!IopCompleteRequest+0x423
ffffa780`d29a7490 00000000`00000001     : 00000000`0020f300 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffa780`d29a75c0
ffffa780`d29a7498 00000000`0020f300     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
ffffa780`d29a74a0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8001`b65d7000 : 0x20f300
SYMBOL_NAME:  nt!KiSwapContext+76
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
IMAGE_VERSION:  10.0.22621.1778
STACK_COMMAND:  .process /r /p 0xffffce8a3d3020c0; .thread 0xffffce8a499a4080 ; kb
BUCKET_ID_FUNC_OFFSET:  76
FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_nt!KiSwapContext
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {65022177-f8d7-d86e-687a-3d30c86c71d3}
Followup:     MachineOwner
---------
10: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 000000000000000a, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff8001b4931180, The PRCB address of the hung processor.
Arg4: 000000000000000c, The index of the hung processor.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
    Key  : Analysis.CPU.mSec
    Value: 703
    Key  : Analysis.DebugAnalysisManager
    Value: Create
    Key  : Analysis.Elapsed.mSec
    Value: 1376
    Key  : Analysis.IO.Other.Mb
    Value: 10
    Key  : Analysis.IO.Read.Mb
    Value: 0
    Key  : Analysis.IO.Write.Mb
    Value: 32
    Key  : Analysis.Init.CPU.mSec
    Value: 1843
    Key  : Analysis.Init.Elapsed.mSec
    Value: 806100
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 101
    Key  : Bugcheck.Code.DumpHeader
    Value: 0x101
    Key  : Bugcheck.Code.Register
    Value: 0x101
    Key  : Dump.Attributes.AsUlong
    Value: 1008
    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:  053023-11718-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump
BUGCHECK_CODE:  101
BUGCHECK_P1: a
BUGCHECK_P2: 0
BUGCHECK_P3: ffff8001b4931180
BUGCHECK_P4: c
FAULTING_PROCESSOR: c
FAULTING_THREAD:  ffffce8a499a4080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  System
STACK_TEXT:  
ffffa780`d29a71e0 ffffce8a`45c49998     : 00000000`00040246 fffff807`2923d86b 00000000`00000000 ffffce8a`45c49998 : nt!KiSwapContext+0x76
ffffa780`d29a7320 00000000`00040246     : fffff807`2923d86b 00000000`00000000 ffffce8a`45c49998 00000000`00000000 : 0xffffce8a`45c49998
ffffa780`d29a7328 fffff807`2923d86b     : 00000000`00000000 ffffce8a`45c49998 00000000`00000000 fffff807`292e7410 : 0x40246
ffffa780`d29a7330 fffff807`292e94a3     : ffffce8a`00000001 ffffa780`d29a7509 ffffce8a`407ea701 ffffce8a`3d3020c0 : nt!KeSetEvent+0xeb
ffffa780`d29a73c0 ffffa780`d29a75c0     : 00000000`00000001 00000000`0020f300 00000000`00000000 00000000`00000000 : nt!IopCompleteRequest+0x423
ffffa780`d29a7490 00000000`00000001     : 00000000`0020f300 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffa780`d29a75c0
ffffa780`d29a7498 00000000`0020f300     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
ffffa780`d29a74a0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8001`b65d7000 : 0x20f300
SYMBOL_NAME:  nt!KiSwapContext+76
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
IMAGE_VERSION:  10.0.22621.1778
STACK_COMMAND:  .process /r /p 0xffffce8a3d3020c0; .thread 0xffffce8a499a4080 ; kb
BUCKET_ID_FUNC_OFFSET:  76
FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_nt!KiSwapContext
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {65022177-f8d7-d86e-687a-3d30c86c71d3}
Followup:     MachineOwner
---------
10: kd> lmvm nt
Browse full module list
start             end                 module name
fffff807`29000000 fffff807`2a048000   nt         (pdb symbols)          C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\DB9E9EC849EB856A93EB8F4736A05ABD1\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: C:\ProgramData\Dbg\sym\ntkrnlmp.exe\44265B0B1048000\ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Browse all global symbols  functions  data
    Image was built with /Brepro flag.
    Timestamp:        44265B0B (This is a reproducible build file hash, not a timestamp)
    CheckSum:         00B99BC8
    ImageSize:        01048000
    File version:     10.0.22621.1778
    Product version:  10.0.22621.1778
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntkrnlmp.exe
        OriginalFilename: ntkrnlmp.exe
        ProductVersion:   10.0.22621.1778
        FileVersion:      10.0.22621.1778 (WinBuild.160101.0800)
        FileDescription:  NT Kernel & System
			 llllyyyy 您好 
我是 Dave, 我会帮助你解决这个问题。
请检查您的 PC 是否正在生成任何小型转储文件，我将检查这些文件以查看它们是否提供了对系统崩溃潜在原因的任何见解。
请注意，我无法从 百度网盘（Baidu CloudDrive 下载，请使用不同的云服务进行上传。
打开 Windows 文件资源管理器。
导航到 C:\Windows\Minidump
将任何小型转储文件复制到您的桌面上，然后将它们压缩。
将 zip 文件上传到云端（OneDrive、DropBox 等），然后选择共享这些文件并获取共享链接。
然后在此处将链接发布到 zip 文件，以便我们为您查找。