On 6/27/2025 at 9:35 AM, ich777 said:

Diagnostics would help a lot to troubleshoot your issue.

Here's diagnostics and a screen recording of how I fix it. I have posted all the things I have been trying to https://forums.unraid.net/topic/191495-unraid-714-random-errors-unsure-where-to-start-troubleshooting/#comment-1563921 as well.

It seems like when the Backup/Restore Appdata plugin runs, the VM that I have takes the GPU over. Even though the graphics driver is set to using a virtual driver.

oldtown-diagnostics-20250628-1220.zip

27 minutes ago, Wedgetastic said:

It seems like when the Backup/Restore Appdata plugin runs, the VM that I have takes the GPU over. Even though the graphics driver is set to using a virtual driver.

Can you possibly try to not stop the containers that use the Nvidia GPU when running appdata backup, I would also report that in the CA Backup/Restore thread since this not seems like a driver issue to me, a running VM usually don't takes over a GPU.

BTW, did you know that I and @Joly0 have a LXC container for AMP ready?

You can also try to uninstall GPU Statistics since it seems to cause issues for a few users lately and see if that fixes the issue.

On 6/24/2025 at 10:02 PM, tykateetee said:

See my messages on this page and the previous one as they may help you. I had the same issue and it was not related to my GPU dying, but something that was present on my flash device. I had no issues for years and then I had my log filled with these errors too. I think it has something to do with updating Unraid to 7.x.x as from 6.x.x as that was roughly when my issues started. I ended up reinstalling and the issue went away.

It’s not related to Unraid 7 because when I posted last week, I was still on 6.12.15. I just tried updating to 7 now and it made no difference.

11 hours ago, Wedgetastic said:

It seems like when the Backup/Restore Appdata plugin runs, the VM that I have takes the GPU over. Even though the graphics driver is set to using a virtual driver.

that is as mentioned ... lets say uncommon ;) but your video looks like it ...weird.

what we see in your logs, many errors like this

Jun 27 05:04:07 Oldtown kernel: NVRM: GPU 0000:09:00.0: RmInitAdapter failed! (0x62:0x51:2584)

Jun 27 05:04:07 Oldtown kernel: NVRM: GPU 0000:09:00.0: rm_init_adapter failed, device minor number 0

Jun 27 05:04:07 Oldtown kernel: NVRM: GPU 0000:09:00.0: RmInitAdapter failed! (0x22:0x51:884)

Jun 27 05:04:07 Oldtown kernel: NVRM: GPU 0000:09:00.0: rm_init_adapter failed, device minor number 0

and looks like not only when plugin runs and so on ...

copy your vm vdisk to sample /domains/amp2/vdisk1.img

may just to make sure, may create a new vm with the same settings like AMP, pointing to the copied vdisk image, make sure you dont select the Nvidia card (also not the audio !!!), try again. VM should run like your original one ... just to exclude something stuck somewhere in libvirt on your AMP VM in terms you played with nvidia passthrough in that VM sometime ...

overall, the vm normally wont take over a pcie gpu while running ... should may even crash the server immediately on startup if it tries while docker/s using it ... really weird ;)

20 hours ago, Groto said:

It’s not related to Unraid 7 because when I posted last week, I was still on 6.12.15. I just tried updating to 7 now and it made no difference.

Good catch. I think I jumped from 6.12.10 to 6.12.14 first and that was more when the issue started for me. At this point, I really don't remember and my guestimates should be taken with a grain of salt. Still a weird issue that I feel was amplified by GPU Statistics constantly polling the card but I don't feel that my issue was caused by it. Had it back for almost 2 weeks now and still no issues after reinstalling.

I'm having a weird bug where on boot my GPU is found fine, but then I go check later and it says Installed GPU(s): No devices were found

However Plex can see it;

And plex thumbnail generator script that uses the GPU is running right now.

There was nothing on the gpu stats dashboard plugin panel, until I selected the igpu;

nvidia smi;

