UNSOLVED

AbsentGravity

updated

23 years ago

Closed

0

9036

April 3rd, 2004 20:00

geforce fx 5650 go/i8600 default clock speed

im using the new 56.72 driver, and was wondering about the 5650's default clock speed. when i use the auto detect function, i get 575/790 (3d) and 120/790 (2d). the default clock speeds, however, are 575/250 (3d) and 120/250 (2d). should i just leave it at default or will the increased memory clock frequency improve performance in games? and is it safe?
  • connorc04

    36 Posts

    691

    0

    Posted April 3rd, 2004 23:00

    I have a Inspiron 5150 and my FX Go5200 clock is supposta be 300/600 according to Nvidia and Dell in its wisdom clocked it at 196/392 because, according to other forum posts, due to thermal specifications, voltage, ect.  you can overclock your card, more than likely, but do this at your own risk.  i have read that mine is stable up to about 235/470.  the best advice seems to be to increase the frequencies by 5Mhz at a time and then test the settings using a benchmark like program (such as 3dmark03 or aquarmark) and see if you notice any video display problems and any overheating, the computer will likely halt and shutdown to prevent damage.  if you havnt already done so, you might want to download I8fanGUI to monitor CPUtemp, and GPU temp. Hope this helps.  someone post if i am incorrect on anything here.

    Inspiron 5150
    3.06GHz with HT
    Nvidia geForce FX Go5200 with 64MB using Nvidia 56.72 driver with moded INF
    60GB 7k60 HDD
    1GB DDR333 (two 512's)
    UXGA
    Windows XP Pro clean install with 3 partions
    Truemobile 1400 wireless
    24x10x24x CD-RW
    Running an External SoundBlaster Audigy 2 NX

  • HMKrieps

    713 Posts

    691

    0

    Posted April 4th, 2004 10:00

    I guess that on the Geforce 5200 you can get some more performance by overclocking, but on the Geforce fx5650 and on the ATI 9600PT you should leave the default clocks as both of the cards are throttled once the temperature reaches 100°C. So if you overclock them, they'll reach the throttling point faster but it will not gain any performance. 3dmark200x isn't good to test performance because the tests are rather short and between the tests, the GPU can cool down. Sso you don't measure the long term performance (10 minutes and more) with 2dmark.
  • 691

    0

    Posted April 4th, 2004 13:00

    The new 56.72 driver doesn't support the geforce FX Go5650.

    If you try to install it says that is has installed the driver and has to restart the system. After that nothing is changed, the old driver is still active.

  • connorc04

    36 Posts

    691

    0

    Posted April 4th, 2004 13:00

    you can make it support the driver by using a modifyed INF file from http://www.laptopvideo2go.com/ . Works like a charm.
  • warmonger

    179 Posts

    691

    0

    Posted April 4th, 2004 16:00

    Yeah they work fine on the 5650 just insalled myself,also they seem to have solved the standby issue with these drivers as well ,because my 8600 now resumes from standby with no problem...

    SPECS 8600 1.7, 128Nvidia 5650FxGo, 768MB 333DDR, 60 Gig Hd, 15.4 WSXGA+, 1300 Wireless, 4xDVDR+RW

  • ofelas

    649 Posts

    691

    0

    Posted April 4th, 2004 17:00

    i believe the default clock speeds of the FX Go5650 are 120/250 (2D) & 325/250 (3D)....NOT 575/xxx.....
  • 691

    0

    Posted April 5th, 2004 03:00

    Hey Conorc04, what's this "I8fanGUI" you mention?  I found a link via yahoo, but it's in like, german.
  • Ripper108

    370 Posts

    691

    0

    Posted April 5th, 2004 04:00



    @egon the Wrangler wrote:
    Hey Conorc04, what's this "I8fanGUI" you mention?  I found a link via yahoo, but it's in like, german.


    Try here
  • 691

    0

    Posted April 5th, 2004 19:00

    The auto-detect function seems to give bugus results if PowerMizer is enabled.  Try this:
    1) Edit the *.inf file in the driver directory, changing the PowerMizerEnable setting from 1 to 0.
    2) Re-install the driver
    3) Now try auto-detect and see if you get more sensible results.  I also use RivaTuner's hardware monitor page to watch the clock settings during the auto-detect cycle.  They should ramp up gradually.  With PowerMizer on, they just stay put, but the driver thinks they are changing.  This leads to the erroneous results.
    4) Note the auto-detect settings and set them as manually overclocked speeds.  Do some stress tests over temperature.
    5) If you want the PowerMizer feature, re-edit the *.inf file and reinstall (once you're satisfied with the clock speeds).

    The above procedure works very well on my fx go5200.  If you try it, let us know how it works.