Sorry if you took the previous answer as sarcastic. I am a IT Manager/Sr. Network Administrator at an NT/2000-based ISP and am far away from stupid jokes. (Had worked in tech support when I was young, though, so I always start with easiest tips level...) Take no offense please.
Now back to the business:
I still believe the reason here lies in hardware. Corroded DIMM socket, for example. Might be poor electric contact. I will hardly believe in m/b screwed up, unless someone pressed REAL hard when installing memory in this bank before...
I must disagree with your point about Win2000 being buggy. It has proved itself _bulletproof_ for our business, and SP1 didn't worsen the server and desktops stability.
Further problem isolation steps I would suggest:
* Try inserting a single, say, 128MB chip instead of 2*64 to isolate RAM amount issues. (I'm sure it works. A Win2000 server works with 512MB for us, and that's 4*128MB chips);
* Examine the second memory socket (that oneyou have tried inserting your DIMM to) closely, to find traces of corrosion. Gold-plated pin DIMMs can cause corrosion when inserted in tin-covered sockets. E.g. Intel specifically warns against it! I myself have seen two computers with this problem. Must say the DIMMs inserted into such slots, usually have problems as early as during POST, reporting incorrect amount of total memory.
* Do you have more DIMM sockets than 2? Try inserting the second chip in 3rd or 4th socket to cut off the socket corrosion issues.
* Some BIOS (e.g. Award 6.0) allow to select memory settings (10ns, 8ns, Normal, Fast, Turbo) independently for each bank. Check if this is the case.
All said above is assuming you get Stop 0x50 right on W2k boot. If not, please notify so we can go further w/ideas.
P.S.
Please provide parameters of STOP 0x50... Are they always the same or differ with each stop?
