Quick answer: Apply resolution and mode changes fully, validate them against supported modes, offer a revert timeout, and persist the chosen settings.
Broken display options are incomplete or unvalidated changes. Here is how to fix them.
How to fix it
1. Apply changes fully
Set the resolution, fullscreen mode, and refresh together and apply them as one coherent change. Partial application (resolution without mode, or vice versa) leaves the game in a wrong or off-screen state.
2. Validate against supported modes
Only offer and apply resolutions and refresh rates the display supports. Applying an unsupported mode can blank the screen or fail. Query supported modes and constrain the options to them.
3. Offer revert and persist
After applying a display change, show a confirm-or-revert timeout so a bad mode the player cannot see auto-reverts, and persist the confirmed settings so they survive restarts without reverting on their own.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.