DisplayPort & Driver Issues – New Build with RTX 5080 + Ryzen 7900X3D

[whysel]

 

Hey everyone! I just finished building my new PC, and I’m running into a couple of issues.

First off, my DisplayPort connection is unstable — sometimes it works, sometimes it doesn’t. I’ve double-checked the cables and ports, but I’m not sure if it's a GPU or monitor issue.

Also worth mentioning: I’m half Chinese, and I bought my CPU and motherboard locally at a market. I’m fairly confident they’re not off-market or counterfeit though, because AMD Software recognizes my CPU, and everything seems to post and boot normally.

Now the bigger issue: my graphics driver keeps crashing whenever I launch games like Valorant, Enlisted, or even Minecraft. The games either freeze, crash, or just fail to launch altogether. I’ve reinstalled drivers multiple times and even tried DDU, but the problem persists.

I haven’t really taken anything apart since the initial build, and I’m fairly confident the GPU is seated properly.

My Specs:

• Motherboard: ASUS TUF B650-PLUS WIFI

• CPU: AMD Ryzen 9 7900X3D

• GPU: ASUS TUF RTX 5080

• RAM: 32GB G.SKILL DDR5

• PSU: ASUS Thor 1200W

• Cooler: Cooler Master ML360 Illusion AIO

• Case Fans: 6x Thermaltake ARGB 140mm

• Storage:

  • 2TB Samsung 990 PRO NVMe SSD

  • 8TB Seagate HDD

Any ideas what might be going wrong? Is it a driver issue, hardware conflict, or maybe something BIOS-related?

Appreciate any help — thanks in advance!

[Agall]

20 minutes ago, whysel said:

Now the bigger issue: my graphics driver keeps crashing whenever I launch games like Valorant, Enlisted, or even Minecraft.

A lot of devs are recommending to revert to nvidia drivers back in December 2024 for RTX 5000 series. Some serious stability issues with the newest.

 

Also, you've got a PCIe 5.0 16x graphics card on a PCIe 5.0 capable CPU but a PCIe 4.0 16x only motherboard. Try setting the PCIe 16x slot version in the UEFI to 4.0 to eliminate that variable of a weird PCIe version negotiation issue upon c-state to p-state transition.

[whysel]

Hello!
I just wanted to thank you — it was probably the driver causing the issues. Mysteriously, all the Windows problems I’d been having have somehow stabilized as well. I’m not sure if the driver had something to do with that, but either way, thank you very much!

[Agall]

58 minutes ago, whysel said:

Hello!
I just wanted to thank you — it was probably the driver causing the issues. Mysteriously, all the Windows problems I’d been having have somehow stabilized as well. I’m not sure if the driver had something to do with that, but either way, thank you very much!

I think there's a combination of drivers, the Nvidia App forcing its features onto games, and potentially one or two settings that simply aren't stable to use. Just last night, I had to turn off frame generation in Diablo 4 because it was reliably rebooting and BSODing my machine (with an nvidia driver tagged as the cause). Enabling DLSS without frame generation in that game makes it look awful, so FSR2 it is.

 

The only reason I bother with the technology is because at 4K, its basically free performance in most games, increasing the framerate by like 40-50% without any loss in visual quality (even staring at pixels). It depends on the game, but in most of them, that's the case. DLSS just has less ghosting issues on moving targets, so its generally what I prefer, unless it breaks the game.