AMD承认GPU驱动Bug持续写入数据磨损SSD

固态硬盘(SSD)一天中大部分时间几乎无事可做,尤其在 PC 闲置时更是如此。但对部分 AMD Radeon 系统来说,情况可能并非如此——有报告称,随 Radeon 驱动一同安装的 AMD External Events Utility(EEU)可能持续向系统盘写入数据,即便电脑几乎无人使用。11 月 8 日,Reddit 用户“darklinkpower”再次引发关注,指出多起关于这种异常硬盘活动的报告。
一位 Radeon 用户称,这个问题已悄然侵蚀其硬盘报告的健康度超过一年,他写道:“我刚发现,这驱动每个月吃掉我 SSD 1% 的健康度,已经持续 16 个月了。”另一位用户报告称,其 PC 闲置时写入速度持续约为 5MB/s。还有人称,自己的 SSD 健康度在 16 个月里每月下降约 1%。AMD 已承认该问题。在 10 月 21 日公司社区论坛的回复中,一位公司代表确认他们正在调查。“是的。我们正在调查,目标是在未来的驱动版本中解决它。”他说。另一位代表 AMAD Vik 随后在 Reddit 上给出了更令人鼓舞的更新,他致歉并表示:“希望下一个版本就能修复。”
值得注意的是,EEU 并非完全陌生的“元凶”。去年 11 月,就出现过一起涉及 AMD 芯片组驱动的类似问题:一位 Reddit 用户称,他发现每当屏幕上的元素被移动或缩放时,该软件就会反复更新一个日志文件。该事件当时也引发了疑问:停止该服务是否会影响 FreeSync。不过,最新的报告是另一回事:一些用户现在看到的写入几乎不停歇,即便他们的 PC 什么也没做。
这些数字值得一看。以 5 MB/s 的速度,一块 SSD 每小时会承受约 18GB 的主机写入。一整天下来就是 432GB,而一个月不间断运行可能让这一数字接近 13TB。不过,这并不一定意味着数据真的被写入了 NAND 闪存本身。SSD 主控会使用缓存、磨损均衡等技术来管理传入的数据。因此,这些报告出的活动中有多少转化为实际的闪存磨损,目前仍不得而知。该用户声称每月损失 1% 的硬盘健康度,也尚未得到独立证实。
此外,不同 Radeon 驱动版本之间似乎也没有明显规律。相关报告既涉及运行 Adrenalin 26.19.2 的系统,也涉及更早的版本,这表明问题可能并不局限于最新的更新。AMD 于 10 月 30 日发布的 Adrenalin 26.20.2 版本说明中也没有提及该问题。就目前而言,很难说是哪些驱动版本、硬件组合或系统配置导致了这一问题。
尽管如此,目前有两种被报告的变通方法。第一种是按下 Win + R 打开 Windows 服务应用,输入 services.msc,然后找到 AMD EEU。用户可以停止该服务,或将其启动类型改为“禁用”。这似乎能阻止过多的写入,但不一定是个干净的解决方案。第二种变通方法是禁用 Resizable Bar(ReBAR),另一位用户报告称,这样做在没有禁用 AMD EEU 的情况下停止了磁盘活动。不过这也不理想,因为 ReBAR 能让 PC 更高效地访问 GPU 内存,从而提升游戏性能。
目前,检查你的 PC 上是否真的存在该问题,可能是最明智的第一步。按下 Win + R,输入 resmon,然后选择“磁盘”选项卡,打开 Windows 资源监视器。按写入活动排序,并留意来自 atieclxx.exe 或 atiesrxx.exe 的持续写入。AMD 表示修复程序正在开发中,但尚未公布确认的发布日期。在此之前,Radeon 用户可能希望监控自己的存储活动,而不是立即禁用驱动程序服务或更改 BIOS 设置。
译文由英文原文机器翻译,术语按行业惯例统一,可在文末展开原文核对。
查看英文原文(AMD admits GPU driver bug is writing data continuously, wearing out SSDs)
An SSD can spend most of its day doing very little, particularly when a PC is sitting idle. That may not be the case for some AMD Radeon systems, however, with reports suggesting that AMD’s External Events Utility (EEU), which is installed alongside Radeon drivers, may be writing data to the system driver continuously, even when the computer is barely being used. The issue drew attention again on November 8, when Reddit user ‘darklinkpower’ highlighted reports of the unusual drive activity.
One Radeon owner claimed the problem had been quietly eating into their drive's reported health for more than a year, writing: "I just found out that the driver eats up 1% of my SSD health every month for 16 months." Another user reported sustained writes of approximately 5MB/s while their PC was idle. Another one claimed their SSD health had dropped by about 1% every month for 16 months. AMD has acknowledged the problem. In an October 21 response on its community forum, a company representative confirmed that they were investigating. “Yes. We're looking into it with the aim to resolve it in a future driver release." He said. Another representative, AMAD Vik, subsequently offered a more encouraging update on Reddit, apologizing and saying, “This is hopefully fixed in the next one."
PSA: As of the latest AMD Adrenaline update, a bug may be causing silent, constant writes to your SSD, unnecessarily killing its lifespan.from r/pcmasterrace
Notably, the EEU is not an entirely unfamiliar culprit. Last November, a similar issue involving AMD chipset drivers arose, with a Redditor claiming he had discovered that the software repeatedly updated a log file whenever on-screen elements were moved or resized. That incident also prompted questions about whether stopping the service would affect FreeSync. The latest reports are a different proposition, though, with some users now seeing writes that barely let up, even when their PCs are doing nothing.
The numbers are worth looking at. At 5 MB/s, an SSD would receive about 18GB of host writes per hour. Over a full day, that's 432GB, and a month of uninterrupted activity could push the figures close to 13TB. That, however, does not necessarily mean being written to the NAND flash itself. SSD controllers use caching and wear-leveling, and other techniques, to manage incoming data. How much of that reported activity thus translates into actual flash wear is still unknown. The user's claim of losing 1% of drive health each month also hasn't been independently confirmed.
Moreover, there doesn't appear to be clear patterns across Radeon driver versions. Reports include systems running Adrenalin 26.19.2, as well as older releases, suggesting the problem may not be limited to the latest update. AMD's October 30 release notes for Adrenalin 26.20.2 don't mention the issue either. For now, it's difficult to say which driver versions, hardware combinations, or system configurations are responsible.
That said, there are two reported workarounds. The first involves opening the Windows Services application by pressing Win + R, entering services.msc, and locating AMD EEU. Users can then stop the service or change its startup type to Disabled. That appears to stop excessive writeups, but isn’t necessarily a clean solution. The second workaround involves disabling Resizable Bar (ReBAR), which another user reported had stopped the disk activity without disabling the EEU. This, however, isn’t ideal either, as ReBAR can improve gaming performance by allowing the PC to access the GPU’S memory more efficiently.
For now, checking whether the problem actually exists on your PC is probably the most sensible first step. Open Windows Resource Monitor by pressing Win + R, typing resmon, and selecting the Disk tab. Sort by write activity and look for sustained writes from atieclxx.exe or atiesrxx.exe. AMD has indicated that a fix is in the works, but hasn’t published a confirmed release date. Until then, Radeon owners may want to monitor their storage activity rather than immediately disabling driver services or changing BIOS settings.
正文保留英文原文,标题与摘要由机器翻译。
原文发布于 Tom's Hardware(AMD admits GPU driver bug is writing data continuously, wearing out SSDs),标题、摘要与正文由机器翻译,术语按行业惯例统一,未经人工逐句校订。