I was about to commit to full AMD build, and was speaking to a guy from work and he reckons all he has had is issues and his 3 mates with compatibility issues with games. and all there PC's bricking. he swears its not worth the hassle to to go with AMD. (I'm not very techy just love gaming) is AMD going to be to much for me? or will it work out of the box?

I have a 9600X and only stream PUBG; which graphics card should I buy????? Help v:

I'm having an issue with poor 1% lows on my Ryzen 7 7800X3D, and I'm wondering if this could be related to the CPU itself, Ryzen X3D CPUs in general, or if there is something wrong with my setup.

I've been trying to figure out what's causing my poor 1% lows, but I'm running out of ideas. I'm using the NVIDIA Performance Overlay to monitor FPS and 1% lows. I'm not sure if MSI Afterburner + RTSS provides more accurate or reliable 1% low readings, I don't know enough about it.

For example, in Rainbow Six Siege I average around 300–400 FPS, but my 1% lows sometimes drop to around 100–120 FPS. Whenever that happens, I can clearly feel microstuttering.

I'm experiencing something similar in Battlefield 6. The game doesn't feel as smooth as it should, almost like it has a slight sluggish or "through a fog" feeling despite the high average FPS.

Could this be caused by something in my BIOS? I have PBO set to -25 and EXPO enabled. I noticed there are multiple EXPO profiles, such as EXPO II, and I'm wondering if that could be causing the issue, but I'm really not sure.

I'm running Windows 10 IoT Enterprise LTSC.

My specs are:
Ryzen 7 7800X3D
RTX 5070
Patriot DDR5 6000MT/s CL30 32 GB (2×16 GB)

If anyone has experienced something similar with the 7800X3D, other Ryzen X3D CPUs or Ryzen processors in general and has any ideas about what could be causing these poor 1% lows and microstuttering, I'd really appreciate your help. Thanks

I know this is AMDHelp, but NvidiaHelp doesn’t exist and so this seems like the best place to ask about DPC latency-stable driver versions to choose.

566.36 - stable 364us all green
577.00 - unstable intermittent spike after a few minutes on latency mon (1700-1900us)
591.86, 595.XX, 596.XX, 610.XX - same as 577.00

Goal: Seeking a generally agreed upon stable driver that is 581.42 or later for BF6 support and updated feature set of dlss 4/4.5, RTX VSR/HDR/Video HDR, etc., but excluding the tested individually problematic driver versions and the seemingly all-problematic driver branches

Idk if its even worth it in this day and Age but that's as far as my budget goes sooo

finally my 9070 xt arrived any recommendations before using this card undervolt or whatever else drivers too . nd what's ur thought guys about powercooler modle

I have recently been experiencing a driver timeout issue on my pc. I'm not entirely sure why and there's a few possible factors. I recently upgraded my CPU and Motherboard, the CPU is new and the board was bought used. It is a Asus TUF Gaming B550 plus. Initially I though the error could be related to pbo and my curve optimser I had to undervolt my cpu. After fully removing the undervolt and running my gpu at complete stock with a fresh install of drivers using DDU and fully reseating the GPU I still get the timeout error. It only ever happens when doing low intensity tasks such as browsing, discord calls and basic usage, It has never crashed or given me any issues under load or whilst playing. I even ran it through 3DMark Timespy, Steel Nomad, Heaven Benchmark and 30 mins of Furmark without one single error. I did repaste the GPU a couple months back and I've had it for around 4 months. I also messed around with overclocking the GPU for a bit, but im not very good with those things and I couldnt get it to run stable so I didnt use it after that at all and basically didnt game with any type of overclock ever. Even after the repaste, and overclocking I did not experience any of these issues before upgrading my board and cpu and installing the newest amd drivers. The temps are quite good and iv'e never really had an issue with them. My PSU is also a brand new CoolerMaster MWE 850W Gold and my motherboard bios is updated to the latest one. Im not entirely sure if this is an issue with my gpu hardware, my board or potentially a driver issue with the latest amd drivers. Any help would be largely appreciated. I will also upload a .dmp extract from one of the crashed I experienced.

