AMD Radeon Driver Bug Is Wearing Out SSDs | What to Do Before the Fix Arrives

AMD has confirmed that a bug in its Radeon graphics drivers can make the AMD External Events Utility write to your SSD nonstop, even when your PC is idle. Most affected users see steady writes of about 0.3 to 1.5 MB/s, and one report reached about 5 MB/s. AMD says a fix should arrive with Adrenalin 26.11.1 later in November 2026. Until then, you can check your PC in two minutes and stop the writes by disabling the service.

Why This Bug Deserves Your Attention Today

Your SSD is supposed to rest when you are not using your PC. Games load, Windows updates, and files save, and then the drive goes quiet. That quiet time matters, because every SSD has a limited amount of writing it can handle over its life. The limit is generous for normal use, and most gamers never come close to it. But a driver bug that writes around the clock changes the math completely.

On November 9, 2026, AMD confirmed the problem. A background part of its Radeon driver, the AMD External Events Utility, can keep writing to the system drive without stopping. The PC can sit idle on the desktop with nothing open, and the writes keep going. AMD says the fix should come with the next driver release, Adrenalin 26.11.1, later this month. No exact date has been given yet.

This article explains what the amd radeon driver ssd writes bug actually does, how much wear it can really cause, how to check your own PC in a few minutes, and what to do right now. It also separates confirmed facts from scary claims that are still unverified, so you can act on evidence instead of panic. One note up front: this is breaking news from November 9, 2026, so these keywords may have no search volume yet. The story is new, and search data has not caught up with it.

 What Happened The Timeline So Far

This bug did not appear overnight. Reports about it go back months, but it took a viral Reddit post to push AMD into a clear public answer. Here is how the story unfolded.

July 2026: the first reports. Owners on AMD’s official support forum began reporting constant disk writes from the AMD External Events Utility. One early report came from a Radeon RX 7800 XT owner running Adrenalin 26.6.4, who saw the process reading and writing at about 2 MB/s. Process Monitor logs in that thread showed 600 MB written in just 10 minutes. At the time, the reports stayed inside forum threads and did not reach the wider tech press.

October 2026: AMD acknowledges the problem. An AMD representative posting as AMD_Matt said on AMD’s community forum that the company was investigating the reports and planned to fix the issue in a future driver release. Around the same time, the optional Adrenalin 26.10.2 driver arrived on October 30, 2026. Its release notes did not mention the write issue in either the fixed list or the known issues list, so updating to the newest driver did not solve it.

November 8, 2026: the Reddit post that broke the story open. Reddit user darklinkpower posted a warning on r/pcmasterrace collecting the reports in one place. The post described the External Events Utility writing at up to about 5 MB/s on an idle PC and warned that the constant writes could wear out SSDs. Within hours, tech sites picked it up, and Radeon owners started checking their own systems. Club386 was among the first to report the bug and the coming fix.

November 9, 2026: AMD confirms the cause and the fix. A second AMD representative, AMD_Vik, explained on Reddit that the problem appears to come from an interaction between the AMD External Events Utility and Microsoft’s PCIe filter driver. He said a fix had already been submitted by a colleague on the kernel-mode driver team, that it was considered low risk, and that it missed Adrenalin 26.10.2 but should be included in the next release, Adrenalin 26.11.1. He added that he could not give an exact date, only that the driver would arrive later in November 2026. VideoCardz reported AMD’s confirmation and the planned fix on November 9, 2026.

That is where things stand today. AMD has confirmed the bug, explained the likely cause, and pointed to a fix in the next driver. The exact release date is still unknown, and until the update is out and affected owners can confirm the writes have stopped, the real cost to SSD lifespans remains an estimate built on user-reported rates.

What the Bug Actually Does

To understand the bug, you need to know what the AMD External Events Utility is for. It is a Windows service that ships with AMD Software: Adrenalin Edition, the driver package for Radeon graphics cards. It handles display-related jobs such as monitor detection, display configuration changes, and Radeon Software hotkeys. It runs as two processes, atiesrxx.exe and atieclxx.exe. The second one, atieclxx.exe, known as the AMD External Events Client Module, is the process users caught writing to their drives.

