The problem and possible resolution(s) are found in MSKB article Q148424. Having given you the official MS stance which takes the onus off of you, my suggestion is to look in code which does, or may do, strange things to memory block allocation.
When I had this problem it was finally tracked down to the fact that I was releasing the source object of a subform contained by an unbound main form. It took me a while to realize that MS, since my main form had no source object, assigned the source object of my sub form to the main form. When I released the source object everything crashed and burned around me. In this particular instance I assigned the main form a source object of a dummy table which allowed me to properly drop the source object of a sub form without any problems.
Robert Berman
Data Base consultant
Vulcan Software Services
thornmastr@yahoo.com