Custom Resolution Utility (CRU)

[kaladar]

(08-08-2023 04:22 PM)ToastyX Wrote:  Sometimes the driver can crash while restarting and the driver stays disabled after rebooting, but that normally wouldn't cause a blank screen because the basic display driver will load just like in safe mode until you restart the driver again. Usually if DDU doesn't help, that indicates a hardware problem. It sounds like the GPU might be faulty unless both monitors somehow have issues. The issue with the old monitor almost looks like it can't read the EDID. While connected to the old monitor, post a screen shot of what's listed in Device Manager under display adapters and monitors. With the newer monitor, try unplugging the monitor's power for a minute to reset it just in case the firmware glitched. If that doesn't help, does the newer monitor work if you boot Windows in safe mode? What about if you boot from a Windows install drive?

Dunno if the driver might have crashed since I did reboot before attaching old monitor. Both monitors had been unplugged before and I could not go into recovery mode since I didnt see anything on new one once in boot manager, but i'll try now for the old one at least.
There's some success, I can now use the new Monitor as before but the old one would stay in 720p. Device Manager detects (by name), I can also install the Monitor driver. CRU does list all the edid infos both monitors supports. It all happend directly on CRU-reset/restart. But I think it might be a Win11(22h2) or Nvidia (536.67) bug.
EDIT: With new monitor plugged in both stay black - could it be it doesnt support that forced reolution? With only the old one I could go into safe mode. But couldnt open device manager. the reolution was forced to 640x480 which I know is not normal on that system/that monitor.