On a healthy system, this service does almost nothing most of the time. It wakes up when you plug in a monitor, change a display setting, or press a hotkey, and then it goes quiet again. On affected systems, it never goes quiet. It writes small amounts of data to the system drive continuously, hour after hour, even when the PC is sitting idle on the desktop with no programs open.

AMD_Vik tied the behavior to an interaction between the External Events Utility and Microsoft’s PCIe filter driver. AMD has not published a deeper technical explanation, and the exact trigger is still unknown. What is known is that the writes are real, they are tied to this one service, and stopping the service stops the writes in user reports.

It helps to keep this bug separate from a related but different episode from November 2025. Back then, Reddit user Takia_Gecko found that AMD chipset drivers were writing to log files in the C:\Windows\System32\AMD\EEUDumps folder every time a window was moved or resized. That behavior also involved the AMD External Events Utility, and Tom’s Hardware covered it at the time, but the amounts of data involved were tiny, and experts concluded the practical risk to SSD life was probably minimal. The 2026 bug is different: the writes are continuous and measured in megabytes per second, not tiny log entries tied to moving windows. Do not mix the two stories up when you read older articles.

Who Is Affected by the AMD Radeon Driver SSD Writes Bug

The honest answer is that nobody knows the full list yet, because the bug does not hit every Radeon owner. Reports span several Adrenalin releases and several graphics cards, but plenty of owners on the same driver versions report no problem at all.

Driver versions with reports. Users have reported the constant writes on Adrenalin 26.5.2, 26.6.4, 26.7.1, 26.8.1, 26.9.2, 26.10.1, and 26.10.2. That is a wider range than the headlines suggest. The bug is not limited to the two newest drivers, even though 26.10.1 and 26.10.2 are the versions most often named in coverage. Some users say they saw no problem on Adrenalin 25.12.1 or 26.2.2, but that is based on individual reports, not on AMD testing, so treat it as a clue rather than a guarantee.

Graphics cards with reports. Reports name cards including the Radeon RX 7800 XT, RX 9060 XT, and RX 9070 XT. That range covers both current-generation RDNA 4 cards and older RDNA 3 cards, which suggests the bug is tied to the driver service rather than to one specific GPU model. If you own any Radeon card and run a recent Adrenalin driver, the check in this article is worth two minutes of your time.

Operating systems. Reports cover both Windows 10 and Windows 11 installations, including Windows 11 26H2. The bug is not limited to one Windows version.

The version number alone cannot tell you whether you are affected. One user on Adrenalin 26.10.2 with an RX 9070 XT reported no problem, while other users on the same version reported constant writes. The behavior appears to depend on the combination of system configuration, driver version, and software state. That is exactly why AMD has not named a cause beyond the interaction with the PCIe filter driver, and why the only reliable test is to look at your own PC, not to guess from your driver version.

The practical takeaway is simple. If you own a Radeon GPU, check. If you own an NVIDIA or Intel GPU, this bug does not apply to you, because the AMD External Events Utility is only installed with AMD drivers. And if you checked and found nothing, check again after your next driver update, since a version change can alter the behavior.

How Much Damage Can the Bug Really Do to Your SSD

This is the question everyone is asking, and it deserves a careful answer, because the scariest numbers floating around are worst-case math, not measured damage. Let us work through the numbers honestly.

What TBW means

Every SSD has an endurance rating called TBW, short for Terabytes Written. It tells you how much data the manufacturer rates the drive to handle over its expected life. A 1 TB drive might be rated at 600 TBW, a 2 TB drive at 1,200 TBW, and a budget QLC drive might be rated lower, around 400 TBW for 1 TB. These ratings vary widely by model, so always check your own drive’s spec sheet rather than assuming a number.

