Application error: imagew64.exe

User discussion and information resource forum for Image products.

Application error: imagew64.exe

Postby rseiler » Sun Jul 02, 2017 4: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.
rseiler
 
Posts: 47
Joined: Sat May 05, 2012 3:29 pm

Re: Application error: imagew64.exe

Postby Focusicr » Tue Jul 04, 2017 12:59 am

You can give us more examples of the issues raised.
Focusicr
 
Posts: 2
Joined: Mon Jul 03, 2017 8:54 pm

Re: Application error: imagew64.exe

Postby TeraByte Support » Tue Jul 04, 2017 12:20 pm

if using a standard pc and normal memory may want to run a memory test over
night just to ensure no weird issues caused by that.

after that, not sure if the minidump would help or not, but can send it to
support if one was created.

"rseiler" wrote in message news:13951@public.image...

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.

TeraByte Support
 
Posts: 2310
Joined: Thu May 05, 2011 3:37 pm

Re: Application error: imagew64.exe

Postby rseiler » Wed Jul 05, 2017 11:33 am

TeraByte Support wrote:
> if using a standard pc and normal memory may want to run a memory test over
>
> night just to ensure no weird issues caused by that.
>
> after that, not sure if the minidump would help or not, but can send it to
>
> support if one was created.

They are two completely different machines, and one uses ECC. Plus, it happens at the same point at the conclusion of the backup. It's not the RAM.

Oh yes, the little .WER files. They're so small, I just put them both in a file and posted them here. Other than loaded modules though, there's nothing really beyond what I mentioned in the top post.
Attachments
reports.wer.zip
(1.9 KiB) Downloaded 40 times
rseiler
 
Posts: 47
Joined: Sat May 05, 2012 3:29 pm

Re: Application error: imagew64.exe

Postby rseiler » Fri Nov 10, 2017 10:19 pm

Woo hoo!

Version 3.13 - November 10, 2017
Corrected exception fault that would occur at end of run when /exlist was used.
rseiler
 
Posts: 47
Joined: Sat May 05, 2012 3:29 pm


Return to Image for DOS/Linux/Windows

cron