Just as the title says I plugged in my new 7900xtx and now my pc wont turn on. Everything is plugged in properly, all I did was add an 8 pin cable for the new gpu and now the motherboard won't even give me an mobo led light up now.

I upgraded to an RX 9070 XT earlier today and I've had nothing but problems with the fans. I did a fresh install of drivers with DDU in safe mode and the card is completely ignoring any fan curve I set in AMD Adrenalin, MSI Afterburner, or Gigabyte's Control Center (the latter two I installed solely to try to fix this problem and uninstalled after they didn't help.)

The BIOS is set to silent mode and I've been running it with -30% power limit. The fans will sit at either 0rpm or 900rpm (20%), then somewhere between 45-50℃ they'll jump up to 100% with no in-between.

Has anyone else ran into this? I'm hesitant to consider returning the card since prices are all out of wack and I got a deal over £120 below current prices in my area for a new card.

I've been trying to get Optiscaler client to work with Cyberpunk 2077. I am using Optiscaler Client from Agustinm28. v1.0.6.1 and a 6750xt. When I auto install the scaler tool shows up fine in game but it defaults to Intel's resolution scaler and nowhere in the tool does it say FSR4. Just 3.1.

Am I missing something?

Hey everyone,

I'm dealing with a really frustrating performance issue in Valorant and could use some help figuring out the root cause. I'm getting constant screen tearing, and whenever it happens, the in-game performance graph shows a direct spike in CPU Wait GPU Time.

The weirdest part is the inconsistency. The game ran perfectly fine for a very long time. Then this issue randomly started, eventually went away on its own (I'm not even sure what fixed it—maybe a background update or a driver change?), but now it is back again and tearing constantly.

Here are my specs:

• CPU: AMD Ryzen 5 9600X
• GPU: AMD Radeon RX 9070
• Motherboard: Gigabyte B850
• RAM: [16x1 6000mhz expo enbaled]
• Monitor/Refresh Rate: [2k 180hz]

I went down a bit of a rabbit hole with DLSS 5.

I'm considering getting a couple of Radeon AI PRO R9700s for AI work because 32 GB per card is very attractive, and while looking at what I would be giving up on the gaming side I started digging into DLSS 5 Neural Rendering.

That eventually turned into getting it actually running on one of my old laptops.

The machine is nothing special:

RTX 2070 Max Q 8 GB
i7-10750H
32 GB DDR4
Linux + Proton

No ReShade.

I'm intercepting the NGX/D3D12 path with a proxy, keeping the game's original DLSS path intact, executing nvngx_dlssnr 310.8, and returning the neural rendered frame.

I'm posting a video comparison with and without the Neural Rendering pass so people can see the actual output rather than just traces or screenshots.

The interesting part came after I started looking at what the DLL was really executing.

From a single frame I extracted 176 CUBINs and traced 174 kernel launches. There are Swin and ViT style blocks, QKV projections, and a lot of kernels with names like fused_swin_*_fp8.

The model is clearly built heavily around FP8 E4M3.

And that explains a lot of what happens on Turing.

The RTX 2070 has Tensor Cores, but no native FP8 support. Looking at the SASS, the FP8 workload gets transformed into a much more complicated FP16 path with unpacking, extra matrix instructions, register pressure, spills and a lot of auxiliary work.

I found alternative non FP8 kernels in the binaries too. In one QKV case the FP8 path was roughly 11.9k static instructions with 368 bytes of stack per thread, while the non FP8 version was around 2.6k instructions and 8 bytes of stack.

I also isolated 16 QKVs of 3600x512x1536 and tested them directly on the 2070 Max Q.

Persistent FP16 weights took about 4.20 ms.

Converting E4M3 to FP16 before every GEMM took about 4.45 ms.

The 16 E4M3 conversions themselves took only about 0.33 ms.

The persistent and converted versions produced bit identical results in that test.

That was probably the most useful result, because it suggests that the problem on Turing isn't simply "FP8 has to be converted to FP16, therefore it is slow".

The conversion itself is cheap.

The expensive part appears to be everything the existing FP8 kernels have to do around that conversion when running on hardware that wasn't designed for native FP8.

And that is what made me start looking at RDNA4.

A 9070 XT is a completely different situation.

RDNA4 has native FP8 matrix support, including E4M3, which is exactly the format I'm finding in the DLSSNR workload.

Obviously you cannot take an NVIDIA CUBIN and execute it on a Radeon. CUDA is not going to magically run on AMD.

But that isn't really the interesting question anymore.

Once you know the model graph, weights, scales, tensor layouts and swizzles, the CUDA kernels are just one implementation of the math.

The heavy parts I'm seeing are things like QKV, projections, attention, Swin/ViT blocks and matrix multiplications.

There is nothing inherently "CUDA" about:

FP8 E4M3 matrix x FP8 E4M3 matrix -> accumulator

On RDNA4 that could be implemented against its native FP8 matrix hardware instead.

So instead of trying to make nvngx_dlssnr.dll execute its NVIDIA kernels on AMD, the more interesting approach would be:

DLSSNR weights / graph

- repack the existing E4M3 weights for RDNA4
- execute the heavy FP8 operations natively through HIP, rocWMMA or Vulkan
- reproduce the smaller normalization, attention, residual and layout operations
- feed the resulting neural frame back into the graphics pipeline

At that point you're not emulating CUDA.

You're just giving the same neural network another backend.

And because the current DLSSNR model already appears to be FP8 oriented, I don't think the idea of a 9070 XT ending up in roughly the same performance class as a 5070 for this particular neural pass is crazy at all.

It might even be a very good fit for RDNA4.

I'm not saying I have a 9070 XT benchmark. I don't.

But after getting this running on a 2070 Max Q and seeing what the kernels are actually doing, the limitation looks much more like a software/backend problem than a fundamental hardware problem.

The 174 launches also don't mean 174 completely unique kernels need to be rewritten. A lot of them appear to be repeated instances of a much smaller set of operations with different tensor sizes.

I'd be very interested to know if anyone with a 9070 XT/R9700 has already looked at the DLSSNR E4M3 weights, scales or swizzles, or played with similar FP8 transformer kernels on gfx1201.

Because after seeing this on Turing, RDNA4 suddenly looks like a very interesting target.

Hello everyone. I wanted to talk a little about something and wanted to see what people think. Bear with the wall of text please.

There's something about RDNA 4 that reminds me a lot of NVIDIA's Turing generation.

Right now most of the discussion around the RX 9000 series is about how the 9070 XT compares to the 5070 Ti, whether FSR 4 is finally good enough, and how AMD is doing in ray tracing. Those are all fair questions, but I think there's a bigger story here.

I've seen people compare RDNA 4 to NVIDIA's RTX 20/Turing generation, and at first I thought that was a bit of a stretch. But the more I think about it, the more the comparison makes sense.

When NVIDIA launched Turing, the first generation of RTX wasn't exactly a runaway success. Ray tracing was extremely demanding and early DLSS wasn't anything like the DLSS we're familiar with today. But Turing introduced something incredibly important which is the hardware foundation NVIDIA needed to build an entirely new rendering ecosystem around AI and ray tracing. The Tensor Cores gave NVIDIA the foundation for DLSS, while the RT Cores gave them dedicated hardware for ray tracing, and NVIDIA spent the following generations getting dramatically better at using that hardware.

I think RDNA 4 could represent a similar turning point for AMD. They already had AI accelerators with RDNA 3, so this isn't a perfect 1:1 comparison with Turing, but RDNA 4 significantly improves AMD's AI hardware and we're now seeing AMD build major gaming features around it.

The obvious example is FSR 4. Older FSR relied much more heavily on traditional shader-based techniques, while FSR 4 uses machine learning for image reconstruction. And that's what makes this interesting to me. FSR 4 is absolutely a starting point.

Think about where DLSS started compared to where NVIDIA has taken it since Turing. If AMD keeps improving its ML models and continues developing the hardware over the next few generations, RDNA 4 could become the foundation for much more than just better upscaling: better frame generation, better ray reconstruction, better image reconstruction, and potentially entirely new AI-assisted rendering techniques.

That's why I'm starting to think the "AMD's RTX 20 series moment" comparison isn't actually that crazy. The RX 9000 series might not necessarily be remembered as the generation that changed everything. It could be remembered as the generation that gave AMD the hardware foundation to start changing things.

Now obviously this is me just speculating and speaking to the wind, and AMD still has a lot to prove, but I'm curious what everyone else thinks.

Hi guys, you might have encountered this problem while playing Ghost Tsushima on pc. I found the solution thanks to a fellow redditor called "wildcat002".

All credits goes to wildcat002

PLEASE NOTE: I do not claim any credit for this fix. My intention is to simply to help fellow gamers who want to fix this annoying bug. I also want to add that I cannot be held responsible if this solution does not solve your problem. Proceed at your own risk and follow the steps carefully. Any small mistake could jeopardize the whole process.

This is the manual that I made myself for anyone to follow.

Step 1: DOWNLOAD DXVK (download the latest version)

Go to your browser and past this link: https://github.com/doitsujin/dxvk/releases/tag/v3.1

Step 1.1: Scroll down and click the dxvk-31.tar.gz link to DOWNLOAD the file.

Step 1.2: Once it downloads, right click > “Extract All” (if needed)

note: if you the file doesn’t appear instantly in the folder’s app, please go to the browser where you got your file and look it up on the download section

note: it might ask you where to open the .gz file. You should only open in the files application

Step 1.3: After this double click the file .gz > click the folder “dxvk-3.1“ > click the folder “x64” > check for the file called “dxgi.dll

Leave it for now and proceed to download another file from GITHUB

Step 2: DOWNLOAD vkd3d-proton (download the latest version

Go to your browser again and paste this link: https://github.com/HansKristian-Work/vkd3d-proton/releases/tag/v3.0.1

Step 2.1: Same procedures: scroll down > click the download link called vkd3d-proton-3.0.1.zst to download the file

Step 2.2: right click “Extract All” > you’ll see the folder that is now called vkd3d-proton-3.0.1

Step 2.3: double click the folder > select and double click folder x64

Step 3: copy all the three files to the game file

Step 3.1: Now you need to find the file of your game and double click the folder of Ghost of Tsushima. All you need to do now is to and paste all these 3 files that we recently downloaded:

1. dxgi.dll
2. d3d12.dll
3. d3d12.dll

Step 3.2: Now, return to dxvk-3.1.tar.gz > dxvk-3.1 > x64 folder > find the file dxgi.dll > right click and copy

Step 3.3: Go to the folder of Ghost of Tsushima again > click the folder > press on an empty space and paste the dxgi.dll file.

Step 3.4: Now let’s copy the two files that we need from the folder vkd3d-proton-3.0.1 > click it again > “x64” > find: d3d12.dll and d3d12core.dll

copy both:

Step 3.5: Same procedure, go to the Ghost Of Tsushima folder again and paste these files

Final Step: The most important (without this, the game won’t launch)

Note: This is the most important step that you should do or else, the game won’t even launch

Now, you should stay on the folder of the Ghost of Tsushima (same level as the .exe file)

click on an empty space > right click > create a .text document and name it dxvk.txt > save it > rename it again to > dxvk.conf

now you have to open this file on Windows Notepad app paste the following:

dxvk.enableAsync=True
dxvk.gplAsyncCache=True
dxvk.enableGraphicsPipelineLibrary=True
dxgi.customDeviceId = 24c9
dxgi.customVendorId = 1002
dxgi.hideNvidiaGpu = False
dxgi.emulateUMA = False
dxvk.enableMemoryDefrag=False

Save it (CTRL + S)

Close the file app and try launching your game again

Salut tout le monde,

Je viens demander de l’aide parce que je commence vraiment à ne plus savoir quoi tester avec ma RX 7800 XT.

Depuis que j’ai monté mon PC, j’ai parfois un crash en plein jeu. Ce n’est pas juste un retour sur le bureau ou un crash du pilote graphique. L’écran devient complètement noir, le jeu est figé et le PC ne répond plus du tout.

J’ai essayé Win + Ctrl + Shift + B, mais ça ne fait absolument rien. Le clavier et la souris ne répondent plus non plus, donc au final je n’ai pas d’autre choix que de maintenir le bouton Power pour éteindre le PC.

Le plus bizarre, c’est que le problème arrive après un certain temps de jeu et sur plusieurs jeux différents. Ce n’est donc pas vraiment lié à un jeu en particulier.

Ma configuration :

GPU : RX 7800 XT

CPU : Ryzen 7 9700X

Carte mère : ASUS ROG STRIX B850-F GAMING WIFI

RAM : Crucial DDR5-6000 EXPO

Alimentation : ASUS TUF Gaming 850W Gold

Ventirad : Thermalright Assassin X 120 SE

Windows 11

Écran : 1920×1080, 75 Hz

J’ai déjà essayé plusieurs choses.

J’ai d’abord désactivé EXPO pour voir si le problème venait de la RAM. La RAM tourne donc maintenant aux paramètres par défaut, mais le problème est toujours là.

J’ai aussi mis à jour le BIOS de la carte mère. Ça a l’air d’avoir amélioré un peu les choses. Avant la mise à jour, le crash pouvait arriver beaucoup plus rapidement. Après la mise à jour, j’ai réussi à jouer pendant plus de deux heures avant que le problème se reproduise. Mais malheureusement, il finit toujours par arriver.

J’ai également changé le câble PCIe de la carte graphique. Là aussi, j’ai eu l’impression que le comportement avait changé pendant un moment, mais le crash est finalement revenu.

Pour le moment, je n’ai fait aucun undervolt ni overclocking sur le GPU. Je préfère garder la carte complètement stock pendant mes tests.

Mon écran est seulement en 75 Hz, donc les solutions que je vois souvent du genre « baisse ton écran de 170 Hz à 120 Hz » ne s’appliquent pas vraiment à mon cas.

Je commence donc à me demander si je n’ai pas un problème avec la carte graphique elle-même, la VRAM, les pilotes AMD, l’alimentation ou éventuellement le PCIe.

J’ai aussi vu beaucoup de discussions concernant le MPO (Multi-Plane Overlay) et le fait de le désactiver pour résoudre certains problèmes d’écran noir avec les GPU AMD.

Mais est-ce que le MPO peut vraiment provoquer un freeze complet comme celui que j’ai ? Dans mon cas, ce n’est pas seulement l’affichage qui plante : Windows entier semble complètement bloqué et je dois forcer l’arrêt du PC.

Est-ce que quelqu’un ici a déjà eu exactement le même problème avec une RX 7800 XT ?

Si oui, qu’est-ce qui a finalement réglé le problème pour vous ?

I originally wanted to get the ASUS Prime RX 9070 OC for 770 usd from Amazon (Germany) but it went out of stock and when it came back it was 100 USD more expensive.
So I found the XFX version for 810 USD. I know it’s really expensive- the card itself is 650 USD but the VAT and shipping comes up to 170 more. It’s still the cheapest option in my country (Azerbaijan)
So now I have a dilemma- the reason i want the OC version is because I don’t want to upgrade for the next 4 years, so should I bite the bullet and get the OC version now or get the GRE version and when prices go down sell it and upgrade?

Hi all, just wanted to check if my PC build performance was normal for Fortnite. I’ve been seeing a lot of benchmarks and forums with people getting much better performance than I am.

I’m averaging 110-160 FPS on Fortnite (higher FPS in solos) using DX12 with everything low except view distance as far and 3D at 100% at 1080p

I’m getting 90-100% CPU usage at around 70-75°C and 20-65% GPU usage at around 60°C.

My specs are the following:

CPU: Ryzen 5 5600x
GPU: ASRock Radeon 6750 XT Challenger Pro
Ram: 16gb Single Channel
MB: Gigabyte B550 UD AC
Monitor: 1080p

P.S. I have tried performance mode with all low settings and 3D at 100% averaging 180-200 FPS at 1080p

Only exists in the NBA game until more new games support it so if you want other games you are forced to jankily mod it in (completely understandable and expected tbh)

Performance hit is the same as the leaked dll which is also to be expected. For a game meant to release a week after the leak there is no optimisation happening.

Locked to 50 series which is just incredibly sad. But it appears the reason is that you are expected to use heavy framegen with it. (Will need to be modded in for 40 series)

As someone who isnt a complete hater and has both amd and NVIDIA GPUs this was the most expected and logical thing to happen on release. It will take atleast a year and a GPU generation before it becomes usable.(this is ignoring the fact it doesnt even look right in its current state but I believe in the vision)

Honestly the leaked DLL saved the entire marketing on it because modders (aka people who care) managed to get it working

cant wait to hook it up gotta get a new PSU tho

I want to order the XFX Swift AMD Radeon RX 9070 OC 16GB from Amazon (Germany), the product itself is 650 USD but the VAT and shipping comes up to 170 more. It’s still the cheapest option in my country (Azerbaijan)

Gigabyte Radeon RX 9070 Gaming 16GB or XFX Swift AMD Radeon RX 9070 OC 16GB
The price difference is 30 USD (Gigabyte is the cheaper one)

I know the performance will be atrocious, I have a handful of games I want to test myself and see how they run, from many years back to current ones.

I want to test DLSS 5 vs other mods to improve visuals and reshades, is it possible?

Not even an official release but the leaked version does looks ass and very off for a majority of games and the performance loss just makes it not worth it at all.

But this is the worst dlss5 will be so how long until amd users start whining about amd not implementing it right or taking forever or lack of game/gpu support just like they have with literally every dlss tech: upscaler, fg, mfg, RT denoiser.

People complain about DLSS 5 being AI slop and stuff, but DLSS technologies have always gotten this kind of reaction when they first launched.

Think about DLSS Upscaling. People said it was shit, and the raw performance is what matters the most, but people were mad at AMD for not supporting FSR 4 on older generations.

Think about Multi Frame Generation. People said anything beyond 2X was useless, but now we’re asking AMD to add MFG to the RX 9000 series.

Think about ray tracing. People said it cost too much performance just for better lighting, but now AMD is talking about its own ray tracing features and improvements.

My point is that I think DLSS 5 is going to follow the same pattern. Right now, people are shitting on DLSS 5 because it’s essentially a new technology and is still immature. But once the technology matures and the results get better, I can already see people asking AMD to support Neural Rendering on Radeon GPUs.

We’ve seen this cycle before.

Nvidia cards age like fine wine, yet a 4 years old modern architecture including the second fastest GPU in the world is being locked out of a feature that they can already run fine.

Qual è la risposta di AMD al Dlss5?

Secondo me, che faccia uscire subito tutta la retrocompatibilità possibile della sua attuale tecnologia, e quindi upscaking 4.11 per RX 6xxx e quanto possibile di Redstone su RX 7xxx.

Sarebbe la mossa più azzeccata, perché Nvidia sta ufficializzando una tecnologia che a malapena si può usare sulle RTX 5xxx.

Rdna5 e FSR Diamond dovrebbero essere un salto generazionale importante anche nei confronti di RX 9xxx.

Se AMD ha in serbo cartucce di retrocompatibilità per Redstone, adesso è il momento di usarle. My2cents

NVIDIA DLSS 5 has officially launched, available starting September 3rd for all GeForce RTX 50 Series GPUs and on GeForce NOW. When can we expect something similar—featuring AI technology for faces and environments—for the 90 series?

Not something like Dlss 5, but a fixed multi frame gen, better ray regen or radiance cache. I know some people are gonna say that “You shouldve bought nvidia" but as a long time Radeon/Ati user i think there is nothing wrong with wanting a higher quality experience.

Hey everyone,

I’m currently using an RX 6700 XT Sapphire Pulse on my micro-(B650M GAMING PLUS WIFI) setup. I’m looking to upgrade to an XFX Swuift/QuickSilver 9070XT card, but I know XFX designs tend to be pretty beefy and long.

Does the cooler overhang or press against the bottom motherboard headers (front panel, USB, HD Audio, fan headers)?
Did you have trouble connecting/bending the bottom cables, or was there enough clearance?

Would appreciate hearing about your experiences or seeing any photos of your setup if you have a similar build!
Thanks!

hi guys i currently have a 3070ti and thinking of moving to a rx 9070 xt when talking to firends they say save for a 5070ti but im thinking amd is the way to go just wondering if anyone else has done this change and if so was it worth it?

Hey everyone, this issue is getting annoying and it seems to only ever do it when my pc hasn’t been turned on in a bit(went to visit family).

I run a sapphire 9060XT. Ive made sure my connections are plugged properly, tried different inputs and swapped HDMI and DP cables. I built this pc not long ago.. i’ve reverted my graphics, its still happening.

Any help would be appreciated!