TBW is a rating, not a death date. A drive does not stop working the moment it passes its TBW rating. It is the manufacturer’s endurance promise, and drives often keep working well past it. But once you pass it, you are outside the rated life, and the risk of wear-related problems rises. That is why needless writes matter: they spend a budget you cannot get back.

The write-rate math

The damage depends entirely on the write rate, and reported rates vary a lot. Most affected users report between 0.3 and 1.5 MB/s. One Reddit report reached about 5 MB/s. Here is what each rate adds up to if it runs nonstop, day and night.

Write rate	Writes per day	Writes per month	Writes per year
0.3 MB/s	About 26 GB	About 0.8 TB	About 9 TB
0.5 MB/s	About 43 GB	About 1.3 TB	About 16 TB
1 MB/s	About 86 GB	About 2.6 TB	About 31 TB
1.5 MB/s	About 130 GB	About 3.9 TB	About 47 TB
5 MB/s	About 432 GB	About 13 TB	About 158 TB

The math is simple multiplication. A rate of 1 MB/s means 86,400 MB per day, which is about 86 GB. A rate of 5 MB/s means about 432 GB per day, or close to 13 TB in a month. These figures assume the writes never stop, which matches what affected users describe, but your PC is probably not on 24 hours a day, so your real totals will be lower if you shut down or sleep the machine.

Worked examples

Take a typical 1 TB drive rated at 600 TBW. At the common reported rate of 1.5 MB/s, running nonstop, the bug would add about 3.9 TB of writes per month. Divide 600 by 3.9 and you get about 154 months, or nearly 13 years, to reach the rated TBW from this bug alone. That sounds reassuring, and for a healthy drive with a high rating, it mostly is.

Now take the worst reported rate, 5 MB/s, on a budget 1 TB QLC drive rated at 400 TBW. That is about 13 TB per month, so 400 divided by 13 gives about 31 months, or roughly two and a half years, to reach the rated TBW from this bug alone. Add normal use on top of that, gaming installs, Windows updates, game downloads, and the picture gets worse. A drive that should have lasted a decade of normal use could burn through its rated endurance in a few years.

Now take the low end, 0.3 MB/s on a 2 TB drive rated at 1,200 TBW. That is about 0.8 TB per month, so reaching 1,200 TBW would take about 1,500 months. At that rate the bug is a nuisance, not a threat.

The point of these examples is not to pick one scary number. It is to show that the risk depends on three things: your write rate, your drive’s TBW rating, and how long the bug runs before you stop it. A high-end drive at a low write rate has little to fear. A budget drive at the highest reported rate has a real problem, especially if the bug runs for months unnoticed.

Two important caveats

First, the numbers above are host writes, meaning the amount of data the system sends to the drive. They do not directly measure how much data is physically written to the NAND flash chips inside the SSD. SSD controllers use caching, wear leveling, and other techniques to manage incoming data, so the physical NAND writes can be lower than the host writes. Tom’s Hardware made this exact point in its coverage: reported host writes do not directly establish how much data reaches the NAND flash. The real wear is probably lower than the raw math suggests, but nobody has measured it precisely for this bug, so do not treat the table above as a damage report. Treat it as a worst-case estimate.

Second, one alarming claim is circulating that a Radeon owner’s SSD lost 1 percent of its reported health every month for 16 months because of this bug. That claim comes from a single Reddit post and has not been independently verified. AMD has not confirmed any link between the bug and a specific health loss, and no publication has reproduced the result. It may be real, it may be coincidence, or it may be a drive that was already wearing out. Until someone verifies it, do not repeat it as fact, and do not use it to judge your own drive. Check your own total host writes instead, using the steps below, and let your own numbers decide how worried you should be.

Is This a Storage Bottleneck for Gamers

A bug that writes to your SSD all day sounds like it should slow your games down, but the honest answer is more complicated. A storage bottleneck happens when your drive cannot deliver data fast enough and your CPU or GPU ends up waiting. The classic signs are long load times, texture pop-in, and hitching when a game streams new areas. To understand the mechanics, it helps to know what a storage bottleneck actually is and how it differs from a CPU or GPU limit.

