NotebookForums.com › Forums › NVIDIA ForceWare & NBF MobileForce Drivers › NBF MobileForce Drivers › Driver Quandry - 169.04 and 169.09
New Posts  All Forums:Forum Nav:

Driver Quandry - 169.04 and 169.09

post #1 of 8
3/4/08 at 9:47am
Thread Starter 
I figured I'd post this here, I know Fenuxx is tired of getting PMs from me .

This is my situation:

I recently purchased both the FX2500 and FX3500 GPU cards for my E1705. When they came in (the 2500 before the 3500), I installed them while using XP Pro. They were both refurbished/new cards.

Out of the box, I was able to install MobileForce 169.04 and ATI Tool to overclock. No flashing was needed. (Again, under XP Pro)

I've recently upgraded to Vista Ultimate 32-bit. I have everything running quite well with the latest updates, and reinstalled 169.04. But now, the cards clocks seem to be locked (the memory clock is locked, core can overclock).

I've tried ATI Tool .27b4 and RivaTuner 2.06. They both seem to crap out.

I haven't tried 169.09 yet, or NTune. But before I make that endeavor, what have you Vista users been using with success? which OC tool and which driver?
Reply
Reply
post #2 of 8
3/4/08 at 2:07pm
Like I told you in my PM to you (no, I'm not tired of getting PM's from you, lol) I use 169.04 in both Vista and XP, and have no issues with the modded/unlocked BIOS.

From what I've read, and from what others have said, you'll need to flash back to the stock BIOS in order to overclock with drivers post-169.04. I haven't personally confirmed this myself, so I don't know. But, if you run into a brick wall, this would be what I would suggest doing.
Reply
Reply
post #3 of 8
3/4/08 at 3:05pm
Thread Starter 
I thought it was a bit unusual for the cards to OC without flashing with XP, then a no go on Vista.

I think I'll first try 169.09 without flashing to see what happens with the new 2.07 RivaTuner. (the easiest route first)

If that fails, I'll know the cards' BIOS were previously flashed.

As far as overclocking with 169.09 vs. 169.04...I know with my flashed 7900GS OCing with 169.09 was definitely a no go.
Reply
Reply
post #4 of 8
3/4/08 at 7:32pm
Thread Starter 
I removed 169.04, installed 169.09 and RivaTuner 2.07. It works like a champ. GPU-Z reports the clocks I set...

The weird thing is I was able to OC w/169.04 and XP Pro evidently without a flashed card.

Going to play for a bit to see how it holds up.
Reply
Reply
post #5 of 8
3/6/08 at 5:12am
If you want to compare what is currently stored in the bios to another rom then you can easily find out in the command line with 'diff' in linux and 'fc' in windows. You can 'diff' or 'fc' the rom you dump from the card with both the unlocked and stock versions of your card's rom. Whichever command generates no output will tell you that the files are the same.

Anyway, yeah, none of this is well defined. If you use a driver and it does not let you overclock, then try to flash an alternative bios, be it "locked" or "unlocked". If that doesn't work then try a different driver. Rinse, wash, repeat. On a side note, I don't think 169.04 overclocks in linux either with an unlocked rom. This is a rare windows moment for me so I'd have to reboot to confirm.
Reply
Reply
post #6 of 8
3/6/08 at 8:50am
Thread Starter 
Thanks zz for the com line info...
Reply
Reply
post #7 of 8
3/8/08 at 2:35am
You know, probably be easier just to say stuff it and flash it for a permanent 3D overclock

Think that's what I'll do when a better driver is out, 620/690 is safe for me

*I stumped up for driver cleaner.net all the same
Reply
Reply
post #8 of 8
3/13/08 at 6:10am
Yeah, if you use the same clocks all the time then definitely I'd recommend the permanent flash. I don't really game anymore so I keep the stock 3d settings. Maybe its time for a few voltage modifications too.
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: NBF MobileForce Drivers
NotebookForums.com › Forums › NVIDIA ForceWare & NBF MobileForce Drivers › NBF MobileForce Drivers › Driver Quandry - 169.04 and 169.09