Simviation Forums

I replaced my Crosshair with a new Asus M3A32MVP Deluxe and they had me in mind when it came to overclocking.

BIOS has a Overclock Profile section that contains all of the parameters you need to OC.

I set the Auto OC to 5% which brought the CPU to 3.15G. That is about the max this chip will do and stay stable. Upped the memory voltage to 2.2v and made a 3DMark03 run.



That is about 200 points higher that the stock settings and Speedfan peaked ot 45 deg.

Will be interesting to see what they have to offer for this board next year.

Yeah you might be able to squeeze 3.2 out of it but thats about as high as that chip seems to want to go.

Had it at 3.2 on the other board but it required a voltage increase and popped over 60 deg running 3DMark06 plus it was not real stable there.

I have seen people in other forums say they had it higher than that but I never saw the proof.

Nick coached me for over 2 weeks and could not get it stable, but part of that might have been my memory at the time (Mushkin)

The new board has an 8/2 phase regulator as I recall

In any case.. the AI clocking system may not boost everything. It may also reduce memory sub timing in order to clock other factors up. It is easier to deal with and does not require much expereince but the fact of the matter is those auto systems usually pull back on areas you can not see in order to show you a big number an it be stable.

The best way to clock is to lock everything where it needs to be manually and I will bet that board is much more stable than the crosshair was

Unfortunately I am really tied up or I would download the manual and look it over. If I get time I will but I can not say if I can get to it before xmas

LOL.. I know..... But I excite easily.

I have not loaded FSX back on yet, but am curious to see how it runs.

Am going to give the 169.25 drivers a try. Was unsure if you finally said the 169.21s were not working properly.

LOL.. I know..... But I excite easily.

I have not loaded FSX back on yet, but am curious to see how it runs.

Am going to give the 169.25 drivers a try. Was unsure if you finally said the 169.21s were not working properly.

dont use th 21's

169.09 or 169.13 seem to be the ticket right now

the 25's resolve the missing resolutions but as of this point I have not tested them.

Here is where many go to read about beta drivers... http://forums.guru3d.com/forumdisplay.php?f=21

Even Nvidia and MS lurks in that forum. Look at the outrageous number of views for the threads about the 21 and 25 drivers.,.. tells you the threads are highly monitored.

Those kids install the latest as soon as it hits the net and usually days before it hits the nvidia servers