Backupper Pro ambakdrv.sys causes system crash
In about 4 out of 5 attempts to do a system backup, with 6.5.0 and some other recent versions, this particular system crashes. On four other systems, one with a similar motherboard and processor, 6.5.0 operates with no problems.
Here is a minidump trace of one crash ...
---------------------------------------------------------------------
Can someone seek a solution?
Here is a minidump trace of one crash ...
---------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\050321-43984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`1200a000 PsLoadedModuleList = 0xfffff803`12c34130
Debug session time: Mon May 3 02:36:07.550 2021 (UTC - 7:00)
System Uptime: 2 days 19:03:44.510
Loading Kernel Symbols
...............................................................
............
Loading User Symbols
Loading unloaded module list
.........................
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffff8a83eadf2b70, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff80314912357, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for ambakdrv.sys
Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 9
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on JOY
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 33
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 50
BUGCHECK_P1: ffff8a83eadf2b70
BUGCHECK_P2: 2
BUGCHECK_P3: fffff80314912357
BUGCHECK_P4: 2
READ_ADDRESS: fffff80312d04390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80312c19378: Unable to get Flags value from nt!KdVersionBlock
fffff80312c19378: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffff8a83eadf2b70
MM_INTERNAL_CODE: 2
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffff9d87f1a6fb60 -- (.trap 0xffff9d87f1a6fb60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=000000000000082f rsi=0000000000000000 rdi=0000000000000000
rip=fffff80314912357 rsp=ffff9d87f1a6fcf0 rbp=ffff8a83d2df9140
r8=000000000002082f r9=000000000000002f r10=fffff803122d1520
r11=0000000000000103 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
ambakdrv+0x2357:
fffff803`14912357 44895f30 mov dword ptr [rdi+30h],r11d ds:00000000`00000030=????????
Resetting default scope
STACK_TEXT:
ffff9d87`f1a6f8b8 fffff803`12497e7d : 00000000`00000050 ffff8a83`eadf2b70 00000000`00000002 ffff9d87`f1a6fb60 : nt!KeBugCheckEx
ffff9d87`f1a6f8c0 fffff803`12332210 : fffff803`11b40180 00000000`00000002 ffff9d87`f1a6fbe0 00000000`00000000 : nt!MiSystemFault+0x147dbd
ffff9d87`f1a6f9c0 fffff803`1240ee5e : ffff8a83`b36e8ef0 fffff803`11b40180 ffff9d87`f1a6fc70 00000000`00000000 : nt!MmAccessFault+0x400
ffff9d87`f1a6fb60 fffff803`14912357 : 00000000`00000000 ffff8a83`d2df9140 ffff8a83`b36e8db0 ffff8a83`cbd54180 : nt!KiPageFault+0x35e
ffff9d87`f1a6fcf0 00000000`00000000 : ffff8a83`d2df9140 ffff8a83`b36e8db0 ffff8a83`cbd54180 00000000`00000000 : ambakdrv+0x2357
SYMBOL_NAME: ambakdrv+2357
MODULE_NAME: ambakdrv
IMAGE_NAME: ambakdrv.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 2357
FAILURE_BUCKET_ID: AV_VRF_INVALID_ambakdrv!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8ed0f2f4-4848-a392-1579-9ae963b45b1f}
Followup: MachineOwner
---------
Can someone seek a solution?
Tagged:
Comments
Could you send us the minidump files? We will submit them to our technician to check.
http://www2.aomeisoftware.com/download/adb/4.5.2/ABPro.exe
In addition, "On four other systems, one with a similar motherboard and processor, 6.5.0 operates with no problems."---Are they using same system versions?
Confirm you want me to try version 4.5.2. That version is 2 1/2 years old! Might it have compatibility problems?
FYI v6.5.0 fails on about 1 of six attempts on this particular computer with all parameters exactly the same for each attempt.
Attached are minidump files etc.