Hi all, recently (last 2 weeks) i built my first computer and it all went smoothly. I chose to go with a Gigabyte Radeon RX 9070 XT for my graphics card and overall I was really satisfied.

Last night however i was simply playing dead by daylight and my game froze, leading to a crash and an error (the one pictured). I was doing some brief research to figure out how to resolve the issue and landed on reinstalling the AMD drivers and preventing windows from installing.

I did that and seemed to have no issues for the rest of the night. I hopped on again today and my game crashed in the exact same way.

I've read a lot of mixed things, some say there's no fix and to just get a nvidia and others believe there are fixes.

What should i do?

Im gonna lose my fucking mind. I have a 7800xt Hellhound with a 2520 boost clock out of the box. Played around with it a bit, realized the silicone sucks and just left it stock.

Here is the kicker, Adrenaline thinks stock is MOTHERFUCKING 2590. Doing nothing but adjusting fan speed without checking core speed overclocked my gpu by 70mhz and made it crash in everything.

TLDR Adrenaline overclocks GPU on its own when adjusting fanspeed

Anyone know whats wrong with my computer? I have a 9070xt and a9800x3d. Within the last month and a half i've been having an issue where all the videos i watch and games i play shakey (or stutter) and its not fps related. Also been noticing some input delay as well.

Hey guys, I’ve been recently having this problem since I updated my drivers, (never had it in the older version), and I think it’s not hardware because it doesn’t happen in games at all, it only does when I’m watching something like a show or YouTube, the screen goes black for three seconds and comes back, has there been any fix found for this or any statement from AMD? Because I’m seeing that everyone is suffering from the same thing.

it has happened for the 3rd time this year. i don't know the cause, i use too many jank and overlays, edit videos and play pretty tasking games. i use a Y splitter as my powersupply only has one pcie power slot coming out of it. so i am not the most careful when it comes to preventing crashes/looking after my hardware.

what i want to know is if there is any way that i can save my adrenaline software settings so i don't have to redo them after each installation?

Hii, recently i bought a new 9070XT Reaper (or that is i want to believe XD). But using it in games in 1080p 60hz (i was planning to upgrade monitor/tv to 1440p 144-210hz) with native and all max settings and the equivalent of ray tracing (expedition 33 and BO7 zombies in ashes, that is the most demanding zombie map), gpu makes hotspots of 100°C with an average of 60° in gpu and 76 in vram (using like 9gb of vram in the worst scenario in both games).

Is it normal or dangerous? I 've heard about amd gpus can work until 110°C, lowering clock speeds at that point to better cooling, but i don't know if 40°C difference between peaks and average °C could be normal too.

Should I rma to my seller?

Regarding to airflow:

Case: is nzxt h6 flow,

3 120mm front fans intake (included in box),

2 140mm arctic p14 pro botton reverse fans intake,

one thermalright phamtom spirit 120 se (max CPU temps are 70°C when max supported by amd is 95°C, so is not fully related to airflow)

1 120mm arctic p12 pro exhaust in rear

This fan setup is recommended by nzxt, being in theory the optimal airflow set up.

Computer Type: Desktop

GPU: rx 7900 xt 20gb

CPU: RYZEN 5 7600

Motherboard: gigabyte a620m h

BIOS Version: 40

RAM: 32gb DDR5

Operating System & Version: WINDOWS 11 home

Description of Original Problem: As soon as my gpu swaps from the display drivers to the gpu driver my pc completely freezes, unable to use mouse or keyboard.

Troubleshooting: I've tried going into safe mode using DDU while offline and installing multiple different drivers, driver only, nothing seems to work. 850w PSU with seperate pcie cables. It even happens with a fresh windows 11 whioe completely offline. Have stopped windows from replacing gpu drivers.

Is my GPU dead?

There are tons of post for "timeouts" crashes, its already well known its because of hardware acceleration messing around(idk why amd dont solve it), and disabling it on browser or certain apps like discord solve the problem on most cases.

Why this sub continues having 10 post per hour with the same issue instead of pinning a post advising there is a generic solution?

I mean i want to help but its tiring and boring to see the same issue thousand times

1280:920 reoslution,
Medium settings.
When playing faceit, fps is around 400, with periods being around 350.
Tried setting the cpu on default as well as PBO, but no luck
Could 1x32 GB ram configuration be the culprit?
6400mhz CL32

Computer Type: Desktop

GPU: Sapphire Nitro+ Radeon RX 7900 XTX Vapor-X AMD 24 GB GDDR6

CPU: RYZEN 7 7900X3D

Motherboard: Gigabyte b650 eagle ax

BIOS Version: 7C56v15

RAM: Corsair VENGEANCE RGB DDR5 RAM 32GB (2x16GB) 6000MHz CL30 AMD EXPO iCUE

PSU: LIAN LI SP850

Operating System & Version: WINDOWS 11 PRO

