Bad Module Info Has Stopped Working | Fast Crash Fixes

When Windows throws this message, a program failed while grabbing graphics, input, or memory. The label looks odd, but the root causes are familiar: a clash with a screen overlay, a flaky display driver, or a strict mitigation that blocks the process. In this guide you’ll get a quick plan that restores stability with minimal trial and error, plus a few deeper repairs if the crash keeps coming back.

What The Error Means And Why It Pops Up

Quick context: The crash often appears in games or heavy 3D apps that switch between display modes or call overlays. Microsoft’s exploit protection applies per application and can be tuned in Windows Security or via policy, so a single program can carry custom rules without lowering safety system-wide. Source, Reference.

Overlay layers introduce another common trigger. Xbox Game Bar, Steam, Nvidia, AMD, or Discord can hook into the same process space. Discord acknowledges reliability limits for its overlay across titles, which makes it a prime suspect when crashes show up only while voice chat is active. Source.

One more pattern: Windows Fullscreen optimizations blends exclusive fullscreen with windowed behavior for faster Alt-Tab and overlays. On some rigs that bridge misbehaves, which leads to sudden exits right after a mode switch. Reliable tutorials show that disabling fullscreen optimizations for the game can stop the crash. Guide, Walkthrough.

Bad Module Info Has Stopped Working — Causes And Fixes

Work through these in order. Start with the fast checks, then move to deeper repairs only if the message returns.

1. Close And Relaunch The App — Kill the process from Task Manager, then reopen. Temporary hooks or failed overlays clear on a fresh start. This alone resolves many “bad module info has stopped working” popups. Source.
2. Disable Fullscreen Optimizations — Right-click the game EXE > Properties > Compatibility > check Disable fullscreen optimizations > Apply. Test again. This toggle removes the hybrid display mode that often trips the crash. Forum tutorial, TheWindowsClub.
3. Run In Compatibility Mode — In the same dialog, tick Run this program in compatibility mode and choose an older Windows version if the title predates your OS build. Many help articles list this as a stable workaround for older games. Source.
4. Turn Off Overlays — Disable Xbox Game Bar (Settings > Gaming), Steam overlay, Nvidia/AMD overlays, and Discord overlay. Discord flags overlay reliability limits, and recent Windows builds can keep Game Bar hooks active even when “off,” so test with every overlay fully disabled. Discord note, Windows report.
5. Update Graphics Drivers — Use the GPU vendor app or Device Manager to install current drivers, then reboot. Out-of-date display stacks cause mode switches to crash. Steps.
6. Tune Exploit Protection Per App — Open Windows Security > App & browser control > Exploit protection settings. Under Program settings, add your game EXE and relax a single mitigation at a time to spot the blocker. You can export a safe XML once you find the sweet spot. How-to, Mitigation list.
7. Repair The Game Files — In Steam, Epic, or the publisher launcher, run the verify or repair tool to replace missing or corrupt files. If the crash is tied to one title, this is a quick win. Guide.
8. Run DISM And SFC — Open an elevated Command Prompt. Run DISM /Online /Cleanup-Image /RestoreHealth, then run sfc /scannow. These built-in tools repair the Windows image and protected files that apps depend on. Microsoft’s support doc lists the exact order. Microsoft, DISM details, SFC how-to.
9. Reinstall The App — If one program always trips the message, remove it from Apps > Installed apps or Control Panel, reboot, and install clean. This clears broken dependencies. Source.

Fast Reference: Symptoms, Likely Causes, And Quick Moves

Step-By-Step: Turn Off Overlays Cleanly

Overlays hook deep into a running process. Turning one off while the game runs can leave stray hooks. Use these clean steps so your test is valid.

• Exit The Game Fully — Quit to desktop and wait a few seconds so the process closes.
• Disable Xbox Game Bar — Go to Settings > Gaming > Xbox Game Bar and toggle off. Reboot if the overlay keeps popping after controller input; some builds retain hooks even when set to off. Report.
• Turn Off Discord Overlay — In Discord, User Settings > Game Overlay > toggle off. Close Discord from the tray. Discord lists overlay reliability limits, so a full exit is a solid test. Note.
• Disable Vendor Overlays — Switch off Steam overlay and GPU overlays in GeForce Experience or AMD Adrenalin. Reboot before testing again.

Step-By-Step: Adjust Exploit Protection Per App