Right now I am on v575.51.02 because I started from the latest (didn't detect on bootup) and went backwards until I found one that worked, but then it disappeared like this again, and I went back even more.

What has happened recently to cause people so many problems?

5 minutes ago, paradoxum said:

What has happened recently to cause people so many problems?

Sorry but not many people having issues, if you read through the posts these are mostly compatibility issues and possibly dying cards or other issues which of most are probably solved by now, I admit not all but most of them.

Usually people come here to report issues and not to say that everything is working fine. 🙂

Please keep in mind that about 16k people have installed the driver plugin and I would not say that many poeple have issues otherwise this thread would be full of support requests lately.

6 minutes ago, paradoxum said:

And plex thumbnail generator script that uses the GPU is running right now.

Can you possibly post your Diagnostics after the error occurs so that we can diagnose the issue further otherwise troubleshoting the issue is really hard and I even can‘t see which system you are having or what possibly could be the cause of the issue.

33 minutes ago, ich777 said:

Sorry but not many people having issues, if you read through the posts these are mostly compatibility issues and possibly dying cards or other issues which of most are probably solved by now, I admit not all but most of them.

Usually people come here to report issues and not to say that everything is working fine. 🙂

Please keep in mind that about 16k people have installed the driver plugin and I would not say that many poeple have issues otherwise this thread would be full of support requests lately.

Can you possibly post your Diagnostics after the error occurs so that we can diagnose the issue further otherwise troubleshoting the issue is really hard and I even can‘t see which system you are having or what possibly could be the cause of the issue.

I can post it now, I haven't rebooted since because i'm currently parity syncing, the plex thumbnail generator is still running, etc.

I'll edit this in a min.

orbitalhub-diagnostics-20250701-2236.zip

Edited July 1, 20251 yr by paradoxum

6 hours ago, paradoxum said:

I can post it now, I haven't rebooted since because i'm currently parity syncing, the plex thumbnail generator is still running, etc.

you may should remove all these vfio binds, doesnt look really good to me (even the Nvidia aint vfio bound, but many other "sys" devices are ...)

BIND=0000:00:02.0|8086:9bc5 0000:00:08.0|8086:1911 0000:00:1f.0|8086:4385 0000:00:1f.3|8086:f0c8 0000:00:1f.4|8086:43a3 0000:00:1f.5|8086:43a4

may test without all these binds ...

13 hours ago, paradoxum said:

I'll edit this in a min.

I think this is your issue:

Jul 1 13:18:36 OrbitalHub kernel: NVRM: GPU at PCI:0000:02:00: GPU-257c8daf-576b-fa9e-c3c1-94f40e3e4347

Jul 1 13:18:36 OrbitalHub kernel: NVRM: GPU Board Serial Number: 1422019097083

Jul 1 13:18:36 OrbitalHub kernel: NVRM: Xid (PCI:0000:02:00): 79, GPU has fallen off the bus.

Jul 1 13:18:36 OrbitalHub kernel: NVRM: GPU 0000:02:00.0: GPU has fallen off the bus.

Jul 1 13:18:36 OrbitalHub kernel: NVRM: GPU 0000:02:00.0: GPU serial number is 1422019097083.

Jul 1 13:18:36 OrbitalHub kernel: NVRM: A GPU crash dump has been created. If possible, please run

Jul 1 13:18:36 OrbitalHub kernel: NVRM: nvidia-bug-report.sh as root to collect this data before

Jul 1 13:18:36 OrbitalHub kernel: NVRM: the NVIDIA kernel module is unloaded.

Jul 1 13:18:36 OrbitalHub kernel: NVRM: Xid (PCI:0000:02:00): 154, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required)

However as you can see you even got a Xid error which you can learn more about here:

https://docs.nvidia.com/deploy/xid-errors/index.html#xid-error-listing

(in your Case you got Error 79)

Does this happen often for you or did this just happen for the first time? If this happened for the first time was this possibly during the Parity check or on the beginning from the Parity check?

