Epox 4PCA3+ Voltage Heaven
 

I obtained an Epox 4PCA3+, and can't begin to tell you the results I'm getting. However, when I exceeed the the board's ability when Overclocking, pressing Insert and hitting Reset doesn't work with the Corsair memory. Clearing CMOS manually is useless, you have to remove the Corsair and replace with another brand? Very strange. I even tried removing the 512MB module, replacing with a 256MB stick of Corsair, clearing the CMOS, and re-starting to no avail? I've never experienced anything like this. I removed the Corsair, and relocated it to different DIMM's to no avail, and tried removing one stick, etc. But I was only able to re-boot after exchanging the Corsair for another memory. This did not happen with the OCZ. When I OC'd the OCZ (which by the way would not do 260MHz at 1:1 Ratio) I simply cleared CMOS as normal, and it worked. So it's not the battery either. I tried this severall times, because when I went to OC the Corsair at 300FSB and 5:4 Ratio, the same anomally occured. It may be a BIOS anomally untested because no one's pushing their systems? Doh I doubt it. The Corsair is excellent memory, it runs stable at high speed, and I love it, but this is crazy for Overclockers. Since we Overclocker's are often pushing our system's to the limit we often must clear BIOS values. Anyone ever experience this?

Anyway with the additional VDIMM Epox offers I was able to put a little Umph in my Corsair Twin-XMS4000 with some nice results. 1:1 Ratio, 266MHz @ 2.9VDIMM, it ran like butta :o

My 8RDA+ suports the insert on boot thingy.
Nice results, someone has way to much time to mess up expensive hardware over here.

Makes me wanna have a P4 (only for the onboard intel CSA gigabit)

I found out it does have the press and hold Insert key feature. It just wouldn't work with the Corsair, even exchaning the 512MB stick for a 256MB stick? Very odd. And very frustrating when overclocking, because everytime I exceed some parameter I have to remove the Corsair, clear CMOS, and replace with another brand, these steps are driving me crazy.

There have indeed been problems with corsair, certain winbond chips on the corsair caused the problem apparently, If I recall correctly

you could try a bios update
the newest versions can be found at the american epox site...