Hasleo Backup hangs system

[Ivan_Strelec]

In the system logs I saw the warning:

svchost (3604,D,0) SRUJet: The request to write to file "C:\WINDOWS\system32\SRU\SRU.log" with offset 36864 (0x0000000000009000) and size 4096 (0x00001000) bytes was completed, but its execution in the OS took too long (948 seconds). This error is probably caused by a hardware failure. Contact the hardware vendor to determine the cause of the error.

I think this message appears because the system hangs while the program is running.

[admin]

In the system logs I saw the warning:

svchost (3604,D,0) SRUJet: The request to write to file "C:\WINDOWS\system32\SRU\SRU.log" with offset 36864 (0x0000000000009000) and size 4096 (0x00001000) bytes was completed, but its execution in the OS took too long (948 seconds). This error is probably caused by a hardware failure. Contact the hardware vendor to determine the cause of the error.

I think this message appears because the system hangs while the program is running.

Other users seem to have encountered similar issues without having HBS installed, it should be caused by a system issue, such as a driver compatibility issue.
https://answers.microsoft.com/en-us/wind...74c268a416
https://answers.microsoft.com/en-us/wind...b7b?page=1

[Ivan_Strelec]

Updated drivers for MB and video. 
The program behavior has not changed. 
Also, at 7%, the progress indicator stopped updating and the explorer froze. After the backup was completed, the system continued to work. 
I am sure that the above SKU warning appears due to the system freezing and the inability to write to the SRU.log file. 
Such a system freeze does not occur when other programs installed in the system are running.

[Ivan_Strelec]

I did another experiment.
I made a backup of the second (non-system) disk and saved it to the system disk.
The program worked as expected. There were no hangs in Explorer, the process indicator correctly showed the work process.
Thus, something happens when backing up the system disk.
I repeat, there are no hangs when backing up via WinPE.

[admin]

I am sorry that HBS uses Microsoft's Volume Shadow Copy Service (VSS) technology to implement Windows hot backup, if VSS is having an effect on SRU.log or the system, then there must be some other anomaly that is causing this and there is nothing we can do about it. Perhaps we should check if this issue exists after a fresh installation of the Windows system.

Please open the elevated cmd.exe prompt and type “vssadmin list writers” and check to see if there are any errors for all writers?

[Ivan_Strelec]

vssadmin list writers no errors found.

During the backup process, the following message also appears in the system log:
Chkdsk was run on a volume snapshot in read-only mode.

Windows checked the file system and found no problems.
No further action required.

The warning about a long record in SCU.log is not an error, but a consequence of the system hanging during the backup creation.
Since the freezing consistently occurs only on one machine, then the problem is clearly in Windows.
I would like to find and fix this problem. Although in the end the program does create a backup.

Unfortunately, doing a clean installation of Windows on this computer is quite problematic due to the possible loss of activation of some products.
Reinstalling Windows while keeping existing programs did not produce any results.

[admin]

vssadmin list writers no errors found.

During the backup process, the following message also appears in the system log:
Chkdsk was run on a volume snapshot in read-only mode.

Windows checked the file system and found no problems.
No further action required.

The warning about a long record in SCU.log is not an error, but a consequence of the system hanging during the backup creation.
Since the freezing consistently occurs only on one machine, then the problem is clearly in Windows.
I would like to find and fix this problem. Although in the end the program does create a backup.

Unfortunately, doing a clean installation of Windows on this computer is quite problematic due to the possible loss of activation of some products.
Reinstalling Windows while keeping existing programs did not produce any results.

Please try the steps below to temporarily disable the 'System Resource Usage Monitor' to see if the issue persists.

[Ivan_Strelec]

Stopping the resource monitor and updating the program to version 5.2.2.3 did not help.
Tried AOMEI backupper. There were no system freezes.

[admin]

Stopping the resource monitor and updating the program to version 5.2.2.3 did not help.
Tried AOMEI backupper. There were no system freezes.

I'm not sure why, but perhaps we'll have to slow down the backup speed.

[Ivan_Strelec]

I'm not sure why, but perhaps we'll have to slow down the backup speed.

Will you make changes to the program code? Or will I need to do something?