🚀 go-pugleaf

Perhaps someone recognizes this problem.  My BC compile, which used to work
just dandy, now randomly crashes with "FATAL ERROR:  GP fault" or somesuch
similar message.  Not always on the same file, and not necessarily occurring
at all, although it pretty regularly comes up at least once every batch.  
Once it even went as far as dumping all my registers to the screen and 
telling me "Press [T] to terminate, but you should reboot as soon as possible
as the system has become unstable..."  I liked that one.  Not.

Here's a quick chronology of what's changed:

Original - 386/40, 8meg ram (100ns), BC 2.0   Works fine.

1)  Changed to a 486 (re: problem calculating logs, for those that remember
			THAT post).  Brought the SIMMs and hard drives over 
			from the 386.  Ok.
	Start to see lots of "GP errors".  These crash BC (note, 2.0) 
	completely, hanging most of my memory and requiring a reboot.
	ADVICE FROM BORLAND:  Oh, 2.0 is too old, get 3.1.

2) Got 3.1.  Can't even install the damn thing.  ZIPs are intermittently 
	corrupted.  Little examination shows that, with cache memory off,
	I have no problem unzipping, with it on, sometimes they get CRC
	errors.  Suggestion from my tech:  100ns memory is probably too 
	slow for the new machine.  Get some 70ns SIMMs and try it.
   Interim solution:  Running w/ cache turned off.  Problem not occurring.

3) Got 70ns SIMMs.  Same problem as before.  If anything, now more rampant
	than before.  

4) Changed motherboards.  Problem persists.

Now, I realize that I can't relay all important information about my system 
in this post.  I'm just hoping that maybe someone recognizes this problem and
can point me in the right direction.  Borland offers little help, even calling
their wonderful 900 number gets me a customer service robot who tells me 
(note, every time I call he tells me this):  Set up a virgin boot, kill your
config sys and your autoexec, go into borland directory slash bin, run 
dpmi inst, you'll get a message saying machine is in the database, it should
work, if not please send us the offending file.  I keep telling them that 
it's not necessarily the same file every time.  At least one of their guys
didn't even believe me when I said "Did that.  Still happens."

Can anybody help with this problem?  Please email responses, as my newsfeed
has been flakey lately and I'd like to get the information as quickly as 
possible.  Thank you.

Thanks in advance,
 Duane Morin
 Software Development Manager
 Walker Sonix, Inc
 Worcester, MA 01604