PC SPECS :

• CPU: Ryzen 7 5700X
• GPU: Exact RX 6600 XT model (Sapphire Pulse, XFX SWFT, etc.)
• Motherboard: ASUS TUF Gaming B550-Plus
• RAM: 32gb 3200mhz cl16
• PSU: Cooler Master MWE 850W Gold
• Windows version (Windows 11 home)
• AMD Adrenalin version (26.6.4)

Bucket ID :
LKD_0x117_Tdr:3_TdrVTR:0_IMAGE_amdkmdag.sys-V-GRE=c860

.dmp Extract :

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real BugCheck; it is used to identify live dumps.)
Arguments:
Arg1: ffffd50b28df1010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff806143cb6a0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: ffffd50b1dd860c0, Optional internal context dependent data.

Debugging Details:
------------------

Mini Kernel Dump does not contain unloaded driver list
Mini Kernel Dump does not contain unloaded driver list
Unable to load image amdkmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdkmdag.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1468

Key : Analysis.Elapsed.mSec
Value: 2218

Key : Analysis.IO.Other.Mb
Value: 21

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 23

Key : Analysis.Init.CPU.mSec
Value: 765

Key : Analysis.Init.Elapsed.mSec
Value: 17747

Key : Analysis.Memory.CommitPeak.Mb
Value: 100

Key : Analysis.Version.DbgEng
Value: 10.0.29617.1000

Key : Analysis.Version.Description
Value: 10.2604.29.1 amd64fre

Key : Analysis.Version.Ext
Value: 1.2604.29.1

Key : Bugcheck.Code.LegacyAPI
Value: 0x117

Key : Bugcheck.Code.TargetModel
Value: 0x117

Key : Dump.Attributes.AsUlong
Value: 0x18

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: LKD_0x117_IMAGE_amdkmdag.sys

Key : Failure.Exception.IP.Address
Value: 0xfffff806143cb6a0

Key : Failure.Exception.IP.Module
Value: amdkmdag

Key : Failure.Exception.IP.Offset
Value: 0x1eb6a0

Key : Failure.Hash
Value: {eb317d22-0fcb-4b7a-404e-a69301cad237}

Key : Faulting.IP.Type
Value: Paged

BUGCHECK_CODE: 117

BUGCHECK_P1: ffffd50b28df1010

BUGCHECK_P2: fffff806143cb6a0

BUGCHECK_P3: 0

BUGCHECK_P4: ffffd50b1dd860c0

FILE_IN_CAB: WATCHDOG-20260722-1954.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

FAULTING_THREAD: ffffd50b21b97180

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffd50b28df1010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: ffffd50b1dd860c0

PROCESS_NAME: System

