Strobelight - LightBoost Utility for AMD/ATI and NVIDIA

[A1N_noBungus]

(10-19-2022 01:00 AM)ToastyX Wrote:  

(10-18-2022 10:51 PM)A1N_noBungus Wrote:  [2022-10-18 18:50:39.126] INIT: No compatible displays found.

Is that log with DisplayPort or HDMI? Show me the log with the other connection as well.

The first log was with DisplayPort. Here is the log with HDMI:

[2022-10-18 21:04:44.637] LOAD(AMD): LoadLibrary("atiadlxx.dll") = SUCCESS
[2022-10-18 21:04:44.644] LOAD(AMD): ADL_Main_Control_Create() = SUCCESS
[2022-10-18 21:04:44.644] LOAD(NVIDIA): NvAPI_Initialize() = ERROR -2
[2022-10-18 21:04:44.644] SEND(AMD, 0, 0, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.644] SEND(AMD, 0, 1, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.644] SEND(AMD, 0, 2, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.644] SEND(AMD, 0, 3, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.644] SEND(AMD, 0, 4, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.644] SEND(AMD, 0, 5, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.644] SEND(AMD, 0, 6, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 0, 7, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 0, 8, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 0, 9, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 0, 10, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 0, 11, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 0, 12, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 0, 13, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 0, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 1, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 2, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 3, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 4, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 5, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 6, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 7, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 8, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 9, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 10, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 11, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 12, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 1, 13, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 0, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 1, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 2, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 3, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 4, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 5, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 6, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 7, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 8, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 9, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 10, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 11, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 12, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 2, 13, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 0, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 1, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 2, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 3, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 4, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 5, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 6, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 7, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 8, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 9, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 10, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 11, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 12, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 3, 13, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 4, 0, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 4, 1, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 4, 2, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 4, 3, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.649] SEND(AMD, 4, 4, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 4, 5, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 4, 6, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 4, 7, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 4, 8, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 4, 9, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 4, 10, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 4, 11, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 4, 12, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 4, 13, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 0, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 1, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 2, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 3, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 4, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 5, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 6, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 7, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 8, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 9, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 10, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 11, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 12, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] SEND(AMD, 5, 13, 0.000): <6E> 51 81 59 E7 = ERROR -7
[2022-10-18 21:04:44.650] INIT: No compatible displays found.

[ToastyX]

(10-19-2022 01:05 AM)A1N_noBungus Wrote:  The first log was with DisplayPort. Here is the log with HDMI:

Is this able to detect the monitor? https://www.monitortests.com/forum/Threa...yID-Writer

If not, it's a driver problem.

[A1N_noBungus]

(10-19-2022 10:09 PM)ToastyX Wrote:  

(10-19-2022 01:05 AM)A1N_noBungus Wrote:  The first log was with DisplayPort. Here is the log with HDMI:

Is this able to detect the monitor? https://www.monitortests.com/forum/Threa...yID-Writer

If not, it's a driver problem.

The EDWriter tool was unable to detect my monitor. I am on AMD driver 30.0.15021.11005. Should I rollback and try Strobelight again?

[ToastyX]

(10-19-2022 10:34 PM)A1N_noBungus Wrote:  The EDWriter tool was unable to detect my monitor. I am on AMD driver 30.0.15021.11005. Should I rollback and try Strobelight again?

That's an old driver. You should try the latest driver: https://www.amd.com/en/support/kb/releas...in-22-10-1

[A1N_noBungus]

(10-19-2022 10:40 PM)ToastyX Wrote:  

(10-19-2022 10:34 PM)A1N_noBungus Wrote:  The EDWriter tool was unable to detect my monitor. I am on AMD driver 30.0.15021.11005. Should I rollback and try Strobelight again?

That's an old driver. You should try the latest driver: https://www.amd.com/en/support/kb/releas...in-22-10-1

Updating my driver worked, thank you Toasty!

[zhAAzy]

Hello dear ToastyX,

