DELL Latitude 5410 get bluescreen when it in idle state

sailingcai 1 Reputation point
2021-01-20T04:41:28.993+00:00

Here is the screenshot when the laptop down:
58418-%E5%BE%AE%E4%BF%A1%E5%9B%BE%E7%89%87-20210120123746.jpg

My laptop info:
设备名称 #####
设备全名 #####.com
处理器 Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz 2.11 GHz
机带 RAM 16.0 GB (15.6 GB 可用)
设备 ID ###
产品 ID ###
系统类型 64 位操作系统, 基于 x64 的处理器
笔和触控 没有可用于此显示器的笔或触控输入

版本 Windows 10 企业版
版本号 20H2
安装日期 ‎2020/‎12/‎17
操作系统版本 19042.746
体验 Windows Feature Experience Pack 120.2212.551.0

Minidump file I put on:
https://pan.baidu.com/s/1_Sa3Zh5EZX2lEx6zjTGGhg
Password: ij98

Can anyone help me find the root cause of the blue screen?
THX.

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Teemo Tang 11,466 Reputation points
    2021-01-20T06:52:49.643+00:00

    百度云盘里的minidump分析如下:

    Loading User Symbols  
    Loading unloaded module list  
    .....................  
    For analysis of this file, run !analyze -v  
    nt!KeBugCheckEx:  
    fffff805`5cff5780 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8a08`781efa20=000000000000014f  
    3: kd> !analyze -v  
    *******************************************************************************  
    *                                                                             *  
    *                        Bugcheck Analysis                                    *  
    *                                                                             *  
    *******************************************************************************  
      
    PDC_WATCHDOG_TIMEOUT (14f)  
    A system component failed to respond within the allocated time period,  
    preventing the system from exiting connected standby.  
    Arguments:  
    Arg1: 0000000000000004, Client ID of the hung component.  
    Arg2: 0000000000000002, A resiliency client failed to respond.  
    Arg3: fffff8055855e5d0, Pointer to the resiliency client (pdc!_PDC_RESILIENCY_CLIENT).  
    Arg4: ffff8a08781efa50, Pointer to a pdc!PDC_14F_TRIAGE structure.  
      
    Debugging Details:  
    ------------------  
      
    *** WARNING: Unable to verify timestamp for win32k.sys  
      
    KEY_VALUES_STRING: 1  
      
        Key  : Analysis.CPU.mSec  
        Value: 2718  
      
        Key  : Analysis.DebugAnalysisProvider.CPP  
        Value: Create: 8007007e on WX-69143  
      
        Key  : Analysis.DebugData  
        Value: CreateObject  
      
        Key  : Analysis.DebugModel  
        Value: CreateObject  
      
        Key  : Analysis.Elapsed.mSec  
        Value: 32784  
      
        Key  : Analysis.Memory.CommitPeak.Mb  
        Value: 79  
      
        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  
      
    BUGCHECK_CODE:  14f  
      
    BUGCHECK_P1: 4  
      
    BUGCHECK_P2: 2  
      
    BUGCHECK_P3: fffff8055855e5d0  
      
    BUGCHECK_P4: ffff8a08781efa50  
      
    IMAGE_NAME:  dam.sys  
      
    BLACKBOXBSD: 1 (!blackboxbsd)  
      
      
    BLACKBOXNTFS: 1 (!blackboxntfs)  
      
      
    BLACKBOXPNP: 1 (!blackboxpnp)  
      
      
    BLACKBOXWINLOGON: 1  
      
    CUSTOMER_CRASH_COUNT:  1  
      
    PROCESS_NAME:  System  
      
    STACK_TEXT:    
    ffff8a08`781efa18 fffff805`5856f316     : 00000000`0000014f 00000000`00000004 00000000`00000002 fffff805`5855e5d0 : nt!KeBugCheckEx  
    ffff8a08`781efa20 fffff805`5ce25975     : ffffbd0d`db502080 fffff805`5ce33e00 ffffbd0d`a7b02560 ffffbd0d`00000000 : pdc!PdcpResiliencyWatchdog+0xa6  
    ffff8a08`781efa70 fffff805`5cf17e25     : ffffbd0d`db502080 00000000`00000080 ffffbd0d`a7ad3140 00000000`00000000 : nt!ExpWorkerThread+0x105  
    ffff8a08`781efb10 fffff805`5cffcdd8     : ffffd080`d4653180 ffffbd0d`db502080 fffff805`5cf17dd0 00000000`00000246 : nt!PspSystemThreadStartup+0x55  
    ffff8a08`781efb60 00000000`00000000     : ffff8a08`781f0000 ffff8a08`781e9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28  
      
      
    MODULE_NAME: dam  
      
    STACK_COMMAND:  .thread ; .cxr ; kb  
      
    FAILURE_BUCKET_ID:  0x14F_DAM_IMAGE_dam.sys  
      
    OS_VERSION:  10.0.19041.1  
      
    BUILDLAB_STR:  vb_release  
      
    OSPLATFORM_TYPE:  x64  
      
    OSNAME:  Windows 10  
      
    IMAGE_VERSION:  10.0.19041.1030  
      
    FAILURE_ID_HASH:  {71a660da-efa0-43ad-07ec-33220699ba4c}  
      
    Followup:     MachineOwner  
    

    推测屏幕上的pdc.sys以及dump分析中的dam.sys与蓝屏的产生相关。
    再加上你的设备是DELL Latitude 5410,和这个Dell社区中的Re: Latitude 5400 Sleep Crashes in Windows 10 2004案例十分相似。
    可以考虑使用类似的解决方法:
    前往Intel官网更新intel UHD graphics driver驱动,更新后的版本号为27.20.100.8935,而在Dell官网的驱动存在问题,版本号是27.20.100.8476.
    另外,禁用hibernate mode
    58367-h.jpg

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.