Clocking a Q9000 on an M17x

I've managed to find a stable FSB constant - I've used 1260MHz... And I managed to see a performance at the CPU of around 2360MHz.

I've done research and found this forum info ( http://forum.notebookreview.com/alienware-m17x/392610-overclocking-q9000-m17x.html ) and this for my GPU:

http://forum.notebookreview.com/alienware/454278-safe-overclock-gtx-260m.html

Many people now wouldn't have our outdated CPUs so I am hoping someone can answer this for me (I dregged up as much info as I could find).

Why does the CPU monitor sometimes register 2360MHz and sometimes 1891MHz?

I'm using the nvidia CPU monitor (Performance Tools).

I've also failed to find a decent (non-crashing) clocking for the GPU (GeFroce GTX 260m).

It seems to not matter what I clock that too using the nvidia device settings - I always seem to get a crash.

Worse still... I can ONLY clock the Q9000 using the BIOS settings and NOT the nvidia settings - if I use nvidia (even to the exact same FSB rating) it will crash.

One thing I notice is the nvidia settings suggest a multiplier of 7.5x where the BIOS suggest a multiplier of 8.5x.

I'm a super noob at clocking - despite hours of research and fiddling... But I can't seem to work out these two issues.

I have searched - so I am sorry if I failed to turn up the exact info required.

Can someone who's had this experience help me out please

Cheers

 

For overclocking the GPU you could Try MSI afterburner. Thats what I used with my 460m and it worked great. Not sure if it will work with 260m's though.

 

The Ntools device settings allows me to clock the CPU or the GPU - but if I clock the CPU in Ntools my computer freezes. If I clock the CPU in BIOS it runs fine.

I have clocked the GPU in Ntools and it does work - but it doesn't seem to have any convincingly safe settings. In other words it appears to crash no matter what settings if I use Ntools!!!

I'd love to use Ntools - because there's more options and plus if it stuffs up, I don't need to remove the battery from the CMOS. Plus I can tune the comp up when needed and leave it stock standard otherwise.

Any suggestions there that have been tried and tested (especially on Ntools) and a Q9000?

I'll have a read about MSI afterburner later on...

 

The GPU is different from user to user. I got a crap card with my 460M as I couldn't clock it higher than 750/1500/3100.

It's all dependent on what your GPU will manage. stock 9800GT settings will probably happen though. I wouldn't see why that's not feasible.

 

I'm still puzzled though - why can I use the same settings my BIOS would have (set FSB at 1260) in Ntools yet my computer freezes. But if I do the setting in BIOS my computer is fine... Not sure I get it

And worse still, clocking my card is impossible at the same time the CPU is clocked - but if the CPU is unclocked I can clock the card (to some various possibilities).

I'm so confused!!

 

This is relevant to my interest

 

I believe your clocking issuses come from using the fsb to overclock. once you do that it makes everything else a little screwy. Before I got my qx9300 I overclocked my t9600 using the fsb and my graphics fans would run 100% all the time, not sure why, they just did. And while using the fsb to overclock, Nvidia's tools would just make the system lock up, not sure why either but I assume that once you increase the fsb it does it system wide and makes everything a little off.
So I ordered a qx9300 and now overclock just using the unlocked multipliers.
and I flashed my 280's to 285's and couldnt be happier.
I never could get the nvidia tools to work quite right until I upgraded my cpu, I can now overclock with nvidia tools, but I dont need to.
hope this helps

 

Thanks - but it helps in the worst possible way

I am going to keep trying... I am sure someone out there has done it successfully...

Could it be a possibility it's just the new drivers are a bit screwy?

Could I back date drivers perhaps?

EEEEEK.... Emergency...

Just after typing the above my computer locked up... I had to power off... When doing so the computer would NOT reboot... Oh dear, I have some serious issues!

Bios had RESET itself!!!

I can't recall the raid settings or anything... Now, the computer is screwed(ish) - I can hardly get this post typed - it's so slow!!! What the hell has happened?