Lenovo X1 Carbon Battery Reset Dec 15, 2019 · This parameter value shows that the Win32k.sys (Windows subsystem) wasn’t able to respond to a monitor-on power request within the specified timeout limit. Effectively, a power IRP was pending for too long and therefore lead to the bugcheck. It is important to note that the monitor-on power requests come from a variety of wake sources.

When the "Clock Watchdog Timeout" BSOD error appeared, the PC froze and the only way to get the PC working again was to Turn Off (or According to Microsoft, the CLOCK_WATCHDOG_TIMEOUT bug check, indicates that an expected clock interrupt on a secondary processor, in a multi-processor...already tried timeout-time: -1 in spigot.yml. and setting max-tick-time=-1 in server.prop. ok found the solution i ended up modifying WatchdogThread.java i commented out lines 55-88 and that effectively disable the watchdog allowing for a debugger to run without stopping the server.

Typically the CLOCK_WATCHDOG_TIMEOUT error means the processor had a problem with one core or thread waiting for another core or thread.

PDC_WATCHDOG_TIMEOUT (14f) A system component failed to respond within the allocated time period, preventing the system from exiting connected standby. Arguments: Arg1: 0000000000000000, Client ID of the hung component. Arg2: 0000000000000100, Win32k did not complete a monitor-on request in a timely manner.

Try removing power and/or the battery from the PC for 10 seconds. Then reapply power so that a fairly clean start up occurs. You may also want to temporally disconnect any physical network connections, to eliminate another possible problem source.