So, you wanted to take a break from work and just play PUBG on your computer. The moment you launched the game, the app crashed and displayed the error: Bad_Module_Info has stopped working on Windows 10.
Well, things don’t seem to look right here, does it?
Games, regardless of whether they’re offline or not, are known to consume a lot of your system’s computing resources. When there aren’t enough resources to launch a game, the app crashes and shows error messages like Bad_Module_Info.
What is Bad_Module_Info on Windows 10?
This error message usually appears after installing the Windows 10 1709 Creators Update. Many users have reportedly received this error while playing Steam games.
According to them, once your computer is affected by this error, all apps, especially games, crash when trying to launch them or while they’re running.
If you are constantly annoyed by this error message, read on because we have the perfect fixes for you.
How to Fix Bad_Module_Info on Windows 10
Here’s what you should do if you encounter the Bad_Module_Info error on your Windows computer:
Fix #1: Close Netflix or the game
If Netflix or the game stops responding, close it by clicking the X button. If it doesn’t work, press the Windows + ALT + Delete keys. This will open the Task Manager. In the list of active apps or processes, find Netflix or the game. Click on it and hit End Task.
At this point, Netflix or the game’s process should be ended. Restart your computer and relaunch the app.
Fix #2: Disable full-screen optimization
The full-screen optimization feature is designed to enhance a user’s video or gaming experience. Although useful, this feature sometimes causes errors. So, disabling it may work and fix the Bad_Module_Info error.
To disable full-screen optimization, right-click on the Netflix or game app and select Properties. Under the Compatibility tab, untick the box next to the Disable Fullscreen Optimizations option. Hit OK to save the changes.
Fix #3: Update the graphics card driver
An outdated graphics card driver can trigger the Bad_Module_Info error to show. In such a case, you might want to check if you are running an updated version of your graphics card driver. Otherwise, update it.
To update your graphics card driver, do the following:
- Use the Windows + R keys to open the Run dialog box.
- Into the text field, input devmgmt.msc.
- Press Enter. This will open the Device Manager window.
- Under Display Adapters, right-click on your graphics card driver.
- Choose Update Driver.
- Restart your computer.
Fix #4: Delete system junk
Often times, errors like the Bad_Module_Info surface because of junk files that are interfering with important system processes. So, if junk files are to blame, make sure you delete them.
Sure, you can perform the deletion process manually. However, that would be time-consuming and daunting as you would have to go through each folder to manually scan for any suspicious files.
The best way to delete system junk is to use a PC repair tool like Outbyte PC Repair. In just a few clicks, this tool can detect unnecessary files that are only consuming a large chunk of your hard drive space. It will also attempt to find and fix whatever issue your computer is dealing with.
Fix #5: Update the BIOS
If all else fails, your last resort is to update your BIOS. For this fix, you need to know the manufacturer and the model of your motherboard. If you are not sure, please do not proceed as you might only worsen the problem.
To update the BIOS, follow these steps:
- Into the search field, input Command Prompt.
- Click on Command Prompt from the search results.
- Into the command line, enter this command: wmic baseboard get product, manufacturer, version, serialnumber
- Take note of the information that displays on your screen. And then, visit the website of your motherboard’s manufacturer. Find the BIOS update that is compatible with your motherboard. Click on it and follow the instructions provided.
- Once the BIOS is updated, relaunch the Netflix or game app.
That’s about the Bad_Module_Info error on Windows 10. The above solutions worked for many users. Work your way down the list until you find a fix that works for you, too.