If this happened during the Parity check for the first time make sure that your Power Supply is up to the task since such errors can happen at peaks where the Power Supply delivers power a bit too late or even to less which is required by the GPU.

Don't forget that power supplies also degrade over time.

Just because I saw it, please remove the file /boot/config/modprobe.d/nvidia.conf <- this isn't needed anymore, you also don't have the correct driver installed anyways.
You can also remove it by issuing this command from a Unraid Terminal:

rm -f /boot/config/modprobe.d/nvidia.conf

Long time no post (yey! for troublefree use until....), really appreciate this plugin!

Joining the camp for the "RmInitAdapter failed!" messages it seems. ☹️

Currently on 7.1.4 with a T400 running the 574.64 driver. I do not recall seeing these on v6 of UnRAID, but know others in their situation have said they did. So not very helpful.

Not too much has changed on my end to cause these. I started noticing some hard lockups lately, and started to investigate to find these messages.

Working with Gemini on some possible fixes, I am current running with "extra_args=NVreg_EnableGpuFirmware=0 NVreg_PowerMizerMode=0x1" in my settings.cfg. Neither argument has helped to resolve the ""RmInitAdapter failed!" messages.

However, I used to have also a "GSP Timeout" message as well, and one of the above arguments seemed to have resolved that one (it was the first one intended to resolve it; see older syslog snippet attached).

I was originally running the open source driver when I noticed this, which was v.570x. I switched to the production branch at the time to troubleshoot (which also allowed one of the arguments added). Same situation.

At times I see the message in the Plugin that no compatible cards are installed. I believe at that time is when these messages are appearing.

I only use this GPU for use with Emby. The VM is headless/virtual, and the host is using the IPMI video card.

A couple things to mention:

• ~6 months ago I went back to this hardware (X11/Xeon) as my primary newer MB went defective. I say this as there might still be some old arguments, etc.. in my configuration. However, again I never noticed these errors up until recently, and the same GPU was used with this current configuration, and the newer one as well.

• I've removed the GPU Statistics plugin, however this same error occurs.

• Between all changes (driver, removing GPU statistics, adding extra args,...) I have restarted the server.

Please let me know what else I may be able to try to resolve this issue.

Appreciate the support!

Edit: I also added an older syslog snippet of the full output I used to receive prior to adding in the extra arguments (and now only getting the much less verbose RMInit failure)

Edit2 (as I troubleshoot): I cleared all extra arguments, fresh install of the plugin, also enable Above 4G decoding (didn't know it was disabled).🤞

server-diagnostics-20250704-0736.zip

OlderSyslog snippet.txt

Edited July 5, 20251 yr by bungee91

I'm glad I'm not alone with these errors as I keep on having them.

Card works perfectly for awhile and then keeps "disconnecting" and stopping docker containers that use the card (Plex and TDARR) and starting them back up seems to stable things out for a bit. It's almost like too many requests to the card causes it to lock up :(

41 minutes ago, musicking said:

TDARR

And you are certain that this isn't the issue?

As said, in the past I had a few reports tdarr crashing Servers.

However did you already try to lower the PCIe Gen in your BIOS?

On 7/4/2025 at 2:56 PM, bungee91 said:

Please let me know what else I may be able to try to resolve this issue.

Oh, interesting you have a Xid error 119, this is completely different than all other issues reported so far.

This basically mean that the GSP (GPU System Processor) times out which can be possibly also be caused by link instability.

On 7/4/2025 at 2:56 PM, bungee91 said:

extra_args=NVreg_EnableGpuFirmware=0 NVreg_PowerMizerMode=0x1

What do you mean by that, where did you enable this? Usually you pass this over in your syslinux.conf

On 6/26/2025 at 11:39 AM, alturismo said:

1st approach, exclude issue with pcie1 ...

about performance hit, well, you are using your GPU on the host for some dockers, lxc, whatever ... you wont see any real difference anyway, in a Gaming VM it would, but therefore we dont need this driver plugin ;)

