This is a real pig of a fault - with quite a few reasons
two favourites are ... a badly behaved program (you don't say which is being terminated or what's running at the time!!)
or faulty RAM - generally the high end of the stack
the prog tries to access ram which is either marked as free ... but won't release when asked - and so can't be accessed .... or the memory is physically faulty and so can't be accessed ...
progs for graphics, video and adobe acrobat are favourites ... but any that use a big chunk of ram (or if you have a few open at once)
start by testing your ram
http://www.memtest.org/
but then again it could be a number of other things as well