RivaTuner 2.04 is on the way!

But Softpedia isn't responsible for the content they show or the updates they provide, they might just update the file and not the description, or stay obsolete as is. Plus it's really not the place you should look for things, why not look up everything where they're originally from?

 

Hi, with riva tuner 2.04 can we overclock now the mobile graphic card???

Right now with riva tuner 2.03 we can't overclock with last driver 16x.xx, I set the new fréquence and when i click on apply the value go back to origin.

I have a toshiba X200-20F

Thanks for your respons

 

@Jamie:

Don't take offense at Unwinder's not-so-gentle replies, he's just trying to help.

Re: unlocking/overlocking your noteboook GPU:

1) Most notebook GPU's are locked in the bios, meaning you cannot overlock using Rivatuner/drivers before you unlock the BIOS. I dunno which GPU you have in your notebook, but you can find for nVidia GPU's here:

http://home.tele2.es/jlgm/peng.html

2) You need modded nVidia drivers, for example from:

http://www.laptopvideo2go.com/forum/index.php?showforum=72

3) Then you can overlock using Rivatuner. I'm using v163.44 myself and after the Bios flash can overlock this with Rivatuner.

 

Your reactions are quite strong to say the least. When I first came to the forum, I said "great program" (which it is, good job on that!) and had a simple Q. Before I asked the Q, I read the FAQ on the forum, so I just didn't ask the Q without 1st seeing if they answer was in the FAQ here.

Anyway, it appeared the info was in the documentation in the program itself - my bad I didn't see that.

But the way you wrote/reacted, locked threads, threatened with banning accounts, etc, thats why I said BOARD-*****. Mind: I'm not calling you a *****. You must have heard the term board-***** before.

http://www.urbandictionary.com/define.php?term=Board+*****

Look @ #2 and you know what I mean. But let's not get into this argument any further

And I'm not complaining here - I just gave Jamie some advice.

 

I wonder that myself too on the forums I visit to be honest.

I am 49 years old now..in the early days you learned to say THANK YOU when you got a cookie.
I am a PC race-gamer myself, and there are a lot of addons (FREE) ..sometimes you see guys shouting also bad names because an addon doesn't work the way they want.

I always say, those guys put a lot of work in it and its free...so calm down

Anyway, doing a great job keep up the good work !!!!

Seven_PRX is only trying to help, maybe only using some wrong words to express this in the beginning.

HAVE A NICE DAY ALL !!

hansje

 

Thanks for your answer my graphic card is a 8700 M GT 256Mo.

 

Well, this is a Forum where other people besides you can answer. So if you get tired of the same questions over and over, why not choose not to reply to those - chances are that somebody else will reply/give an answer.

No reason to get worked up over 'stupid' questions if you ask me.

Peace,

-7

 

Unwinder,

Preliminarily, the Shader ROP ratio seems to working admirably. Using 612mhz core on my 8800GTS, I've managed to push the working ratio up to 2.65. As this card isn't water cooled and the new drivers seem to be pushing the card much harder for the same clocks.

I was using 648mhz core with and upto 163.44, and suddenly its way too much, as the prediction you posted originally about a lot of overclockers having problems with these drivers. With even 626mhz core freq now, it is causing occasionally BSOD's in Bioshock or at the least sometimes driver restarting errors. This is all in Vista x64.

I know these errors are related to overclocking and perhaps even ratio of ROP to Shader, as they don't occur at lower clocks. I'll try to see if I can find ratio ranges where there are no intermittent BSOD's / display driver restarts, as perhaps there are some sweet spots for different cards. If you'd like me to spend a few hours mucking around with this, just shoot me a yes and I'll be happy to waste a few hours getting results.

Also on a side note, these BSOD's/driver resets aren't happening as a result of high chip temps, as the highest I have logged during a session of Bioshock maxed out is ~61-62c. And my avg idle temp is 48c @ 33c ambient and 51-52c @ 38c ambient. I have real trouble getting my card above 64-65c unless ambient is nearer to 50c.

Regards,

Michael

 

of course it's important that you try to discover your maximum shader speed *independently* of memory and core speed. In other words, keep your core and memory speeds down to normal frequencies and slowly bump up the ratio watching the rivatuner monitor for when the shader speed jumps up (in steps of 54 MHz). once you've determined the maximum shader speed (which is stable under load), then as a seperate step you need to work out what ratio to use to achieve this shader speed with your maximum (presumably previously determined) core speed.

I believe 1674 and 1728 are pretty common maximum usable shader speeds on GTS models (but I have seen people report higher).

with a core of 648 and 163.44 drivers, your shader would probably have been running at something like 1458 or 1512. with a shaderclockratio of 2.65 and 163.67 drivers, this would push the shader to 1728 (and I know my GTS certainly isn't stable at this speed). to drop the shader speed down to 1512, you would want a ratio of 1512/648=2.33 instead.

 

Sam,

My card is oc'd in bios for the most part, since I dont really need it running at ridiculous clocks all the time, 100% fan gets on your nerves real quick! Well 2.65 shader ratio seems comfortable at the moment, thats 612/1620/2016. My bios is flashed to 567/1404/1792, which is very comfortable for most things, and happily sits at 48-52c idle with 70% fan duty cycle. I might try adjusting the shaders up another clock or 2 in bios and see if its stable / trouble free.

Note, what I meant in my previous post was, see if i can find ranges of shader ratio where the card itself is happiest, much like there are when increasing FSB on chipsets, or anything really, sometimes chips have certain frequencies they prefer working together with, in this case the relationship would be shader to ROP, and perhaps ever DDR3 clocks.

 

No worries, and the answer is yes, works great even upto 2.76.

 

Unwinder,
Is it intentional that the ratio has to be a multiple of 0.05?
For example, if you were to set 2.42, in reality it's considered to be 2.40, while 2.43 is boosted to 2.45 to conform to the above.

Don't know this bit, whether it's a limitation in the hardware, the driver set or RivaTuner.

 

So if i set GPU to 692 and it jumps to 684, while setting GPU to 693 it jumps to 702 its normal? :smoke:
Its nice to experiment with Shaderclockration .. setting 2.5 and having GPU 702Mhz caused, white dots at end of deep freeze test, while setting 2.45 fixes it