描述:联想小新pro13 锐龙版 2020(4800U),在休眠情况下经常无法正常唤醒,表现为出现开机LOGO界面后持续黑屏,最后重启。已关闭快速启动,固态硬盘驱动使用三星官网最新版本,BIOS为最新版本,LENOVO vantage检测无硬件故障和驱动更新。电源设置为睡眠2小时后进入休眠。使用 sfc /scannow 命令扫描显示系统100%完整。检查事件查看器,发现一个错误事件为:Windows 无法从休眠状态恢复,错误状态为 0xC0000001。 Minidmp文件:https://1drv.ms/u/s!AmDvBD5wxidLkPFpr9P7mj0fYLBH8g?e=r07eXr Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. Symbol search path is: srv* Executable search path is:  Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff805`14a00000 PsLoadedModuleList = 0xfffff805`1562a2f0 Debug session time: Thu Sep  3 22:15:55.496 2020 (UTC 8:00) System Uptime: 1 days 0:32:34.282 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........................................... Loading User Symbols PEB is paged out (Peb.Ldr = 000000b7`b2603018).  Type ".hh dbgerr001" for details Loading unloaded module list ................................... KEY_VALUES_STRING: 1     Key  : Analysis.CPU.mSec     Value: 186     Key  : Analysis.DebugAnalysisProvider.CPP     Value: Create: 8007007e on LAPTOP-VL89HN1Q     Key  : Analysis.DebugData     Value: CreateObject     Key  : Analysis.DebugModel     Value: CreateObject     Key  : Analysis.Elapsed.mSec     Value: 17327     Key  : Analysis.Memory.CommitPeak.Mb     Value: 65     Key  : Analysis.System     Value: CreateObject     Key  : WER.OS.Branch     Value: vb_release     Key  : WER.OS.Timestamp     Value: 2019-12-06T14:06:00Z     Key  : WER.OS.Version     Value: 10.0.19041.1 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 ADDITIONAL_DEBUG_TEXT:   You can run '.symfix; .reload' to try to fix the symbol path and load symbols. WRONG_SYMBOLS_TIMESTAMP: 7503e39 WRONG_SYMBOLS_SIZE: 1046000 FAULTING_MODULE: fffff80514a00000 nt BUGCHECK_CODE:  133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff805156fa320 DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 STACK_TEXT:   ffff8000`27c52e18 fffff805`14e595ba     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffff8000`27c52e20 fffff805`14cc98bd     : 00002fa5`7c69d092 00000000`00000000 ffffb506`1643e900 ffff8000`27c00180 : nt!memset 0x6857a ffff8000`27c52e80 fffff805`14cc973a     : ffffcf02`735030e0 ffffb506`1643e9c0 fffff805`00564892 00000000`00000000 : nt!KeClockInterruptNotify 0xbd ffff8000`27c52f30 fffff805`14c08725     : ffffcf02`735030e0 ffff8000`27c52f40 00000000`00000010 ffffdbbb`c71466c8 : nt!KeInsertQueueDpc 0x183a ffff8000`27c52f60 fffff805`14ddf9ea     : ffffb506`1643e9c0 ffffcf02`735030e0 00002f9d`1d1ec880 00000000`00000000 : nt!KeInitializeEnumerationContext 0x4b5 ffff8000`27c52fb0 fffff805`14ddff57     : 00000000`00000000 ffff297b`6cb2e0e1 ffffb506`1643eb80 fffff805`14ddff64 : nt!KeSynchronizeExecution 0x88a ffffb506`1643e940 fffff805`14c333b7     : 00000000`00000010 00000000`00000286 ffffb506`1643eaf8 00000000`00000000 : nt!KeSynchronizeExecution 0xdf7 ffffb506`1643ead0 fffff805`14ca7e8a     : ffffb506`1643ea00 ffff8000`27c03200 ffffb506`1643eb70 00000000`00000002 : nt!RtlVirtualUnwind 0x227 ffffb506`1643eb00 fffff805`14d11700     : 00400a02`1ed27b6a 00002f9d`18c0f012 ffffcf02`739fd8e8 ffffcf02`738de040 : nt!KeAcquireInStackQueuedSpinLock 0xba ffffb506`1643eb30 fffff805`1be13fe7     : ffffcf02`7b27e180 00000000`000008d8 00000000`00000f44 00000000`00400a02 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel 0x60 ffffb506`1643eb60 fffff805`14c3a6be     : ffff8000`27c03240 ffffcf02`736e7000 ffffb506`1643ee70 ffff8000`00000002 : dxgkrnl!DpSynchronizeExecution 0xba7 ffffb506`1643ebb0 fffff805`14c399a4     : ffff8000`27c00180 00000000`00000000 00000000`0000002a 00000000`00296100 : nt!RtlWalkFrameChain 0x2b0e ffffb506`1643ed20 fffff805`14de4f85     : 00000000`00000000 ffff8000`27c00180 ffff8000`28b6d3c0 00000000`00000063 : nt!RtlWalkFrameChain 0x1df4 ffffb506`1643efb0 fffff805`14de4d70     : 00000000`00000074 fffff805`14de4611 00000000`01000010 00000000`00000286 : nt!KeSynchronizeExecution 0x5e25 ffffb506`1a422ac0 fffff805`14de4625     : 00000000`00000063 fffff805`14ddfab1 00000000`00000070 00000000`00000001 : nt!KeSynchronizeExecution 0x5c10 ffffb506`1a422af0 fffff805`14ddfab1     : 00000000`00000070 00000000`00000001 ffffb506`1a422b80 ffffb506`1a422b80 : nt!KeSynchronizeExecution 0x54c5 ffffb506`1a422b00 00007fff`0ae0f364     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution 0x951 000000b7`b377e868 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`0ae0f364 SYMBOL_NAME:  nt_wrong_symbols!07503E391046000 STACK_COMMAND:  .thread ; .cxr ; kb EXCEPTION_CODE_STR:  07503E39 EXCEPTION_STR:  WRONG_SYMBOLS PROCESS_NAME:  ntoskrnl.wrong.symbols.exe IMAGE_NAME:  ntoskrnl.wrong.symbols.exe MODULE_NAME: nt_wrong_symbols FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X64_19041.1.amd64fre.vb_release.191206-1406_TIMESTAMP_07503E39_nt_wrong_symbols!07503E391046000 OS_VERSION:  10.0.19041.1 BUILDLAB_STR:  vb_release OSPLATFORM_TYPE:  x64 OSNAME:  Windows 10 FAILURE_ID_HASH:  {bebaccfa-228b-3e33-c888-5872b3587dbe} Followup:     MachineOwner ---------

您好,了解到您的问题


点赞(26) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部