Hmmm. The only display-related "known" bug that I know of is when your graphics driver updates, it *can* crash Rainmeter. It's usually happens if a skin is currently being redrawn while the drivers are in the middle of an update.
But, most of the crashes described here seem to be something else.
First let me address some of the questions:
SilverAzide wrote: ↑November 15th, 2022, 1:48 am
Could something in Windows be telling Rainmeter there are ZERO active display devices and causing it to crash?
I doubt this is the problem but you never know. Since you said you can't easily reproduce it (I can't either). Nothing significant has changed with monitor detection - at least on the Rainmeter end. Maybe a Windows update changed something with its monitor detection...
rlnoonan wrote: ↑November 15th, 2022, 10:27 pm
Is it possible that it holds the old video information from the last crash or something?
All that information is provided by Windows just before Rainmeter logs it. Rainmeter asks Windows for monitor information when the application starts, and if any of the display settings (or work area) changes. Rainmeter doesn't retain any of this information when Rainmeter closes, it just gets it from Windows at start up (or changes).
If those values are wrong at the time when Rainmeter logs it, then something has to be wrong on the Windows side of things.
But there is something about your logs that intrigues me...there are 2 System: Display settings changed
messages back to back (literally a few milliseconds apart). Normally, when this message happens Rainmeter will get all the monitor information again (basically to update the monitor variables, and move any skins that are no longer on a monitor). Since these messages happen rapidly, there might be a timing issue where the first message is in the process of clearing the "old" monitor values and setting the new ones - and then the second message clears them again before the first message is finished.
But this is all speculation.
Could both of you revert back to Rainmeter 220.127.116.1163
and check if Rainmeter is crashing in the same manner as you described?
You will probably want to uncheck
"automatic updating" first
, so that Rainmeter won't update to the latest again.
I would also leave "Debug mode" on, and it would be helpful if you could just run the standard "illustro" skins to test with (to eliminate the possibility that a 3rd party skin or plugin is causing this in some way). You can use Rainmeter safe start
to load the standard skins.
If Rainmeter version 4.5.14 doesn't cause any crashes, I can look for other issues that might cause crashing, but if the crashes still happen, then I fear some sort of Windows/driver update might be causing issues.