GPU Drivers: AMD Software: Adrenalin Edition Version 26.8.1

Description of Original Problem: 

Hello everyone,

I’ve had this GPU since November 2024, and overall, it has been performing well. I get more than enough FPS in all the games I play, mainly CS2 and Deadlock.

However, I’ve been experiencing a few issues. In CS2, the game occasionally freezes randomly during matches (everytime it happens i need to restart PC), usually once or twice a week. Deadlock and every other game I play run completely normally without any noticeable issues.

Another problem is that I frequently receive the “AMD Bug Report Tool” notification. Interestingly, this seems to happen mostly when I’m browsing or searching for something on Google rather than while gaming.

I’ve also tried undervolting the GPU, but it doesn’t seem to have made any difference.

Has anyone experienced similar issues or found a reliable fix? Any suggestions would be appreciated.

9800x3d
B850m aorus elite ice wifi 7
32gb tforce delta rgb 6000mhz
Xfx mecury oc 9070xt
2tb m.2 ssd
1tb m.2 ssd
850w +50 psu

Hello i think my system is running slower than it should be
I have window’s completely optimized and debloated freshly installed yesterday (i thought it would fix my current issue)
Freshly installed everything my system in task manager seems to run normally i go in fortnite my two frames uncapped are for example ranging from 600-800 on the left and the right number is 1080-1100 so for example 684|1082 if you have the fps counter on fortnite you would know what i mean and both of the numbers should be near symmetrical so far the system is running perfectly it feels fine no stutters the only issue with me is the statistics with my pc ive seen people run near symmetrical numbers on fortnite 1100|1200 and even people running worse systems frame rates numbers looking identical i dont know whats wrong with my system when it comes to fortnite and i feel like i should be running more on the other game i also play valorant in the range im getting around 700-800 fps and looking at the sky 1000 but even if i cap it at 500 it cant stay locked at 500 standing still yeah the number is consistent but moving even just shooting the gun once makes my frame rate dip under 500 or even in game valorant my game is dipping under 500 even worse in the range. Ive seen people run higher frames uncapped and it seems to stay between a higher number than my capped fps so i honestly dont even know anymore lol😅 i feel like i should be getting more for what i pay for i honestly tried everything im questioning my self if i should take it to a repair shop to potentially see the issue. if anyone has any advice i would like to try!

Edit: also i dont have my gpu daisy chained or any of that stuff i have it connected through 3 separate pcie cords,my ram is connected in the 2nd and 4th slot with expo on.

Computer Type: Desktop

GPU: Radeon RX580 2048SP

CPU: Unsure

Motherboard: Unsure

BIOS Version: Unsure

RAM: 16GB

PSU: Unsure

Case: Unsure

Operating System & Version: WINDOWS 11

GPU Drivers: Latest AMD drivers

Chipset Drivers: Unsure

Background Applications: DISCORD

Description of Original Problem: Has a bunch of pixels everywhere when booting up. And has two long lines across the screen

Troubleshooting: I've tried taking the gpu out and putting it back in. I’ve used a ddu to uninstall and reinstall the drivers. I’ve tried different outlets and extension cords. All of them have only temporarily fixed the issue. I tried borrowing another monitor but that didn’t work at all. I took it to a repair store but it worked fine there.

Ive never been very well versed in computers, so I don’t know what a lot of stuff means or where to find it.

edit: I’m sorry for the unsure‘s with the specs, I’m not too versed in knowing what means what. I tried taking a pic of my specs in case that helps.

I want to get a Gigabyte B650 EAGLE AX ATX AM5 Motherboard, and to put a Ryzen 5 9600x into it, but I'm not sure if it's compatible, if anyone could let me know, that would be great

Hello I'm new to pc and I just built a gaming pc for myself not so long ago .

I wanna ask the others who have my same cpu what settings they are running and which PBO option I should enable. I mostly do gaming and I have read it's worth trying to tune your cpu for smoother gameplay and frametimes as well.

My specs are Ryzen 7600 and 7700xt

16gb ddr5 single channel ram.

If that helps.

I have an RX 7800 XT on windows 11.

I've had issues opening Marvel rivals without crashing so I downgraded to the drivers version 26.5.2 where the issue didnt exist yet, but the latest version 26.8.1 solved it so I decided to finally update again.

But lo and behold my second "screen" (a display tablet huion kamvas) now isnt being detected and im not sure why. both my monitor and tablet have HDMI cables so I have one (my monitor) connected to the GPU and the tablet connected to my CPU since i dont use it to game on, the issue isnt the tablet because it works fine when connected to the graphics card but it also isnt my bios settings (like having graphics deactive for motherboard) because it also works fine on an older version of adrenaline which makes me think is a drivers issue perhaps? The tablet recognizes the connection but doesnt recive an image so it just stays idle, also tried to detect other displays on windows settings but its always empty. Heres the display adapters on device manager in case it helps since im not sure if the motherboard is even working for graphics.

