#1409 Application Crash Silently After Last Entry Processed, Data Not Synced

[Alex D]

Between March 31st and April 1st, GCSM stopped successfully completing syncs of a client's Outlook to Google address book, and the application closes without warning after the last entry appears to be processed. The application logs show it getting all the way to the last contact (of which there are almost 3000) and then the log ends. Checking windows event viewer, the following application error logs are shown (attached). I've witnessed other errors during previous crashes that seem to point to .NET modules faulting, also attached. Prior to updating to 4.2.1 (I believe 4.1.3 was the version), the application was crashing earlier in the process, and 4.2.1 allows it to get further, but still never completes successfully. This user has been utilizing GCSM for a decade, and it was still functional until the 1st of April of this year.

Attempts to fix:
Latest version (4.2.1) installed
.NET Framework 4.8.1 has been installed/repaired
sfc /scannow has been run successfully, nothing of note

I know you'd like application logs attached, but this user has nearly 3000 contacts worth of details that would need to be purged, and there's nothing abnormal in the logs to indicate any problem with execution anyway. The logs through March 31st look the same as those after, but those after March 31st just end after the last contact is claimed to be updated. The logs from previous successful runs include 3 additional lines noting the disconnect from Outlook, and the application doesn't just close.

Additionally, it doesn't seem that any of the contacts claiming to be synced make it to Google. There are a handful of new contacts added in the last two weeks in outlook that the application lists as being synced, but checking in Google, those contacts were never pushed.

If there's any specific information you'd like to see from the logs, I can retrieve that, but due to the sheer volume of data in the log that the user would rather not share, I won't be attaching the log in its entirety.

[George Franklin Phelps]

Same issue. Started when I upgraded to Windows 11.

Faulting application name: GOContactSync.exe, version: 4.2.1.0, time stamp: 0x67fcec41
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00000fd
Fault offset: 0x00007ffb5c26f133
Faulting process id: 0x6CB8
Faulting application start time: 0x1DBB937A83279F3
Faulting application path: C:\Program Files (x86)\GO Contact Sync Mod\GOContactSync.exe
Faulting module path: unknown
Report Id: 3ba71f74-0bab-4c06-ae14-bc1496877ebf
Faulting package full name:
Faulting package-relative application ID:

[George Franklin Phelps]

What is the status of this bug report?

[George Franklin Phelps]

What is the status of this bug report?