
Jesus Pedrosa1
164 discussion posts
It happens when the display driver crashes. It can be forced using
CRU's 'restart.exe
• Attachment [protected]: DisplayFusionDebugInfo.zip [166,747 bytes]
3 days ago (modified 3 days ago)
•
#3
Oh yeah that will definitely cause some weird effects, it looks like DisplayFusion can't read the monitor ID's after it's happened. If you restart DisplayFusion does that fix it up?