At the reported write rates, this bug is unlikely to saturate a modern NVMe drive. A rate of 1.5 MB/s is a tiny fraction of what even a budget NVMe SSD can handle, and it should not cause load-time problems on its own. That said, one Reddit report described stuttering and audio interruptions in a game, plus asset-loading issues in another title, and said disabling the AMD External Events Utility appeared to resolve the symptoms. That account is anecdotal. AMD has not confirmed that the disk activity causes game stuttering, asset-loading delays, or any other symptom, and no controlled test has established the link yet.

So where does that leave gamers? The main risk from this bug is endurance, not frame rates. The writes quietly spend your SSD’s write budget in the background while you play, and the cost shows up months later as wear, not today as stutter. If you do notice stuttering and your disk activity looks abnormal, the bug is worth checking, but do not assume it is the cause of every performance problem. A slow game can have many causes, and our FPS troubleshooting guide covers the usual suspects in order. The bug is one more item on that list now, not the whole list.

There is a second, subtler gaming angle. SSD health affects load times over the long run, and a drive that is wearing out can develop problems that look like a storage bottleneck. If your games have started loading slower than they used to, check your drive health before you blame your GPU. The steps below show you how, and if you find a genuine performance problem, our guide on how to increase FPS covers the fixes that actually move the needle.

How to Check If Your PC Is Affected

You do not need special skills or paid software to check. The whole test takes about two minutes, and you should do it with nothing else running so background programs do not confuse the result.

Step 1: Look at live disk activity in Resource Monitor

Resource Monitor is built into Windows and shows exactly which process is writing, and how fast.

1. Close your games, browser, and other programs, then wait about a minute so the system settles.
2. Press Win + R, type resmon, and press Enter.
3. Open the Disk tab.
4. In the Disk Activity list, click the Write (B/sec) column header to sort by write speed, highest first.
5. Watch for a minute. Look for atieclxx.exe or atiesrxx.exe near the top with a steady write rate.

If atieclxx.exe shows sustained writes, minute after minute, while nothing else is running, you are very likely affected. Normal background activity comes in bursts and then stops. This bug does not stop. Note that the writes can sometimes appear under the System process with a file path pointing to atieclxx.exe, so check the file path column if the numbers look odd.

Step 2: Check Task Manager as a cross-check

Task Manager is faster but less detailed. Press Ctrl + Shift + Esc, open the Processes tab, click the Disk column to sort, and look for AMD External Events Utility or atieclxx.exe holding a steady disk percentage while the PC is idle. Task Manager alone is not enough to confirm the bug, because it does not show write rates clearly, but it is a useful first glance before you open Resource Monitor.

Step 3: Check your total host writes in CrystalDiskInfo

Live activity tells you whether the bug is running right now. Total host writes tell you how much damage it may already have done. CrystalDiskInfo is a free tool that reads your drive’s own health data, and it is one of the best free benchmark and diagnostic tools you can keep on a gaming PC.

1. Download CrystalDiskInfo from its official website and install it.
2. Run it as administrator and select your system drive from the tabs at the top.
3. Read the Health Status badge first. Blue means Good, yellow means Caution, and red means Bad.
4. Find Total Host Writes and Percentage Used. Total Host Writes is the running total of everything your system has written to the drive since day one. Percentage Used tells you how much of the drive’s rated life is already spent.
5. Write both numbers down, with today’s date.

Now compare. If your drive is a year old and Total Host Writes is far higher than your actual use explains, for example hundreds of terabytes on a PC used mainly for gaming and browsing, something has been writing in the background. If you apply a workaround from the next section and check again in a week, the daily increase should drop back to normal levels. That before-and-after comparison is the most convincing test you can run at home.

Step 4: Use Windows built-in tools if you prefer not to install anything

