Sudden Problem

Discussion in 'FirstDefense-ISR Forum' started by tradetime, May 20, 2011.

Thread Status:
Not open for further replies.
  1. tradetime

    tradetime Registered Member

    Hi I have been running FDISR Ver 3.31 Build 233 quite happily on my Vista 64 computer for just over 2 years now. Suddenly this week when I run a copy the program says it is starting the VSS as normal, Indexing as normal, however shortly after it begins "Preparing to Copy" the program stops delivering the following message;
    FD-ISR Error
    Copy Engine Unexpectedly Terminated (Only additional info in detail log is I assume the error number 1117)

    I have installed no new programs since the last successful copy. The only changes to the system would be Firefox updates, Windows updates and Avast updates.

    Any help, suggestions etc would be greatly appreciated.

    Windows Event lists this if it helps

    Problem Event Name: APPCRASH
    Application Name: ISRCopy.exe
    Application Version:
    Application Timestamp: 489618e7
    Fault Module Name: ntdll.dll
    Fault Module Version: 6.0.6002.18327
    Fault Module Timestamp: 4cb7341c
    Exception Code: c00000fd
    Exception Offset: 0004e45b
    OS Version: 6.0.6002.
    Locale ID: 2057
    Additional Information 1: 6139
    Additional Information 2: 3079317b57ae6c4a6ed692835e52f9d8
    Additional Information 3: b2fa
    Additional Information 4: 1ebf742c43f7d02ad5693625c5076dff
    Last edited: May 20, 2011
  2. jwcca

    jwcca Registered Member

    Any chance that a security app is interfering?
    The ISRcopy.exe process first creates a ton of Lists, then corresponding .exes that use the Lists. If something is stopping the Lists or exes from being created the copy will fail.
  3. tradetime

    tradetime Registered Member

    Hi JW, thanks for the response, the only security app on that computer that is not Native windows is Avast, the computer setup has remained the same for the two years odd I have been using FD-ISR on it, other than normal program updates. As such if a windows or Avast update had introduced a problem I would have expected someone else might have encountered it
  4. tradetime

    tradetime Registered Member

    No other suggestions, shame, guess that's the death of that program for me then.
Thread Status:
Not open for further replies.