I usually use WinSCP to "Keep remote directory up to date" and, also, I usually put Windows to hibernate at the end of the day, while WinSCP is still "Watching for changes in XX directories...". It doesn't transfer anything when Windows starts hibernate, it is idle.

Next day, when Windows wakes up, WinSCP 5.0.2 looks like nothing happened but actually it is not responding anymore.
The same happens when the Internet connection breaks (for any reason.)

On wake up, the previous versions detect the connection was interrupted, display a message box with the error message "Host does not exist" and three buttons including "Reconnect" and they try to reconnect after a couple of seconds.
This happens for 4.3.4 and also for 4.3.5. I cannot tell for sure for older versions but I cannot remember having this issue in the last year. Yes, it used to happen in the past and it was fixed.

I configured WinSCP to produce log files and these are the last lines from the log. The computer was hibernating between 14:34 and 14:37. It runs Windows 7 (+ SP1)

-------- 8< ----------------------------------------- >8 ---------
. 2011-09-22 14:34:15.678 Session upkeep
. 2011-09-22 14:34:15.678 Looking for network events
. 2011-09-22 14:34:15.678 Timeout waiting for network events
. 2011-09-22 14:34:16.193 Session upkeep
. 2011-09-22 14:34:16.193 Looking for network events
. 2011-09-22 14:34:16.193 Timeout waiting for network events
. 2011-09-22 14:34:16.738 Session upkeep
. 2011-09-22 14:34:16.738 Looking for network events
. 2011-09-22 14:34:16.738 Detected network event
. 2011-09-22 14:34:16.739 Enumerating network events for socket 796
. 2011-09-22 14:34:16.739 Enumerated 32 network events making 32 cumulative events for socket 796
. 2011-09-22 14:34:16.739 Handling network close event on socket 796 with error 10053
. 2011-09-22 14:34:16.739 Selecting events 0 for socket 796
. 2011-09-22 14:34:16.739 Network error: Software caused connection abort
* 2011-09-22 14:34:16.739 (ESshFatal) Network error: Software caused connection abort
. 2011-09-22 14:37:56.771 Looking up host "******.*********.com"
* 2011-09-22 14:37:56.821 (ESshFatal) Invalid access to memory
-------- 8< ----------------------------------------- >8 ---------


Thank you.

Every morning when I wake up my WinXP from 'hibernate', WinSCP shows an error "invalid memory access". Due to its new auto-retry feature, it loops into showing the error message again every 5 seconds (until I press the [OK] button). But even then WinSCP is not usable, as after reconnecting it shows an "external exception EEFFACE" error.
After closing WinSCP and restarting, everything works fine.

This problem occurs with WinSCP 4.2.4 (Build 610), which is the first 4.x version I installed. It did not occur with any of the many 3.x versions I used in the past years.

I usually connect to several HP-UX servers via SFTP-3 using the GUI.