Okay, this is a weird one.
When I’ve been working in RM11 and then finish and close out (complete with doing a backup) there is what I can only describe as a frame ghost left behind. It is the very top banner that the file opens up in and its frame. It is transparent in that my background whether a solid color or an image shows through in the frame. It cannot be closed by clicking the X on the frame - it’s totally non-responsive. RM11 does not show up in the Task Manager when this happens. Sometimes it will disappear spontaneously but usually the only way to make it go away is to do a Restart or full Shutdown. But as soon as I use RM11 again the same thing happens.
Has anyone else had this happen? I’m on Windows 11 using Edge as my browser.
1 Like
This symptom was experienced, in the thread linked below, but no solution or follow-up:
RM Screen artificat left after closing program - RootsMagic - RootsMagic Community
Yes I have seen it occur – not sure why and I have not been able to replicate on demand.
Not sure it it has to do with display driver or Windows. I doubt the browser is relevant but you never know
I was seeing this not only with RM but other programs in my last computer. It’s a “Windows graphics redraw problem”. Doesn’t happen in my new computer. Google it and you should find several things to test and resolve it.
1 Like
well it still happens on my less than one year old computer. Respectfully that does not mean much. I can not say its RM – but it only happens with RM when it does/
Win + Ctrl + Shift + B. does not resolve. I have also tried different monitor configurations and unpluggin display port cord – not of that helps.
Curious do you use display port or HMDI ?
Just to rule things out, you might try temporarily disabling hardware acceleration in Windows 11:
navigate to Settings > System > Display > Graphics > Change default graphics settings and toggle off “Hardware-accelerated GPU scheduling”.
A system restart is required to apply changes.
1 Like
per AI
When this feature is enabled, the GPU manages its own memory and scheduling rather than the operating system. While this is intended to reduce latency and improve performance, it can sometimes cause the desktop window manager (DWM) to “forget” to redraw a specific area of the screen when a window is closed, leaving a transparent or static frame behind.
Why this often works
-
Buffer Synchronization: HAGS can occasionally cause a mismatch between the application’s frame buffer and what the Windows desktop is actually displaying.
-
Driver Conflict: Certain GPU drivers (particularly older or beta versions) struggle with the handoff between the OS and the hardware, leading to visual artifacts like stuck borders.
1 Like