I am using your Strobelight since around 2015 when I bought my xl2411t. Since then I loved every second of it. Sadly now days GPU's don't have any DVI connection anymore. Last week I upgraded from a GTX 1070 TI to a RTX 4070 TI and hooked my xl2411t with the Club 3D CAC-1010 active Adapter DisplayPort to DVI-D HDCP ON to the my new GPU. Everything is working fine besides I can't use your Strobelight tool anymore. The program tells me: no required monitor found / no compatible monitor found

"Device DISPLAY\BNQ7F1E\5&26ffd291&0&UID4353 was configured.

Driver Name: monitor.inf
Class Guid: {4d36e96e-e325-11ce-bfc1-08002be10318}
Driver Date: 06/21/2006
Driver Version: 10.0.19041.1151
Driver Provider: Microsoft
Driver Section: PnPMonitor.Install
Driver Rank: 0xFF2000
Matching Device Id: *PNP09FF
Outranked Drivers:
Device Updated: false
Parent Device: PCI\VEN_10DE&DEV_2782&SUBSYS_88A61043&REV_A1\4&341ca995&0&0008"

any idea how I could get it back to work with your tool? Since I am experiencing really, really low blackbleeding? but it's kinda driving me nuts since I never had this issue. I also already tried getting rid of it with tweaking RGB, Gamma und Monitor settings.

[ToastyX]

(04-27-2023 12:47 AM)zhAAzy Wrote:  Hello dear ToastyX,

I am using your Strobelight since around 2015 when I bought my xl2411t. Since then I loved every second of it. Sadly now days GPU's don't have any DVI connection anymore. Last week I upgraded from a GTX 1070 TI to a RTX 4070 TI and hooked my xl2411t with the Club 3D CAC-1010 active Adapter DisplayPort to DVI-D HDCP ON to the my new GPU. Everything is working fine besides I can't use your Strobelight tool anymore. The program tells me: no required monitor found / no compatible monitor found

"Device DISPLAY\BNQ7F1E\5&26ffd291&0&UID4353 was configured.

Driver Name: monitor.inf
Class Guid: {4d36e96e-e325-11ce-bfc1-08002be10318}
Driver Date: 06/21/2006
Driver Version: 10.0.19041.1151
Driver Provider: Microsoft
Driver Section: PnPMonitor.Install
Driver Rank: 0xFF2000
Matching Device Id: *PNP09FF
Outranked Drivers:
Device Updated: false
Parent Device: PCI\VEN_10DE&DEV_2782&SUBSYS_88A61043&REV_A1\4&341ca995&0&0008"

any idea how I could get it back to work with your tool? Since I am experiencing really, really low blackbleeding? but it's kinda driving me nuts since I never had this issue. I also already tried getting rid of it with tweaking RGB, Gamma und Monitor settings.

Initializing the monitor won't work with the adapter, but you can use HDMI to initialize if necessary. Don't install the refresh rates with HDMI. Just run strobelight.exe and ignore the message about refresh rates. Once the monitor is initialized, it will stay initialized unless the monitor is unplugged or loses power (you can still turn it off). Then you can use the monitor with the adapter after installing the refresh rates as you would normally, but to run Strobelight as a refresh rate switcher, you will need to skip the initialization part by downloading this and renaming it to strobelight-skip.exe: https://www.monitortests.com/strobelight-d2.zip

[zhAAzy]

(04-29-2023 05:12 AM)ToastyX Wrote:  

(04-27-2023 12:47 AM)zhAAzy Wrote:  Hello dear ToastyX,

I am using your Strobelight since around 2015 when I bought my xl2411t. Since then I loved every second of it. Sadly now days GPU's don't have any DVI connection anymore. Last week I upgraded from a GTX 1070 TI to a RTX 4070 TI and hooked my xl2411t with the Club 3D CAC-1010 active Adapter DisplayPort to DVI-D HDCP ON to the my new GPU. Everything is working fine besides I can't use your Strobelight tool anymore. The program tells me: no required monitor found / no compatible monitor found