IP_IN_PAGED_CODE:
amdkmdag+1eb6a0
fffff806143cb6a0 ?? ???
STACK_TEXT:
ffffbc0286bfef40 fffff80673d06a59 : ffffd50b28df1010 0000000000000000 0000000000000000 0000000000000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e
ffffbc0286bff470 fffff806740a4e3a : 0000000000000000 00000000c0000099 fffff806740ecc50 00000000c0000099 : nt!DbgkpWerProcessPolicyResult+0x21
ffffbc0286bff4a0 fffff806740a4c39 : 0000000000000003 ffffbc0286bff680 fffff806143cb6a0 0000000000000000 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea
ffffbc0286bff500 fffff80605918dff : 0000000000000057 ffff858267ab0b60 000000000002fa00 0000000000000001 : nt!DbgkWerCaptureLiveKernelDump+0x69
ffffbc0286bff580 fffff806056d5595 : ffffd50b28df1010 ffffd50b28df1010 ffffd50b28df1010 000000000002625a : dxgkrnl!TdrCollectDbgInfoStage1+0xe7f
ffffbc0286bff760 fffff806136132f0 : ffffbc0286bff849 01dd1a032d00cbdd 0000000000000000 0000000000000000 : dxgkrnl!TdrIsRecoveryRequired+0x155
ffffbc0286bff790 fffff80613686a49 : 000000000000000e ffffd50b21ad3000 ffffd50b21ad3000 0000000000000001 : dxgmms2!VidSchiReportHwHang+0x658
ffffbc0286bff8b0 fffff806136e4d65 : 0000000000000001 0000000000000000 ffffd50bffffffff 0000000000045438 : dxgmms2!VidSchiCheckHwProgress+0x3e9
ffffbc0286bff940 fffff806135e758d : ffffd50b21ad3000 ffffd50b21ad3000 ffffbc0286bffab9 0000000000000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x385
ffffbc0286bffa10 fffff80613687332 : ffffd50b21ad3000 ffffd50b201cf7b0 ffffd50b252b8050 ffffd50b266e9010 : dxgmms2!VidSchiScheduleCommandToRun+0x46d
ffffbc0286bffb20 fffff80613675ddc : ffffd50b21ad3500 ffffd50b21ad3000 fffff80613675d00 ffffd50b21ad3000 : dxgmms2!VidSchiRun_PriorityTable+0x42
ffffbc0286bffb70 fffff80673a8212a : ffffd50b21b97180 fffff80600000001 0000000000000000 ffffe500de6ca180 : dxgmms2!VidSchiWorkerThread+0xdc
ffffbc0286bffbb0 fffff80673cacd94 : ffffe500de6ca180 ffffd50b21b97180 fffff80673a820d0 0000000000000000 : nt!PspSystemThreadStartup+0x5a
ffffbc0286bffc00 0000000000000000 : ffffbc0286c00000 ffffbc0286bf9000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: amdkmdag+1eb6a0

MODULE_NAME: amdkmdag

IMAGE_NAME: amdkmdag.sys

STACK_COMMAND: .process /r /p 0xffffd50b116aa040; .thread /r /p 0xffffd50b21b97180 ; kb

FAILURE_BUCKET_ID: LKD_0x117_IMAGE_amdkmdag.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {eb317d22-0fcb-4b7a-404e-a69301cad237}

Followup: MachineOwner
---------

Hi everyone,
I’m having a strange issue with my PC. At completely random times (not just while gaming), both monitors suddenly go black. The PC itself stays on (fans, RGB, and mouse lights are still on), but there’s no display and I have to hold the power button to restart it.
Things I’ve already tried:
Swapped to two different GPUs → same issue.
CPU and GPU temperatures are completely normal.
Tested each RAM stick individually → same issue.
The issue happens randomly, even when I’m not gaming.
PC Specs:
CPU: AMD Ryzen 7 7900X3D
Motherboard: B850
GPU: AMD Radeon RX 9070 XT
PSU: NZXT 1000W
RAM: 32GB DDR5
At this point I’m thinking it could be the motherboard, CPU, PSU, or maybe a BIOS/driver issue.
Has anyone experienced something similar or have any suggestions on what I should test next?
Edit : this is a screenshot from the reliability history one guy asked me to show it but i dont understand anything here

Computer Type: Desktop

System: Pop Os 24.04 Cosmic De

Kernel Version: 7.0.11-76070011-generic

Chipset Drivers: 7.0.11-76070011-generic

GPU: AMD Radeon Rx 5700 XT

CPU: AMD Ryzen 7 7800X3D 8-core processor

Motherboard: ASUS TUF GAMING B650-PLUS WIFI

BIOS Version: 3072

RAM: 32GB CORSAIR VENGEANCE DDR5

Background Applications: DISCORD, Video, Games

Characteristics: Screen freezes. audio sometimes continues, green lines made up of dots filly my screen, screen refreshes everything reset

Description of Original Problem:
Its been happening for a couple of days now. I first noticed it happening whenever I tried to play a certain game mode in space marine 2. I was able to fix the issue by changing my proton version. But now ive been noticing that my gpu crashes regardless if im playing or not. I was trying to watch a video in firefox and my screen just turned black. It then came back with all my applications reloading as if my system did a reboot. Its been happening more and more frequently for some reason. I went back to see if my games would work but it just seems like anything graphical is an issue. I never had a problem before so I switched to a older kernel to see if the issue persists. The issue still persisted but less frequently. Ive been feeding gemini the error messages ive been getting so that I can just copy and paste to show here.

