Announcement

Collapse
No announcement yet.

MTSTU410 troubles...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • MTSTU410 troubles...

    I used the utility to o/c, and I set it to 110%, pretty tame, but I wanted to make sure all was stable because I push my machine hard at times and have little patience with failures..
    The problem is, when I check the clock speed after I did the "Permanent" setting and of course rebooted, I now am clocked at:
    PLL: 330.75
    Gclk: 165.38
    Mclk: 165.38
    Wclk: 165.38
    This was checked with MGA Tweak..
    Why and how did my dividers get changed??
    I haven't had time to test this in 3D apps yet but so far in windows all is well...
    I've waited alittle while and either missed a post dealing with this or it hasn't happened to another lucky fellow..

    I'd appreciate any ideas as to a remedy...
    thanks
    Craig

    ------------------
    P3-700e cB0 @980Mhz - Watercooled, DangerDen waterblock, Enhiem 1046 pump, 8x6x2 HeaterCore Radiator - Asus P2b Rev. 1.10 /w MSI slocket - 128Mb PC100 - G400 DH 32b SGR - IBM 20Gb 75GXP HDD - InWin A500
    1.3 Taulatin @1600 - Watercooled, DangerDen waterblock, Enhiem 1046 pump, 8x6x2 HeaterCore Radiator - Asus TUSL2C - 256 MB Corsair PC150 - G400 DH 32b SGR - IBM 20Gb 75GXP HDD - InWin A500

  • #2
    A new build will get posted this week that will fix this along with the default readings for the G200 cards.

    Haig

    Comment


    • #3
      I'm kinda locked at Fo=345.60MHz, all other settings 172.80MHz at the moment, can't go any lower, but I can go higher

      Will the new version unlock the locked versions as well, Haig?

      Btw, I did test it at some 3D games, mostly driving sims and I do see a big difference with my P3-450. I guess it works

      Jord.

      Jordâ„¢

      Comment


      • #4
        Thanks Haig !!

        Apparently I was OC'ing at 131%, instead of 115%

        I now used MTSTU4.00.14 to clock back down to 115%, Fo=297.00 all other settings at 148.50MHz

        Although I did get a clocking error #2 the first time I tested the new clock setting. It works okay now !!

        Jord.
        Jordâ„¢

        Comment

        Working...
        X