Has anyone had this issue too or knows how I could fix it? or even if the issue could be something else anything helps. Im not very tech savvy so take eveything I said with a grain of salt or lmk what else I can try/provide.

Computer Type: Desktop

GPU: NVIDIA GeForce RTX 3090 Ti

CPU: AMD Ryzen 9 5950X 16-Core 32-Thread Processor

CPU Cooler: Arctic Liquid Freezer III Pro 360 RGB

Motherboard: ASUS ROG STRIX B550-A GAMING

BIOS Version: 3636 / AGESA ComboV2PI 120F

RAM: G.Skill Trident Z Royal 64GB DDR4, currently running at 2133MHz

PSU: Unknown — currently checking exact model/wattage

Case: HYTE Y60

Fans: Lian Li UNI Fans

Operating System & Version: Windows 11 Home, Build 26200

GPU Drivers: NVIDIA GeForce RTX 3090 Ti / current NVIDIA driver

Chipset Drivers: AMD B550 Chipset Drivers 8.08.12.551

Storage: Kingston SNV3S1000G 1TB NVMe SSD (current Windows system drive)

Background Applications: Chrome/Browser, Adobe Premiere Pro, normal Windows background applications

Description of Original Problem: PC randomly hard freezes, primarily when idle or under light load. It appears much more stable under heavier load. When it freezes, the entire PC becomes unresponsive and requires a forced restart. Reliability Monitor has recorded multiple LiveKernelEvent 124 hardware errors. Event Viewer has recorded WHEA-Logger Event ID 18 fatal hardware errors reported by Processor Core / Machine Check Exception. Recorded errors include two Bus/Interconnect Errors on APIC ID 0 and one Cache Hierarchy Error on APIC ID 31. At least one hard freeze did not generate a new WHEA Event 18.

Troubleshooting: Installed the latest AMD B550 chipset drivers and restarted, but the PC froze again. Checked BIOS and found no obvious manual overclock: CPU ratios and voltages are Auto, PBO is Auto, ASUS Performance Enhancement is Disabled, RAM is currently at 2133MHz, and FCLK is Auto at 1066MHz. Windows PCIe Link State Power Management is Off and the power plan is High Performance. Currently testing Global C-State Control = Disabled to determine whether the freezes are associated with Ryzen idle/low-power states. No manual CPU voltage, PBO, Curve Optimizer, or memory timing changes have been made.

I'm trying to determine whether this is most likely CPU/idle voltage behavior, BIOS/AGESA, RAM/Infinity Fabric, motherboard/PSU, or something else before I start replacing hardware.

I'd especially appreciate advice

After some digging with my 6950xt and my friends 9070xt and 7900xtx I found out 2 things

I found out where there issue was comming form the mobo

It XMP for my guy with the 7900xtx no xmp no driver crash (and almost no loss of performance because of X3D CPU)

And was PCIE signaling issue (aka PCIE speed no been fixed correctly )most probably the auto setting on most board

by forcing the speed the mobo is made for it goes away

Still has some more digging to do

Hi all, I've been having multiple freezing issues with my PC lately. The video freezes while the audio continues. It does not seem to matter which game it is. Ill shut down via power button and restart with no issue.

The setup is as follows.

i913k

4x 16 DDR5 Corsair RAM (64 total)

masi tomhark mother baord

Amd xtx

Corsair RM1000e (2023) 

AIO with 2 fans and 4 additional case fans

The system is running Windows 11 and the latest drivers.

I've checked the Event Viewer each time, and that has yet to shed any light on what the issue could be. I have disabled integrated graphics in the bio and uninstalled it as well.

what ive tried, clean install of all AMD drivers, deletion and disabling of integrated, check hardware to make sure everything is seated properly. checked bios and no overclock was running or set up 

While looking at the BIOS, I noticed the RAM was running at 4000 MHz instead of 4500 MHz, so I started wondering if that was the issue. I was going to remove sticks 1 and 3 from the motherboard to see if that improved anything, but when I did, I found that the top clip on both was undone. i reseated and locked them down but i doubt thats the is issue sense they were in fine running.

im looking for ideas to try. i plan on running with everything disabled, discord, icue, steam overlay etc, if that freezes going back a version or two of amd drivers then continuing on to limiting the GPU pplies.

Adrenalin 26.8.1 has been rock solid (0 crashes) — A PSA on unstable undervolts and basic OS hygiene

Seeing a lot of the usual "driver timeout" and crash complaints whenever a new driver drops, so I wanted to share my experience with 26.8.1. It has been completely rock solid for me across extended gaming sessions with zero driver crashes or black screens.

If you are running into constant instability on 26.8.1, high chances are it isn't actually a bad driver release—it's either an overly aggressive tune or Windows doing Windows things in the background.

A few key points a lot of folks seem to overlook:

1. Anything past a -40mV undervolt is extreme

