我使用 BOXD34010WYKH1 英特尔 NUC 作为我的媒体中心已有 5 年多了。它已连接到我的电视，运行 LibreElec (Kodi)。我在上面观看了许多 h264 1080p 视频，从我的 NAS 通过网络传输，没有任何问题。
最近，我尝试了一些 1080p HEVC 10 位内容，但我的 NUC 无法处理。我不明白为什么。它将完美流畅地运行 h265 视频几分钟。剩余大量可用 RAM。所有 4 个核心的 CPU 利用率仅为 70% 左右。 lm_sensors 显示温度约为 50 摄氏度。然后，屏幕突然变暗并冻结。
我认为这可能是软件问题，所以我尝试更新 LibreElec - 没有帮助。然后我尝试安装 Linux Mint，在另一台机器上设置 Plex 服务器，并在 NUC 上通过 Firefox 观看。完全相同的事情 - 运行良好几分钟，然后就死掉了。
我唯一的线索是：
运行 Linux Mint 时，我从笔记本电脑连接到 NUC，一边观看视频一边跟踪日志，直到它停止运行。当它死掉时，我在 /var/log/syslog 中得到这些日志条目：
May 12 19:50:26 tal-media-nuc kernel: [ 228.055952] nuvoton-cir 00:05: RX FIFO overrun detected, flushing data! [6/23]
May 12 19:50:26 tal-media-nuc kernel: [ 228.058145] nuvoton-cir 00:05: RX FIFO overrun detected, flushing data!
May 12 19:50:26 tal-media-nuc kernel: [ 228.059121] nuvoton-cir 00:05: RX FIFO overrun detected, flushing data!
May 12 19:50:26 tal-media-nuc kernel: [ 228.060019] nuvoton-cir 00:05: RX FIFO overrun detected, flushing data!
May 12 19:50:26 tal-media-nuc kernel: [ 228.062556] nuvoton-cir 00:05: RX FIFO overrun detected, flushing data!
May 12 19:50:26 tal-media-nuc kernel: [ 228.062836] nuvoton-cir 00:05: RX FIFO overrun detected, flushing data!
May 12 19:50:29 tal-media-nuc kernel: [ 231.751820] ata1.00: exception Emask 0x10 SAct 0x3f8000 SErr 0x4040000 action 0xe frozen
May 12 19:50:29 tal-media-nuc kernel: [ 231.751832] ata1.00: irq_stat 0x00000040, connection status changed
May 12 19:50:29 tal-media-nuc kernel: [ 231.751837] ata1: SError: { CommWake DevExch }
May 12 19:50:29 tal-media-nuc kernel: [ 231.751843] ata1.00: failed command: WRITE FPDMA QUEUED
May 12 19:50:29 tal-media-nuc kernel: [ 231.751849] ata1.00: cmd 61/18:78:d8:7a:d4/00:00:1f:00:00/40 tag 15 ncq dma 12288 out
May 12 19:50:29 tal-media-nuc kernel: [ 231.751849] res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
May 12 19:50:29 tal-media-nuc kernel: [ 231.751851] ata1.00: status: { DRDY }
May 12 19:50:29 tal-media-nuc kernel: [ 231.751853] ata1.00: failed command: WRITE FPDMA QUEUED
May 12 19:50:29 tal-media-nuc kernel: [ 231.751857] ata1.00: cmd 61/68:80:48:94:d4/01:00:1f:00:00/40 tag 16 ncq dma 184320 out
May 12 19:50:29 tal-media-nuc kernel: [ 231.751857] res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
May 12 19:50:29 tal-media-nuc kernel: [ 231.751860] ata1.00: status: { DRDY }
May 12 19:50:29 tal-media-nuc kernel: [ 231.751863] ata1.00: failed command: WRITE FPDMA QUEUED
May 12 19:50:29 tal-media-nuc kernel: [ 231.751867] ata1.00: cmd 61/f0:88:18:cd:f1/07:00:1f:00:00/40 tag 17 ncq dma 1040384 ou
May 12 19:50:29 tal-media-nuc kernel: [ 231.751867] res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
May 12 19:50:29 tal-media-nuc kernel: [ 231.751868] ata1.00: status: { DRDY }
May 12 19:50:29 tal-media-nuc kernel: [ 231.751870] ata1.00: failed command: WRITE FPDMA QUEUED
May 12 19:50:29 tal-media-nuc kernel: [ 231.751874] ata1.00: cmd 61/10:90:08:d5:f1/08:00:1f:00:00/40 tag 18 ncq dma 1056768 ou
May 12 19:50:29 tal-media-nuc kernel: [ 231.751874] res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
May 12 19:50:29 tal-media-nuc kernel: [ 231.751876] ata1.00: status: { DRDY }
May 12 19:50:29 tal-media-nuc kernel: [ 231.751877] ata1.00: failed command: WRITE FPDMA QUEUED
May 12 19:50:29 tal-media-nuc kernel: [ 231.751881] ata1.00: cmd 61/00:98:18:dd:f1/0a:00:1f:00:00/40 tag 19 ncq dma 1310720 ou
May 12 19:50:29 tal-media-nuc kernel: [ 231.751881] res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
May 12 19:50:29 tal-media-nuc kernel: [ 231.751883] ata1.00: status: { DRDY }
May 12 19:50:29 tal-media-nuc kernel: [ 231.751884] ata1.00: failed command: WRITE FPDMA QUEUED
May 12 19:50:29 tal-media-nuc kernel: [ 231.751888] ata1.00: cmd 61/00:a0:18:e7:f1/06:00:1f:00:00/40 tag 20 ncq dma 786432 out
May 12 19:50:29 tal-media-nuc kernel: [ 231.751888] res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
May 12 19:50:29 tal-media-nuc kernel: [ 231.751890] ata1.00: status: { DRDY }
May 12 19:50:29 tal-media-nuc kernel: [ 231.751892] ata1.00: failed command: WRITE FPDMA QUEUED
May 12 19:50:29 tal-media-nuc kernel: [ 231.751896] ata1.00: cmd 61/b8:a8:18:ed:f1/08:00:1f:00:00/40 tag 21 ncq dma 1142784 ou
May 12 19:50:29 tal-media-nuc kernel: [ 231.751896] res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
May 12 19:50:29 tal-media-nuc kernel: [ 231.751897] ata1.00: status: { DRDY }
May 12 19:50:29 tal-media-nuc kernel: [ 231.751909] ata1: hard resetting link
May 12 19:50:32 tal-media-nuc kernel: [ 234.239049] ata1: SATA link down (SStatus 1 SControl 300)
May 12 19:50:32 tal-media-nuc kernel: [ 234.239364] ata1: hard resetting link
May 12 19:50:34 tal-media-nuc kernel: [ 236.466987] ata1: COMRESET failed (errno=-32)
May 12 19:50:34 tal-media-nuc kernel: [ 236.466995] ata1: reset failed (errno=-32), retrying in 8 secs
May 12 19:50:42 tal-media-nuc kernel: [ 244.253793] ata1: hard resetting link
May 12 19:50:44 tal-media-nuc kernel: [ 246.465503] ata1: SATA link down (SStatus 1 SControl 300)
May 12 19:50:44 tal-media-nuc kernel: [ 246.466243] ata1: hard resetting link
SSH 保持连接，但我的 bash 变得疯狂。如果我运行ls或任何其他命令，它会显示ls: command not found.如果我运行类似的东西/usr/bin/ls，它会说-bash: /usr/bin/ls: Input/output error。如果我断开 SSH 并尝试重新连接，它不会让我这样做。我必须硬重置 NUC 才能恢复正常状态。
我从 NUC 中取出 2.5 英寸驱动器并进行了检查。SMART 说没问题。badblocks 说没问题。
这种情况仅发生在 HEVC 中。 H264 仍然可以正常播放，没有任何问题。我不知道这是否是某种硬件错误，或者某些硬件出现故障，或者是否有什么我可以做的。如果我知道这只是需要一个更强大的 NUC，我就会去买一个，但在播放视频时它似乎还没有接近最大化其资源。我不能保证新的不会做同样的事情。