I run a scheduled full backup every Sunday at 23:30. This task has failed to produce a backup for the last couple of weeks. Running the task from the Task Scheduler with History enabled show that the task starts and then completes a few seconds later, no Macrium log file is produced and no backup is performed.
Examination of the Windows 'System' event log shows the following event at around 23:30 on Sunday when the scheduled event should have run:--
<System> <Provider Name="Win32k
" /> <EventID Qualifiers="32768
">243</EventID> <Level>3</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-08-13T22:30:26.143872200Z
" /> <EventRecordID>4512</EventRecordID> <Channel>System</Channel> <Computer>MBSPECIALIST</Computer> <Security /> </System>-
<EventData> <Data /> <Binary>000000000100000000000000F3000080000000000000000000000000000000000000000000000000</Binary> </EventData> </Event>
Searching on-line indicates that the heap has been exhausted, this is a global resource for the Winstation running the System Account under which the Task Scheduler runs. The only solution seems to be re-booting the machine. It seems that once the heap is full lots of other scheduled tasks that use the SYSTEM account fail to run, including Windows Update.
I have two machines exhibiting this problem, both running Windows 10 1703, OS Build 15063.502, one machine is Windows 10 Home, one Windows 10 Pro.
An idle thought - does reflect.exe register window handles etc. even when running in a non-windowed environment?