Still bluescreens and crashes when an AOMEI Backupper scheduled task starts running
Last year I had a problem with AOMEI Backupper which lead to a blue screen when a scheduled task starts.
I found some posts regarding this (i.e. https://www.aomeitech.com/forum/discussion/6824/issues-after-applying-bsod-patch-to-cure-system-crash-in-windows-10-v-18365) and after some time the problem disappeared. I assumed a Win10 made the scheduling work again and regarded the problem as solved.
But now after some Win10 updates and some AOMEI Backupper updates I have this effect again. Not always but once in a while. I couldn't manage to find a soulution. When I start the task through Window's task scheduler the system freezes and crashes. The same task started directly from within AOMEI Backupper runs fine without problems.
In the task's options I switched the scheduling to the AOMEI service but still the task crashes when run by the scheduling.
I found some posts regarding this (i.e. https://www.aomeitech.com/forum/discussion/6824/issues-after-applying-bsod-patch-to-cure-system-crash-in-windows-10-v-18365) and after some time the problem disappeared. I assumed a Win10 made the scheduling work again and regarded the problem as solved.
But now after some Win10 updates and some AOMEI Backupper updates I have this effect again. Not always but once in a while. I couldn't manage to find a soulution. When I start the task through Window's task scheduler the system freezes and crashes. The same task started directly from within AOMEI Backupper runs fine without problems.
In the task's options I switched the scheduling to the AOMEI service but still the task crashes when run by the scheduling.
Since I tried to restart the task directly after a crash while the scheduling starts the task when the system is running for some while I wonder if the problem lies in the fact that the target drive might have gone into some sort of hibernation or sleep mode. Does AOMEI Backupper check the availibility of the target when trying to back up? Or does it just start and crashes because the target is not reachable immidiately?
Or are there other ideas how to fix this issue?
(I am running AOMEI Backupper Professional 5.6.0)
Comments
Will this driver be shipped with an upcoming version?
Looking forward to that.
1) Still has the old driver, and not the test driver "amwrtdrv.sys" dated 19-12-2019 17:57.
Still many crashes with scheduled tasks. Please include the test driver, that is the only one that is OK!
2) Furthermore with version 5.7 when I check for update manually, the program creates a child process with an executable file (.exe) in the temporary directory named AutoUpdate.exe.
That is very bad practice! Since my virus scanner and firewall block any programs located in temporary maps with aribitrary names: "autoupdate{9bc00b53-0cde-49c2-89f3-cea264cd6d78}". Version 5.6 had no such problems.
3) Furthermore the installation file created a desktop icon. At first the icon is ok, but after a reboot the icon is blank and cannot be recreated. The link on the desktop has no access to the icon stored within backupper.exe and I had to point to another program to get my icon back.
4) And lastly the installer will only install the program in "C:\Program Files (x86)\Aomei\AOMEI Backupper 5.7.0". I am not able to choose a name myself if I want to install it elsewhere.
Why all these strange and unnecessary changes to the program?
I am not happy. Extremely bad update!
And for
Was this a wrong statement? I cannot try version 5.7 myself, because the fixed driver is not included there and so I would get bluescreens with that version.
See also post https://www.aomeitech.com/forum/discussion/4995/backerupper-amwrtdrv-sys-causing-bsod-on-windows-10#latest
You cannot replace this file from within Windows because then it is in use. Thus this must be done outside of Windows.
So you have to have the test version of Backupper installed first. Copy the file "C:\Windows\System32\amwrtdrv.sys" to a safe place. The correct file has the date 19th of December 2019 and is 27,360 bytes. I keep it on an external drive in case I might have to replace the file again in the future when I update Backupper.
Then also copy this test version of "amwrtdrv.sys" to the bootable Backupper rescue USB that you must have made earlier. Next step is to uninstall the test version of Backupper and reboot. Then install the latest normal version (Pro or Standard) and make sure that the installation went OK.
Next you have to quit Windows and start the computer with Backupper from the bootable USB.
There you will find the option to start a command prompt (in the Tools section). Now from the command prompt you can replace the file manually. The file resides in C:\Windows\System32. Delete the old file and copy the test file from the USB over to your SSD. Reboot into Windows and check that now the correct file is in place. You can check by size or date of the file.
Would be nice if AOMEI would simply include the test version of the file in the normal installation program for users of Windows 10. I can confirm after using the test version of the file with the latest builds of Backupper (currently using 5.7.0 Pro) in this way for a long time that it works OK. I don't have BSODs anymore when Backupper performs an automated backup.
I.e. if I want to install it to "D:\Backups" then the installer puts it in "D:\Backups\AOMEI Backupper 5.7.0". So you can only partially choose where the program is installed.
I think the easiest way for all (Win10-) users would be if AOMEI would
– include the correct driver in the next version of Backupper and
– let the user have full control over the installation path without adding a subdirectory
The culprit file is amwrtdrv.sys and is of the year 2017.
The test version of amwrtdrv.sys is of the year 2019 and works OK, it is not giving any BSOD.
So please, insert this newer file into the installation setup.
Why keeping the old file that is giving people troubles?
I simpy don't understand anymore...
And yes, I went through the bothersome routine again to overwrite amwrtdrv.sys again, just to keep Backupper working... Oh, brother...
... the new amwrtdrv.sys with v5.8 is dated 8Jun20 and is 43KB.
A straight upgrade from v5.7 does not upgrade the sys - it has to be manually deleted as above.
And do theses three drivers belong to VSS or to the AOMEI Backup Service?