Aktív témák

• #3 e-biza őstag e-biza #1

  2003-10-18 21:42:36 #3

  Összes hozzászólása itt Válaszok az összes hozzászólására itt Válaszok erre a hozzászólásra

  Privát üzenet küldése

  

  e-biza

  őstag

  válasz e-biza #1 üzenetére

  Itt van angolul is :)
  
  While we're not quite sure what part of the Catalyst 3.8 drivers are causing this, some part of the driver (whether it's the new VPU Recovery feature, HyperZ Enhancements or the ATI Overclocking software) is causing the core on BBA and OEM Radeon cards that are identified as ''RADEON 9800 XT'', ''RADEON 9800 PRO'' and ''RADEON 9800'' in Windows to have their GPU's overheat by as much as 15*C over normal during 3D graphics sessions. This has caused a number of fans on the Radeon 9800 XT series to fail, allowing the heat to completely destroy the card.
  
  This news is especially important for individuals who performed the 9800 to 9800 Pro BIOS flash and did not include additional cooling on your card, as the GPU is already overclocked and producing more heat than normal.
  
  As a safety precaution, I am strongly encouraging that anyone with any of the affected cards above roll their drivers back to the Omega Catalyst 3.7 drivers or the ATI Catalyst 3.7 drivers, as they are verified not to cause this overheating issue.
  
  I did some testing with my Radeon 9800 NP BIOS-flashed to a 9800 Pro. The results are not encouraging.
  
  Running looping 3DMark2003 for 30 minutes and utilizing a temperature probe on my GPU (regular cooling), the following temperatures were recorded:
  
  Catalyst 3.8: 135 Fahrenheit
  Catalyst 3.7: 117 Fahrenheit
  The heatsink on my Sapphire Atlantis 9800 was so hot during the Catalyst 3.8 test that I burnt my hand when I accidently touched it.
  
  2) The Catalyst 3.8's seem to have a bug in some systems that allows the driver to process the SECONDARY adapter settings when a game is started and tries to switch to the resolution and refresh rate specified in the program.
  
  Normally, the card is limited by the INF file settings for the PRIMARY adapter, so that no resolution or refresh rate is attempted that is beyond the capability of the monitor hardware. But in the 3.8's, it seems to be processing the SECONDARY adapter settings first. In a system without a monitor plugged into the second adapter, there is no INF file limiting refresh rates and resolutions, so, the system is trying to force refresh rates and resolutions beyond what the monitor on the PRIMARY adapter is capable of.
  
  So instead of having the monitor ''flicker'' once when it switches to the desired resolution/refresh, monitors are ''flickering'' between 4 and 8 times, with resolutions and refresh rates that are beyond the capability of the actual monitor. As a result, some monitors have been damaged, while others have blinked out and recovered. Some users monitors are under warranty and can be RMA'd, but for those who don't have a monitor under warranty, their monitor is damaged and they must buy a new one.

  Liƒє is too short. - http://www.lowcostdomain.eu

Aktív témák