so, to exclude some issue with your pcie slot and rbar reservation, give it a try ...

On 6/27/2025 at 2:21 AM, ich777 said:

To me this seems like a firmware issue, however have you yet tried to limit the PCIe Generation to something like Gen4 or even lower to Gen3 to see if that fixes the issue.

About the performance I'm on the same page as @alturismo because for transcoding it doesn't matter much however for AI related stuff you would need as much bandwidth as possible but I'm not sure if dropping down the PCIe Generation would have such a significant impact (at least not to Gen4) in a real world scenario.

Sorry for the delayed reply, I was able to swap my GPU to the other PCIe slot, but the problem is still presenting itself in the same way. I'm still seeing "no devices" when I check the driver settings and nvidia-smi. Still seeing errors in the logs. I've attached an updated diagnostics file.

Are there any other motherboard settings I might need to switch in BIOS? I'm using a ROG STRIX B550-F GAMING (WI-FI).

Any assistance would be appreciated.

whale-diagnostics-20250706-1336.zip

30 minutes ago, jm028 said:

Any assistance would be appreciated.

sorry, AMD devices im out ...

you still have thiis error

Jul 6 13:28:46 WHALE kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 239

Jul 6 13:28:46 WHALE kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

Jul 6 13:28:46 WHALE kernel: NVRM: BAR1 is 0M @ 0x0 (PCI:0000:04:00.0)

Jul 6 13:28:46 WHALE kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

Jul 6 13:28:46 WHALE kernel: NVRM: BAR2 is 0M @ 0x0 (PCI:0000:04:00.0)

Jul 6 13:28:46 WHALE kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

Jul 6 13:28:46 WHALE kernel: NVRM: BAR3 is 0M @ 0x0 (PCI:0000:04:00.0)

Jul 6 13:28:46 WHALE kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

Jul 6 13:28:46 WHALE kernel: NVRM: BAR4 is 0M @ 0x0 (PCI:0000:04:00.0)

Jul 6 13:28:46 WHALE kernel: nvidia 0000:04:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem

Jul 6 13:28:46 WHALE kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64 575.57.08 Release Build (dvs-builder@U22-I3-H04-01-5) Sat May 24 07:03:13 UTC 2025

Jul 6 13:28:46 WHALE kernel: nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64 575.57.08 Release Build (dvs-builder@U22-I3-H04-01-5) Sat May 24 06:53:21 UTC 2025

personally looking like issues with rbar addressing ... but there others may can say something with AMD hardware.

you also tried already hard fixing pcie gen on your slot and so on, like described in some threads already.

also enabling rbar support on your mainboard etc ...

Hello - looking to get some help. I installed an RTX 1070. Previously, I had a 1660 TI. The 1660 was working perfectly. The 1070 doesn't show up in my Nvidia Plugin when I look for it. If I install the open-source version, then it gives me an Nvidia-Smi not found error. I can see the device in my Tools/System Devices. Attached my diagnostic.

I did mess around in BIOS with enabling and disabling VT-D. If I enable it, it shows up as a device in VM but not for the plugin.

tower-diagnostics-20250706-2018.zip

Edited July 7, 2025Jul 7 by Shawn Dlima

On 7/5/2025 at 11:45 AM, ich777 said:

Oh, interesting you have a Xid error 119, this is completely different than all other issues reported so far.

This basically mean that the GSP (GPU System Processor) times out which can be possibly also be caused by link instability.

What do you mean by that, where did you enable this? Usually you pass this over in your syslinux.conf

"Interesting" huh? 🤣 Uncertain, just want to make sure I'm providing as many details as possible.

As to the extra arguments, I was just adding them into the flash\config\plugins\nvidia-driver\settings.cfg file. Which likely meant they did nothing, as that was the incorrect spot for it to initialize the card (AI/Gemini can be incorrect).

Update, same issues as before with Above 4G decoding enabled.