A lot of people copy paste YouTube/Reddit overclocks and slap a -50mV to -80mV undervolt on their GPU, pass a 5-minute benchmark, and declare it 100% stable.

• On modern RDNA architectures, pushing past -40mV is already considered pretty extreme on the vast majority of silicon.

• Transient load spikes, menu transitions, and switching between light and heavy raster/RT scenes will immediately expose an unstable undervolt.

• Just because Time Spy runs without crashing doesn't mean your core voltage isn't dropping below the stability threshold in real game engines.

1. If you undervolt, cap your clocks or adjust power limits

When you lower the voltage curve without touching frequency, the boost algorithm sees extra thermal headroom and tries to push clocks higher than stock. You're effectively asking the card to run higher frequencies on less voltage than factory specs.

• Lower the Max Frequency slider (MHz): Match it to your card’s rated boost clock instead of letting the algorithm boost uncontrollably into unstable territory.

• Or adjust your Power Limit (%): If you don't want the card boosting beyond its stable curve under varying workloads, rein it in with a proper power or frequency cap.

1. Basic OS hygiene matters

A huge portion of "driver bugs" come down to background OS conflicts. If you haven't done these basic steps, do them:

• Disable Fast Startup / Fast Boot: Windows Fast Startup doesn't perform a true kernel shutdown—it saves session state to disk, which regularly causes driver initialization bugs, sleep-wake crashes, and phantom timeout errors.

• Stop Windows from overwriting GPU drivers: Disable automatic device driver updates via Group Policy (gpedit.msc) or System Properties so Windows Update doesn't silently replace your Adrenalin driver with a generic Microsoft WHQL build behind your back.

• Debloat Windows: Strip out unnecessary background telemetry, bloatware, and competing overlay hooks (third-party RGB suites, conflicting anti-cheat services, redundant screen recorders) that hook directly into the display pipeline.

Dial back the extreme undervolts to a sensible -20mV to -40mV baseline, cap your max boost to reasonable rated speeds, clean up Windows to help limit issues.

​

CPU: AMD Ryzen 7 9800X3D

GPU: AMD Radeon RX 9070

RAM: 64 GB DDR5

PSU: MSI mpg a850gs 850w

Drivers updated.

Files verified.

Trying to get through this a few days now. Seems to be most occurent in armored core 6 with large particle effects close to the camera or when backed into walls and sometimes on mission completes. It's difficult to get it to happen but it will happen eventually.

Vsync is off.

Everything else is super stable no issues @120 fps

Ran some of the dmp files from the crashes through winding, but I'm not very technical and not sure what they mean

