All memory used when copying files from Truecrypt container

I'm in the process of moving data from a WD 3TB USB drive to a larger WD 5TB USB drive, so there is a LOT of data to move around.
While this is in all probability a Truecrypt (TC) issue, it doesn't hurt to ask anyway!
I have a quad core i7 pc with Win 7 Home and 16GB RAM, which is the limit for that OS.
When I copy or move files TO the encrypted container file FROM the main pc, all is well. I can move huge files no problem. Today for example I copied a 130 Gigabye file no problem. RAM sat at around 8GB used.
When I copy or move files FROM the encrypted container on the 3TB drive TO the pc, RAM usage climbs rapidly eventually consuming all system RAM, which slows the pc to almost being unresponsive. If I keep the size of the file being moved to around 5-8GB, I can stop the pc going as unresponsive but somewhat sluggish.
The problem is that I have a LOT of files to move.
This is a one-way issue (from encrypted source to unencrypted destination) and even Truecrypt's successor of Veracrypt is getting reports of the same issue. Other Truecrypt users have reported the same issue too. It looks to be a bug, but of course TC is defunct now.I tried Veracrypt and it suffered the same problem.


I disabled caching for C: but that just made copying VERY slow and the memory usage climbed to full as before albeit slowly.
The best "solution" I have so far is to mount the TC file as removable and shutdown all non essential running programs to conserve RAM and help stability.
There seems to be no shortage of people suffering from "full ram while copying" issues across different OS'es so maybe no answer is forthcoming...
I tried 3rd party copying apps but no solution there either.


Is there a way of limiting how much RAM can be used for caching?


Any ideas

Have you try to extend or give more space for the pagefile.
Pagefile is part of the RAM.

Virtual Memory Paging File - Change

I looked at it and increased it 50% as Windows suggested.
Made no difference...

Thanks.

I have however seen that thread and countless others. I do use cascading encryption, but the strange thing is that, as per my original description, this memory usage is strictly one way.
If cascading encryption was the cause then you'd reasonably expect it to cause problems when writing to the encrypted container too. Similarly for file caching etc etc.
It's another "too hard basket" one by the looks of it...

Ok.. try copying say a 40GB file and see what happens... a few GB are nothing for me too...