Custom Resolution Utility (CRU)

[EeK]

(10-30-2019 09:49 PM)ToastyX Wrote:  Even if the driver crashed while running restart64.exe, it shouldn't have caused a reboot loop. If you're willing to experiement, what happens if you disable and enable the GPU in Device Manager? If it crashes when disabling and causes a boot loop, it might actually be a bug in Microsoft's Basic Display Adapter driver, although that shouldn't listen to EDID overrides. If it crashes when enabling, it's definitely an NVIDIA driver bug. Then again, now that it's working, it might not crash at all.

At this point, I'm honestly scared of trying anything else and messing up all of my settings again.

But another person on a different forum mentioned having the same issue as me, when trying to add a custom resolution via CRU. It's most certainly an Nvidia driver bug, as none of that was happening on previous versions, and the new driver won't even allow the same resolution/refresh rates as before.