Asphodel wrote:

is there some sort of log which could help determine the source of the problem?

There is a log. I do not think it will help, but you may try to post it, in case you are able to reproduce this. If it is too large, mail it to me.

Usually I am doing nothing. I usually leave it open because I would transfer data as my data sets are updated. So usually it just sitting idle. I leave winscp connected overnight, it has crashed by morning

I agree that there might be a bug in the system. I think it is a conflict with nview (nvidia multiple desktop stuff) which could be causing the problem which I have mentioned in another thread.

is there some sort of log which could help determine the source of the problem?

Thanks

What are you doing before WinSCP starts running at 99%?

BTW, if you computer crashes, it is bug of the hardware or operating system. But an application can be an initiator, of course.

If I leave winscp open for a long time, it seems to make my computer crash. Winscp starts running at 99%, then if I close winscp, it still causes my computer to crash. Everything freezes. I am not sure what information what I can give you to determine if winscp is the problem. However, from everything I have done, I am pretty sure it is winscp.