"Device DISPLAY\BNQ7F1E\5&26ffd291&0&UID4353 was configured.

Driver Name: monitor.inf
Class Guid: {4d36e96e-e325-11ce-bfc1-08002be10318}
Driver Date: 06/21/2006
Driver Version: 10.0.19041.1151
Driver Provider: Microsoft
Driver Section: PnPMonitor.Install
Driver Rank: 0xFF2000
Matching Device Id: *PNP09FF
Outranked Drivers:
Device Updated: false
Parent Device: PCI\VEN_10DE&DEV_2782&SUBSYS_88A61043&REV_A1\4&341ca995&0&0008"

any idea how I could get it back to work with your tool? Since I am experiencing really, really low blackbleeding? but it's kinda driving me nuts since I never had this issue. I also already tried getting rid of it with tweaking RGB, Gamma und Monitor settings.

Initializing the monitor won't work with the adapter, but you can use HDMI to initialize if necessary. Don't install the refresh rates with HDMI. Just run strobelight.exe and ignore the message about refresh rates. Once the monitor is initialized, it will stay initialized unless the monitor is unplugged or loses power (you can still turn it off). Then you can use the monitor with the adapter after installing the refresh rates as you would normally, but to run Strobelight as a refresh rate switcher, you will need to skip the initialization part by downloading this and renaming it to strobelight-skip.exe: https://www.monitortests.com/strobelight-d2.zip

So, I tried. Plugged in HDMI /w PC. Did run Strobelight.exe (the normal one) it did initialized but gave me an error like you said. Replugged DVI, did run Strobelight-setup.exe. Installed rates and rebooted. Tried to reintialized with strobelight-skip but didnt worked - still no compatible found.

Dunno. Maybe its just me who's imaging something is off. But when I look in black corners it doesn't feel right. It feels not what I used to. Also what i meant with blackbleeding, I guess i meant artifacts. Its not smooth like it was when Strobelight was working w/o adapter.

Nvm I got it to work now. Dunno how redid everything and it works now Monitor OSD shows me 3d Mode again =)

[chinobino]

Hi ToastyX, first I want to say thank you for creating the strobelight application, which I have been using for 10 years!

Unfortunately I have come across an issue using the latest Nvidia driver 535.98 (both Game Ready and Studio versions) in Windows 10 and Windows 11.

My monitor is the ASUS VG278H and is connected to an ASUS RTX 2070 mini via Dual DVI (with no adapters required).

I have installed 'strobelight-beta4-swapped' using the strobelight-setup.exe and the monitor is running at 121 Hz with lightboost enabled, which is great.

The problem is that the 'strobelight.exe' (that I use daily to adjust the monitor brightness) won't start and I get the error 'No compatible displays found.'

I ran 'strobelight-d2.exe' and here is the debug log:

Code:

[2023-05-31 14:40:44.787] LOAD(AMD): LoadLibrary("atiadlxx.dll") = ERROR 126
[2023-05-31 14:40:44.790] LOAD(AMD): LoadLibrary("atiadlxy.dll") = ERROR 126
[2023-05-31 14:40:44.795] LOAD(NVIDIA): NvAPI_Initialize() = SUCCESS
[2023-05-31 14:40:44.796] SEND(NVIDIA, 0, 8, 0.000): <6E> 51 81 59 E7 = ERROR -1
[2023-05-31 14:40:44.796] INIT: No compatible displays found.

If you need more info just let me know.

[Edit] EDWriter-beta2 also says 'No compatible displays found.'

[ToastyX]

(05-31-2023 06:54 AM)chinobino Wrote:  Hi ToastyX, first I want to say thank you for creating the strobelight application, which I have been using for 10 years!

Unfortunately I have come across an issue using the latest Nvidia driver 535.98 (both Game Ready and Studio versions) in Windows 10 and Windows 11.

If the problem only happens with that driver version and not previous versions, then it's a driver bug that needs to be reported to NVIDIA. This has happened before, and NVIDIA fixed it within a couple of releases.