I'm also having this issue (with version 4.5.1 but it also happened with the previous version), it started a couple of weeks ago. I have two daily scheduled backups. The odds of the crash are about 1 to 10. It seems to happen at the end of either backup...
The log says the backup was successful but the backup is actually corrupted.
Sept 14 2018: Any updates to this? I'm on version 4.5 and both Backupper Pro and BAckupper Technician versions and it still happens. I've reinstalled my computer numerous times swapped hardware, updates, drives, etc. I've now narrowed it aomei backupper. If I plug in usb drives and schedule jobs it may run once, maybe a couple times but it WILL lock up. Screen black as if in power save but like others, no mouse or keyboard. Can unplug, replug, add diffent usb devices but it never comes back. If I don't schedule any jobs, even if Aomie service is running in memory but no jobs run then my computer will run for weeks with never an issue. As soon as I start backups again, lockups, no usb and have to hard power or reset button. It's clearly backupper and it's probably running something out of resources but it's really irritating now. I own backupper pro and backupper technician plus versions and it does the same thing in both. It happens in 4.1 and 4.5. Anyone have a fix for this yet? Thank you for any assistance. Dan
Same thing on my system... has been going on for over 6 months.... happens when a backup is scheduled using the service or Windows Task... manually running backup works fine... WhoCrashed says it is its the amwrtdrv.sys file causing the crash everytime... 3 other computers running same Aomei Backupper laterst rev 4.5.2 have no problems... no idea where to turn next... Acronis TI 2018 working just fine ( I use use 2 backup programs just to be sure)
Any news on this? Not using VSS is better but it still makes the system unstable as it locks the files being backed up. If Windows is doing something important at this time it may also freeze the computer.
I also have to run AOMEI main interface in limited graphical mode (though windows shortcut) else it makes the whole windows interface to become sluguish and unusabel until the graphical driver is restarted(ctrl+shift+win+B)... (I reported this particular issue at least a year ago...)
Have you lost your main developper? What's happening? I'm seriously considering switching software, the lack of reply is not helping...
I've updated to the latest version released since my last post and switched back to VSS to see if it's fixed (nothing in the changelog seems to indicate this possibility though... *fingers crossed*).
2,5 months are gone. Several updates came, but the problem here is more often than before the updates. If it doesn't give a solution, I can't use Aomei any longer. Several crashes every week need to much time.
I was watching as this happened to me. After a backup I got a BSOD. It said it was collecting data and would restart but never did. After a few minutes the screen went dark. Like the screen was going to sleep but it never got completely black. There was a slight backlight glow to the monitor. (This was also my first clue I had a problem when I woke up in the morning and looked at my PC. I let it run 24/7 and Aomei runs a backup during the night. If it locked up after a backup I'd see this glow instead of a black screen.) Like others, at this point the mouse and keyboard were inop. I would have to do a reset to be able to use the PC. This has happened multiple times these past few weeks but only on my PC. My wife's PC hasn't had the problem yet it is also on 24/7 and runs an Aomei backup each night. Both running Win10 Home, 64 bit, ver 1809. This is not good.
I am experiencing BSOD at the end of the daily backup. The error is IRQL_NOT_LESS_OR_EQUAL and the crash dump analysis points to amwrtdrv.sys. Backupper Professional Edition V 4.6.3. Windows 10 Home, 64 bit, V1809.
It looked like it was solved with version 5.3.0 but after updating to 5.6.0 I started to get BSOD (IRQL_NOT_LESS_OR_EQUAL) again. Crash dump analysis points to ABCore.exe, to amwrtdrv.sys, and specifically to symbol amwrtdrv+14d2.
It is about time to have this problem solved. It is not acceptable to have commercial software with this type of problem unsolved for months. After all it is not free.
Oh what's the problem, there isn't a damn status! Always the same small talk with repetitive emails etc ... This problem has not been sloved for 2 years.
Why not include the file "amwrtdrv.sys" of the test version into the latest normal build of Backupper?
When I install the latest version (currently using 5.7.0 Pro) then immediately after this installation I replace this file with the test version. It is residing in C:\Windows\System32\. The properties of the test file I use are 27.360 bytes, date 19 dec 2019 17:57, digitally signed by AOMEI International Network Limited (sha1) and Microsoft Windows Hardware Compatability Publisher (sha256). This file works OK and I do not have any BSOD with automated tasks of Backupper.
One cannot replace this file from within Windows because then it is in use. So you have to quit Windows, start an external shell program from USB (actually Backupper has the option to start a command prompt from USB!) and replace the file manually. This is of course a big PITA.
So why not include it in the normal installation procedure for people who install Backupper on Windows 10? Would save us a lot of trouble... Thank you.
GakuseiJO45@Renehoss Sorry for the inconvenience. Our technician will optimize the problem further and update the solution to the after versions as possible. Once we release the new version, we will attach it to the forum. Sorry again.
What does 'we will attach the new version asap' mean? Hasn't the problem gone on for a very very long time? I only wish that I had found this forum before embarking on Professional. June 2018: 'We are still working on the issue'.
It is a standard edition. If you have a license code, you can register it.
Please first uninstall AOMEI Backupper you have installed via Control Panel, then delete ambakdrv.sys, ammntdrv.sys, amwrtdrv.sys under C:\Windows\System32, reboot the computer, install the new version we sent.
After that, please open Task Manager-->Service-->"Open Services", then disable VSS service. And, please open AOMEI Backupper to select "Use AOMEI Backup Sevice" under Settings (Click three-line button on the main interface).
Comments
The log says the backup was successful but the backup is actually corrupted.
Is there a workaround?
Here is a windbg output: https://gist.github.com/2072/7f923e65759eee78e03807f19015287a
As soon as I start backups again, lockups, no usb and have to hard power or reset button.
It's clearly backupper and it's probably running something out of resources but it's really irritating now.
I own backupper pro and backupper technician plus versions and it does the same thing in both. It happens in 4.1 and 4.5. Anyone have a fix for this yet?
Thank you for any assistance.
Dan
I also have to run AOMEI main interface in limited graphical mode (though windows shortcut) else it makes the whole windows interface to become sluguish and unusabel until the graphical driver is restarted(ctrl+shift+win+B)... (I reported this particular issue at least a year ago...)
Have you lost your main developper? What's happening? I'm seriously considering switching software, the lack of reply is not helping...
I've updated to the latest version released since my last post and switched back to VSS to see if it's fixed (nothing in the changelog seems to indicate this possibility though... *fingers crossed*).
What is the status on this bug?
When do you expect to release a fix?
PROCESS_NAME: ABCore.exe TRAP_FRAME: ffffa786f94d5fe0 -- (.trap 0xffffa786f94d5fe0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff8041ff97180 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8042313011a rsp=ffffa786f94d6170 rbp=ffffbf0965897e60 r8=ffffd083b185a196 r9=000000000000000e r10=00000000ffffffff r11=000000000000020e r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!IoGetLowerDeviceObjectWithTag+0x1e: fffff804`2313011a 488b8b38010000 mov rcx,qword ptr [rbx+138h] ds:00000000`00000138=???????????????? Resetting default scope STACK_TEXT: ffffa786`f94d5e98 fffff804`231d32e9 : 00000000`0000000a 00000000`00000138 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffa786`f94d5ea0 fffff804`231cf62b : 00000000`00000b32 ffffd083`b1860450 00000000`00000000 00000000`67727453 : nt!KiBugCheckDispatch+0x69 ffffa786`f94d5fe0 fffff804`2313011a : 00000000`00000000 00000000`746c6644 fffff804`231300e0 fffff804`236ddbfd : nt!KiPageFault+0x46b ffffa786`f94d6170 fffff804`231300ee : 00000000`00000000 fffff804`231300e0 00000000`00000000 00000000`00000000 : nt!IoGetLowerDeviceObjectWithTag+0x1e ffffa786`f94d61a0 fffff804`1f4c14d2 : 00000000`00000000 00000000`0000003e 00000000`00000000 ffffbf09`66cfb400 : nt!IoGetLowerDeviceObject+0xe ffffa786`f94d61d0 fffff804`1f4c1afa : ffffa786`00000010 ffffa786`f94d6568 fffff804`235e5b05 ffffa786`f94d6860 : amwrtdrv+0x14d2 ffffa786`f94d6530 fffff804`23031f79 : 00000000`000000c8 00000000`00000000 00000000`00000001 00000000`00000000 : amwrtdrv+0x1afa ffffa786`f94d6560 fffff804`23031024 : 00000000`00000003 00000000`00000000 00000000`00000000 fffff804`230317e3 : nt!IofCallDriver+0x59 ffffa786`f94d65a0 fffff804`235e61eb : ffffa786`f94d6860 fffff804`235e5b05 ffffa786`f94d67d0 ffffbf09`5fe74010 : nt!IoCallDriverWithTracing+0x34 ffffa786`f94d65f0 fffff804`235ed1bf : ffffbf09`6501fc50 ffffbf09`6501fc05 ffffbf09`67b47ae0 00000000`00000001 : nt!IopParseDevice+0x62b ffffa786`f94d6760 fffff804`235eb621 : ffffbf09`67b47a00 ffffa786`f94d69a8 00000000`00000040 ffffbf09`5eece980 : nt!ObpLookupObjectName+0x78f ffffa786`f94d6920 fffff804`23630df0 : 00000000`00000001 00000000`03cef2b0 00000000`00000001 00000000`00000000 : nt!ObOpenObjectByNameEx+0x201 ffffa786`f94d6a60 fffff804`236305b9 : 00000000`03cee9e0 00000000`c0100080 00000000`03cef2b0 00000000`03cee9f8 : nt!IopCreateFile+0x820 ffffa786`f94d6b00 fffff804`231d3251 : 00000000`00280000 fffff804`23331010 00000000`00000000 ffffa786`f94d6c80 : nt!NtCreateFile+0x79 ffffa786`f94d6b90 00007ffa`2c2fcb64 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2bc 00000000`03cee968 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`2c2fcb64 SYMBOL_NAME: amwrtdrv+14d2 MODULE_NAME: amwrtdrv IMAGE_NAME: amwrtdrv.sys STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 14d2 FAILURE_BUCKET_ID: AV_amwrtdrv!unknown_function OS_VERSION: 10.0.18362.1 BUILDLAB_STR: 19h1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {a361eca5-d0db-3770-cd80-4f2652e24440} Followup: MachineOwner --------- 0: kd> lmvm amwrtdrv Browse full module list start end module name fffff804`1f4c0000 fffff804`1f4c8000 amwrtdrv (no symbols) Loaded symbol image file: amwrtdrv.sys Mapped memory image file: C:\WINDOWS\system32\amwrtdrv.sys Image path: \??\C:\WINDOWS\system32\amwrtdrv.sys Image name: amwrtdrv.sys Browse all global symbols functions data Timestamp: Tue Dec 25 03:46:38 2012 (50D967EE) CheckSum: 0001711F ImageSize: 00008000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables: 0: kd> .f+ 01 ffffa786`f94d5ea0 fffff804`231cf62b nt!KiBugCheckDispatch+0x69 0: kd> .f+ 02 ffffa786`f94d5fe0 fffff804`2313011a nt!KiPageFault+0x46b 0: kd> .f+ 03 ffffa786`f94d6170 fffff804`231300ee nt!IoGetLowerDeviceObjectWithTag+0x1e 0: kd> .f+ 04 ffffa786`f94d61a0 fffff804`1f4c14d2 nt!IoGetLowerDeviceObject+0xe 0: kd> .f+ 05 ffffa786`f94d61d0 fffff804`1f4c1afa amwrtdrv+0x14d2 0: kd> .f+ 06 ffffa786`f94d6530 fffff804`23031f79 amwrtdrv+0x1afa 0: kd> .f+ 07 ffffa786`f94d6560 fffff804`23031024 nt!IofCallDriver+0x59 0: kd> .f+ 08 ffffa786`f94d65a0 fffff804`235e61eb nt!IoCallDriverWithTracing+0x34 0: kd> .f+ 09 ffffa786`f94d65f0 fffff804`235ed1bf nt!IopParseDevice+0x62b 0: kd> .f+ 0a ffffa786`f94d6760 fffff804`235eb621 nt!ObpLookupObjectName+0x78f 0: kd> .f+ 0b ffffa786`f94d6920 fffff804`23630df0 nt!ObOpenObjectByNameEx+0x201Note: the test version is only for Windows 10.
This problem has not been sloved for 2 years.
When I install the latest version (currently using 5.7.0 Pro) then immediately after this installation I replace this file with the test version. It is residing in C:\Windows\System32\.
The properties of the test file I use are 27.360 bytes, date 19 dec 2019 17:57, digitally signed by AOMEI International Network Limited (sha1) and Microsoft Windows Hardware Compatability Publisher (sha256). This file works OK and I do not have any BSOD with automated tasks of Backupper.
One cannot replace this file from within Windows because then it is in use.
So you have to quit Windows, start an external shell program from USB (actually Backupper has the option to start a command prompt from USB!) and replace the file manually. This is of course a big PITA.
So why not include it in the normal installation procedure for people who install Backupper on Windows 10? Would save us a lot of trouble... Thank you.
I will no longer use Aomei Backupper starting today.
I only wish that I had found this forum before embarking on Professional.
June 2018: 'We are still working on the issue'.