Check this out. I've been slowly undoing just about every mod to my V5 in an effort to fix the problems mentioned above, and I've found a strange relationship. First of all, after extensive testing with GoldMem, I've found that the stock 32 meg SODIMM in the stock Iopener (Rise w/o any SW1/2 mods) shows bad bits all over the place! (That's IF it doesn't freeze hard before finishing the test)
The 128meg SODIMM from MemoryToGo never gets that far. It just freezes within a minute or two every time. This behavior didn't change much after dropping VCore to 2.0v and installing a K6III+ (It just checked the memory a little faster and then froze).
But, guess what happenned when I installed some DIPs and set FSB to 75mhz. It worked great (with the stock SODIMM or the 128) and showed no bad bits anywhere. I also tried the eighty-something Mhz FSB setting w/ 2.0 multiplier and had fine results too. (100 Mhz w/ 2.0 wouldn't boot unfortunately) I booted windows and ran some stress-tests (about 6 simultaneous MP3's in media player) and it hasn't crashed yet (5 hours).
So, my big questions are:
1.) How could the default IOP configuration be so unstable? It's been unrealiable ever since I got it, but I never figured out why until now. This isn't rhetorical, I'm really curious if others have had similar experiences. (I haven't read any)
2.) Is it normal to have components that support higher FSB's but not lower ones. (Shouldn't it be the other way around?)
3.) This is a dumb one. How will the BIOS report the CPU during POST? Mine says "-66mhz CPU" or something, regardless of my FSB. Is this normal?