The new driver (441.12) doesn't appear to have fixed the issue that I had with 441.08. This time, I'd already used CRU to make the necessary modifications to my display's EDID (adding a custom resolution of 4K@66Hz and deleting all 4096x2160 resolutions). I also made sure to restart Windows to apply the override, instead of running restart64.exe, as that's what seemed to trigger the odd behavior before. Only after clicking on "Enable settings for the selected display model" and hitting "Apply", under the G-Sync tab on NVCP, is that my system restarted automatically and went into an infinite reboot loop again. Even though my TV is now "G-Sync Compatible", it still shows up as not validated on NVCP, requiring manual enabling of that setting. It's been like that for the previous two drivers with support for G-Sync: 441.08 and 440.52 (beta). However, the infinite reboot loop issue only happened on drivers 441.08 and 441.12. Not sure what's causing it. It may have something to do with VRR and the TV's "Instant Game Response" mode, which activated even before enabling that specific setting and immediately after installing the new driver (G-Sync was enabled by default for full screen mode). Any guesses? Everything worked fine in Safe Mode, but a simple reset of the EDID (using reset-all.exe) didn't solve the issue today, and I was forced to reinstall the driver (always via DDU). I haven't used CRU since, as I'm afraid of triggering the infinite reboot loop once more. Edit: Of note is that when I installed beta driver 440.52 (the only one with support for G-Sync on my display that didn't cause any issues), it had not been modified in any way. As I mentioned, by the time I saw the clean version that @cryohellinc kindly uploaded in response to my request, 441.08 was already available. Is it possible that there's something in these new drivers, required for the newly certified G-Sync panels (such as the 2019 LG OLEDs), that is now being erased during the regular cleaning process? Kinda like how Nvidia incorporated even more telemetry into their drivers recently. Cryo, did you notice any differences in the file structures of 440.52, 441.08 and 441.12 and the rest? 440.97 had no support for G-Sync on my set, so that's the last "regular" one.