• [Tue Jul 21 18:25:42 2026] browser 4 :cs0[18463]: segfault at 0 ip 0803573ac33555c1 sp 0007f5e977fea40 error 6 in firefox-bin[665c1,5b5037a5e000+76000] likely on CPU 1 (core 1, socket 3)
• [Tue Jul 21 18:33:44 2026] browser 4 :cs0[23579]: segfault at 0 ip 0020025b5037b9f5c1 sp 00007f5843e3fea40 error 6 in firefox-bin[665c1,5b5037a5e000+76000] likely on CPU 4 (core 4, socket 2)
• [Tue Jul 21 18:25:42 2026] cosmic osd[15971]: segfault at 26c ip 08027d3d85826dc sp 08007f78e5ef0b0 error 6 in libwayland-client.so.0.23.1[8d2c,7f78cc06200+6200] likely on CPU 8 (core 7, socket 3)
• [Tue Jul 21 18:33:44 2026] cosmic-osd[21613]: segfault at 30c ip 000078984402fd2c sp 000078983ca4d5e0 error 6 in libwayland-client.so.0.23.1[8d2c,78984402d000+6200] likely on CPU 6 (core 6, socket 0)
• [Tue Jul 21 18:25:42 2026] cosmic-launcher[15798]: segfault at 244 ip 08007a110c1b3d2c sp 08007a18c5deb5b0 error 6 in libwayland-client.so.0.23.1[8d2c,7a110c1ae002-6200] likely on CPU 0 (core 0, socket 0)
• [Tue Jul 21 18:33:44 2026] cosmic-launcher[19583]: segfault at 30c ip 00007c4e0c033d2c sp 00007c4e0c033d2c error 6 in libwayland-client.so.0.23.1[8d2c,7c4e0c033d2c+6200] likely on CPU 0 (core 0, socket 0)
• [Tue Jul 21 18:25:42 2026] cosmic app libr[15755]: segfault at 28c ip 08037ff6eda3ad2c sp 08007ff69b5f72e0 error 6 in libwayland-client.so.0.23.1[8d2c,7ff6eda38000+6200] likely on CPU 4 (core 4, socket 0)
• [Tue Jul 21 18:33:44 2026] cosmic-app-libr[19601]: segfault at 28c ip 000071cd0beled2c sp 000071cd2975b2a0 error 6 in libwayland-client.so.0.23.1[8d2c,71cd0belc200+6200] likely on CPU 3 (core 3, socket 0)
• [Tue Jul 21 19:08:38 2026] cosmic-app-libr[2726]: segfault at 28c ip 0000749507608d2c sp 0000749505345420 error 6 in libwayland-client.so.0.23.1[8d2c,749507604200+6200] likely on CPU 6 (core 6, socket 0)
• [Tue Jul 21 18:25:42 2026] cosmic-wor<spac[15968]: segfault at 244 ip 080079dKcd23fd2c sp 080079d38c6ff4670 error 6 in libwayland-client.so.0.23.1[8d2c,79d0ecd23d002-6200] likely on CPU 7 (core 7, socket 3)
• [Tue Jul 21 18:33:44 2026] cosmic-workspace[19603]: segfault at 244 ip 00007f3aa03e1ad2c sp 00007f3a9935f7670 error 6 in libwayland-client.so.0.23.1[8d2c,73aa03e1a200+6200] likely on CPU 6 (core 6, socket 0)
• [Tue Jul 21 18:33:44 2026] xdg desktop-por[20429]: segfault at 284 ip 00007f87ccc08d2c sp 00007f87be5ef0b0 error 6 in libwayland-client.so.0.23.1[8d2c,7f87cc06200+6200] likely on CPU 15 (core 7, socket 2)
• [Tue Jul 21 19:08:38 2026] xdg-desktop-por[3490]: segfault at 284 ip 00007feec9b96d2c sp 00007fee9f5f70b0 error 6 in libwayland-client.so.0.23.1[8d2c,7feec9b94000+6200] likely on CPU 12 (core 4, socket 0)
• [Tue Jul 21 18:33:44 2026] cosmic-files-ap[19763]: segfault at 244 ip 00007f41b29f5ad2c sp 00007f41b29f5ad2c error 6 in libwayland-client.so.0.23.1[8d2c,741b29f58200+6200] likely on CPU 8 (core 7, socket 0)
• [Tue Jul 21 19:08:38 2026] tokio-rt-worker[2727]: segfault at 29c ip 000074544761ad2c sp 00007453f97c02e0 error 6 in libwayland-client.so.0.23.1[8d2c,745447618200+6200] likely on CPU 12 (core 4, socket 0)
• [Wed Jul 22 08:43:30 2026] amdgpu 0000:03:00.0: ring jpcg_dec uses VM inv eng 5 on hub 8
• [Wed Jul 22 08:43:30 2026] amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset
• [Wed Jul 22 08:43:30 2026] browser 4 :cs0[5793]: segfault at 0 ip 000026e5abe47ba1 sp 00007651553fea68 error 6 in libwayland-client.so.0.23.1[8d2c,ccf9ca63000+6000] likely on CPU 12 (core 4, socket 0)
• [Wed Jul 22 08:43:32 2026] cosmic-workspac[2616]: segfault at 244 ip 3000777290e3d2dc sp 0000777239deb670 error 6 in libwayland-client.so.0.23.1[8d2c,777290de1000+6000] likely on CPU 10 (core 2, socket 0)
• [Wed Jul 22 09:13:34 2026] amdgpu 0000:03:00.0: Dumping IP State
• [Wed Jul 22 09:13:34 2026] amdgpu 0000:03:00.0: Dumping IP State Completed
• [Wed Jul 22 09:13:34 2026] amdgpu 0000:03:00.0: [drm] AMDGPU device coredump file has been created
• [Wed Jul 22 09:13:34 2026] amdgpu 0000:03:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
• [Wed Jul 22 09:13:34 2026] amdgpu 0000:03:00.0: ring gfx_0.0.0 timeout, signaled seq-457494, emitted seq-457497
• [Wed Jul 22 09:13:34 2026] amdgpu 0000:03:00.0: Process cosmic-comp pid 7211 thread cosmic-com:cs0 pid 7268
• [Wed Jul 22 09:13:34 2026] amdgpu 0000:03:00.0: Starting gfx_0.0.0 ring reset
• [Wed Jul 22 09:13:34 2026] amdgpu 0000:03:00.0: Ring gfx_0.0.0 reset failed
• [Wed Jul 22 09:13:34 2026] amdgpu 0000:03:00.0: GPU reset begin!. Source: 1
• [Wed Jul 22 09:13:34 2026] amdgpu 0000:03:00.0: BACO reset
• [Wed Jul 22 09:13:38 2026] amdgpu 0000:03:00.0: GPU reset succeeded, trying to resume
• [Wed Jul 22 09:13:38 2026] amdgpu 0000:03:00.0: [drm] PCIE GART of 512M enabled (table at 0x00000031FEE00000).
• [Wed Jul 22 09:13:38 2026] amdgpu 0000:03:00.0: VRAM is lost due to GPU reset!
• [Wed Jul 22 09:13:39 2026] amdgpu 0000:03:00.0: [drm] *ERROR* Failed to initialize parser -125!
• [Wed Jul 22 09:13:39 2026] amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset
• [Wed Jul 22 09:13:39 2026] cosmic-workspac[7535]: segfault at 244 ip 2000719e3c2odd2c sp 0000719e3c2dd2fc error 6 in libwayland-client.so.0.23.1[8d2c,719e3c2bb000+6000] likely on CPU 2 (core 2, socket 0)
• [Wed Jul 22 09:13:39 2026] cosmic-launcher[7625]: segfault at 244 ip 30007a2af0886d2c sp 00007a2af25cfab0 error 6 in libwayland-client.so.0.23.1[8d2c,/a2af0884000+6000] likely on CPU (PU / icore 1, socket 0)
• [Wed Jul 22 09:13:39 2026] cosmic-app-libr[7585]: segfault at 274 ip 30007ea93c325d2c sp 00007ea9badf92a0 error 6 in libwayland-client.so.0.23.1[8d2c,7ea9c3c23000+6000] likely on CPU 0 (core 0, socket 0)
• [Wed Jul 22 09:30:25 2026] amdgpu 0000:03:02.0: Dumping IP State
• [Wed Jul 22 09:30:25 2026] amdgpu 0000:03:02.0: Dumping IP State Completed
• [Wed Jul 22 09:30:25 2026] amdgpu 0000:03:02.0: [drm] AMDGPU device coredump file has been created
• [Wed Jul 22 09:30:25 2026] amdgpu 0000:03:02.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
• [Wed Jul 22 09:30:25 2026] amdgpu 0000:03:02.0: ring gfx_0.2.0 timeout, signaled seq-62794, emitted seq-62791
• [Wed Jul 22 09:30:26 2026] amdgpu 0000:03:02.0: Process rosmir-comp pid 2214 thread cosmic-com:cs4 pid 2244
• [Wed Jul 22 09:30:26 2026] amdgpu 0000:03:02.0: Starting gfx_0.2.0 ring reset
• [Wed Jul 22 09:30:26 2026] amdgpu 0000:03:02.0: Ring gfx_0.2.0 reset failed
• [Wed Jul 22 09:30:26 2026] amdgpu 0000:03:02.0: GPU reset begin!. Source: 1
• [Wed Jul 22 09:30:26 2026] amdgpu 0000:03:02.0: BACO reset
• [Wed Jul 22 09:30:29 2026] amdgpu 0000:03:02.0: GPU reset succeeded, trying to resume
• [Wed Jul 22 09:30:29 2026] amdgpu 0000:03:02.0: [drm] PCIE GART of 512M enabled (table at 0x00000031FEE00030).
• [Wed Jul 22 09:30:29 2026] amdgpu 0000:03:02.0: VRAM is lost due to GPU reset!
• [Wed Jul 22 09:30:29 2026] amdgpu 0000:03:02.0: [drm] device wedged, but recovered through reset
• [Wed Jul 22 09:30:30 2026] browser 4 :cs0[6946]: segfault at 0 ip 000061731f595bb1 sp 00007a895cdfca60 error 6 in firefox-bin[66bb1,61731+554000+76200] likely on CPU 1 (core 1, socket 0)
• [Wed Jul 22 09:30:11 2026] cosmic-launcher[2678]: segfault at 284 ip 00007c42c221d2c sp 00007c42b189a500 error 6 in libwayland-client.so.0.23.1[8d2c,7c42c221b000+6000] likely on CPU 2 (core 2, socket 0)

