Madshrimps Forum Madness

Madshrimps Forum Madness (https://www.madshrimps.be/vbulletin/)

- WebNews (https://www.madshrimps.be/vbulletin/f22/)

- - Catalyst 3.8 (https://www.madshrimps.be/vbulletin/f22/catalyst-3-8-a-3248/)

Quote:

I used the Cat 3.8's and the Omega 3.8s for a short time after they were released to the public. I noticed a dramatic system temp increase. It went from around 28 degrees to 39 after half hour playing the call of duty demo. I wasn't satisfied with this, and as this was the ONLY reason for my temp increase I decided to roll-back to the Omega 3.7's. I did so and within half hour my temps were back to normal. Go figure. There is *definitely* something odd going on there.

http://www.xtremesystems.org/forums/...threadid=20906

uninstalled them.

don't know if it's true, but you never know.

Quote:

With Radeon 9800/9700's capable of syncing @ a refresh rate of 200 Hz, that means 99% of the world's monitors are at risk of damage.

So far, a total of 183 monitors, ranging from high-end 22" Viewsonic P225F's to lowly 14" Compaq SVGA monitors have been reported as dead/damaged due to this problem. It is to be taken seriously.

does that count for tft's alsow??

greetz

wrong refresh rates for TFT's is also bad, so I think yes

omfg crap .. I guess I'll go uninstall them now :( and reinstall when it's fixed or something .. Or would the Omega drivers fix this issue ?

the Omega drivers are based on the ATI ones and have the same core code.. so in short: don't use them either

i haven't noticed anything, probably the pelt is keeping things as they should, muy overclock rests at 470/760 or sth.

I ain't changing, I live on the wild side

you're just looking for an excuse to buy new hardware :grin:

@ MrC: don't care about the OC, better care about that monitor of yours, unless you want it to try do to the 9800Pro giving the wrong refresh rate config?

At driverheaven they have tested different catalyst driver versions.

http://www.driverheaven.net/showthre...pagenu mber=1

ATI drivers put to the test: temperatures exposed:
There has been an awful lot of talk lately about the Cat 3.8 set raising the temperatures of ATI hardware, to get some truth to the matter one of our board members Neon Cowboy has spent alot of time testing various drivers using a probe on the back of his 9800 PCB with the 3.7 set, the 3.8 set and the Omega 3.8.5 set based on the dell drivers.

Final Results

Room Temperature 25.9C

Omegas based on 3.8.5
GPU
Idle 47.1
Full Load 55.6

Memory*
Idle 40.9
Full Load 52.1

Official Cat. 3.8’s
Idle 40.9
Full Load 46.3

Memory*
Idle 40.9
Full Load 52.1

Official Cat. 3.7’s
Idle 41.5
Full Load 47.6

Memory*
Idle 40.9
Full Load 52.1

Summary

The drivers based on the dell 3.8.5 leaked betas were the hottest. Closely followed by the cat 3.7’s and finally the cat 3.8’s were the coolest. The results were surprising to me to say the least.

Update

After some suggestions I went back through and checked the memory temps. This time also with the memory nudged up to 350 MHz* from stock to appease the over-clockers here. I was also surprised to get the exact same readings in each driver.

I was right!
they're the coolest :D

who cares...? it's not the MAIN issue here, if by using the 3.8 drivers you fry your monitor, than it won't matter how hot your GPU gets...

Guru3D = copy of first link btw :)

Quote:

Originally posted by jmke
Guru3D = copy of first link btw :)

Can't find any excuse to justify why i did a repost ... but of course i can apologize by posting a pic :D

ATI's statement:

Quote:

RESPONSE TO ALLEGED MONITOR FAILURE ISSUE

We have spent a great deal of time trying to reproduce this problem and analyzing our driver code. There is nothing in our driver code that has changed since CAT 3.7 to CAT 3.8 that could possibly cause this behaviour. We believe that our drivers are not causing these alleged problems.

We do not currently believe these stories are valid. We have already confirmed that of the nearly 100 OEM customer programs have asked for and received this driver, we have received no reports on any such problem from the OEMs. We have also run comprehensive QA tests on the driver before releasing it and have had no cases of failed monitors.

Since we announced CATALYST 3.8 on October 8th, we have recorded hundreds of thousands of downloads, and thus far there have been absolutely no reports whatsoever to ATI's Customer Support department to report monitors failing.

RESPONSE TO ALLEGED HARDWARE OVERHEATING ISSUE

We have spent a great deal of time analyzing the temperatures due to the CATALYST 3.8 drivers. We do not under any circumstance see anything near a 10 degree Celsius increase in temperature (but we don't overclock our test cards either). We do see a slight increase in temperature in certain cases (3Dmark2003 Nature Scene for example). However any temperature increase is well within our safety range. Investigation continues and we are trying to determine why this change in temperature exits. At this point we are reproducing individual driver packages with code being checked in and measuring the temperature. However nothing shows the alleged increase in temperature. One independent website even tried to reproduce this issue, and found no measurable difference in temperature between CATALYST 3.7 and 3.8.

TECHNICAL REBUTTAL OF MONITOR FAILURE ALLEGATIONS

There have been many posts in the forums discussing this issue, it seems it is a common theory, picked up from one place and keep being circulated. One such theory suggests the following:

"Instead of reading the refresh rates from the PRIMARY display INF files, it is reading the SECONDARY display INF refresh rates."

In XP and 2K, we don't have access to monitor INF information in our driver component that manages display capability. We have never used this monitor information for any purpose. We rely on EDID data or user override information to determine monitor capability. Even though the OS may use the monitor information to expose high refresh rate based on monitor INF content, the driver always restricts the actual refresh rate going to the monitor based on EDID or the user override. In essence, the user may be able to select from OS controlled monitor page (in advanced property pages) a high refresh rate but internally driver will restrict the refresh rate going to the monitor based on EDID information or user override information. If user set the override information incorrectly then incompatible signals would be sent to the monitor.

In 9x, we can access monitor INF information but due to issues with how OS maps the INF to a monitor, we had disabled reading the monitor INF via registry. Unless someone deliberately changes the registry setting for this in 9x, they would not run into any monitor INF related issues.

so normally the prob would be "solved" ( even never existed ) because i don't whant my brand new tft to fry??

BTW this is the first ati card i have, what are some good tune programms?

greetz