On an NVMe drive, open Settings, then System, then Storage, then Advanced storage settings, then Disks and volumes, then Properties on your drive. Windows shows a health estimate there. For a deeper look, open PowerShell as administrator and run Get-PhysicalDisk | Get-StorageReliabilityCounter. That command prints Windows storage reliability counters, including write totals. These built-in tools show less detail than CrystalDiskInfo, and Windows only monitors NVMe drives in that settings page, not SATA drives, but they are enough to confirm whether your drive is healthy or already showing wear.

How often to re-check

Check once now, and check again after you install Adrenalin 26.11.1. That second check is the important one: it confirms the fix actually stopped the writes on your machine. If you apply a workaround today, check again in a week to confirm the daily write totals have dropped. A single check tells you the present. Two checks tell you the trend, and the trend is what matters for SSD life.

What to Do Right Now Three Workarounds That Work

AMD’s real fix is coming with Adrenalin 26.11.1, but that driver has no release date yet, and every day the bug runs is another day of needless writes. These three workarounds can stop the writes today. They are not official AMD fixes, and none of them works for everyone, so try them in order and verify with Resource Monitor after each one.

Workaround 1: Disable the AMD External Events Utility service

This is the most widely reported workaround, and the one most users should try first. It stops the service that generates the writes.

1. Press Win + R, type services.msc, and press Enter.
2. Find AMD External Events Utility in the list.
3. Right-click it, choose Properties, and set Startup type to Disabled.
4. Click Stop to end the service immediately, then click OK.
5. Open Resource Monitor again and watch for a few minutes to confirm the writes have stopped.

What you lose. The service handles monitor detection, some display configuration changes, and Radeon Software hotkeys. Disabling it may break Adrenalin hotkeys and could affect how your PC responds when you plug in or switch monitors. Some users have also reported side effects such as frame pacing changes in games, though those reports are anecdotal and not confirmed by AMD. One Reddit user reported that disabling the service caused frame timing problems on an RX 6700 XT, while others report no side effects at all. The safest approach is to test it yourself: disable the service, play your usual games for a day, and watch for anything unusual. If something breaks, re-enable the service and try the next workaround instead.

Re-enable it later. This is a temporary workaround, not a permanent change. When Adrenalin 26.11.1 arrives, install it, set the service back to Automatic, start it, and verify in Resource Monitor that the writes stay stopped with the service running. That confirms the fix works on your machine.

Workaround 2: Disable Resizable BAR in your BIOS

AMD_Vik also said that disabling Resizable BAR, often shortened to ReBAR, appears to work around the problem. Resizable BAR lets the CPU access the GPU’s full memory at once instead of in small chunks, and it can improve frame rates in some games. That is why this workaround has a real cost.

1. Restart your PC and enter the BIOS or UEFI setup, usually by pressing Del or F2 during boot.
2. Find the Resizable BAR setting, often under PCIe settings or in the same menu as Above 4G Decoding. The exact location varies by motherboard.
3. Set it to Disabled, save, and exit.
4. Boot into Windows and check Resource Monitor to confirm the writes have stopped.

What you lose. Disabling ReBAR can cost you a few percent of performance in games that benefit from it. How much depends on the game and the GPU, and many games will not change at all. Because of that cost, treat this as a second choice, not a first choice, and only if disabling the service did not work for you or caused side effects you cannot live with. Remember to re-enable ReBAR after you install the fixed driver, so you get the performance back.

Workaround 3: Roll back to an older driver

Some users report no problem on Adrenalin 25.12.1 or 26.2.2. If the first two workarounds fail, rolling back to one of those versions is worth trying, but do it carefully.

1. Download the older driver from AMD’s official website first, so you have it ready before you remove the current one.
2. Download Display Driver Uninstaller, known as DDU, and run it in Safe Mode to remove the current driver completely. A clean removal matters here, because leftover driver files can carry the problem into the new install.
3. Install the older driver, restart, and check Resource Monitor.

The catch. Rolling back means giving up newer game optimizations, bug fixes, and features that came with later drivers. It is a trade, and for most people it is only worth it if the writes are running at a high rate and the other workarounds failed. Also note that “unaffected on 25.12.1” is based on user reports, not on AMD testing, so a rollback is not guaranteed to help. Verify with Resource Monitor after every change, and never assume a workaround worked until you see the writes stop with your own eyes.

