我的台式机构造相当简单，配有技嘉主板、一对 NVME 驱动器、DVD R/W 驱动器和 64GB RAM。运行 Windows 10 并连接到 TrippLite UPS。
我通常每晚都会关闭它，但最近我一直在运行一些需要连续几天开机的计算机进程。在这些情况下，我观察到只要我不碰机器，它就会在中午自动进入休眠状态。所有睡眠选项都被禁用，包括“隐藏”选项，需要进行一些简单的注册表编辑才能访问。
解析事件日志清楚地显示机器正在进入睡眠状态。我今天早上检查了一下，想看看它在夜间是什么时候进入这种状态的，结果发现了其他东西——一连串 6 条“电源已更改”消息，持续约 7 分钟。
我也检查了我的 UPS 的日志，它们也显示机器进入睡眠状态，具体来说：
2023-09-28T17:52:40Z tradingPC - -1: [info] CommandInfo [ name='Get Discharging'; id=103; variation=5; protocolId=0x3016; className='Command_getdischarging_3016_com_hid_103'; priority='MEDIUM'; executionGroup='DATA'; commandType='GET'; communicationType='HID'; isIdle=false; isLiteral=false; isNullCommand=false; isCommandDataFormula=false; commandData=' 00 84 00 02 00 85 00 45 '; data=' '; inboundDataLength=1; outboundDataLength=8; line=0; dependsOnVariable=''; updatedVariables=('Battery Discharging','Battery Charge'); isAvailable=true; tag=;) ]
2023-09-28T17:52:40Z tradingPC - -1: [info] Sending 8 bytes to device: 00 84 00 02 00 85 00 45
2023-09-28T17:52:40Z tradingPC - -1: [info] Port '\\?\hid#vid_09ae&pid_3016#6&12b3d71&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' Outbound to device: combined=0x84000200850045
2023-09-28T17:52:40Z tradingPC - -5: [debug] Received message <<14>Sep 28 10:52:40 tradingPC CommandInfo [ name='Get Discharging'; id=103; variation=5; protocolId=0x3016; className='Command_getdischarging_3016_com_hid_103'; priority='MEDIUM'; executionGroup='DATA'; commandType='GET'; communicationType='HID'; isIdle=false; isLiteral=false; isNullCommand=false; isCommandDataFormula=false; commandData=' 00 84 00 02 00 85 00 45 '; data=' '; inboundDataLength=1; outboundDataLength=8; line=0; dependsOnVariable=''; updatedVariables=('Battery Discharging','Battery Charge'); isAvailable=true; tag=;) ]>
2023-09-28T17:52:40Z tradingPC - -5: [debug] Received message <<14>Sep 28 10:52:40 tradingPC Sending 8 bytes to device: 00 84 00 02 00 85 00 45 >
2023-09-28T17:52:40Z tradingPC - -5: [debug] Received message <<14>Sep 28 10:52:40 tradingPC Port '\\?\hid#vid_09ae&pid_3016#6&12b3d71&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' Outbound to device: combined=0x84000200850045>
2023-09-28T17:52:40Z tradingPC - -1: [info] Port '\\?\hid#vid_09ae&pid_3016#6&12b3d71&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' Inbound (four byte) from device: 00 00 00 00
2023-09-28T17:52:40Z tradingPC - -5: [debug] Received message <<14>Sep 28 10:52:40 tradingPC Port '\\?\hid#vid_09ae&pid_3016#6&12b3d71&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' Inbound (four byte) from device: 00 00 00 00 >
**2023-09-28T17:52:40Z tradingPC - -1: [info] Handling entry to hibernation...**
2023-09-28T17:52:40Z tradingPC - -1: [info] Iterate over device 1
**2023-09-28T17:52:40Z tradingPC - -5: [debug] Received message <<14>Sep 28 10:52:40 tradingPC Handling entry to hibernation...>**
2023-09-28T17:52:40Z tradingPC - -5: [debug] Received message <<14>Sep 28 10:52:40 tradingPC Iterate over device 1>
2023-09-28T17:52:40Z tradingPC - -1: [info] CommandInfo [ name='Stop Watchdog Timer'; id=239; variation=14; protocolId=0x3016; className='Command_stopwatchdogtimer_3016_com_hid_239'; priority='MEDIUM'; executionGroup='EXIT'; commandType='SET'; communicationType='HID'; isIdle=false; isLiteral=false; isNullCommand=false; isCommandDataFormula=false; commandData=' 00 84 00 20 ff ff 00 92 '; data=' 00 '; inboundDataLength=1; outboundDataLength=8; line=0; dependsOnVariable='Cmd Stop Watchdog Timer Data'; updatedVariables=(); isAvailable=true; tag=;) ]
2023-09-28T17:52:40Z tradingPC - -1: [info] Sending 8 bytes to device: 00 84 00 20 ff ff 00 92
2023-09-28T17:52:40Z tradingPC - -1: [info] Port '\\?\hid#vid_09ae&pid_3016#6&12b3d71&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' Outbound to device: combined=0x00840020ffff0092; data=00
2023-09-28T17:52:40Z tradingPC - -5: [debug] Received message <<14>Sep 28 10:52:40 tradingPC CommandInfo [ name='Stop Watchdog Timer'; id=239; variation=14; protocolId=0x3016; className='Command_stopwatchdogtimer_3016_com_hid_239'; priority='MEDIUM'; executionGroup='EXIT'; commandType='SET'; communicationType='HID'; isIdle=false; isLiteral=false; isNullCommand=false; isCommandDataFormula=false; commandData=' 00 84 00 20 ff ff 00 92 '; data=' 00 '; inboundDataLength=1; outboundDataLength=8; line=0; dependsOnVariable='Cmd Stop Watchdog Timer Data'; updatedVariables=(); isAvailable=true; tag=;) ]>
2023-09-28T17:52:40Z tradingPC - -5: [debug] Received message <<14>Sep 28 10:52:40 tradingPC Sending 8 bytes to device: 00 84 00 20 ff ff 00 92 >
2023-09-28T17:52:40Z tradingPC - -5: [debug] Received message <<14>Sep 28 10:52:40 tradingPC Port '\\?\hid#vid_09ae&pid_3016#6&12b3d71&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' Outbound to device: combined=0x00840020ffff0092; data=00 >
**2023-09-28T17:52:40Z tradingPC - -1: [info] Handled entry to hibernation**
**2023-09-28T17:52:40Z tradingPC - -5: [debug] Received message <<14>Sep 28 10:52:40 tradingPC Handled entry to hibernation>**
**2023-09-28T17:52:59Z tradingPC - -1: [info] Handling exit from hibernation...**
**2023-09-28T17:52:59Z tradingPC - -1: [info] Handled exit from hibernation**
2023-09-28T17:52:59Z tradingPC - -1: [debug] set 'memoized_setups' on path 'CachingEntityRegistry((<Mapper at 0x197d3106550; SysLogServerModel>,))' to '{}'
2023-09-28T17:52:59Z tradingPC - -1: [debug] Returning 1 devices
2023-09-28T17:52:59Z tradingPC - -1: [info] updating active state for device 1. Updating active to false and initialized to false
2023-09-28T17:52:59Z tradingPC - -1: [info] Device ID 1 is going inactive; clear Communication Lost Event = false
2023-09-28T17:52:59Z tradingPC - -1: [debug] Clearing event active state and alarms only for device 1
2023-09-28T17:52:59Z tradingPC - -1: [debug] successfully got the list of alarms. Received 0 alarms
2023-09-28T17:52:59Z tradingPC - -1: [debug] gRPC OK, in: (, <grpc._server._Context object at 0x00000197D3C)
**2023-09-28T17:52:59Z tradingPC - -5: [debug] Received message <<14>Sep 28 10:52:59 tradingPC Handling exit from hibernation...>**
**2023-09-28T17:52:59Z tradingPC - -5: [debug] Received message <<14>Sep 28 10:52:59 tradingPC Handled exit from hibernation>**
（我试图将休眠行加粗，但这在代码块中不起作用......所以将星号视为与休眠直接相关的行）
我退出了所有后台应用程序，安装了 PowerToys 并使用了“始终唤醒”选项……除了我移动鼠标之外，没有什么可以阻止这种情况。我已经束手无策了，因为我需要我的机器能够在无人看管的情况下运行相当长的时间。
答案1
我简直不敢相信解决方案是什么，所以如果其他人也遇到同样的模糊情况，这里就是这种情况的最终答案。
甚至连软件都可以随机间隔移动鼠标，以及软件Caffeine都无法让机器在一夜之间保持清醒……我完全没有主意了。然后今天早上我想起了一个很久以前的记忆片段。
我查看了任务计划程序，果然……晚上 11 点安排了任务Sleep。它被设置为仅在空闲 10 分钟后开启，并且如果中断则恢复。
我依稀记得几年前就设置了这个。直到晚上 11 点才启动，需要 10 分钟的空闲时间，再加上中断后恢复，这些因素结合在一起，让它变得随机到毫无意义，也不是一个明显的预定事件。现在我已经禁用了该事件……不再有自发休眠！