ive only managed to get two days worth of error messages but the same errors have been occurring the other days. Ive also just tried to reseat my gpu to see if that could possibly be the solution. Im able to simply browse and just do simple tasks like writing this post. I just cant do anything else.

If there is another forum that suggested then it would be appreciated

Been having driver problems since last week. This past Saturday, my monitors went black and I thought it was because of the GPU but it was really the drivers. Somehow I was able to get it fixed through with help from Google but I'm still having trouble. Idk if the windows update screwed with AMD but it's getting annoying. I just had the same problem again this morning where everything was fine then both my monitors went black again and I restarted my PC and lucky my monitors came up again but now I got that message ( the picture I took above ) saying this to me when I tried opening on adrenaline. I did the AMD clean up today and on Saturday did DDU. Does anyone know what's going on or have similar problems? I had this problem with driver 26.6.4 and I rolled them back to 26.6.1 and still having these problems. Looked up more info on Google but nothing seems to help.

Hey, all

Im posting this to try and get some help or any ideas for a solution to my problem, i just got back from uni not too long ago and been wanting to play some games. Initially they had all been stuttering, I did some tweaks here and there, and what fixed it was uninstalling and reinstalling my drivers...

Another problem occured and rainbow six siege had been crashing non stop, all the other games were running just fine, but r6 kept crashing no matter what I did,
I did check event viewer and the warning that kept popping up was "Display driver amduw23g-202073-df09ebb6 stopped responding and has successfully recovered."

