FYI, I am getting the same problem on W10 Home 1903 18362.175.
On Sat 15/06/2019 1:14:03
PM your computer crashed or a problem was reported crash dump file:
C:\WINDOWS\MEMORY.DMP This was probably caused by the following module: amwrtdrv.sys (amwrtdrv+0x1845) Bugcheck code: 0x3B
(0xC0000005, 0xFFFFF8067C031CB4, 0xFFFFFD0B0BBA9DE0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path:
C:\WINDOWS\system32\amwrtdrv.sys
Will wait until there is a proper fix, rather than the manual workaround(s).
This thread is from March, now we have June and still no fix. Wow. No "We are aware of the problem", no "We are working on it", no explanation whatsoever if there will EVER be a fix. My trust in this product is gone now. The worst thing a company can do is to NOT communicate with the customers. Because that sends a message like "We don't give shit about your problems, we just want your money".
Thank you guys. I am NOT testing the patch either but am waiting to hear that this is fixed. I am not a tester. I am a end user that wants this software to be fixed before purchasing it again.
@slf exactly my opinion. Although I know how to do all that command line stuff, I simply don't want to do the work the Aomei team has to do. That's not my job as a customer and end user. If it would be an installable patch... ok, maybe. But not this way.
We see crashes when doing nightly backups on a particular production server once a week or so. So to be confident that the problem is fixed, we'd need several weeks of no crashes. We really can't disable driver signing on a production server for that long. A test server, where disabling signing would not be too bad, just doesn't crash. I had it do a backup every 10 minutes for 24 hours and it never failed. It's good to know that a fix is in the pipeline, but until it's signed, we can't do any useful testing. We've been holding off on full deployment even on workstations although we haven't seen crashes on the few that are using Backupper.
I installed the patch and subsequently I had another crash, which is rather disappointing. I have the impression that the crashes occur when using Windows Scheduler to run Backupper, but not when using the internal scheduling service. I will be testing this in the next few days, but in the meantime I'd like to see what other users experience is with respect to this. I prefer to use Windows Scheduling service so it wakes up the computer from hibernation to run the Backup; also, to have the option to reattempt the operation a few times if it fails for some reason. I don't think Backupper scheduling service does either one of those.
I have been running scheduled backups for a week now without any BSOD. It looks like the patch solved the problem. Now I would like to be able to tell my clients, to whom I have recommended Backupper, that the problem is solved, but I cannot expect them to be able o willing to use Recovery Mode Startup options, so it is essential to get a patch that does not have the requirement of disabling Driver Signature Enforcement.
GAR123, Thank you for doing the testing you did. I wish they showed that they are testing this and not just relying on you/us to do their beta testing for them. This problem was around for some time and it took a really long time to fix it.
The release notes for 5.1 say "Fixed issue: the program crashes because of hundreds of thousands of files in NAS/Share folder." Is that the problem discussed in this thread or something else?
I cannot understand why the patch that solves the amwrtdrv.sys BSOD bug was not included in 5.1 -- we have been waiting long enough, it seems very clear that the patch works, we need it in production. It is ridiculous that a Windows restart (due to an installation that requires it or to a power failure, or to any other reason) would cause Backupper to fail unexpectedly. I expect the Pro version to include timely support, otherwise why pay for it.
Comments
On Sat 15/06/2019 1:14:03 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: amwrtdrv.sys (amwrtdrv+0x1845)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8067C031CB4, 0xFFFFFD0B0BBA9DE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\amwrtdrv.sys
Will wait until there is a proper fix, rather than the manual workaround(s).
Attaching MS debugger info:
https://drive.google.com/file/d/1gBd3bf2vst-Gkv6b5KL5G41_OwpqjIsm