Backupper Pro 6.2 crashing Win10 machine when copying files from mounted 'explore image'

Trying to restore files from a mounted (explored) incremental backup image using v6.2 of Backupper Pro.
adi Images reside on an external USB 3 Seagate Backup Unit.
Incremental Image has successfully passed the image check 100% no errors.
Copying small handfuls of files can sometimes succeed however increasing this to multiple folders will lockup|crash|reboot the Windows 10 Pro x64 (20H2) desktop.
Files have been attempted to be file copied to two different internally attached destination drives (m.2 ssd and sata 7200rpm) both tested to be error free and exceeding the space required however the crash result is the same.
The number of files in question is less than 35GB.

Jason

Comments

  • After Uninstalling/reinstalling v6.2 now getting BSOD referring the ammntdrv.sys (21/12/2016) driver causing PAGE_FAULT_IN_NONPAGED_AREA
  • Hello Imershon,
    Did you get the BSOD when you perform the backup manually? or schedule backup?
    Could you take a screenshot of the BSOD? And, please send us the minidump file under C:/WINDOWS/Minidump.
  • No backup involved at all - the BSOD was during copying files from a mounted image.
  • Same issue applies with v6.3 but given the changelog that isn't surprising.
    Have also now copied the adi files onto a local drive to rule out the connection to the USB 3 backup unit but the same crash/reboot occurs with 6.3 copying files from the explored image.
    Both the ammntdrv.sys and ambakdrv.sys drivers have not been recompiled since 21/12/2016 are they going to be updated?
  • @Imershon, Sorry to reply to you late. Could you help us test the new ammntdrv.sys file and check if you will get the problem again? 
    Please download the ammntdrv.sys file from the following link, and then put it to C:\Windows\System32 to replace. 
    https://drive.google.com/file/d/1zneGtfWU5iJk4ETeIN3JZbHIYnr2ldNa/view?usp=drivesdk
    Please note, for replace them successfully, please first run "CMD" as Administrator to open Command Prompt,  then type into "net stop ammntdrv", then copy the ammntdrv.sys to replace, then type into "net start ammntdrv" to start again.
    In addition, because the driver hasn't yet been signed, you need to “Disable driver signature enforcement" when boot the computer:
    You can hold down the Shift key while you click the “Restart” option in Windows. 
    Select the “Troubleshoot” tile on the Choose an option screen that appears.
    Select “Advanced options”.
    Click the “Startup Settings” tile.
    Click the “Restart” button to restart your PC into the Startup Settings screen.
    Type “7” or “F7” at the Startup Settings screen to activate the “Disable driver signature enforcement” option.
    Your PC will boot with driver signature enforcement disabled and you’ll be able to install unsigned drivers. However, the next time you restart your computer, driver signature enforcement will be disabled—unless you go through this menu again.

  • Looks like a winner! - was able to copy 26GB+ files from the explored image without any problems at all.
    If you can sign and release you have a good candidate for v6.4 :)
  • @Imershon, Yes, we will fix the problem in the next version.
  • Is there an ETA on v6.4 - rebooting to disable drive signature enforcement is getting old fast.

  • @Imershon, We will send you the new v6.4 later this week.
Sign In or Register to comment.