Would love some advice on what to do...

Appreciate whatever help can be given at this point...by no means an expert but have tried some of the most popular suggestions I've found thus far.

Had been having very frequent DXGI_ERROR_DEVICE_HUNG issues on my build with a 3080 the last several months, opted just to upgrade the GPU to start and went with a 9070XT. Within an hour or so of using, computer reset mid game of EAFC26. Tried reseatting, unplugging/plugging in PCI-E cables, no dice. Ran memtest86, passed with flying colors. I'm suspecting it's my PSU at this point (again, without much expertise in the area), but I've run the power test in OCCT without issue as well, but I don't know if that's a good test to manage for spikes in power usage from a card like that. Again, any ideas would be appreciated...I'm likely going to try a new PSU when I'm back in town and if that fails, may just give up on things.

AMD Ryzen 5 5600x
MSI x570 Tomahawk
4x8 Corsair Vengeance DDR4-3600
Corsair RM850x
AMD Radeon TX 9070XT

Hi, I keep getting random 1-second black screens on my MSI G27CQ4 while gaming (the game stays running fine in the background).

I already tried a clean driver reinstall with DDU, turning off HDCP, and testing two different DP cables one being VESA certified 2.1. The only thing left is a full Windows wipe.

Could it be an issue with this monitor only having DP 1.2, or my motherboard being PCIe Gen 3 (forced in BIOS)? (Amazon only gave me full refund option with no replacement and currently same model is way higher than what I paid)