After the fix arrives: install Adrenalin 26.11.1

When Adrenalin 26.11.1 is released, install it through AMD Software or from AMD’s website, then check the release notes for a mention of the SSD write fix. AMD_Vik said the fix should appear in the release notes, so look for it before you assume you are protected. After installing, re-enable anything you disabled, the External Events Utility service and ReBAR, restart, and watch Resource Monitor for a few minutes. Then check CrystalDiskInfo again in a week and compare your daily write totals with the numbers you recorded before. If the writes are gone with the service running, the fix worked on your machine, and you can stop worrying about this bug.

What Not to Do

Panic leads to bad decisions, and this bug has already produced a few. Avoid these mistakes.

Do not delete AMD driver files by hand. Deleting atieclxx.exe or other files from the Windows System32 folder will break your driver installation and can leave you with a black screen or a PC that will not boot properly. Use the service disable or a proper driver rollback instead.

Do not rush out and buy a new SSD. A new drive does not fix the bug. The same driver will write to the new drive just as happily. Fix the cause first, then judge whether your current drive is actually worn enough to replace. Most affected drives will still have years of rated life left once the writes stop.

Do not install random registry fixes or scripts from forums. Unverified scripts that promise to stop the writes can change system settings you do not understand, and some are outright malware. Stick to the three workarounds above, all of which use built-in Windows tools or official AMD drivers.

Do not ignore it either. The opposite mistake is just as bad. The writes are small per second, so it is tempting to shrug and wait for the driver. But months of unnoticed writes on a budget drive add up, and the check takes two minutes. Check now, apply a workaround if you are affected, and re-check after the fix. That is the whole job.

The Bigger Picture Protecting Your Hardware in Late 2026

This bug lands at an awkward moment for PC builders. Hardware prices are moving in ways that make every component you already own more valuable. The Ryzen 7 9800X3D, the gaming CPU many builders want most, has returned to $399.99 at Newegg with promo code BFF36, according to VideoCardz on November 8, 2026, which makes it a tempting upgrade. At the same time, RAM prices are climbing, which raises the cost of any new build or upgrade. When replacement parts cost more, protecting the parts you already own matters more, and that includes the SSD quietly sitting under your graphics card.

That is the real lesson of this bug. A storage drive is easy to forget. It has no fan, no lights, and no frame rate counter. It just works, until the day it does not. A two-minute health check every few months costs nothing and catches problems while they are still cheap to fix. If this bug got you to open CrystalDiskInfo for the first time, keep the habit. Your future self, staring at a drive health report before a big game install, will be glad you did.

It is also worth remembering that a PC is a system, not a collection of parts. A driver bug in your graphics card can wear out your storage drive. A hot GPU can throttle and drag down a fast CPU. A slow drive can hold back a powerful graphics card. When you diagnose a problem, look at the whole machine, not just the part you suspect. Our guide comparing CPU bottlenecks and GPU bottlenecks explains how to tell which part is actually holding you back, and that skill matters far beyond this one bug. Heat is part of the same picture: if your graphics card is running hot, read our explainer on GPU thermal throttling before you assume a driver is the problem.

Frequently Asked Questions

How do I know if my PC is affected by the AMD Radeon driver SSD writes bug?

Open Resource Monitor by pressing Win + R, typing resmon, and pressing Enter. Go to the Disk tab, sort by Write (B/sec), and watch for a minute with nothing else running. If atieclxx.exe shows steady, continuous writes while the PC is idle, you are likely affected. Confirm it with CrystalDiskInfo by checking Total Host Writes and Percentage Used, and compare the numbers again in a week to see how fast they are growing.

Will the AMD driver bug kill my SSD?

