Guess what?I got the *&% thing working!
Here is a lesson for all of you.
Even when technical support tells you its a hardware issue (not a BIOS issue), even when you ask the community for help (and they either ignore you or ridicule you), and even when you begin to doubt yourself - just persist!
In case any of you failed to follow my earlier postings, I purchased an EPoX EP-8NPA SLI to replace my Chaintech VNF3-250.
Why? Well, I wanted SATAII support, a PCI-E based video card, and gigabyte networking (and SLi support didn't hurt either). I diidn't want to give up my curent socket 754 processor ('cause its just that good).
To explain, I had an A64 4000+ mobile processor installed in the Chaintech MB running @ 2880 MHz (with Cool 'n Quiet disabled, processor voltage set to 1.4 or 1.45 v, multiplier set to 12X, and FSB set to 240 MHz).
Well, to make a long story shorter, what worked in the Chaintech MB refused to work in the EPoX MB. EPoX support claimed a hardware limitation prevented my use of the mobile processor. My own opinion leaned toward a BIOS limitation.
Well, what really went wrong?
I examined BIOS options (on the EP-8NPA) and came to focus on the limitations presented by the manner that processor voltage is selected (under BIOS). Epox choose to allow AUTO , plus (.25 or .5v), and a multitude of minus/undervolted values. No specific voltage selection is allowed (under the current BIOS).
Surprisingly enough, there is an easy work around!
Anyone remember CPUMSR?
I do. The program allows voltage and multiplier values to be set from within Windows. I originally used this utility to allow the use of Athlon XP-M (socket-A mobile) processors in motherboards that did support these processor in BIOS. Until Asrock released a beta BIOS supporting these processors, using this program was the only way I was able to get an XP-M working in my K7S8XE+ motherboard. Eventually, I was able to use a Barton-core processor @ 2500 MHz in my last Socket-A motherboard. Good stuff (and cheap too)!
Using CPUMSR to enable an A64 mobile is VERY similar to using the program within a Socket A mobile system.
First, it helps if you've got a desktop processor on hand (to make the initial BIOS adjustments). Personally, I installed a desktop 3000+ I had on hand. Then you boot he system and disable variable processor mutiplier adjustments (like Cool 'n Quiet) and set the processor multiplier at its lowest value (in this case 4X). Save and exit and you are ready to install the mobile processor. Do that and boot into Windows at this setting (in my case 800 MHz). Then, once you are logged into Windows just use CPUMSR to up the processor voltage and multiplier values.
This works fairly well (with one limitation). I got the processor to work at 1.4v, but CPUMSR (while it would show a 13X multiplier) would only adjust the speed of the processor to 2400 MHz (an obvious 12X multiplier).
However, sometimes we just luck out when experimenting. You see, when I used CPUMSR to change the processor voltage value in Windows the EPOX EP-8NPA rebooted at that voltage (weird, but I am NOT complaining). Then, it was a simple matter to adjust the processor multiplier (in BIOS) and move forward. First I tried the stock speed of 2600 MHz. The system ran stable and smooth. Then I lowered the processor multiplier to 12X with a FSB of 240 MHz (allowing me to continue to use my Cas2 DDR400 memory by setting the BIOS to DDR333). At this setting I was back at 2880MHz (on a cheap air cooling setup no less)!
This has been fun and I see no reason to stop here. Now I'll go on to install my watercooling block and a second video card. I see no reason that a 3GHz overclock should not be possible. Low-end cost and high-end performance. Gotta love it.
Oh, BTW - NONE of you (outside of the Comblock programmers behind CPUMSR) were of any help what-so-ever. The only support I got was from a post on Tom's Hardware (from an Aussie no less). Thanks guys! Really underwhelming!
Sincerely,
JRI
Facebook
Twitter