Display Port Issues RX 7900 XT, Help?

[Geoff]

So I have been using this GPU since I built this PC back in February along with my LG UltraGear QHD 34-Inch 144hz monitor. For the display I'm using DisplayPort not HDMI.

In the back of my RX 7900 XT there's 4 ports, 1-HDMI and 3-DisplayPort. Just now my monitor went black and did not come back on. The monitor popped up with a message saying "No signal" and went to a black screen. I switched to another DisplayPort cable and the same problem.

I decided to use another DisplayPort in the back of the GPU and it works however the other 2 DP ports do not work and stays on a black screen. Furthermore what's weird is that I'm unable to change my monitor's refresh rate now.

I used to have it set on 144hz but now the option under (Advanced Display) in the settings is now gone and the refresh rate of my monitor is noticeably slower like it's on 30hz since changing to the only DP port in the back of the GPU that works.

Also I used to be able to use HDR, however the option in (HDR) settings is now gone and I cannot use HDR anymore it even says "HDR is not supported" like it has been removed, same with the refresh rate option. Any help would be awesome, might seem like the DP ports stopped working maybe?

Before coming here
1 - Switched to a different DP cable and didn't work
2 - I Unplugged my my GPU from the MoBo and plugged it back in and that didn't work
3 - re-installed AMD GPU drivers and that didn't work

EDIT - My sound is also gone. I'm using a headset but my headset is not giving sound nor is the option to select my headset there anymore. Driver problems maybe?

So I reset my CMOS and now my DP ports appear to be working however I still cannot change my refresh rate and I can't use HDR anymore nor do I have the option to use my headset for sound. I noticed my RX 7900 XT is not detected inside the Adrenalin Driver software now. It says I'm using AMD APU graphics.

[Julien, cut it out.]

Share your dxdiag log by the means of pastebin.

I recommend to update the bios from the motherboard manufacturer site and the chipsetdriver from the AMD site. Use DDU in Windows Safe mode and then do a fresh install of the GPU drivers.

[Geoff]

Julien, cut it out.님이 먼저 게시:

Share your dxdiag log by the means of pastebin.

I recommend to update the bios from the motherboard manufacturer site and the chipsetdriver from the AMD site. Use DDU in Windows Safe mode and then do a fresh install of the GPU drivers.

I'll see what I can do

[Geoff]

The (Display) portion says this "There is a problem with AMD Radeon RX 7900 XT device. For more information, search for 'graphics device driver error code 22' and that's it. Here is the pastebin

https://pastebin.com/Fegqcqb2

[emoticorpse]

After you reset bios/cmos did you ddu the gpu drivers?

[pasa]

the suggested search says code 22 is you disabled the device and shall use the 'enable' command there.

[Geoff]

pasa님이 먼저 게시:

the suggested search says code 22 is you disabled the device and shall use the 'enable' command there.

I turned it back on what's weird is I don't know what caused it to turn off in the first place though. Seems to be working so far now.

[C1REX]

Geoff님이 먼저 게시:

So I reset my CMOS and now my DP ports appear to be working however I still cannot change my refresh rate and I can't use HDR anymore nor do I have the option to use my headset for sound. I noticed my RX 7900 XT is not detected inside the Adrenalin Driver software now. It says I'm using AMD APU graphics.

Some Windows updates could mess up your drivers and override your AMD drivers with their own generic ones. Windows can do this. Check if reinstalling your Adrenaline+ drivers helps.

[Bad 💀 Motha]

WinOS + AMD GPUs = just asking for troubles.

At this point I see PC as... If must buy AMD GPU, then use Linux suited for Gaming.
If NVIDIA GPU you don't mind spending that money and really want NVIDIA, then use Win10/11

What also can cause problems in WinOS is having an AMD CPU that has an onboard AMD GPU, which many of those do have one now. Disable it. Otherwise WU is going to auto update that GPU driver and when using a dedicated AMD GPU, it's going to cause problems. The main issue being that if that is the case for you, both of your AMD GPUs are trying to share the same Adrenaline software. If I have say Ryzen 7xxx CPU w/ onboard Radeon GPU + dedicated NVIDIA GPU. I won't see that problem because everything I've configured is done so that everything uses my NVIDIA GPU. So WU can do whatever it wants with that onboard AMD GPU, it won't negatively affect me in any ways with regards to messing with my NVIDIA GPU or my apps/games.

[Crawl]

Bad 💀 Motha님이 먼저 게시:

WinOS + AMD GPUs = just asking for troubles.

At this point I see PC as... If must buy AMD GPU, then use Linux suited for Gaming.
If NVIDIA GPU you don't mind spending that money and really want NVIDIA, then use Win10/11

What also can cause problems in WinOS is having an AMD CPU that has an onboard AMD GPU, which many of those do have one now. Disable it. Otherwise WU is going to auto update that GPU driver and when using a dedicated AMD GPU, it's going to cause problems. The main issue being that if that is the case for you, both of your AMD GPUs are trying to share the same Adrenaline software. If I have say Ryzen 7xxx CPU w/ onboard Radeon GPU + dedicated NVIDIA GPU. I won't see that problem because everything I've configured is done so that everything uses my NVIDIA GPU. So WU can do whatever it wants with that onboard AMD GPU, it won't negatively affect me in any ways with regards to messing with my NVIDIA GPU or my apps/games.

All of this sounds like the same junk people repeat over and over but has no actual basis in reality. I have had both Adrenalin and Nvidia Experience installed on my pc since I built it. I run my main display on the 4090 and a secondary display on the igpu from the 7950X3D (7950X before that). I update both any time there is an update and I have never had the igpu try to "take over". I have never had to do any special configuration, it just works. If you want to disable your igpu go for it but it's definitely not necessary.

[Bad 💀 Motha]

