After upgrading to 25.10, Transcoding was not working all the time. Seems the system would run for a few hours, then I would get 1000s of errors like this: [50136.610981] NVRM: gpuHandleSanityCheckRegReadError_GM107: Possible bad register read: addr: 0x110100, regvalue: 0xbadf5620, error code: Unknown SYS_PRI_ERROR_CODE. I have a RTX3050 GPU. If I rebooted the system, transcoding would again work for a few hours then stop and more of this error. nvidia-smi would show nothing. Seems like the driver was crashing. I am thinking this has something to do with 25.10 moving from the proprietary nvidia driver to the open GPU kernel drivers. Took me a week or so to recognize I had a problem and narrow it down. I have since rolled back to 25.04.2.5 and everything works again. Been up and running for a day now. Any help would be appreciated.
If it is a version specific driver fault I can’t think of any fix outside of making a bug report - though the million dollar question is who will want to work the report? The devs of the driver, plex devs (assuming since you’re transcoding), or TrueNAS devs. I could see quickly how everyone will point back to someone else’s jurisdiction…
Sorry for the double post. My system glitched on me and I can’t update the deleted post.
This sounds like as noted, an issue with the new Nvidia drives. You could go back to 25.10 and install the older drivers using @zzzhouuu patch and see if the issue goes away.
https://forums.truenas.com/t/nvidia-compatible-driver-test-for-truenas-25-10-goldeye/53395
This was supposed to be not only a “driver works, but it just spams the log” issue, but also fixed in 570.86.15 and later (which we’re on) for Ampere GPUs (of which the RTX 3050 is a member) - so there’s no passing the buck here, NVIDIA is already owning this one. 
@IRON99 can you run nvidia-bug-report.sh from the TrueNAS shell or SSH session and gather the info for them? They’re tracking upstream: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/688
I have rolled back to 25.04.2.5 so I am assuming that this bug report would be of no use as I am not using the open GPU kernel drivers. Maybe one day when I have time, I will upgrade again and do it. For now, it works, so I will just let it as is. To me, it looks like this issue has been around for more than a year and it is not fixed, so I will not hold my breath. Perhaps, I will just throw in the towel and get an Intel Arc GPU and be done with it.
Sorry to hear you’re having difficulty. If you do get a chance to update and grab a capture for their bug tracker, that’s appreciated - but I understand the need to get back to a working state.
Thanks for bringing this one to our attention!