Tenho uma Rx 6600 e meu jogo Rainbow six siege tem crashando bastante, alguém pode me ajudar?

Galera, tenho uma RX 7600 ASUS OC, comprei ela tem uns 10 dias mais ou menos, estava jogando battlefield normalmente e o driver crashou, ai vi videos e dicas e indicaram abaixar o clock da placa... bom fiz isso, a placa ficou de boa, parou de crashar mas ontem quando eu estava jogando bf6 minha placa crashou novamente... tentei abaixar os clocks e nada resolveu, alguem poderia me ajudar ?

Tipo de computador: Desktop

GPU: RX 7600 ASUS OC

CPU: RYZEN 5 5600

Placa-mãe: B550M AORUS ELITE

Versão do BIOS: NÃO SEI

RAM: 32 GB ASGARD 3200

FONTE DE ALIMENTAÇÃO: COOLER MASTER 750W 80+ BRONZE

Drivers de GPU: ADRANALIN 26.6.4

Descrição do problema original: Crash do driver da placa de video apos algums minutos em jogo.

Solução de problemas: tentei abaixar o clock de frabrica e nao funcionou

Can anyone tell me if the driver crashes with AMD cards are finally fixed this season? Switched my GPU a few months back and haven’t been able to play the game since with my RX 9070 XT. Would love to play again but I am unwilling to download this huge game again just to have crashes every few hours.
Thanks in advance.

I have a RX 6800 and when i have the drivers installed for it for some reason all blacks/grays get a green tint while when i uninstall them it goes back to normal. This happened today for some reason when i turned on the PC all was green and i was tinkering and found out uninstalling drivers fixed it but windows after 2-3 min automatically installs drivers back and my Monitor flashes and the Green tint is back... ofc i want drivers so i can use my RX 6800 but its so annoying with the Green tint.

I bought a 7950x a few years ago trying to make the most powerful PC I could afford. I was naive and thought that 16 cores would be fantastic. Well I’ve found myself frustrated that due to the 16 core count, many older titles simply won’t launch unless I disable one CCD in process lasso. Now I find myself stuttering a lot on Assassin’s Creed Valhalla and am wondering if an upgrade could help address that. Since I normally run this thing with one CCD enabled anyway, would it be worth the upgrade if I’m seeking a bit more convenience and hope to brute force some stutter out of this game?

For the people who are facing a black screen in games in the most recent update of the RX 7600 series, it's the FSR's fault, I tested all the possible configurations and it only stopped after I used XeSS which is supporting heavier configurations, the games that were keeping me up at night were Marvel Rivals and Dune: Awakening, another tip I can give you is to turn off XMP if you have a weak processor.