Application error: imagew64.exe
Posted: Sun Jul 02, 2017 11:14 pm
On two different Windows Server 2016's, I've noticed this happening at the very end of some full-backup scheduled jobs. I haven't seen it happen with differentials yet, despite those being far more frequent, nor very small full-backups, so that may be a clue.
Faulting application name: imagew64.exe, version: 3.0.8.0, time stamp: 0x59531673
Faulting module name: ntdll.dll, version: 10.0.14393.479, time stamp: 0x5825887f
Exception code: 0xc0000374
Fault offset: 0x00000000000f8283
Faulting process id: 0x13c0
Faulting application start time: 0x01d2f320412024e9
Faulting application path: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\imagew64.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 4ee50a62-9f18-43f1-ae3e-b801c11b8961
Faulting package full name:
Faulting package-relative application ID:
And by "very end" I mean at the very last second. The above is recorded at 7:04:31am, and ifw.log ends this way:
[7/2/2017 7:04:29 AM] Notifying VSS that backup completed...
[7/2/2017 7:04:30 AM] Time Elapsed: 0:00:19:30
[7/2/2017 7:04:30 AM] Operation Completed with Error Code 0
[7/2/2017 7:04:30 AM] Stop
[7/2/2017 7:04:31 AM] Email sent to...
It all works, but I thought I'd mention it just in case. I've seen it with 3.06 and 3.08 (installs are too new to have used older versions).
I do have the IFW directory excluded from Windows Defender. I was going to except IFW from Windows DEP too, but it doesn't accept 64-bit exes.
Faulting application name: imagew64.exe, version: 3.0.8.0, time stamp: 0x59531673
Faulting module name: ntdll.dll, version: 10.0.14393.479, time stamp: 0x5825887f
Exception code: 0xc0000374
Fault offset: 0x00000000000f8283
Faulting process id: 0x13c0
Faulting application start time: 0x01d2f320412024e9
Faulting application path: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\imagew64.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 4ee50a62-9f18-43f1-ae3e-b801c11b8961
Faulting package full name:
Faulting package-relative application ID:
And by "very end" I mean at the very last second. The above is recorded at 7:04:31am, and ifw.log ends this way:
[7/2/2017 7:04:29 AM] Notifying VSS that backup completed...
[7/2/2017 7:04:30 AM] Time Elapsed: 0:00:19:30
[7/2/2017 7:04:30 AM] Operation Completed with Error Code 0
[7/2/2017 7:04:30 AM] Stop
[7/2/2017 7:04:31 AM] Email sent to...
It all works, but I thought I'd mention it just in case. I've seen it with 3.06 and 3.08 (installs are too new to have used older versions).
I do have the IFW directory excluded from Windows Defender. I was going to except IFW from Windows DEP too, but it doesn't accept 64-bit exes.