I'd really like to try an old, old driver ~540 branch (I'm told that was a fairly stable/long release). Is there a way for the plugin to allow for other selections than what is listed on the settings page?

Updated diagnostics attached. Any other ideas here?

The platform I'm currently on (again my previous hardware) is pretty well supported/widely used (X11SSM and older Xeon with ECC ram).

Uncertain what other settings I can try. I'll look for an updated BIOS just in case.

server-diagnostics-20250706-2019.zip

Edited July 7, 2025Jul 7 by bungee91

4 hours ago, Shawn Dlima said:

I did mess around in BIOS with enabling and disabling VT-D. If I enable it, it shows up as a device in VM but not for the plugin.

open source aint compatible with your GTX 1070

try with official, but be aware, GTX 10xx support will be dropped soon (driver 580 ++)

compaible cards, take a look here

GitHub

GitHub - NVIDIA/open-gpu-kernel-modules: NVIDIA Linux ope...

NVIDIA Linux open GPU kernel module source. Contribute to NVIDIA/open-gpu-kernel-modules development by creating an account on GitHub.

I recently installed an RTX 5060 TI 16 Gig with PCIe bifurcation adapter 8x 8x. This board only has one 16x slot. Nvidia Open Source Driver: v575.57.08 installed. It works fine for a couple hours then I start to get out of memory errors then the GPU is no longer detectable. A reboot will fix it for a couple more hours. Any idea what settings could be adjusted to resolve this issue?

Unraid system: Unraid server Lifetime, version 7.1.4

Motherboard: GIGABYTE MC12-LE0-00, Version: 01010101, s/n: MH9N2400394

Processor: AMD Ryzen 7 PRO 5750G with Radeon Graphics @ 3800 MHz

HVM: Enabled

IOMMU: Enabled

Cache: L1 - Cache = 512 KiB (max. capacity 512 KiB)

L2 - Cache = 4 MiB (max. capacity 4 MiB)

L3 - Cache = 16 MiB (max. capacity 16 MiB)

Memory: 128 GiB DDR4 Multi-bit ECC (max. installable capacity 128 GiB)

DIMM_P0_A0: Kingston 9965745-039.A00G, 32 GiB DDR4 @ 3200 MT/s

DIMM_P0_A1: Kingston 9965745-039.A00G, 32 GiB DDR4 @ 3200 MT/s

DIMM_P0_B0: Kingston 9965745-039.A00G, 32 GiB DDR4 @ 3200 MT/s

DIMM_P0_B1: Kingston 9965745-039.A00G, 32 GiB DDR4 @ 3200 MT/s

Network: eth0: 10000 Mbps, full duplex, mtu 1500

eth1: interface down

eth2: interface down

Kernel: Linux 6.12.24-Unraid x86_64

OpenSSL: 3.5.0

P + Q algorithm: 6175 MB/s + 44629 MB/s

Jul 7 06:26:32 Jarvis kernel: NVRM: kgspInitRm_IMPL: Error preparing GSP-RM image

Jul 7 06:26:32 Jarvis kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM

Jul 7 06:26:32 Jarvis kernel: NVRM: GPU 0000:0a:00.0: RmInitAdapter failed! (0x62:0x51:1941)

Jul 7 06:26:32 Jarvis kernel: NVRM: GPU 0000:0a:00.0: rm_init_adapter failed, device minor number 0

Jul 7 06:26:32 Jarvis kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1353

Jul 7 06:26:32 Jarvis kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from nvStatus @ message_queue_cpu.c:242

Jul 7 06:26:32 Jarvis kernel: NVRM: _kgspInitRpcInfrastructure: GspMsgQueueInit failed

Jul 7 06:26:32 Jarvis kernel: NVRM: kgspConstructEngine_IMPL: init RPC infrastructure failed

Jul 7 06:26:32 Jarvis kernel: NVRM: osInitNvMapping: *** Cannot attach gpu

Jul 7 06:26:32 Jarvis kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter

Jul 7 06:26:32 Jarvis kernel: NVRM: GPU 0000:0a:00.0: RmInitAdapter failed! (0x22:0x51:742)

Jul 7 06:26:32 Jarvis kernel: NVRM: GPU 0000:0a:00.0: rm_init_adapter failed, device minor number 0

Jul 7 06:26:58 Jarvis kernel: block nvme0n1: the capability attribute has been deprecated.

Jul 7 06:27:12 Jarvis kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1353

Jul 7 06:27:12 Jarvis kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from status @ kernel_gsp.c:4615

Jul 7 06:27:12 Jarvis kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from kgspCreateRadix3(pGpu, pKernelGsp, &pKernelGsp->pGspUCodeRadix3Descriptor, NULL, pGspFw->pImageData, pGspFw->imageSize) @ kernel_gsp.c:4502

diagnostics-20250707-0626.zip

On 7/7/2025 at 12:43 PM, Jeffrolc said:

Motherboard: GIGABYTE MC12-LE0-00, Version: 01010101, s/n: MH9N2400394

Processor: AMD Ryzen 7 PRO 5750G with Radeon Graphics @ 3800 MHz

Please check that you are on the latest BIOS, switch to PCIe Gen 4 or even Gen 3 in the BIOS if possible, make sure that Resizable BAR Support and Above 4G Decoding is enabled.

Usually that is related to some kind of bus error what you are seeing.

I think I've resolved this for my specific issue, the log has been clean the entire day, with a couple of transcoding sessions occurring successfully and silently (log wise). I thought this may be the case for my older hardware (that again, I fell back to due to a MB failure).

Legacy boot/non-UEFI has seemed to resolve all of my issues. This isn't shocking to me given the age of the platform. I'll report back if that changes, however think I'm all set.

Thanks again for the plugin and follow up support!

On 8/18/2023 at 5:07 AM, Jus said:

I am on latest 2023.07.06 and didnt had this before I updated Unraid to 6.12.3
PHP error reporting is not enabled.

in PHP log i have bunch of this:
 

#0 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(705) : eval()'d code(64): log('0\x02', 1000)
#1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(705) : eval()'d code(173): presetSpace('0\x02')
#2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(705): eval()
#3 /usr/local/emhttp/plugins/dynamix/template.php(82): require_once('/usr/local/emht...')
#4 {main}
  thrown in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(705) : eval()'d code on line 64
[18-Aug-2023 09:27:24 Europe/Paris] PHP Fatal error:  Uncaught TypeError: log(): Argument #1 ($num) must be of type float, string given in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(705) : eval()'d code:64
Stack trace:
#0 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(705) : eval()'d code(64): log('0\x02', 1000)
#1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(705) : eval()'d code(173): presetSpace('0\x02')
#2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(705): eval()
#3 /usr/local/emhttp/plugins/dynamix/template.php(82): require_once('/usr/local/emht...')
#4 {main}
  thrown in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(705) : eval()'d code on line 64
[18-Aug-2023 09:34:54 Europe/Paris] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(705) : eval()'d code on line 174

 

Did you resolve your issue? I am seeing this on the latest Unraid version myself. Been removing custom themes and other dynamixs items like crazy. Replaced my flash drive, and currently uninstalled (and will re-install) the NVIDIA driver plugin.

3 hours ago, Waddoo said:

Did you resolve your issue? I am seeing this on the latest Unraid version myself. Been removing custom themes and other dynamixs items like crazy. Replaced my flash drive, and currently uninstalled (and will re-install) the NVIDIA driver plugin.

I think your post would be better be suited (alongside with Diagnostics) in the General Subforums.

On 7/7/2025 at 5:24 AM, alturismo said:

...but be aware, GTX 10xx support will be dropped soon (driver 580 ++)

Sorry to hijack, but didn't know this - are you saying my trusty 1050 won't be supported soon? Roughly how long have I got until I need to find a quiet and efficient replacement?