Exploit protection can stop memory tricks used by malware. On some games, one mitigation collides with a legit call. Windows lets you change settings for a single EXE so you stay safe elsewhere.

1. Open Exploit Protection — Windows Security > App & browser control > Exploit protection settings. Guide.
2. Add The Game EXE — Under Program settings choose Add program to customize > Choose exact file path and point to the EXE.
3. Relax One Mitigation — Toggle off one item such as Control flow guard or Force randomization for images. Test the game. If it runs, export XML so you can share the policy or restore later. Reference.
4. Roll Back Tests — If nothing helps, remove the per-app entry to return to defaults.

Deep Repair: Fix Core Windows Files Safely

When crashes appear across many apps, repair the OS image and protected files.

1. Open An Elevated Command Prompt — Type cmd in Start, right-click Command Prompt, and choose Run as administrator. Microsoft.
2. Repair The Image — Run DISM /Online /Cleanup-Image /RestoreHealth and wait. Learn.
3. Repair Protected Files — Run sfc /scannow and let it replace any damaged files. Reboot when done. How-to.

Clean Boot And Reliability Checks

A clean boot strips startup apps and third-party services so you can see whether a background tool is the real culprit. Microsoft’s guide outlines the exact MSConfig switches. Run this test when the crash happens even with overlays off. Steps, Forum tutorial.

• Start A Clean Boot — Open msconfig, hide Microsoft services, disable the rest, and reboot. Retest the game.
• Re-enable In Batches — Turn services back on in groups so you catch the offender fast.
• Use Reliability Monitor — Open perfmon /rel. Look for red X entries around the time of the pop-up. Click an entry to read details and spot repeat patterns. Guide, Dell.

Display Mode Tweaks That Prevent The Crash

Display mode switches are where many apps fall over. Two adjustments keep the pipeline stable on finicky rigs.

• Prefer Borderless Window — If disabling fullscreen optimizations isn’t enough, try borderless window in the game’s settings. This avoids full exclusive mode and reduces mode switching.
• Match Refresh And V-Sync — Set the game refresh to the panel rate and toggle V-Sync or Enhanced Sync to reduce rapid flips during focus changes. Even small mismatches can trigger timing bugs in overlays.

When The Error Mentions Specific Games Or Launchers

Some launchers inject helpers that run alongside the game. If the crash only hits one ecosystem, target that stack.

• Epic Games Titles — If the message appears with Fortnite, also disable fullscreen optimizations on EpicGamesLauncher.exe so the background helper doesn’t trigger the mode bridge. Tip.
• Steam — Turn off the Steam overlay and verify files. If controller shortcuts call Game Bar instead of Steam’s menu, reset Game Bar and retest.
• Legacy Games — Use compatibility mode and disable overlays entirely. Old DirectX titles react badly to modern overlay hooks.

When To Suspect Hardware Or Thermal Limits

Most cases trace back to software, yet stressed hardware can present the same crash label. Short spikes in temperature or a borderline PSU rail can crash a 3D title during a map load. Before buying parts, run quick checks.

• Watch Temperatures — Use your GPU tool to log temps during a match. If spikes align with the error, clean dust and retest at a lower power target.
• Reset GPU Tuning — If you overclocked, return to default. Forum threads link sudden crashes with unstable boosts under overlay load. Example.
• Check RAM Stability — If the system recently gained new memory, test with the vendor tool or Windows Memory Diagnostic.

Keep The Fixes Without Losing Safety

You don’t need to lower security across the system to stop this crash. Windows lets you apply exploit protection changes to one executable, export those edits, and re-import after a reinstall. Microsoft’s docs describe the XML workflow for consistency on multiple PCs. How-to.

After you find the winning combo, make a tiny checklist for that title: display mode, overlays to leave off, and any program-level mitigations you changed. Keep that note next to the launcher so the fix survives driver updates and OS refreshes.

Why The Name Looks Strange In Logs

In Reliability Monitor or Event Viewer you may see the application listed as bad_module_info with version 0.0.0.0 and an unknown faulting module. That label is a Windows placeholder for a crash where the process context is missing or a StackHash is recorded instead of a named DLL. It points to a generic access violation rather than a single vendor file. You can still act on patterns: repeated entries near mode switches, overlay use, or driver updates. Microsoft Q&A threads show this exact label and logs. Example.

With these steps, the odd label starts to make sense. A small tweak to display mode, overlays, or exploit rules removes the clash and gives your game a clean runway again. Test again for your setup today.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback