Discussion in 'Videocards - AMD Radeon Drivers Section' started by MerolaC, Apr 8, 2021.
If you have trouble following those instructions, stick with regular stable drivers.
but I really want to try it. And I want help. And there's really no detailed explanation
Even if you WANT to try it, you are probably not qualified enough.
These are test drivers for a reason.
There is so many ways to completely f*ck up Windows, meaning if you aren't sure or don't know what to do. DO NOT DO IT!
Otherwise you may spend good day fixing stuff you broke in 5 minutes (which i had been done few times already. And i do know what i am doing most of the times!)
Why are you trying to discourage me instead of teaching?
Where do I say to upload anything?
And, what it's so hard to follow that you don't understand?
I right click on the inf file and there is no install.
I go to the uwp pair folder and click on the inf file there, only open with appears, I can't run it like an exe file
You aren't going to break windows with a UWP driver. Even if it failed it's a simple process to remove the driver with the DDU or Amdclean software. Goal here is to help people not to discourage.
damn so good for mine 6600 with hags on
Are you on Windows 11?
Did you click the "Show more Options" in the context menu?
There you should see the install option.
U0391400.inf and uwppair.inf
I'm just going to install these inf files right?
Yes, just like it's said in the how to.
right click U0391400.inf click install ( may be in show more options if on windows 11 )
do the same with uwppair.inf
wish you would explain in more detail as I said, I think it would be more descriptive because there are more than one inf file. and thank you
In the root folder, there is only one INF file.
Same in UWPair folder.
In the whole package, there is only 3 in total
And the main one is in the root folder.
You can break Windows with crap ton of different ways. Especially if person doesn't know what he is doing.
Sorry for disappointing. I witnessed how much jank there is in Windows myself spending hours troubleshooting.
At this point problem lies not in helping by itself. But in troubleshooting his issues if something goes wrong for some reason.
Performance with preview driver feels good in my DX11 and DX12 titles with HAGS enabled on my 6900XT on Windows 11 22H2. However, I am noticing a weird bug HAGS enabled or disabled where the memory clock occasionally reports 0 mhz in GPU-Z, Hwinfo64, and Adrenalin panel. While its showing 0 mhz in those programs, alt+tabbing back into games will freeze the PC for roughly 10 seconds and then resume like normal and begin reporting the memory clock correctly again until this all randomly happens again. I noticed it occurs when the computers current workload is not stressing the GPU. I could play an intensive game in main focus exclusively for hours and it doesn't happen but if I alt+tab for a few mins to let the GPU idle then alt+tab back into a intensive game it has a chance to happen.
Installed latest Chipsets, and my DX12 games no longer choke on themselves like before after awhile. \o/ Since 23.5.1 will be out any day now, I'll wait for those.
This is not because of HAGS or preview drivers (it happens for me since i bought 6750XT and drivers were about... 22.7.1). Memory is just EXTREMELY agressive in going into power down state. Except freezing after return in games lasts only about 2-3 seconds for me.
And yes. Memory just goes to 0 mHz and powers down. but for desktop GPU it sure have really obscure timings and conditions for happening.
what do i need to do to remove it completely clean?
I've had this issue occur on latest stable drivers as well, except the freezing only lasts 2-3 seconds like you said. With this preview driver the freezing can last anywhere from 10 seconds to up to a minute. Audio still works and all, it's just the system comes to a standstill. It's always linked to the memory clocks reporting 0 mhz. I've noticed that changing displays with Win Key+ P or resetting/reapplying the GPU tuning settings will fix the 0 mhz issue until it randomly appears again. I've also heard somewhere that disabling freesync to have the memory clocks run at max at all times might solve it but I don't like my card idling at 30-40w instead of 7-10w.