Strobelight - LightBoost Utility for AMD/ATI and NVIDIA

[Wizard]

(08-07-2015 01:56 PM)ToastyX Wrote:  

(08-07-2015 05:17 AM)Wizard Wrote:  The issues started happening when I upgraded to windows 10. Basically what happens is the setup works perfectly fine, it installs the refresh rates, and overrides the EDID. Then I restart my computer as it tells me. When I run strobelight.exe it tells me 'no strobed refresh rates found.' which isn't right.

So I did some debugging, downloaded CRU and looked at my monitor's EDID to find that the strobelight override is still there. Wtf?

Eventually I figured out that if I run restart64.exe (which basically restarts the entire graphics driver) it will restart my displays, and will apply the EDID override, therefore allowing strobelight to work again.

But the problem is I have to run restart64.exe EVERY TIME I startup my computer to get the strobelight to work. This is a minor annoyance to me, but I wanted to let everyone know that this workaround does exist.

Are the refresh rates not available at all in Windows until after you run restart.exe or is it only Strobelight not finding the refresh rates? I can't do anything if EDID overrides aren't loading. That would be a driver issue, but I haven't heard of this happening with NVIDIA. Try reinstalling the driver after using DDU to wipe everything: http://www.wagnardmobile.com/DDU/

Yes, the refresh rates aren't available in windows until restart64.exe is ran. This hasn't happened to me before either, the only difference is I upgraded to windows 10, and I updated the graphics driver to the Windows 10 Ready version.

I'll try your suggestion and use DDU to wipe the display driver, and post back with results. Thanks for the quick reply!

EDIT: Test was a no-go. Ran DDU and completely reinstalled NVIDIA. Same thing happens, when the computer boots up the EDID override is still visible in Custom Resolution Utility, but restart.exe must be ran in order to apply the override.
Is there no way strobelight can be programmed to restart the graphics driver on start for windows 10 users?

EDIT2: OK... restarted one last time after I posted this and it magically worked. I guess it was a driver problem. I don't know why it took two restarts to fix this issue.

EDIT3: Apparently it sometimes works and sometimes requires me to run restart.exe. Some of my other startup programs are misbehaving randomly too, requiring me to restart them, although that may not even be relevant to this issue. But if it is, it is quite possible that Microsoft will fix this weird behavior in a later update