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

Leftovers: Gaming

Leftovers: Software

today's howtos

ACPI, kernels and contracts with firmware

This ends up being a pain in the neck in the x86 world, but it could be much worse. Way back in 2008 I wrote something about why the Linux kernel reports itself to firmware as "Windows" but refuses to identify itself as Linux. The short version is that "Linux" doesn't actually identify the behaviour of the kernel in a meaningful way. "Linux" doesn't tell you whether the kernel can deal with buffers being passed when the spec says it should be a package. "Linux" doesn't tell you whether the OS knows how to deal with an HPET. "Linux" doesn't tell you whether the OS can reinitialise graphics hardware. Read more