1. #1
    pssstif your monitor refresh rate was forced too high you would get a black screen on start up....all you would need to do is start up in safe mode and uninstall the drivers....[img]/i/smilies/16x16_smiley-wink.gif[/img]

    In any event the claims are incorrect from what I am told and my 21" Viewsonic is running great on them [img]/i/smilies/16x16_smiley-happy.gif[/img]

    =======================================
    Ubisoft IL2/Lock On Moderator
    ATI Catalyst Driver Beta Tester
    Hunter82 wrote:"I did not have technical relations with that question"
    Mudmovers </center>
    Catalyst Bug Reporting </center>
    =======================================
    Share this post

  2. #2
    acutally this has been confirmed by ATI and they suggest users rollback to 3.7.


    here is a quote from Nvnews:

    I was furnished with a link to this forum thread over at Short-Media. One of their moderators stated that the Catalyst 3.8 drivers are responsbile for damaging his Dell UltraScan P1110 21" monitor.

    It seems like the new driver series is attempting to pass way too many unsupported resolution/refresh rates to the monitor, overloading the monitor's relay system and frying the monitor. Instead of reading the refresh rates from the PRIMARY display INF files, it is reading the SECONDARY display INF refresh rates. For those of us with only 1 monitor hooked up, there is no SECONDARY display INF refresh rate file, to the video card starts at its own highest supported refresh rate and starts passing that onto the monitor. 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.

    I'll attest to this problem, as my Dell UltraScan P1110 21" Trinitron has been damaged due to this problem. Running the Catalyst 3.8's on my Corona system @ 1600x1200 @ 85 Hz and playing Unreal Tournament 2003, I exited the game and the monitor started flickering like mad, attempting to change refresh rates. After 8 unsuccessful retries, the monitor displayed the "NO VIDEO SIGNAL FROM INPUT 1" message and the power light turned orange. A burning smell was coming from the back of the monitor. Hooking the monitor up to another system proved useless, as it did not start up.



    Message Edited on 10/20/0312:39PM by LLv34_Jani
    Share this post

  3. #3
    Zayets's Avatar Senior Member
    Join Date
    Aug 2002
    Posts
    1,680
    Hunter must have the bug free version [img]/i/smilies/16x16_smiley-wink.gif[/img]
    Not like I care , I still love my Ti4600

    Zayets out

    Share this post

  4. #4
    no it hasn't been confirmed by ATI and nvnews is a Nvidia fanboy site...and cheesy one to boot [img]/i/smilies/16x16_smiley-wink.gif[/img] Also Dell's drivers are not 'ATI' releases per say.

    If it was conformed by ATI they would have pulled 3.8 from DL availability.... I'll try and get more official new from them later today.




    =======================================
    Ubisoft IL2/Lock On Moderator
    ATI Catalyst Driver Beta Tester
    Hunter82 wrote:"I did not have technical relations with that question"
    Mudmovers </center>
    Catalyst Bug Reporting </center>
    =======================================
    Share this post

  5. #5
    As I have said in an earlier post if the refresh rate was increased to 200 and your monitor could not support it you would get a garbled out of synch screen or black screen.

    For people to even post/make articles with non-sense on refresh rates higher than the monitor can accept is funny since it would not would not work on install at a value so high over the monitor limit. In any event all that would be needed is to start in safe mode and uninstall the driver if that had happened...

    No ruined monitors but probably alot of bruised egos after their screaming [img]/i/smilies/16x16_smiley-very-happy.gif[/img]

    As far as core and memory temps the 3.8's are equal to the 3.7 +/- a few degrees. Some drivers like Dell and Omega based on 3.9 cat beta's (leaked dell sets) are running hotter but that's not ATI's fault if you are using them and have problems...ATI does NOT release beta sets to the public and should not be used by the average user.

    =======================================
    Ubisoft IL2/Lock On Moderator
    ATI Catalyst Driver Beta Tester
    Hunter82 wrote:"I did not have technical relations with that question"
    Mudmovers </center>
    Catalyst Bug Reporting </center>
    =======================================
    Share this post

  6. #6
    I can confirm that drivers forcing a 200mhz refresh rate cannot possibly damage the hardware. Most monitors will give you a 'value out of range message - or simply not display or display at a lower rate anyway. I'd definitely question the credibility of a website that would post such a thing inasmuch as it shows tremendous ignorance. I suppose it might be possible to damage a monitor if there was some kind of short in the mainboard or video card that fed voltage back up through the vga cable - but I've never seen or heard of such a thing

    Share this post

  7. #7
    - Let me see. NVnews. NV as in NVidia? [img]/i/smilies/16x16_smiley-happy.gif[/img]

    If you bother to check all the major 3D sites you will see the warnings on all of them and YES it has been confirmed by ATI in an interview with ATI at www.guru3d.com.
    Share this post

  8. #8
    ATI SPEAK: CATALYST 3.8 - The TRUTH not the Rumours
    Posted on Monday, October 20, 2003
    at 7:24 PM by Zardon - View Article Comments


    Terry Makedon and Chris Hook from ATI have posted a reply to statements made recently regarding problems with Cat 3.8 overheating and all sorts of other claims, you can read and discuss in This thread

    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.

    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.

    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 (DriverHeaven.net) even tried to reproduce this issue, and found no measurable difference in temperature between CATALYST 3.7 and 3.8.

    =======================================
    Ubisoft IL2/Lock On Moderator
    ATI Catalyst Driver Beta Tester
    Hunter82 wrote:"I did not have technical relations with that question"
    Mudmovers </center>
    Catalyst Bug Reporting </center>
    =======================================
    Share this post

  9. #9
    Guru 3d is a great website if you're an Nvidia fan [img]/i/smilies/16x16_smiley-wink.gif[/img]



    BaldieJr wrote:
    - Oh well.
    -
    - http://www.guru3d.com/news.php#641
    -
    -
    - Thanks for the kind words Rogodin.


    =======================================
    Ubisoft IL2/Lock On Moderator
    ATI Catalyst Driver Beta Tester
    Hunter82 wrote:"I did not have technical relations with that question"
    Mudmovers </center>
    Catalyst Bug Reporting </center>
    =======================================
    Share this post

  10. #10
    it could be since the monitors are usually Dell that are supposedly blowing up

    =======================================
    Ubisoft IL2/Lock On Moderator
    ATI Catalyst Driver Beta Tester
    Hunter82 wrote:"I did not have technical relations with that question"
    Mudmovers </center>
    Catalyst Bug Reporting </center>
    =======================================
    Share this post