For me its not a problem. The problem is trying to get uneducated users to do what's right and never use Win10/11 Home Edition. Use Pro so you can use Group Policy and actually have control over such things.

[Crawl]

Midnight Aurais님이 먼저 게시:

Crawl님이 먼저 게시:

All of this sounds like the same junk people repeat over and over but has no actual basis in reality. I have had both Adrenalin and Nvidia Experience installed on my pc since I built it. I run my main display on the 4090 and a secondary display on the igpu from the 7950X3D (7950X before that). I update both any time there is an update and I have never had the igpu try to "take over". I have never had to do any special configuration, it just works. If you want to disable your igpu go for it but it's definitely not necessary.

no thats not what he ment he ment amd chipset+amd videocard windows would try to keep the chipset up to date this seems to cause a issue were by it prioritzes the chipset adrenaline version over the manuel installed regardless if the manuel one is newer

The only all AMD system I've had recently is a laptop which has a 5980HX and 6800M, didn't have any issues there either.

[CaptObvious75]

Bad 💀 Motha님이 먼저 게시:

WinOS + AMD GPUs = just asking for troubles.

At this point I see PC as... If must buy AMD GPU, then use Linux suited for Gaming.
If NVIDIA GPU you don't mind spending that money and really want NVIDIA, then use Win10/11

What also can cause problems in WinOS is having an AMD CPU that has an onboard AMD GPU, which many of those do have one now. Disable it. Otherwise WU is going to auto update that GPU driver and when using a dedicated AMD GPU, it's going to cause problems. The main issue being that if that is the case for you, both of your AMD GPUs are trying to share the same Adrenaline software. If I have say Ryzen 7xxx CPU w/ onboard Radeon GPU + dedicated NVIDIA GPU. I won't see that problem because everything I've configured is done so that everything uses my NVIDIA GPU. So WU can do whatever it wants with that onboard AMD GPU, it won't negatively affect me in any ways with regards to messing with my NVIDIA GPU or my apps/games.

Ok relax. I have had two AMD GPUs back to back (6700xt and now a 7900xt day 1) and never had any issues. I also run a 7600x which has an iGPU and again, no issues. Lets not blow his out of proportion here.

[Bad 💀 Motha]

CaptObvious75님이 먼저 게시:

Bad 💀 Motha님이 먼저 게시:

WinOS + AMD GPUs = just asking for troubles.

At this point I see PC as... If must buy AMD GPU, then use Linux suited for Gaming.
If NVIDIA GPU you don't mind spending that money and really want NVIDIA, then use Win10/11

What also can cause problems in WinOS is having an AMD CPU that has an onboard AMD GPU, which many of those do have one now. Disable it. Otherwise WU is going to auto update that GPU driver and when using a dedicated AMD GPU, it's going to cause problems. The main issue being that if that is the case for you, both of your AMD GPUs are trying to share the same Adrenaline software. If I have say Ryzen 7xxx CPU w/ onboard Radeon GPU + dedicated NVIDIA GPU. I won't see that problem because everything I've configured is done so that everything uses my NVIDIA GPU. So WU can do whatever it wants with that onboard AMD GPU, it won't negatively affect me in any ways with regards to messing with my NVIDIA GPU or my apps/games.

Ok relax. I have had two AMD GPUs back to back (6700xt and now a 7900xt day 1) and never had any issues. I also run a 7600x which has an iGPU and again, no issues. Lets not blow his out of proportion here.

All I was saying was you'd probably get more out of your AMD hardware if you used Linux instead of WinOS

[Bad 💀 Motha]

Crawl님이 먼저 게시:

Bad 💀 Motha님이 먼저 게시:

WinOS + AMD GPUs = just asking for troubles.

At this point I see PC as... If must buy AMD GPU, then use Linux suited for Gaming.
If NVIDIA GPU you don't mind spending that money and really want NVIDIA, then use Win10/11

What also can cause problems in WinOS is having an AMD CPU that has an onboard AMD GPU, which many of those do have one now. Disable it. Otherwise WU is going to auto update that GPU driver and when using a dedicated AMD GPU, it's going to cause problems. The main issue being that if that is the case for you, both of your AMD GPUs are trying to share the same Adrenaline software. If I have say Ryzen 7xxx CPU w/ onboard Radeon GPU + dedicated NVIDIA GPU. I won't see that problem because everything I've configured is done so that everything uses my NVIDIA GPU. So WU can do whatever it wants with that onboard AMD GPU, it won't negatively affect me in any ways with regards to messing with my NVIDIA GPU or my apps/games.

All of this sounds like the same junk people repeat over and over but has no actual basis in reality. I have had both Adrenalin and Nvidia Experience installed on my pc since I built it. I run my main display on the 4090 and a secondary display on the igpu from the 7950X3D (7950X before that). I update both any time there is an update and I have never had the igpu try to "take over". I have never had to do any special configuration, it just works. If you want to disable your igpu go for it but it's definitely not necessary.

You don't seem to comprehend any thing I said in what you quoted me on. I never suggested the iGPU would take over. I said you CAN have problems when having both gpu being AMD also because Windows Updates likes to mess with the AMD drivers which is doesn't on NVIDIA. You shouldn't be constantly updating your GPU drivers. This is another problem people have where they seem to feel like they are wrapping themselves in a warm security blanket when updating to the latest drivers MS Windows Updates should never be touching your Drivers is my main point. That should always be up to the user to decide. Cause very often we see the latest device driver is not always the best, especially with regards to GPUs where they quickly push out drivers without in-depth testing. Overall the best practice is if you have a PC you wish to use WinOS on, always install Pro, never Home. That way you will have Group Policy with Pro and be able to turn off Windows Updates rules regarding driver updates. Something you can not do with Home Edition