OCing not working...

[Gamingphreek]

Yeah i have had my A7N8X-E Deluxe for a while and it is rock solid. However i kind of wanted to push my CPU to around 2.3 (AXP 2500+ NOT MOBILE) so i went about OCing. however when i set the FSB memory speed to 1mhz over 200 it immediately underclocks my processor to 1100mhz, basically it sets my FSB RAM speed to 100!! Then i fi put my multiplier .5x over IIRC 11 it automatically underclocks.

Also if i try to run at 3200+ speeds i can never boot into windows i always get the same stop error, except wheni pump 1.85v into it in which case it boots into windows the auto restarts while flashing a blue screen.

There seems to be something wrong here. is this a known problem with the Asus boards? I have heard of rumors of a "super" bios that is unnoficial but fixes some of this!?

I should say though that i am running DDR333 Kingston Value RAM and i have the VDIMM set up to 2.8, even though it passes memtest for 24 (that is when i said all right enough i want my computer back, it didn't fail) hours @ 2.7.

-Kevin

 

[JBT]

You are talking about the Uber bios which doesn't fix those problems really it only give you a few more voltage options and a sometimes a tad better performance along with newer a newer SATA BIOS. Also you must have a Barton with locked mulitpliers so you are limited to the FSB. do not change the mulit's at all or you will always 1100 mhz or close to that.

 

[Gamingphreek]

My barton does not have the locked multipliers... i assure you. I got it much earlier than what you're thinking. Where cani get this uber BIOS and who makes it?

What about my OCing though i would like to experiment with it but i would still like to know whats wrong.

-Kevin

 

[Gamingphreek]

Bump

 

[DAPUNISHER]

I haven't used that board but it sounds like it's booting into a BIOS safe mode due to unstable overclock settings, my SN45G does that. It'll set the lowest fail safe settings after a failed overclock attempt to protect the bios from the corruption problems early revisions of the nF2 suffered from.

Now, the overclock issues you are having sound like just a setting mistake or 2 so here are a couple of things to help you determine if that's the case. Set the system to expert, the ram to 133mhz to start, that way as you boost the fsb speed you don't immediately push your ram out of spec and start limiting the overclock due to it's being unstable. Set the vdd chipset voltage to it's highest available setting *provided you have access to it, you may need the UBER bios to get at it* and set the timings manually to the defaults for everything but the (T)RAS which I recommend to set at 10 or 11. Those settings along with the Vcore and vDIMM boosts should get you going.

EDIT: as an alternative to lowering the ram speed you can just use the multiplier to overclock since you have an older Barton that allows multi manipulation. That way you can set the ram to 100% and keep 333DDR synch mode and avoid the latency penalty that causes a performance hit when nF2 is run asynch.

 

[Gamingphreek]

Alright ill do that.. but where do i get this uber BIOS.

-Kevin

 

[DAPUNISHER]

Post up in the nForcersHQ.com Asus forum and someone will turn you on to the best overclocking bios

 

[Gamingphreek]

Ok well i got the bios i am running the BIOS revision 1011 Uber with the new SATA bios.. not that im using the SATA at all... yet .

I will try to OC shortly. I have never had the option to use chipset voltage. What should i do with that should i increase that 1 notch.

-Kevin

 

[DAPUNISHER]

As long as you have good case and chipset cooling you can crank it to max voltage. If you decide to stay synch with your ram, which is probably best, you can skip it all together since you won't be pushing a high fsb that might need the greater fault tolerance.

 

[Gamingphreek]

So as long as i stay synced i do not need to up my chipset voltage or did i misinterpret the post.

Also, should i up my VDIMM to 2.9 even though it passed 24 hours of memtest at 2.8?

-Kevin

 

[DAPUNISHER]

You have it right, if running 333DDR synch you can leave the vdd default. I'd leave the ram@lower voltage if stable, and it seems it is, since extra heat and voltage are definitely not desirables and should only be used when necessary.