Announcement

Collapse
No announcement yet.

PHP's Git Server Compromised, Now Switching To GitHub

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #61
    Originally posted by skeevy420 View Post

    I've tried the GPE method but it seems to reset itself between Insider build updates; twice now. Haven't tried the Regedit method so hopefully that one sticks. Thanks.
    Yeah, what Birdie said, turn off automatic driver updates. Opt out from Windows Insider if it keeps causing problems.
    Also, download dozen different drivers from widely different year/month (Guru3D is good source, allowing downloading far older driver packages than you can get from AMD's own site),

    Unpack them exes with 7z and uninstall official current one along with its additional crap (Radeon ReLive and whatnot).
    Use driver cleaning utilities if need be. Then install and test bunch of downloaded/unpacked drivers one-by-one using 3dmark or equivalent. Install through Windows Device Manager by selecting relevant graphic driver .inf file manually.
    Said .inf files contain driver installation routines and thus you install bare minimum of software to get GPU going with 3D accel. support.

    If you need screenshots, fan profiles - you can use MSI Afterburner. You need streaming/video clipping? - install OBS Studio - its FOSS. You dont really need that bloated extra software AMD wraps around their drivers.

    Since your GPU is older, test lots of drivers, often you get better perf with namely older drivers, newer ones are mostly optimized for newer cards. My Vega 64 has been rock solid this way.
    My 2 cents.
    Last edited by aht0; 31 March 2021, 04:21 PM.

    Comment


    • #62
      I'm using HP official AMD drivers (2020) on a laptop (A4 9210 core) and they are far better than AMD's official release, which is far and away better than MS's option. I also used WPD to strip out EVERYTHING telemetric (which in W10, is everything). No updates for that machine, except from WSUSOffline.
      Last edited by stiiixy; 31 March 2021, 09:50 PM.
      Hi

      Comment


      • #63
        What does this late conversation have to do with PHP? o-o

        Comment


        • #64
          Since when are people interested in sticking to the subject? It was derailed in the first comment, and lasted several dozen comments.
          Hi

          Comment


          • #65
            Originally posted by tildearrow View Post
            What does this late conversation have to do with PHP? o-o
            It's more into topic than Amazon workers pissing into bottles not that many pages back. At least it was about computers.

            Comment


            • #66
              Originally posted by aht0 View Post

              Yeah, what Birdie said, turn off automatic driver updates. Opt out from Windows Insider if it keeps causing problems.
              Also, download dozen different drivers from widely different year/month (Guru3D is good source, allowing downloading far older driver packages than you can get from AMD's own site),

              Unpack them exes with 7z and uninstall official current one along with its additional crap (Radeon ReLive and whatnot).
              Use driver cleaning utilities if need be. Then install and test bunch of downloaded/unpacked drivers one-by-one using 3dmark or equivalent. Install through Windows Device Manager by selecting relevant graphic driver .inf file manually.
              Said .inf files contain driver installation routines and thus you install bare minimum of software to get GPU going with 3D accel. support.

              If you need screenshots, fan profiles - you can use MSI Afterburner. You need streaming/video clipping? - install OBS Studio - its FOSS. You dont really need that bloated extra software AMD wraps around their drivers.

              Since your GPU is older, test lots of drivers, often you get better perf with namely older drivers, newer ones are mostly optimized for newer cards. My Vega 64 has been rock solid this way.
              My 2 cents.
              It's mainly an issue when I enable my iGPU when I'm doing VM stuff on Linux and forget to switch UEFI profiles when booting back into Windows to play a game. Windows detects the new or removed hardware and installs the appropriate MS provided driver. Nothing I can do about that. That's how Windows is.

              It just so happens that my dGPU and iGPU use the same driver which doesn't seem to be a very commonly tested configuration. Most people, I assume, aren't using both an AMD iGPU and dGPU together so when they turn the iGPU on and off it's just the Intel driver installing which doesn't effect an AMD or Nvidia dGPU at all...or they're using AMD iGPU and Nvidia dGPU which, again, have no effect on each other. When they're both the from the same manufacturer the new hardware configuration tool will change the driver even though you have it setup to not do that for what I assume will be obvious reasons to fellow geeks now that I've described it in better detail.

              Insider...that's just a one-time thing once a week or two whenever the builds advance. Annoying, but predictable. I'm leaving Insider once AutoHDR gets moved over to Windows stable. It's actually pretty nice; especially once I switched to Game Mode for my TV's picture setting and calibrated that -- it has the least amount of TV post processing effects and was the only setting where reds, pinks, and oranges weren't bleeding and overwhelming.

              Comment

              Working...
              X