Language Selection

English French German Italian Portuguese Spanish

Driver glitch limits overclocking of Nvidia's GeForce 7800 GTX chip

Filed under
Software

Modern hardware such as Nvidia's latest graphic chip generation support temperature monitoring features that automatically can decrease clock speed and even disable graphic cards when the chip gets too hot. This "software protection mode" however works in two directions.

The card is not only shut down when temperatures get too high, but also when they fall below a certain level. This is especially the case when GeForce 7800 GTX cards are prepared for overclocking with water or liquid nitrogen cooling systems.

Nvidia confirmed in an email to Tom's Hardware Guide that the graphic chip will switch into software protection mode when die temperatures reach a range of 30 to 35 degrees Celsius. "There is an issue with our thermal detection software that doesn't let you supercool the chip to run overclocking tests," Nvidia's Nick Stam said.

Nvidia did not provide more details on the glitch. Card manufacturers told us that effects of the activation of software protection mode can range from a decrease in clock speed or even a shutdown of the card. Usually, the card only slows down when temperatures climb above 115 degress Celsius. Typical operation temperatures are between 55 and 75 degrees, Stam said.

According to Nvidia, the issue is based solely on software and will be corrected with a new driver version that is scheduled to be available by mid-July. Until then, there is a "quick/dirty fix" available from XFX for users who need to solve the problem right away. "But the driver fix will be best route" to enable overclocking through extreme cooling devices, Nvidia said.

By D. Polkowski & W. Gruener
Tom's Hardware Guide

More in Tux Machines

today's leftovers

Leftovers: Gaming

Leftovers: KDE Software

  • Wayland & Other Tasks Being Worked On For KDE Plasma 5.4
    Now that KDE Plasma 5.3 was released this week, KDE developers are starting to plan out and work on the new material intended for KDE Plasma 5.4.
  • Interview with Wolthera
    My name is Wolthera, I am 25, studied Game Design and currently studying Humanities, because I want to become a better game designer, and I hope to make games in the future as a job. I also draw comics, though nothing has been published yet. [...] After I played a lot with MyPaint, I heard from people that Krita 2.4 was the shit. When I went to the website at the time (which is the one before the one before the current) it just looked alien and strange, and worse: there was no Windows version, so I couldn’t even try it out. So I spent a few more years having fun with MyPaint alone, but eventually I got tired of its brush engine and wanted to try something more rough. When I checked Krita again, it had two things: a new, considerably more coherent website (the one before this one) and a Windows build. Around that time it was still super unstable and it didn’t work with my tablet. But MyPaint also had tablet problems, so I had no qualms about dual booting to Linux and trying it out there.
  • GSoC with KDE
    So, my project is titled: Better Tooling for Baloo. Let me begin by explaining what Baloo is. According to its wiki page it is "Baloo is a metadata and search framework by KDE." What exactly does it mean? Baloo is responsible for providing full text search capabilities to KDE applications. It doesn't end there it also provides searching on basis of metadata of various types of files. To acomplish this it indexes file contents and metadata using various plugins ,called extractors, to handle different types of files. It then exposes the data it has indexed with the help of various API's. So thats a very high level view of how it works. Now, my project, as the title states will provide better tools for Baloo. These tools will mainly be: