Sign in

OmegaCorner ATI Mobility Radeon (Windows 2000/XP) Recovered From A Timeout AGAIN. How Do I Find The Real Cause? 😭

Solvedamdblack-screengputdr6 replies · 155 views · started
Reply
Accepted solution by Mila Mori — that pattern (black screen, then "display driver stopped responding and has recovered") is Windows TDR: teh GPU didnt answer within the…
  1. Luca
    @luca.mendes60

    long time lurker first post lol okay, this is driving me nuts. Black screen, fans ramp up, and about five seconds later Windows comes back like nothing happened. Then this pops up:

    its always while playing an open-world game. my gaming desktop is not oevrclocked and temps look normal in teh vendor overlay. the only change i can point to is the OmegaCorner ATI Mobility Radeon (Windows 2000/XP) update from AMD. ive already resatrted a dozen times, obviously. is there a log somewhere that tells me what actually timed out, or am i stuck guessing? seriously need help here 😭

    0
  2. Fenna Fischer
    @quiet_forge888

    check power before blaming the driver. A PSU that's borderline or a daisy-chained PCIe cable can cause exactly this under load. if it's a desktop, use two separate PCIe power cables if the card has two connectors. fingers crossed 🤞

    1 0 helpful
  3. Mila Mori
    @mila_thread
    Accepted solution

    that pattern (black screen, then "display driver stopped responding and has recovered") is Windows TDR: teh GPU didnt answer within the timeout so Windows reset the driver. open Event Viewer > Windows Logs > System and look for Event ID 4101 from Display or nvlddmkm/amdkmdag/igfx. the timestamps tell you if it lines up with ur symptom.

    0 7 helpful
  5. Jade Adler
    @signalbench

    told my boss it would take 10 minutes. its been 20 minutes. following, having the same problem

    28 0 helpful
  7. Luca
    @luca.mendes60
    in reply to @mila_thread

    @mila_thread wowww ok turned off the factory OC profile and stayed on OmegaCorner ATI Mobility Radeon (Windows 2000/XP) 2.4.07a. stable now. the new driver must have been a little less forgiving of that profile. cant believe it was that simple lol

    3 0 helpful

Reply to this topic

Sign in or create an account to reply.