小新pro13锐龙版休眠唤醒有概率死机重启

发表于 2021-6-3 15:42   |   来自Microsoft Edge浏览器 [复制链接]   
581 4  

品牌 小新
机型版本 小新Pro 13 2020锐龙版
ROM版本 操作系统版本
模块/分类 系统>死机
复现概率
问题描述 进入休眠模式后 (Hibernate, S4模式) 再唤醒,Windows 启动圈转完后会出现较长时间黑屏,并有概率在一段时间内死机重启。在事件管理器中可看到 BugCheck,MEMORY.DUMP 文件网盘链接见补充说明。 复现环境:系统版本 Windows 10 build 19043.1023,系统开启内 Windows Subsystem Linux 和 Virtual Machine Platform 功能(即虚拟化平台相关功能),驱动和BIOS均为官网最新版本。
复现步骤 本帖最后由 jimmy19990 于 2021-6-3 15:50 编辑

0. 驱动和BIOS更新为官网最新版本;
1. 在控制面板电源管理设置中开启显示休眠按钮,并通过开始菜单进入休眠模式;
2. 待机器休眠后按下开关键从休眠中唤醒;
3. 观察到 Windows 启动转圈完毕后进入较长时间黑屏,并有一定概率自动重启重新开始转圈;
4. 自动重启能够正常进入操作系统,在事件管理器中能看到 BugCheck 记录。
补充说明 MEMORY.DMP 网盘链接: https://pan.baidu.com/s/1G9ghisWTU0QHmLsYYqrSrA 提取码: pqfd 下面附上 Windbg analyze 输出: 1: 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: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace. Arg2: 0000000000000501, The DPC time count (in ticks). Arg3: 0000000000000500, The DPC time allotment (in ticks). Arg4: fffff80351cfb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding this single DPC timeout 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: 4280 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 4446 Key : Analysis.Init.CPU.mSec Value: 624 Key : Analysis.Init.Elapsed.mSec Value: 3559 Key : Analysis.Memory.CommitPeak.Mb Value: 83 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 BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff80351cfb320 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED TRAP_FRAME: ffffd985070295f0 -- (.trap 0xffffd985070295f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000001afc7b6e rbx=0000000000000000 rcx=ffffd985070297e0 rdx=fffff803540ed830 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80351309c27 rsp=ffffd98507029780 rbp=ffffd98507029960 r8=0000000000000000 r9=0000000000000000 r10=fffff80351347950 r11=ffffb8f8a7e00000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!KeYieldProcessorEx+0x17: fffff803`51309c27 4883c420 add rsp,20h Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: ffffc901`95771e18 fffff803`5141ee32 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffc901`95771e20 fffff803`51216ac3 : 00000033`39c97c70 ffffc901`95758180 00000000`00000000 ffffc901`95758180 : nt!KeAccumulateTicks+0x205b12 ffffc901`95771e80 fffff803`512165aa : ffff8009`c50d6480 ffffd985`07029670 fffff803`56844300 00000000`00008401 : nt!KeClockInterruptNotify+0x453 ffffc901`95771f30 fffff803`5127e795 : ffff8009`c50d6480 ffffc901`95771f40 00000000`00000010 ffff6bad`dcb1efdd : nt!HalpTimerClockIpiRoutine+0x1a ffffc901`95771f60 fffff803`513f873a : ffffd985`07029670 ffff8009`c50d6480 0000002a`dbbb7bc4 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5 ffffc901`95771fb0 fffff803`513f8ca7 : 00000000`00000000 fffff803`512197ae ffffd985`070297e0 fffff803`513f8794 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffffd985`070295f0 fffff803`51309c27 : 00000000`01000010 00000000`00000286 ffffd985`070297a0 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffffd985`07029780 fffff803`5134994a : ffffffff`ffffffff ffffffff`ffffffff 00000000`ffffffff ffff8009`cc975148 : nt!KeYieldProcessorEx+0x17 ffffd985`070297b0 fffff803`513479c3 : 00000000`1afc7b6e 00000000`00000000 ffff8009`cc975368 ffffc901`95758180 : nt!KxWaitForLockOwnerShip+0x2a ffffd985`070297e0 fffff803`56844cf7 : ffff8009`ccfeb180 ffffd985`07029b31 ffffd985`07029b60 00000000`00000000 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x73 ffffd985`07029810 fffff803`513230ce : ffffc901`9575b240 ffff8009`c52f1000 ffffd985`07029b20 ffffc901`00000002 : dxgkrnl!DpiFdoDpcForIsr+0x37 ffffd985`07029860 fffff803`513223b4 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e ffffd985`070299d0 fffff803`513fa7fe : ffffffff`00000000 ffffc901`95758180 ffffc901`95763440 ffff8009`d3ded040 : nt!KiRetireDpcList+0x1f4 ffffd985`07029c60 00000000`00000000 : ffffd985`0702a000 ffffd985`07024000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e SYMBOL_NAME: dxgkrnl!DpiFdoDpcForIsr+37 MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 37 FAILURE_BUCKET_ID: 0x133_DPC_dxgkrnl!DpiFdoDpcForIsr OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {ba837505-1263-7a6a-27ed-8858d50757c2} Followup: MachineOwner ---------
图片/文件
4条回复
来自Microsoft Edge浏览器 发表于 2021-6-4 08:02:52
一样的问题,带出去每次都要重启一次才能正常使用。
回复 支持 反对

使用道具 举报

来自Microsoft Edge浏览器  楼主| 发表于 2021-8-19 00:01:45
没人来看吗?
回复 支持 反对

使用道具 举报

来自Chrome浏览器 发表于 2021-8-24 20:05:38
我也有同样问题,楼主有解决吗
回复 支持 反对

使用道具 举报

来自火狐浏览器  楼主| 发表于 2021-9-30 22:04:11
lenovo56716103 发表于 2021-8-24 20:05
我也有同样问题,楼主有解决吗

哎,已经对联想路转黑了,这明摆着是显卡驱动的问题更新一下显卡驱动就行。
当然我们也可以自己去安装公版驱动,但是公版驱动又有这个问题:https://club.lenovo.com.cn/thread-7801380-1-1.html
回复 支持 反对

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则