• Nevrome@lemmy.ca
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    8 months ago

    I’m pretty sure it is.

    However, when using a DP cable, my GPU disables itself if the computer is left unattended for 20ish minutes. Moving the mouse, using the keyboard, turning the monitor on and off, nothing is displayed once it shuts down even if I hear music/apps/games running.

    Without changing any settings, using a HDMI cable solves that problem.

    I’m gaming at QHD/120fps so a HDMI cable is plenty for the task.

    • PenguinTD@lemmy.ca
      link
      fedilink
      arrow-up
      5
      ·
      8 months ago

      there seems to be a black screen driver bug or something for the windows sleep power management function that plague quite a bit spectrum of cards. In my case it’s not DP but when my GPU go sleep on older system, it just can’t wake up anymore.(both monitor, one DP one HDMI) that includes the shorter auto sleep mode when you lock the computer.

      My newer system doesn’t have that issue even with the same monitor/port. So it must be something like BIOS for MB/monitor/GPU and system all together that the protocol from say, windows and GPU is updated, but the MB or the monitor is not. Unfortunately, I can’t get any more newer BIOS for my old 4+ years AM4 MB nor for the 3+yo monitor. I simply disable the monitor sleep function and all is good, I just need to turn off monitor manually.

      • Nevrome@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        8 months ago

        Everything is up to date and monitor sleep is turned off.

        I’m starting to wonder if I give up on the 7700XT and go back to my 6600XT, it was sure as hell less troublesome.

    • SpikesOtherDog@ani.social
      link
      fedilink
      arrow-up
      2
      ·
      8 months ago

      Just curious, is it a Samsung monitor? My company had a run of monitors that all started acting up about three years after they were bought.

      Also, while I’m sure you have checked this, this sounds like a hardware problem. It might be fixed with drivers or firmware on either end.