ClasH
User
Junior Boarder
| Posts: 19 |   |
Karma: 0
|
Re:A temp bug or what??? - 2005/03/16 14:50
You dont have to put the core at 401 Mhz at all times and keep it there, what you can do is run coolbits and then you check the manual overclocking, set the core to 401Mhz in 2d and do the test, then you apply. Once that is done, just clock the no overclocking button and apply that again, now the temperature should dropp to a lower level.
You have to do this procedure everytime you start the computer...but it is worth it because the drivers are really fast, i noticed huge boosts on my brothers computer on some games.
One more thing is, that the bugg is not really a fault of the tempsensor, but the card actually does get a higher temperature....but nvidia are not concerned over this since it does not affect the full load temperature and their cards can handle up to over 80 degrees pretty well. Otherwise they would remove the drivers from the site etc.
I also found another funny bugg in 71.84, and that is...if you run coolbits2 and set the refreshrate in for example 1024*768 (the standard 3dmarktest resolution). This affected my fps in 3dmark03 and made my point dropp 1500points, when i then put the refreshrate override back to default i got these 1500points back (im not using vertical sync, its set to always off).
I was thinking that maybe this is an issue for 3dmark only, so i tried the stresstest for CS Source and found out that the fps is actually lower. With the refreshrate set to 85Hz we get an average fps in CS at 92.93fps. And with the refreshrate set to default we got and fps at 120.91fps.
Huuuuge difference, let me know if you try this and you see the same bugg, because then we should infact report this to nvidia 
|
TpuGPU-Z v0.2.9
