SSD-LED on Windows 11 terminates with pop-up "Something went wrong ..."

[sigma415]

Some minutes after booting my Windows 11 machine I get this message and SSD-LED terminates.
SSD-LED is configured to start with windows.
I could restart SSD-LED and it looks like that from now on it stays stable for the wohl session.
Where can I find some kind of logs for reporting here ?

Thanks a lot for your help

[sigma415]

Unfortunately it happened now a second time during the same windows session.
See the screenshot of the popup window:

[SIRprise]

Sorry for the delay: The error happens, if no data could be received multiple times in sequence. You could try to start it after all other tools started. I know somewhere in earlier windows versions was an option to start selected apps in autostart delayed.
You could also try version 1.0.6 which didn't have that kind of error detection. But I'm not sure what the behavior it have.

Your 2nd question was about the location of an error log: Windows is here a bit special, too. Local Apps are stored in C:\Users{your username}\AppData\Local\Apps - and from there in subfolders with cryptic numbers. On my laptop the path continues with Local\Apps\2.0\Data\OECN1W5E.QZQ\1RQ0QDAM.G2G\ssd-..tion_0000000000000000_0001.0000_4883eabc0888858a\Data\1.0.7.1 - there is a file SSDLED20230618.log which could contain more information.

My plan for future releases is to change that logging system. Hope I find time for that soon.

[barcoboy]

Could this dialog be changed so that this dialog box closes automatically in say 30 or 60 seconds? This would allow for the app to be started via the Task Scheduler upon login, and automatically restarted if the app crashes. This is impossible to do now as the dialog staying up keeps the app open, so a restart cannot occur.

[CyberTacoX]

SIRprise: When no data's coming in and you show the error box, is that it; no data will be coming in anymore and the program must be restarted, or would waiting longer possibly get things going again?

If waiting longer could get things going again, could we have an option to not stop everything? To just, for instance, show no drive activity and silently wait for data to start coming in again?

If waiting longer won't help, how about silently auto-reconnecting to whatever's providing that data to get things rolling again?

(As the IT person for my friends and family, I want to use this on their computers, but having the errors popping up during their regular usage is a bit of a full stop for that. Having the "no data" error silently correct itself would be absolutely fantastic.)

[CyberTacoX]

(For the record, if it helps any, I've had the "something went wrong" box pop up at completely random times on various systems, all running Windows 10.)

[SIRprise]

Ah, I think I found a solution. Sorry for the delay, I'm really busy...
https://github.com/SIRprise/SSD-LED/blob/3a4b2d2741cd4d3f139d9612d7bb5d6c88cca9bb/SSD-LED/Form1.cs#L40C28-L40C28 - the tickErrorCountMax is set to 3 to tolerate 3 errors in sequence. It could be increased... This doesn't solve the problem cause. I guess it happens if the computer CPU load is too high or if there is a drive monitored that doesn't exist.
I think I will move the constant tickErrorCountMax to the config file, so it could be changed easily. The fast solution would be to change and compile by yourself or use an older version. I'm not sure if I got the time to rewrite the logging system and include the changes/fixes the next weeks.

Hmm, I'm not sure if a self hiding message (after 30s or something) is a good solution for an error message. Maybe I could show a tooltip instead and add a status line in GUI. I will think about that.