Two OC'ing Problems!

[fractalzero]

TOPIC NAME WAS MEANT TO SAY TWO OC'ING PROBLEMS!


I own an MSI K8N Sli Platinum motherboard, along with an Athlon 3200+ CPU and Nvidia 7600GT - I know it's outdated but it works and I'm fine with that.
I decided to do some overclocking and general tweaking. Downloded RivaTuner, anyway it wont let me clock the card but thats not the problem. I went into bios and FSB speed and put it up in multiples of five rebooting everytime. Default was 200, so I went 205 which was fine, 210, 215, fine. Put it to 220 and booted up. Wireless card couldn't connect to my network :/ Rebooted, still wouldn't connect. Went back into BIOS and put it back to 200. Connection worked fine.

Anyway for RivaTuner, I can put Memory clock up, but for Core clock I get a "The Driver failed to pass internal test" error, then I can't put the Memory clock up either.

Any help on this?

[slaveofconvention]

You may need to mess with the dividers in the BIOS to keep the network card working - when you push up the FSB you speed up everything - the CPU, RAM and the PCI slots too - those should be running at (I think) 66mhz - a 10% overclock (which your 220fsb is) will be forcing the PCI card to run at 72mhz. As for the graphics problems, I think you may just have hit the limit of the card - not everything is overclockable.

I am, not will I ever be, an expert in overclocking - so take this with a pinch of salt.... My main PC is overclocked from Quad 2.67 to 2.75 for no other reason than to push my memory score under vista from 5.8 to 5.9 - I wanted a clean sweep of 5.9's which I now have lol (well had before I went to 7 - I'm still on 5.9 under 7, but that's down to hard disk performance and not a lot I can do about that, otherwise it'd be 7.1)

[XcOM]

the PCI bus, SATA controller and PCI-express should NEVER be overclocked, cards don't like it, manufactures design there devices to work at a set speed, if you increase that speed the card's generally don't know what to do, and with Wireless you tend to push the card faster which in turn scrambles the frequency its running at (2.4GHz normally)

My system is a Q8400 2.66GHz OC'ed to 3.21GHz, i forgot to lock the SATA controller from the OC and it fried my raid and i had to rebuild it, after i locked the SATA bus it works fine and I've not had anymore R/W errors in smart

[Kayin]

TBH, I run PCI-E at 110 for certain benchmarks, but I know what I'm doing there too. It's not always (or normally) a good idea.

[LiTHiUM0XiD3]

pinmods r your friend... especially if you have a cheap motherboard

[Kayin]

Pinmods can do quite a bit.