"Yeth, Mathter!"
As previously mentioned, I've been fighting a memory error problem for some time that at first looked like a bad RAM module. babylon5 has run perfectly stably for about eight years with 3x 256MB DDR333 RAM modules, but with the three 1GB DDR333 modules I was recently given, it developed severe stability issues, including gcc internal compiler errors (gcc works memory subsystems very hard, and is an excellent canary for memory problems), kernel "oopses", and even kernel panics. Any two of the modules would work together fine in any two slots, but add the third module, and things went to hell.
After scratching my head over this for some time, I did some calculations and came up with a working theory. Although in theory my existing 420W power supply should be adequate for the load, I came to suspect that (a) being a cheap, no-name power supply, it was not actually delivering its full rated 420W output, and (b) as a result, it was allowing the 3.3v rail to sag when the system was under heavy load and demanding peak power.
Well, I didn't have a spare power supply, so I bought one, a normally-$70 650W power supply from NewEgg on sale for $40 after rebates. I swapped the new power supply in last night, and after first making sure everything worked properly with 2GB RAM and the new supply, added the third RAM module back in. babylon5 is now most of the way through recompiling BRL-CAD (again ... I've been having trouble with it), and gcc hasn't so much as hiccupped, although system load factor has climbed into double digits with up to 13 gcc processes running at a time.
So, it looks as though my theory of insufficient power on the 3.3v rail was correct, and the problem is now solved.
(The other good news, of course, is that I now have a spare power supply. The bad news is that it appears to be putting out about 350W, about 17% below its rated output, at best...)