It is very important to note that not all systems will support Modern Standby and to support it, the firmware must meet these requirements:
Modern Standby is directly analogous to how if you press the power button on your smartphone, it won’t be powered off, but rather go into a very low powered idle state and respond to certain events such as app notifications, etc. It was primarily introduced as Microsoft began to shift its focus to portable devices such as tablets. Essentially, its purpose was to allow devices to ‘instantly’ wake from sleep. This power policy was introduced with Windows 8 and developed further with the introduction of Windows 10. PDC is an acronym for Power Dependency Coordinator and is a component of Modern Standby. This bugcheck is fairly uncommon and is typically found with devices such as tablets like the Surface Pro. Preventing the system from exiting connected standby.Īrg1: 000000000000000 4, Client ID of the hung component.Īrg2: 0000000000000001, A notification client failed to respond.Īrg3: ffffc001079315c0, Pointer to the notification client (pdc!_PDC_NOTIFICATION_CLIENT).Īrg4: ffffd00021701b50, Pointer to a pdc!PDC_14F_TRIAGE structure.Īs previously mentioned by Patrick, this bugcheck is caused when a system process has been unable to respond in a timely fashion when waking from standby mode, and therefore the system ends up in a bugcheck as shown above.įortunately, both of the data structures mentioned in the bugcheck parameters can be dumped using a Minidump, however, before we do that, we’ll need to familiarise ourselves with what the bugcheck is about. PDC_WATCHDOG_TIMEOUT (14f)Ī system component failed to respond within the allocated time period, I’ll continuing from earlier analysis which Patrick made here. This another rare bugcheck which I’ve only seen on a handful of occasions, which makes it even important that we explore it and create some documentation.
0 kommentar(er)
