Can anyone explain why I, and others are seeing VolSnap errors on a regular basis?

The error stored in the Event Viewer reports as "The Flush & Hold operation for Volume C: was aborted because of low system memory".  In my case this only happens when no other hardware is accessing the unit, and it normally appears at around midnight according to the event viewer.  At that time of night the MSS is the only hardware running apart from the LAN/WAN broadband router which is also permanently on.

This error causes a 'Yellow" Network Health Warning on user desktops with a report that the 'Sys' drive is failing and requiring a repair followed by a restart - somewhat annoying to have to keep doing.  Servers are designed to run and run, not need "fixing" every few days.

I get these errors every three or four days and interestingly it appears that some users have reported the error as having stopped once they have applied a 2GB memory update to their MSS.

I have a few questions:

What is causing this recurring error?

Is the HP Update going to solve this problem?

Is there a fix already in existence? 

Is there a more fundamental issue with the MSS actually being "light" on memory in the real world of computer useage as against the designers perceived world?

My own system is an EX470 with a 500GB OEM drive and a 750GB Seagate drive, but it is always 'Sys' that reports the errors.  My current available capacity is 46% so the device is not being overfilled. 

 Any clues from the membership?