FreeFileSync Forum

I suspect the general system non-responsiveness issues are caused by the USB3 driver. USB3 drivers are still flaky even on Windows 7 where they lead to exactly the symptoms you describe. Practically speaking the best solution is to upgrade to the most recent USB3 drivers available for your ...

Is this snapshot taken during a "stops responding" situation? Except for a lot of threads scanning directories in parallel, the main thread is not blocked with file I/O.
Here's a log of a similar run.

[Attachment was removed! File name: SyncSettings 2015-10-12 060551 [Warning].log (770094 bytes)]

Is this snapshot taken during a "stops responding" situation? Except for a lot of threads scanning directories in parallel, the main thread is not blocked with file I/O.
Yes... This particular one is a slow responding, not a stops responding. Sometimes it struggles on just at really poor speeds ...

Yes, Process *Explorer*. A full dump is better of course, ideally a few ones (this is monte-carlo debugging...)Zenju

Also, at the moment, I can't create a dump again. I'm told "error opening process - access is denied"

Yes, Process *Explorer*. A full dump is better of course, ideally a few ones (this is monte-carlo debugging...)
The problem seems to be related to the external drive connected to the PC running FFS. I'm sitting here now, watching FFS go through a run, it's just into its second hour on what is ...

Nah, I can't get the dump for the 64bit exe to upload. The zip file is about 40meg and sourceforge keeps barfing before the upload completes.bob_down

One more try

[Attachment was removed! File name: FreeFileSync_x64.7z (40423436 bytes)]

Yes, Process *Explorer*. A full dump is better of course, ideally a few ones (this is monte-carlo debugging...)Zenju

Nah, I can't get the dump for the 64bit exe to upload. The zip file is about 40meg and sourceforge keeps barfing before the upload completes.

Yes, Process *Explorer*. A full dump is better of course, ideally a few ones (this is monte-carlo debugging...)
FFS seems to be bogging down on every run now, Windows 10 keeps offering to close the program. I assume you wanted a dump of both exes? It's not easy uploading such large files ...

Yes, Process *Explorer*. A full dump is better of course, ideally a few ones (this is monte-carlo debugging...)
It wouldn't let me. when I tried to save a dump with Process Explorer it complained about something and refused (permissions I believe). I'll try to make a note of the error next time ...

I thought the remote machine may have been part of the issue, but I am now syncing with a different PC entirely and the issues persist.

I was referring to "Process Explorer", not "Process Monitor". (However having a pml file for analysis never hurts...)
You mean this then? https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

Forgive my confusion, but you actually asked for Process Monitor. :)

If the answer is yes, do ...

By "dump", do you mean File -> Save?

[Attachment was removed! File name: Logfile.7z (10974969 bytes)]

For the record: a workaround for this issue is to disable the TimeBroker service via the registry (sevices.msc GUI does not allow to set this service to disabled).
Having very similar issues, since updating from Win 8.1 to Win 10. I have FFS running in batch mode at a scheduled time. Around half ...