通过

如何解决我的Windows上的0x14F_PLM_IMAGE_ModernExecServer.dll问题

^^ AME 40 信誉分
2024-08-14T12:36:23.3566667+00:00 
************ Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.032 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

Microsoft (R) Windows Debugger Version 10.0.27668.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\lenovo\Desktop\070524-20390-01.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 22621 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff804`0d600000 PsLoadedModuleList = 0xfffff804`0e213150
Debug session time: Fri Jul  5 22:48:41.954 2024 (UTC + 8:00)
System Uptime: 0 days 0:51:55.068
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000028`b5123018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`0da1a240 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8184`b114f290=000000000000014f
6: 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: 0000000000000001, Client ID of the hung component.
Arg2: 0000000000000001, A notification client failed to respond.
Arg3: ffffe201d6e75ea0, Pointer to the notification client (pdc!_PDC_NOTIFICATION_CLIENT).
Arg4: ffff8184b114f2e0, Pointer to a pdc!_PDC_14F_TRIAGE structure.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3406

    Key  : Analysis.Elapsed.mSec
    Value: 45160

    Key  : Analysis.IO.Other.Mb
    Value: 4

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 33

    Key  : Analysis.Init.CPU.mSec
    Value: 796

    Key  : Analysis.Init.Elapsed.mSec
    Value: 30453

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 104

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x14f

    Key  : Bugcheck.Code.TargetModel
    Value: 0x14f

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    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

    Key  : Failure.Bucket
    Value: 0x14F_PLM_IMAGE_ModernExecServer.dll

    Key  : Failure.Hash
    Value: {8007afec-a3d4-8394-2075-d7ee4442d125}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  14f

BUGCHECK_P1: 1

BUGCHECK_P2: 1

BUGCHECK_P3: ffffe201d6e75ea0

BUGCHECK_P4: ffff8184b114f2e0

FILE_IN_CAB:  070524-20390-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffaa0979520040

IMAGE_NAME:  ModernExecServer.dll

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

STACK_TEXT:  
ffff8184`b3cd5d60 fffff804`0d85a265     : ffffaa09`75c9b6e0 00000000`00000000 ffffbb00`9021d180 ffffbb00`9021d180 : nt!KiSwapContext+0x76
ffff8184`b3cd5ea0 fffff804`0d85c447     : ffffaa09`75c9b040 fffff804`00000000 ffff49d1`07a65984 00000000`00000000 : nt!KiSwapThread+0xaa5
ffff8184`b3cd5ff0 fffff804`0d85e356     : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x137
ffff8184`b3cd60a0 fffff804`1233fb26     : ffff8184`b3cd6480 ffff8184`b3cd6480 ffffaa09`7a96e7e8 00000000`00000000 : nt!KeWaitForSingleObject+0x256
ffff8184`b3cd6440 fffff804`1234b218     : ffffaa09`7a96e7e8 ffffaa09`7a96e7e8 00000000`00000002 ffff8184`b3cd6910 : Ntfs!NtfsNonCachedIo+0x5b6
ffff8184`b3cd6710 fffff804`1234bc57     : ffffaa09`7a96e7e8 ffffaa09`788325a0 ffffaa09`15000000 ffffaa09`6cb0ed70 : Ntfs!NtfsCommonRead+0x1e28
ffff8184`b3cd68e0 fffff804`0d849b05     : ffffaa09`74466010 ffffaa09`788325a0 ffffaa09`6cb0ed70 ffffaa09`788329d0 : Ntfs!NtfsFsdRead+0x227
ffff8184`b3cd69d0 fffff804`0bdfa1fb     : 00000000`00000000 ffffaa09`74466010 00000000`00002000 fffff804`0bdf90c1 : nt!IofCallDriver+0x55
ffff8184`b3cd6a10 fffff804`0bdfc438     : ffff8184`b3cd6aa8 ffff8184`b3cd1000 00000000`00000000 00000000`00000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x15b
ffff8184`b3cd6a80 fffff804`12316c9f     : ffffaa09`74466010 ffffaa09`7ab06bb0 00000000`00002000 00000000`00000000 : FLTMGR!FltPerformSynchronousIo+0x2d8
ffff8184`b3cd6b30 fffff804`12316841     : ffffaa09`744660f8 00000000`0005091a ffffaa09`7ab06bc8 00000000`00000000 : Wof!FileProvReadCompressed+0x1bf
ffff8184`b3cd6b90 fffff804`122eaeee     : ffffaa09`00002000 ffffaa09`0000091a 00000000`0005091a 00000000`0000003f : Wof!FileProvReadCompressedOnNewStack+0x211
ffff8184`b3cd6c20 fffff804`0d84870a     : ffffaa09`7af8b648 ffffaa09`7ab06bc8 ffff8184`00000000 ffffaa09`7af8b601 : Wof!FileProvReadCompressedCallout+0xe
ffff8184`b3cd6c50 fffff804`0d84867d     : fffff804`122eaee0 ffffaa09`7ab06bc8 fffff804`122f8880 fffff804`0d81e853 : nt!KeExpandKernelStackAndCalloutInternal+0x7a
ffff8184`b3cd6cc0 fffff804`12317583     : ffffaa09`7af8b648 ffffaa09`7ab06bc8 ffffffff`00000010 00000002`ffffffff : nt!KeExpandKernelStackAndCalloutEx+0x1d
ffff8184`b3cd6d00 fffff804`123173ae     : ffffaa09`7ab06bc8 ffffaa09`7af8b648 ffff8184`00000000 fffff804`00000004 : Wof!FileProvReadCompressedSwitchStacks+0x53
ffff8184`b3cd6d40 fffff804`122e86d1     : 00000000`0007e000 00000000`00000000 ffff8184`b3cd6e20 00000000`00000000 : Wof!FileProvCbRead+0x12e
ffff8184`b3cd6da0 fffff804`0bdf963b     : 00000000`000002c0 00000000`00000001 ffffaa09`74e89010 ffffe201`d6ff5380 : Wof!WofPreReadCallback+0x281
ffff8184`b3cd6e60 fffff804`0bdf90c1     : ffff8184`b3cd7080 ffff8184`b3cd7303 00000000`00000000 00000000`00000000 : FLTMGR!FltpPerformPreCallbacksWorker+0x37b
ffff8184`b3cd6f70 fffff804`0bdf8049     : ffff8184`b3cd8000 ffff8184`b3cd1000 00000000`00000000 ffff8184`b3cd7090 : FLTMGR!FltpPassThroughInternal+0xd1
ffff8184`b3cd6fc0 fffff804`0bdf7e2b     : 00000000`00000000 00000000`00000000 ffff8184`b3cd71e0 00007ffb`5e96e630 : FLTMGR!FltpPassThrough+0x179
ffff8184`b3cd7060 fffff804`0d849b05     : ffffaa09`77aa8580 fffff804`0d89fa3b 00000001`00000000 00000001`00000000 : FLTMGR!FltpDispatch+0x8b
ffff8184`b3cd70c0 fffff804`0d8a2a47     : ffffaa09`7480e900 00000000`00000000 00000000`00000043 00000000`00000002 : nt!IofCallDriver+0x55
ffff8184`b3cd7100 fffff804`0d8e1c37     : 00000000`00000001 fffff804`0d852611 ffffaa09`7278da20 ffffaa09`7278d9e0 : nt!IoPageReadEx+0x2d7
ffff8184`b3cd7170 fffff804`0d8e1207     : 00000000`00000003 ffff8184`b3cd7300 ffffaa09`7278d9c0 fffff804`0d856939 : nt!MiIssueHardFaultIo+0x107
ffff8184`b3cd71c0 fffff804`0d84fa51     : 00000000`c0033333 00000000`00000001 00007ffb`5e96e630 00000000`00000000 : nt!MiIssueHardFault+0x207
ffff8184`b3cd72c0 fffff804`0da2b47e     : ffffaa09`75c9b040 ffffaa09`748a6c60 00000000`00000000 ffffaa09`00000000 : nt!MmAccessFault+0x331
ffff8184`b3cd73e0 00007ffb`5e96e630     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x37e
00000028`ba8fed68 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`5e96e630


MODULE_NAME: ModernExecServer

STACK_COMMAND:  .process /r /p 0xffffaa09744a9080; .thread 0xffffaa0979520040 ; kb

FAILURE_BUCKET_ID:  0x14F_PLM_IMAGE_ModernExecServer.dll

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8007afec-a3d4-8394-2075-d7ee4442d125}

Followup:     MachineOwner
---------
Windows 商业版 | 面向 IT 专业人士的 Windows 客户端 | 用户体验 | 其他
0 个注释

2 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. Wesley Li 11,285 信誉分
    2024-08-14T16:25:29.1866667+00:00

    您好，

    PDC_WATCHDOG_TIMEOUT （14f） 错误表示系统组件未能在分配的时间段内响应，从而阻止系统退出连接待机状态。产生此问题的原因有很多，像驱动程序问题、硬件问题或软件冲突等。

    您可以尝试通过下面一些操作步骤进行排查：

    更新驱动程序：确保所有驱动程序都是最新的，尤其是与电源管理和系统组件相关的驱动程序。

    检查 Windows 更新：确保您的 Windows 操作系统已完全更新。

    禁用快速启动：有时，禁用快速启动会有所帮助。您可以通过转到“控制面板”>“电源选项”>“选择电源按钮的功能”>更改当前不可用的设置>取消选中“打开快速启动”来执行此操作。

    运行系统文件检查器：以管理员身份打开命令提示符并运行命令 sfc /scannow 以检查并修复任何损坏的系统文件。

    检查硬件问题：确保所有硬件组件都运行正常且连接正确。

    0 个注释
  2. Wesley Li 11,285 信誉分
    2024-09-03T12:43:46.95+00:00

    您好，

    请问您的问题解决了吗？

    如果以上回复对您有帮助，烦请您将回复标记为答案，非常感谢！

    若您还有其他疑问，请随时与我们联系。

    Thanks

    0 个注释

你的答案

问题作者可以将答案标记为“接受的答案”，这有助于用户了解已解决作者问题的答案。