Strobelight - LightBoost Utility for AMD/ATI and NVIDIA

[Wizard]

(09-14-2015 03:53 AM)kevindd992002 Wrote:  I installed a fresh Windows 10 OS on my system and found a weird bug with Strobelight. Well, when I come from a standard boot process of Windows stroblight does one of two things randomly:

1.) Triggers properly (strobelight mode with green 3D LED turned on my my BenQ XL2420TX) at the logon screen, no problems whatsoever. When I logon using my username and password, it stay at strobelight mode and would function without any problems.

2.) Strobelight is off at the logon screen and would not turn on until I logon using my username and password. What's more weird is that after I logon and wait for a few seconds, it flashes the screen black for a few seconds before strobelight mode activates (very similar to when enabling 3D mode coming from standard mode which I know that it is in fact what strobelight does).

What gives?

I'm actually experiencing exactly the same thing you are. I'm also sure it did not happen before I installed windows 10. ToastyX said it might be a driver problem but I'm just starting to think it's part of Windows 10 now.

For me there's actually a super-rare 3rd option. Sometimes my computer BOOTS in LIGHTBOOST mode, and when that happens, strobelight starts normally (I don't get that accursed 'no strobed refresh rates found' error, which I actually just fixed by task scheduling restart.exe on boot as per ToastyX's recommendation) but the Strobing on/Strobing Off buttons do nothing more than flash the screen for about 3 seconds. It's very peculiar, not even a restart.exe fixes it, only a complete system reboot.

Anyway my point is: None of these weird issues happened before windows 10, strobelight worked perfectly, so that leads me to believe that windows 10 is just buggy. I'm also leaning towards the idea that the 'Fast Startup' option or the 'wake from hybrid sleep' or similar power options are causing it.

EDIT: Whoops, apparently 'Fast Startup' WAS in windows 8.1, but that doesn't mean that a change in the functionality in windows 10 can't still be the culprit.