Probably not on its own, and not quickly, but it depends on your drive and your write rate. At the most common reported rates of 0.3 to 1.5 MB/s, the extra writes amount to roughly 0.8 to 3.9 TB per month, which would take many years to reach the rated TBW of a typical drive. At the highest reported rate of about 5 MB/s, a budget drive with a low TBW rating could reach its rated endurance in a few years. AMD has not confirmed any specific lifespan impact, and host writes do not translate directly into NAND wear, so treat the scary numbers as worst-case estimates, check your own drive, and stop the writes if you are affected.

Is it safe to disable AMD External Events Utility?

For most users, yes, as a temporary workaround, but it has trade-offs. Disabling the service stops the writes in user reports, and many people notice no side effects. However, the service handles monitor detection and Radeon Software hotkeys, so those features may stop working, and some users have reported frame pacing changes in games. Test it yourself for a day with your usual games. If something breaks, re-enable the service and try disabling Resizable BAR instead. Remember to set the service back to Automatic after you install the fixed driver.

Does disabling Resizable BAR fix the SSD writes?

AMD representative AMD_Vik said disabling Resizable BAR appears to work around the problem, and some users report that it stops the writes. It does not work for everyone, so verify with Resource Monitor after you change the setting. The cost is real: Resizable BAR can improve frame rates in some games, so you may lose a few percent of performance while it is off. Re-enable it after installing Adrenalin 26.11.1 and confirm the writes stay stopped.

Should I roll back to an older AMD driver?

Only if the other workarounds fail. Some users report no problem on Adrenalin 25.12.1 or 26.2.2, but that is based on individual reports, not AMD testing, so a rollback is not guaranteed to help. Rolling back also means losing newer game optimizations and fixes. If you do roll back, download the older driver from AMD’s website first, remove the current driver cleanly with Display Driver Uninstaller in Safe Mode, install the older driver, and verify in Resource Monitor that the writes have stopped.

When will Adrenalin 26.11.1 be released?

AMD has not given an exact date. AMD_Vik said the fix should be included in Adrenalin 26.11.1 and that the driver is expected later in November 2026. Check AMD’s release notes when the driver appears, and look for a mention of the SSD write fix before assuming you are protected. Until then, use one of the workarounds in this article and keep checking your drive.

Key Takeaways

• AMD has confirmed that a bug in its Radeon drivers can make the AMD External Events Utility write to your SSD nonstop, even when your PC is idle.
• Most affected users see writes of about 0.3 to 1.5 MB/s, and one report reached about 5 MB/s. Reports span Adrenalin 26.5.2 through 26.10.2, and not every owner on those versions is affected.
• The fix is expected in Adrenalin 26.11.1 later in November 2026, with no exact date announced yet.
• Check your PC with Resource Monitor and CrystalDiskInfo. Live writes tell you if the bug is running now, and Total Host Writes tells you how much it may already have cost you.
• Disabling the AMD External Events Utility service is the best first workaround. Disabling Resizable BAR and rolling back to an older driver are backups if the first option fails or causes side effects.
• Host writes are not the same as physical NAND wear, and the widely shared claim of 1 percent health loss per month is a single unverified Reddit report, not a confirmed fact.
• Re-enable everything you disabled after installing the fixed driver, and verify the writes have stopped.

Conclusion

The amd radeon driver ssd writes bug is a real problem with a real fix on the way, and it is also a useful reminder that the most dangerous PC problems are the quiet ones. Nothing crashed. No error message appeared. A background service simply kept writing, a megabyte or two at a time, while the PC sat idle. Left alone for months, those megabytes would have added up to terabytes of wear on drives that did nothing to deserve it.

You now know how to find out if your PC is affected, how to read the numbers honestly, and how to stop the writes today. The check takes two minutes. The workaround takes five. The fixed driver should arrive before the end of November 2026, and when it does, a final check will confirm the story is over on your machine.

Do the check tonight, before you launch your next game. Your SSD will not thank you, because SSDs cannot talk, but it will last longer, and that is the same thing. If this article helped you catch the bug, share it with another Radeon owner. They may be running the same driver, on the same idle desktop, with the same quiet writes, and they may not know yet.