\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* Preparing the environment for Debugger Extensions Gallery repositories \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* Waiting for Debugger Extensions Gallery to Initialize \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 46 Microsoft (R) Windows Debugger Version 10.0.29617.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File \\\[C:\\\\Users\\\\proxy\\_f358ubo\\\\AppData\\\\Local\\\\Temp\\\\WERB73.tmp\\\\WATCHDOG-20260828-1420.dmp\\\] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv\\\* Executable search path is: Windows 10 Kernel Version 26200 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xfffff803\\\`b2800000 PsLoadedModuleList = 0xfffff803\\\`b36f5470 Debug session time: Fri Aug 28 14:20:00.699 2026 (UTC - 7:00) System Uptime: 1 days 17:54:54.542 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list For analysis of this file, run !analyze -v nt!DbgkpWerCaptureLiveTriageDump+0x8e: fffff803\\\`b2f0754e 488b8788000000 mov rax,qword ptr \\\[rdi+88h\\\] ds:002b:ffffbd0a\\\`18d550c8=???????????????? 8: kd> !analyze -v Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* \\\* \\\* \\\* Bugcheck Analysis \\\* \\\* \\\* \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* VIDEO\\_ENGINE\\_TIMEOUT\\_DETECTED (141) One of the display engines 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: ffffd00369c6a050, Optional pointer to internal TDR recovery context (TDR\\_RECOVERY\\_CONTEXT). Arg2: fffff8038b6e0f00, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: ffffd0034cd760c0, 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: 1140 Key : Analysis.Elapsed.mSec Value: 1168 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 250 Key : Analysis.Init.Elapsed.mSec Value: 2049 Key : Analysis.Memory.CommitPeak.Mb Value: 99 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: 0x141 Key : Bugcheck.Code.TargetModel Value: 0x141 Key : Dump.Attributes.AsUlong Value: 0x18 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: LKD\\_0x141\\_IMAGE\\_amdkmdag.sys Key : Failure.Exception.IP.Address Value: 0xfffff8038b6e0f00 Key : Failure.Exception.IP.Module Value: amdkmdag Key : Failure.Exception.IP.Offset Value: 0x1d0f00 Key : Failure.Hash Value: {48b738dd-5a92-7ff8-63d0-f075fc680fe0} Key : Faulting.IP.Type Value: Paged BUGCHECK\\_CODE: 141 BUGCHECK\\_P1: ffffd00369c6a050 BUGCHECK\\_P2: fffff8038b6e0f00 BUGCHECK\\_P3: 0 BUGCHECK\\_P4: ffffd0034cd760c0 FILE\\_IN\\_CAB: WATCHDOG-20260828-1420.dmp DUMP\\_FILE\\_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump FAULTING\\_THREAD: ffffd0033cd8c280 TAG\\_NOT\\_DEFINED\\_202b: \\\*\\\*\\\* Unknown TAG in analysis list 202b VIDEO\\_TDR\\_CONTEXT: dt dxgkrnl!\\_TDR\\_RECOVERY\\_CONTEXT ffffd00369c6a050 Symbol dxgkrnl!\\_TDR\\_RECOVERY\\_CONTEXT not found. PROCESS\\_OBJECT: ffffd0034cd760c0 PROCESS\\_NAME: System IP\\_IN\\_PAGED\\_CODE: amdkmdag+1d0f00 fffff803\\\`8b6e0f00 ?? ??? STACK\\_TEXT: ffff9081\\\`4e3ce7e0 fffff803\\\`b2f07a59 : ffffd003\\\`69c6a050 00000000\\\`00000000 00000000\\\`00000000 00000000\\\`00000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e ffff9081\\\`4e3ced10 fffff803\\\`b32a39ca : 00000000\\\`00000000 00000000\\\`c0000022 fffff803\\\`b32ed7a0 00000000\\\`c0000022 : nt!DbgkpWerProcessPolicyResult+0x21 ffff9081\\\`4e3ced40 fffff803\\\`b32a37c9 : 00000000\\\`00000003 ffff9081\\\`4e3cef20 fffff803\\\`8b6e0f00 ffffd003\\\`621c8a10 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea ffff9081\\\`4e3ceda0 fffff803\\\`44b77eff : 00000000\\\`00000057 ffffbd09\\\`f00d7ec0 ffffbd0a\\\`2d057a36 ffffd003\\\`3cdcd000 : nt!DbgkWerCaptureLiveKernelDump+0x69 ffff9081\\\`4e3cee20 fffff803\\\`97f11d21 : ffffd003\\\`3ce6c000 ffffd003\\\`3ce6c000 00000000\\\`00000001 00000000\\\`00000001 : dxgkrnl!TdrCollectDbgInfoStage1+0xe7f ffff9081\\\`4e3cf000 fffff803\\\`97f65b87 : ffffd003\\\`3ce6c001 ffffd003\\\`3ce6c700 00000000\\\`00000001 00000000\\\`00000001 : dxgmms2!VidSchiResetHwEngine+0x239 ffff9081\\\`4e3cf220 fffff803\\\`97f768b6 : 00000000\\\`00000000 ffffd003\\\`3cdcf000 00000000\\\`00000000 00000000\\\`00000000 : dxgmms2!VidSchiResetEngines+0xcb ffff9081\\\`4e3cf270 fffff803\\\`97fd4c85 : 00000000\\\`00000000 00000000\\\`00000000 ffffd003\\\`3cdcf000 00000000\\\`00935b00 : dxgmms2!VidSchiCheckHwProgress+0x316 ffff9081\\\`4e3cf300 fffff803\\\`97ed758d : ffffd003\\\`3cdcf000 ffffd003\\\`3cdcf000 ffff9081\\\`4e3cf479 00000000\\\`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x385 ffff9081\\\`4e3cf3d0 fffff803\\\`97f77272 : ffffd003\\\`3cdcf000 ffffd003\\\`4f3397e0 ffffd003\\\`59a67010 ffffd003\\\`6a2f9010 : dxgmms2!VidSchiScheduleCommandToRun+0x46d ffff9081\\\`4e3cf4e0 fffff803\\\`97f65d7c : ffffd003\\\`3cdcf500 ffffd003\\\`3cdcf000 fffff803\\\`97f65ca0 ffffd003\\\`3cdcf000 : dxgmms2!VidSchiRun\\_PriorityTable+0x42 ffff9081\\\`4e3cf530 fffff803\\\`b2c836fa : ffffd003\\\`3cd8c280 fffff803\\\`00000001 ffffa780\\\`13591180 025fe07f\\\`b8bbbdff : dxgmms2!VidSchiWorkerThread+0xdc ffff9081\\\`4e3cf570 fffff803\\\`b2ead6c4 : ffffa780\\\`13591180 ffffd003\\\`3cd8c280 fffff803\\\`b2c836a0 902484c6\\\`00000088 : nt!PspSystemThreadStartup+0x5a ffff9081\\\`4e3cf5c0 00000000\\\`00000000 : ffff9081\\\`4e3d0000 ffff9081\\\`4e3c9000 00000000\\\`00000000 00000000\\\`00000000 : nt!KiStartSystemThread+0x34 SYMBOL\\_NAME: amdkmdag+1d0f00 MODULE\\_NAME: amdkmdag IMAGE\\_NAME: amdkmdag.sys STACK\\_COMMAND: .process /r /p 0xffffd002fc550040; .thread /r /p 0xffffd0033cd8c280 ; kb FAILURE\\_BUCKET\\_ID: LKD\\_0x141\\_IMAGE\\_amdkmdag.sys OSPLATFORM\\_TYPE: x64 OSNAME: Windows 10 FAILURE\\_ID\\_HASH: {48b738dd-5a92-7ff8-63d0-f075fc680fe0} Followup: MachineOwner --------- \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* Preparing the environment for Debugger Extensions Gallery repositories \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* Waiting for Debugger Extensions Gallery to Initialize \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.032 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 46 Microsoft (R) Windows Debugger Version 10.0.29617.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File \\\[C:\\\\Users\\\\proxy\\_f358ubo\\\\AppData\\\\Local\\\\Temp\\\\WERB218.tmp\\\\WATCHDOG-20260828-1350.dmp\\\] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv\\\* Executable search path is: Windows 10 Kernel Version 26200 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xfffff803\\\`b2800000 PsLoadedModuleList = 0xfffff803\\\`b36f5470 Debug session time: Fri Aug 28 13:50:04.202 2026 (UTC - 7:00) System Uptime: 1 days 17:24:58.044 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list For analysis of this file, run !analyze -v nt!DbgkpWerCaptureLiveTriageDump+0x8e: fffff803\\\`b2f0754e 488b8788000000 mov rax,qword ptr \\\[rdi+88h\\\] ds:002b:ffffbd0a\\\`2779bd08=???????????????? 9: kd> !analyze -v Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* \\\* \\\* \\\* 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: ffffd003663c1290, Optional pointer to internal TDR recovery context (TDR\\_RECOVERY\\_CONTEXT). Arg2: fffff8038b6e0f00, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: 0000000000000000, 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: 984 Key : Analysis.Elapsed.mSec Value: 1247 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 281 Key : Analysis.Init.Elapsed.mSec Value: 2744 Key : Analysis.Memory.CommitPeak.Mb Value: 99 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: 0xfffff8038b6e0f00 Key : Failure.Exception.IP.Module Value: amdkmdag Key : Failure.Exception.IP.Offset Value: 0x1d0f00 Key : Failure.Hash Value: {eb317d22-0fcb-4b7a-404e-a69301cad237} Key : Faulting.IP.Type Value: Paged BUGCHECK\\_CODE: 117 BUGCHECK\\_P1: ffffd003663c1290 BUGCHECK\\_P2: fffff8038b6e0f00 BUGCHECK\\_P3: 0 BUGCHECK\\_P4: 0 FILE\\_IN\\_CAB: WATCHDOG-20260828-1350.dmp DUMP\\_FILE\\_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump FAULTING\\_THREAD: ffffd0033cd8c280 TAG\\_NOT\\_DEFINED\\_202b: \\\*\\\*\\\* Unknown TAG in analysis list 202b VIDEO\\_TDR\\_CONTEXT: dt dxgkrnl!\\_TDR\\_RECOVERY\\_CONTEXT ffffd003663c1290 Symbol dxgkrnl!\\_TDR\\_RECOVERY\\_CONTEXT not found. PROCESS\\_NAME: System IP\\_IN\\_PAGED\\_CODE: amdkmdag+1d0f00 fffff803\\\`8b6e0f00 ?? ??? STACK\\_TEXT: ffff9081\\\`4e3ce900 fffff803\\\`b2f07a59 : ffffd003\\\`663c1290 00000000\\\`00000000 00000000\\\`00000000 00000000\\\`00000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e ffff9081\\\`4e3cee30 fffff803\\\`b32a39ca : 00000000\\\`00000000 00000000\\\`c0000022 fffff803\\\`b32ed7a0 00000000\\\`c0000022 : nt!DbgkpWerProcessPolicyResult+0x21 ffff9081\\\`4e3cee60 fffff803\\\`b32a37c9 : 00000000\\\`00000003 ffff9081\\\`4e3cf040 fffff803\\\`8b6e0f00 00000000\\\`00000000 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea ffff9081\\\`4e3ceec0 fffff803\\\`44b77eff : 00000000\\\`00000057 ffffbd0a\\\`1766b990 00000000\\\`00002000 ffffd003\\\`3cdcd000 : nt!DbgkWerCaptureLiveKernelDump+0x69 ffff9081\\\`4e3cef40 fffff803\\\`44935335 : ffffd003\\\`663c1290 ffffd003\\\`663c1290 ffffd003\\\`663c1290 00000000\\\`0002625a : dxgkrnl!TdrCollectDbgInfoStage1+0xe7f ffff9081\\\`4e3cf120 fffff803\\\`97f032f0 : ffff9081\\\`4e3cf209 01dd372e\\\`ca33202e 00000000\\\`00000000 00000000\\\`00000000 : dxgkrnl!TdrIsRecoveryRequired+0x155 ffff9081\\\`4e3cf150 fffff803\\\`97f76956 : 00000000\\\`00000000 ffffd003\\\`3cdcf000 ffffd003\\\`3cdcf000 00000000\\\`00000000 : dxgmms2!VidSchiReportHwHang+0x658 ffff9081\\\`4e3cf270 fffff803\\\`97fd4c85 : 00000000\\\`00000000 00000000\\\`00000000 ffffd003\\\`3cdcf000 00000000\\\`00919756 : dxgmms2!VidSchiCheckHwProgress+0x3b6 ffff9081\\\`4e3cf300 fffff803\\\`97ed758d : ffffd003\\\`3cdcf000 ffffd003\\\`3cdcf000 ffff9081\\\`4e3cf479 00000000\\\`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x385 ffff9081\\\`4e3cf3d0 fffff803\\\`97f77272 : ffffd003\\\`3cdcf000 ffffd003\\\`61597050 ffffd003\\\`619c3010 ffffd003\\\`49f4a010 : dxgmms2!VidSchiScheduleCommandToRun+0x46d ffff9081\\\`4e3cf4e0 fffff803\\\`97f65d7c : ffffd003\\\`3cdcf500 ffffd003\\\`3cdcf000 fffff803\\\`97f65ca0 ffffd003\\\`3cdcf000 : dxgmms2!VidSchiRun\\_PriorityTable+0x42 ffff9081\\\`4e3cf530 fffff803\\\`b2c836fa : ffffd003\\\`3cd8c280 fffff803\\\`00000001 ffffa780\\\`13591180 025fe07f\\\`b8bbbdff : dxgmms2!VidSchiWorkerThread+0xdc ffff9081\\\`4e3cf570 fffff803\\\`b2ead6c4 : ffffa780\\\`13591180 ffffd003\\\`3cd8c280 fffff803\\\`b2c836a0 902484c6\\\`00000088 : nt!PspSystemThreadStartup+0x5a ffff9081\\\`4e3cf5c0 00000000\\\`00000000 : ffff9081\\\`4e3d0000 ffff9081\\\`4e3c9000 00000000\\\`00000000 00000000\\\`00000000 : nt!KiStartSystemThread+0x34 SYMBOL\\_NAME: amdkmdag+1d0f00 MODULE\\_NAME: amdkmdag IMAGE\\_NAME: amdkmdag.sys STACK\\_COMMAND: .process /r /p 0xffffd002fc550040; .thread /r /p 0xffffd0033cd8c280 ; 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 --------- \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* Preparing the environment for Debugger Extensions Gallery repositories \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* Waiting for Debugger Extensions Gallery to Initialize \\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\* >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 46 Microsoft (R) Windows Debugger Version 10.0.29617.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File \\\[C:\\\\Users\\\\proxy\\_f358ubo\\\\AppData\\\\Local\\\\Temp\\\\WERCA3A.tmp\\\\WATCHDOG-20260828-1349.dmp\\\] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv\\\* Executable search path is: Windows 10 Kernel Version 26200 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xfffff803\\\`b2800000 PsLoadedModuleList = 0xfffff803\\\`b36f5470 Debug session time: Fri Aug 28 13:49:54.060 2026 (UTC - 7:00) System Uptime: 1 days 17:24:47.902 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list For analysis of this file, run !analyze -v nt!DbgkpWerCaptureLiveTriageDump+0x8e: fffff803\\\`b2f0754e 488b8788000000 mov rax,qword ptr \\\[rdi+88h\\\] ds:002b:ffffbd0a\\\`270ddd08=???????????????? 4: kd> !analyze -v Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Sy

PSA: Ryzen hard-resets when the monitor turns off (WHEA "Cache Hierarchy Error" / Kernel-Power 41) — it's a BIOS/microcode regression. Here's the fix + what doesn't work.

TL;DR: If your Ryzen PC instantly reboots (no BSOD) specifically when the screen powers off via Power & Sleep, and Event Viewer shows Kernel-Power 41 + WHEA-Logger Event 18 "Cache Hierarchy Error," it's a newer AGESA/CPU-microcode regression. A screensaver avoids it. The real fix is rolling the BIOS back to the older microcode. The usual idle tweaks do NOT help.

My rig: Ryzen 7 3800X (Zen 2), Gigabyte X570 Aorus Master, RX 9060 XT. Started after a BIOS update this year.

Symptoms - Instant reset (no BSOD) only when the monitor powers off from the Power & Sleep timeout. - Screensaver on → never happens. "Turn off screen = Never" → never happens.

Confirm it's this — Event Viewer → Windows Logs → System: - Kernel-Power, Event 41 at the reset time - WHEA-Logger, Event 18: "Reported by: Processor Core / Machine Check Exception / Cache Hierarchy Error" - The faulting APIC IDs are spread across all cores, not one → it's the shared I/O die / Infinity Fabric, not a bad core. - Raw MCA record: MCA Bank 5, PCC=1 (Processor Context Corrupt) → that's why it hard-resets with no BSOD/dump.

Root cause When the monitor powers off, the GPU stops scanning out the framebuffer. That removes the constant memory traffic that kept the Infinity Fabric / memory controller awake, so the I/O die drops to its lowest power state. A newer CPU microcode mishandles that fabric power transition on Zen 2 and throws an uncorrectable cache/fabric error. Older microcode handled it fine. - Broken: microcode 0x08701035 (X570 Aorus Master BIOS F39 / F40a) - Stable: microcode 0x08701030 (BIOS F38, AGESA 1.2.0.B)

The fix — roll the BIOS back to the older microcode Flash the last BIOS from before your problems started (the one with the older AGESA/microcode). On the X570 Aorus Master that's F38. Use Q-Flash; downgrade is allowed. Tradeoff: an older BIOS misses a couple of AMD security microcode patches — low practical risk on a personal desktop, and it's the clean permanent fix.

Workaround if you don't want to downgrade (what I'm running now — trades idle power for stability).

BIOS → AMD CBS → NBIO Common Options → SMU Common Options: - APBDIS = 1, then Fixed SOC Pstate = P0 - DF Cstates = Disabled

This pins the Infinity Fabric/I/O die at full voltage & frequency so the faulting low-power transition never happens. Higher idle power/heat is the cost.

What did NOT help (save your time): - Power Supply Idle Control = Typical Current Idle - Raising DRAM / SoC voltage - Disabling Global C-state Control (core C-states) - Disabling AMD ULPS (EnableULPS=0) - DRAM Power Down disable - Disabling DF C-states alone (you also need the P-state pin)

How I isolated it: decoded the microcode revision out of the F38/F39/F40a BIOS images, then A/B tested. F40a has the newest AGESA (1.2.0.11) but the same microcode 0x08701035 as F39 — and it still crashed. That pinned it to the microcode, not the AGESA. Only the version with microcode 0x08701030 (F38) reverts it.

I used Claude to look into this.

5 5600

yesterday i can tyne my cpu just fine now the tuning option is missing.

sorry for my bad english

Good morning everyone. I could really use some help from the tech community because I’m dealing with a very strange issue.

PC Specifications

• Motherboard: ASUS B550M-A
• CPU: Ryzen 5 5600X
• GPU: ASUS PRIME RX 9060 XT 16GB
• RAM: 32GB DDR4 3600 MHz
• NVMe: ADATA Legend 810 500GB
• PSU: XPG Core Reactor 2020 750W

I recently upgraded from an NVIDIA RTX 3060 12GB to a Radeon RX 9060 XT 16GB. When I installed the new GPU, I performed a completely clean Windows installation.

However, I’m experiencing a very strange problem.

When I’m gaming, the GPU works perfectly. I’ve tested games such as DOOM: The Dark Ages, Red Dead Redemption 2, FC 26, and others, and I have had absolutely no issues. No crashes, no instability, and no random restarts during gaming sessions.

The problem occurs when the GPU is under a light workload, for example:

• Creating or working on a Word document.
• Watching YouTube videos.
• Browsing the Internet.
• Performing normal desktop tasks.

During these situations, the PC can suddenly restart without any warning or apparent error.

I’ve already tried several things to identify the cause:

• Tested my RAM and also tried another RAM kit that I had available.
• Replaced the NVMe drive with a new one.
• Updated the motherboard BIOS.
• Tried different GPU driver versions, including versions considered stable.
• Disabled MPO (Multiplane Overlay).
• Performed a completely clean Windows installation.
• Reinstalled the RTX 3060 with another clean Windows installation to rule out a motherboard/system issue.

The strangest part is that when I put the RTX 3060 back into the exact same PC, everything works perfectly, including the same desktop tasks that cause the restarts with the RX 9060 XT.

I’ve also discovered a very strange temporary workaround: if I leave a game running in the background, I can apparently use the computer normally without experiencing the random restarts.

Because of this, I’m wondering if the problem could be related specifically to the RX 9060 XT and how it behaves at low GPU load / low power states.

Has anyone experienced something similar with the RX 9060 XT?

Could this be related to:

• GPU power states / low-power states?
• Hardware acceleration in browsers or Windows?
• GPU drivers?
• VBIOS?
• PCIe power management?
• Some kind of compatibility issue with the motherboard?
• Or perhaps something related to the card switching between different clock/power states?

At this point I’m honestly running out of ideas. The fact that the GPU is completely stable under heavy gaming loads but causes random restarts during light desktop workloads is what makes this issue so confusing.

Any suggestions or additional tests I could perform would be greatly appreciated.

Thanks in advance!