From your screenshot, the “dotted lines” look exactly like
an overlay UI “safe frame / guides / selection” box being drawn on top of the game (it’s not part of the game’s HUD). The key clue is what you described:
they stay in the same relative place and scale with the window—that’s classic overlay behavior.
On your list of installed apps, the
most common causes are:
1)
Xbox Game Bar (widgets / capture UI)
2)
Discord in‑game overlay
3)
Steam overlay
4) (Less often)
Intel Graphics / Arc overlay / driver glitch on newer Yoga 7i models
Here’s the fastest way to nail which one it is.
A) Kill overlays one by one (fast isolation)
1) Discord overlay (very common)
- Discord → User Settings → Game Overlay
- Turn Enable in-game overlay = Off
- Also go to Registered Games and make sure the overlay is off for that game specifically.
- Restart the game and check.
2) Steam overlay
- Steam → Settings → In Game
- Turn off Enable the Steam Overlay while in-game
- Restart the game and check.
3) Xbox Game Bar
- Windows Settings → Gaming → Xbox Game Bar → toggle Off
- Then: Settings → Apps → Installed apps → Xbox Game Bar → Advanced options → Terminate
- Restart the game and check.
If the dotted boxes disappear after disabling one of these, you’ve found the culprit.
B) If it still happens with overlays off: likely graphics / windowed optimization
This can happen if a driver started acting up “yesterday”.
- Windows Settings → System → Display → Graphics
- Click Change default graphics settings
- Turn OFF:
- Optimizations for windowed games
- Variable refresh rate (if you see it)
- Reboot and test again.
C) One question that instantly confirms “overlay vs driver”
Do the dotted lines show up in a
screen recording (Xbox capture / Steam recording / OBS), or are they
only visible on the laptop display?
- If they show in recordings/screenshots: it’s almost certainly a software overlay.
- If they do NOT show in recordings: it’s more likely a driver/display composition artifact.
If you tell me:
1) which game(s) this happens in, and
2) whether it appears in recordings,
I can point to the single most likely setting and exact fix.