I'm glad you like Recent Files.  If anyone downloaded the 2.0.0.1 build you might want to get the new 2.0.0.2 build, since I actually had to fix a bug (file names with ampersands weren't being displayed correctly) -- choover3 found it.  Nice catch on finding it for him.

As for DS having problems with your scenes, most of my scenes eat far more memory than that and I don't have any problems at all.  And my main box is like yours Win 7 Ultimate and only has 12gigs of physical ram.  Different CPU and motherboard though.

Here's my advice: get some tools to monitor your computer and see what the problem is.  Personally I'd most likely use Process Explorer from the SysInternal team at Microsoft http://technet.microsoft.com/en-us/sysinternals/bb896653  And if that didn't leave me a clue I'd look into it more with their Process Monitor tool  http://technet.microsoft.com/en-us/sysinternals/bb896645

See what is really happening and you might be able to figure out exactly what the problem is. It's very likely there is something about your computer that is causing the issue.  It could be something you can fix.  Just assuming it's a memory issue is likely a wrong path.  When your computer does something, it happens for a reason.  Stalls aren't random.  And things can be monitored.  Then with that data you can work your way to a solution.  Or if not a solution you can understand the problem enough that you might be able to help the developers fix the problem.  And no it's not easy.  But you may be surprised at how much of it is under your control.

-Matt