dllexp_SetLedData returns ERROR_INSUFFICIENT_BUFFER when setting any configuration

[windows2000bug]

Got message yesterday and forgot to save it. It mentioned some buffer got full and would not allow me to change colors of the lights. I even switched to RGB Fusion and I couldn't do anything with that. The only way I got it to work again was to turn the PC off and kill the power. The LEDs stayed lit after shutdown and went off after I killed the main power switch.

[tylerszabo]

I've hit this issue a few times with GLedAPI. My best guess is that it's timing related as it occurs most often when repeating the set LED flow from Init. If anyone can find a reliable way to reproduce it then it might be possible to work around the driver issue.

[tylerszabo]

Is this related to #8 ?

[windows2000bug]

No it looks like I might be introducing an issue when I have RGB Fusion running at the same time and I switch the lights off from Fusion. I am working to see if I can more easily reproduce the issue on a more consistent basis:

C:\Users\israel\Desktop\rgb fusion>RGBFusionTool.exe -v --color white
Static color: Color [White]
Brightness: 100
Usage: RGBFusionTool.exe [OPTION]...
Set RGB Fusion motherboard LEDs

Options:
-v, --verbose
-c, --color, --static=VALUE
set static color
--cycle, --colorcycle[=SECONDS]
cycle colors, changing color every SECONDS
-b, --brightness=VALUE brightness (0-100)
-l, --list list zones
-?, -h, --help show help and exit

Error: GLedApiDotNet.Raw.GLedAPIv1_0_0Exception: dllexp_SetLedData returned ERROR_INSUFFICIENT_BUFFER
at GLedApiDotNet.Raw.GLedAPIv1_0_0Wrapper.CheckReturn(String apiFunction, UInt32 result)
at GLedApiDotNet.Raw.GLedAPIv1_0_0Wrapper.SetLedData(IEnumerable`1 settings)
at GLedApiDotNet.RGBFusionMotherboard.Set(Int32[] divisions)
at GLedApiDotNet.RGBFusionMotherboard.SetAll(LedSetting ledSetting)
at RGBFusionTool.RGBFusionMain.LazyMotherboard.SetAll(LedSetting ledSetting)
at RGBFusionTool.Application.Main(String[] args)

This might be completely avoided if I or other users don't have RGB Fusion open or using both at the same time.

[windows2000bug]

Just for testing, I powered off my system and pulled the power. I then launched windows and started using the tool w/o even launching RGB Fusion. Just to make sure there was nothing in the buffer.

When repeated commands in quick succession:
RGBFusionTool.exe -v --color blue
Static color: Color [Blue]
Brightness: 100

RGBFusionTool.exe -v --color blue
Static color: Color [Blue]
Brightness: 100

RGBFusionTool.exe -v --color blue
Static color: Color [Blue]
Brightness: 100

RGBFusionTool.exe -v --color blue
Static color: Color [Blue]
Brightness: 100
Usage: RGBFusionTool.exe [OPTION]...
Set RGB Fusion motherboard LEDs

Options:
-v, --verbose
-c, --color, --static=VALUE
set static color
--cycle, --colorcycle[=SECONDS]
cycle colors, changing color every SECONDS
-b, --brightness=VALUE brightness (0-100)
-l, --list list zones
-?, -h, --help show help and exit

Error: GLedApiDotNet.Raw.GLedAPIv1_0_0Exception: dllexp_SetLedData returned ERROR_INSUFFICIENT_BUFFER
at GLedApiDotNet.Raw.GLedAPIv1_0_0Wrapper.CheckReturn(String apiFunction, UInt32 result)
at GLedApiDotNet.Raw.GLedAPIv1_0_0Wrapper.SetLedData(IEnumerable`1 settings)
at GLedApiDotNet.RGBFusionMotherboard.Set(Int32[] divisions)
at GLedApiDotNet.RGBFusionMotherboard.SetAll(LedSetting ledSetting)
at RGBFusionTool.RGBFusionMain.LazyMotherboard.SetAll(LedSetting ledSetting)
at RGBFusionTool.Application.Main(String[] args)

In both of these two cases tonight, I was able to continue using after getting the error message. This unlike last night where the lights were unresponsive, even after reboot. To fix that, I had to pull the power.

[tylerszabo]

I suspect that having this tool run while anything else is trying to set LEDs will not work well. Gigabyte's tools go to some effort to kill other processes that might be trying to set lights. I've created issue #11 to track work on detecting and warning of conflicting processes.

[windows2000bug]

I did try on a fresh boot w/o starting the Fusion UI, though on startup there has to be some processes associated with Fusion as the lights come on, when I login to Windows. I was able to generate this one entering a lot of commands in quick succession. Do you have Fusion installed and/or running in the background?

[tylerszabo]

Whenever you run one of those tools Gigabyte puts some daemons in startup. I put a list of processes I've identified in issue #11.

[windows2000bug]

I keep upping the sleep time and I don't know if it really has any effect on throwing this error. It isn't one zone in particular. Granted once I get setting multi zone, I am hoping it will help, though it might also turn into an all or nothing.

[windows2000bug]

Good news the tool can run w/o RGB Fusion installed, bad news it didn't fix the issue. I did different tests and I can not find anything in common that would cause the problem. I wrote a SPAM script to help test:

$path = $PSScriptRoot + "\RGBFusionTool.exe"

$x=0
while ($true) {

if ($x -eq 0) {
    $rgb="red"
} elseif ($x -eq 1) {
    $rgb="green"
} elseif ($x -eq 2) {
    $rgb="blue"
    $x=-1
}
& $path -v -c $rgb
write-host $x   
sleep  2

$x+=1

}

I will up the time a lot to like 5 seconds on sleep to see if it is just a red herring or not.