How to Fix Games Crashing With Out-of-Memory Errors (2026 Guide)

Nothing kills a gaming session faster than a crash to desktop with an “out of memory” error staring back at you. The frustration doubles when you are running 32 GB of RAM and a high-end GPU that should handle anything you throw at it. I have spent years helping PC gamers troubleshoot this exact problem, and the root cause is almost never what people expect.

If you want to learn how to fix games crashing with out-of-memory errors, you are in the right place. This guide walks through every common cause, from simple background app overload to deep system-level memory leaks. I will cover quick fixes you can try right now, plus advanced diagnostics for stubborn crashes.

The key insight is that “out of memory” does not always mean you need more RAM. Games use two different types of memory, and Windows manages them differently. Understanding that distinction is what separates a five-minute fix from weeks of frustration.

Let us start with what actually causes these errors, then work through the solutions from easiest to most advanced.

What Causes Out-of-Memory Errors in Games?

Out-of-memory errors happen when a game requests memory and Windows cannot provide it at that moment. The request fails, and the game crashes to desktop. That sounds simple, but the reason Windows cannot fulfill the request varies wildly.

The most common causes I see in gaming communities break down into a few categories. Here is what triggers OOM crashes:

• Memory leaks – A bug in the game or a background application causes memory to be allocated but never freed. Usage climbs steadily until the system runs dry, even if you have 32 GB or more of RAM.

• VRAM exhaustion – Texture quality, resolution, and mods consume more video memory than your GPU has available. The game tries to allocate a rendering resource and fails.

• Background application drain – Browsers with dozens of tabs, Discord overlays, streaming software, and even webview processes silently eat gigabytes before your game even launches.

• Page file disabled or too small – Many gamers disable the page file thinking it improves performance. This actually causes OOM crashes because Windows has no overflow buffer when physical RAM fills up.

• Corrupted or outdated graphics drivers – Driver problems can cause incorrect memory reporting, phantom VRAM usage, or allocation failures on GPUs that should have plenty of headroom.

• Hardware instability – Overclocked RAM, loose memory sticks, or failing modules can produce memory errors that look exactly like software OOM crashes.

The tricky part is that Task Manager often shows plenty of free RAM when these crashes happen. That leads many gamers to assume the error message is wrong. It is not wrong. It is telling you about a different type of memory than what you are looking at.

RAM vs VRAM: Understanding the Difference

The single biggest source of confusion in OOM troubleshooting is the difference between system RAM and video RAM. Games use both, Windows manages them separately, and error messages rarely specify which one ran out.

RAM (system memory) is the general-purpose memory installed on your motherboard. It holds game logic, AI calculations, audio data, physics computations, and everything the CPU processes. Most gaming PCs today have 16 GB to 64 GB of RAM.

VRAM (video memory) is dedicated memory on your graphics card. It stores textures, frame buffers, shader data, and geometry that the GPU needs to render frames. A mid-range GPU might have 8 GB of VRAM, while high-end cards have 16 GB to 24 GB.

When a game says “out of memory,” it could mean either type is exhausted. When it says “out of video memory” or mentions a “rendering resource,” that specifically points to VRAM. The error wording matters.

Here is the part that trips people up: lowering in-game graphics settings reduces VRAM usage but barely touches system RAM. If your crash is a VRAM issue, turning down texture quality and resolution will fix it. If it is a system RAM issue, you need to look at background apps and page file settings instead.

Committed Memory vs Physical Memory Explained

This is where most troubleshooting guides lose people. You can have 32 GB of physical RAM installed, Task Manager can show 20 GB free, and you still get an out-of-memory error. How is that possible?

The answer lies in committed memory. Windows has a two-tier memory system: physical RAM and a virtual memory buffer called the commit charge. The commit limit equals your physical RAM plus your page file size.

When an application asks Windows for memory, Windows allocates committed memory. That commitment is backed by physical RAM first, then the page file as overflow. The problem is that Windows tracks the commitment, not the actual usage.

Imagine this scenario: you have 32 GB of RAM and no page file. A background process like msedgewebview2.exe quietly commits 28 GB of virtual memory without actually using most of it. Your game tries to commit another 8 GB. Windows refuses because the commit limit of 32 GB is already consumed. You crash with an out-of-memory error even though Task Manager shows 20 GB of physical RAM sitting unused.

This is why disabling the page file is dangerous. The page file is not just overflow storage. It raises the commit limit, giving Windows room to grant memory commitments that applications request. Without it, the commit limit equals your physical RAM, and background processes can exhaust that limit long before your game gets its share.

The fix is simple: keep the page file enabled and let Windows manage it, or set a custom size of at least 1 to 1.5 times your physical RAM. I cover the exact steps later in this guide.

How to Diagnose Memory Issues Using Task Manager

Before changing anything, you need to figure out what is actually consuming your memory. Task Manager is your first diagnostic tool, and it reveals more than most people realize.

Here is how to use it effectively for OOM troubleshooting:

Step 1: Press Ctrl + Shift + Esc to open Task Manager. Click the “Performance” tab and select “Memory” in the left sidebar.

Step 2: Look at three numbers: “In use” (physical RAM actively consumed), “Available” (RAM ready for use), and “Committed” (the charge against your commit limit). The committed number is the one most people ignore, and it is often the key.

Step 3: If committed memory is near your commit limit but “in use” memory is low, you have a committed memory problem. A background process is reserving memory without using it. Keep the page file enabled and identify the culprit.

Step 4: Switch to the “Details” tab. Click the “Commit size” column header to sort by committed memory. Look for processes committing large amounts of memory. Common offenders include msedgewebview2.exe, browser processes, Discord, and game launchers.

Step 5: For VRAM diagnostics, open Task Manager, go to the “Performance” tab, and click on your GPU. You will see “Dedicated GPU memory” usage. If your game crashes when that number approaches your GPU’s VRAM capacity, you have a VRAM problem.

Step 6: Launch your game and keep Task Manager visible on a second monitor or windowed mode. Watch how memory climbs over time. If usage increases steadily without plateauing, you are looking at a memory leak.

For deeper diagnostics, Resource Monitor provides a more detailed breakdown than Task Manager. Press Win + R, type “resmon,” and check the Memory tab for a detailed per-process breakdown including standby and modified memory.

Quick Fixes for Games Crashing With Out-of-Memory Errors

How to fix games crashing with out-of-memory errors starts with these quick fixes. They resolve the majority of OOM crashes without any advanced tools.

1. Close background applications before launching your game. Close browsers, streaming apps, and unnecessary background processes. Discord and Spotify alone can consume 1 to 2 GB. A browser with 30 tabs open can eat another 4 GB or more. Use Task Manager to identify and close resource hogs.

2. Re-enable and resize the page file. If you disabled the page file for performance reasons, turn it back on. Go to Settings > System > About > Advanced system settings > Performance Settings > Advanced > Virtual memory. Set it to “System managed size” or set a custom size of at least 1.5 times your physical RAM.

3. Update your graphics drivers. Outdated or corrupted drivers can cause phantom VRAM issues and incorrect memory allocation. Download the latest drivers from NVIDIA, AMD, or Intel. For stubborn issues, use DDU for a clean install, which I cover in detail below.

4. Lower texture quality and resolution. Textures are the biggest VRAM consumer. Dropping from Ultra to High textures can free up 2 to 4 GB of VRAM. If the error message mentions “video memory” or “rendering resource,” this is your first move.

5. Disable in-game overlays. Discord overlay, Steam overlay, NVIDIA GeForce Experience overlay, and Xbox Game Bar all consume memory. Disable them one at a time to see if crashes stop.

6. Verify game file integrity. Corrupted game files can cause abnormal memory behavior. On Steam, right-click the game > Properties > Installed Files > Verify integrity of game files. On Epic Games, click the three dots next to the game > Verify.

7. Check for Windows updates. Windows memory management updates can resolve OOM bugs. Go to Settings > Windows Update and install any pending updates, especially cumulative updates that may contain memory management fixes.

8. Run SFC and DISM scans. Corrupted system files can cause memory management failures. Open Command Prompt as administrator and run “sfc /scannow” followed by “DISM /Online /Cleanup-Image /RestoreHealth.”

How to Configure Virtual Memory for Gaming

Virtual memory configuration is one of the most effective fixes for OOM crashes, yet it is also the most commonly misconfigured setting. Many gaming optimization guides recommend disabling the page file entirely, and that advice causes more crashes than it prevents.

Here is how to set up virtual memory properly for gaming:

Step 1: Press Win + R, type “sysdm.cpl,” and press Enter. This opens System Properties.

Step 2: Go to the Advanced tab and click “Settings” under Performance.

Step 3: In the Performance Options window, switch to the Advanced tab and click “Change” under Virtual memory.

Step 4: Uncheck “Automatically manage paging file size for all drives.” This lets you set a custom size.

Step 5: Select your system drive (usually C:), choose “Custom size,” and enter values. For 16 GB of RAM, set initial size to 8192 MB and maximum to 24576 MB. For 32 GB of RAM, set initial to 16384 MB and maximum to 49152 MB. The general rule is initial size equals half your RAM, and maximum equals 1.5 times your RAM.

Step 6: Click “Set,” then “OK.” Restart your computer for changes to take effect.

If you prefer simplicity, just leave the page file on “System managed size.” Windows does a good job of resizing it dynamically. The important thing is that it is enabled and has room to grow.

One more tip: put the page file on an SSD, not an HDD. If you have multiple drives, placing the page file on a fast NVMe drive reduces the performance penalty when Windows needs to use it.

How to Clean Reinstall Graphics Drivers Using DDU

Standard driver updates sometimes leave behind old files and registry entries that cause memory allocation problems. A clean install using Display Driver Uninstaller (DDU) removes every trace of the old driver so you start fresh. I recommend this whenever driver-related OOM errors are suspected.

DDU is a free tool widely trusted in gaming communities. Here is how to use it safely:

Step 1: Download the latest driver for your GPU from NVIDIA, AMD, or Intel. Save the installer to your desktop but do not run it yet.

Step 2: Download Display Driver Uninstaller from its official GitHub page or Wagnardsoft forum. Extract it to a folder.

Step 3: Disconnect from the internet. This prevents Windows Update from automatically installing a generic driver while you are cleaning up.

Step 4: Boot into Safe Mode. Press Win + R, type “msconfig,” go to the Boot tab, check “Safe boot,” and restart. After using DDU, you will need to uncheck this and restart again.

Step 5: Run DDU. Select your GPU manufacturer (NVIDIA, AMD, or Intel) from the dropdown. Click “Clean and restart.”

Step 6: After your computer restarts in normal mode, install the new driver you downloaded in Step 1. Choose “Custom installation” and check “Perform a clean install” if the option appears.

Step 7: Reconnect to the internet and test your game.

Forum users on Reddit and Tom’s Hardware consistently report that DDU resolves “out of video memory” errors on high-end GPUs that should have plenty of VRAM. The cause is often leftover driver files corrupting the new installation.

How to Detect Memory Leaks With PoolMon

When games crash after 30 minutes or an hour of playtime but run fine at launch, a memory leak is usually the culprit. The problem could be in the game itself, a background driver, or a Windows service. PoolMon is a free Microsoft diagnostic tool that identifies exactly which component is leaking.

PoolMon shows how memory is allocated across the system by tracking memory tags. Each tag corresponds to a specific driver or system component. Here is how to use it:

Step 1: Download the Windows Driver Kit (WDK) from the Microsoft website. PoolMon is included in the WDK tools package. Alternatively, some standalone PoolMon downloads are available from trusted sources.

Step 2: Extract PoolMon and run it as administrator. You will see a list of memory tags with columns for allocated bytes, freed bytes, and the difference.

Step 3: Press the “B” key to sort by bytes allocated. This puts the biggest memory consumers at the top.

Step 4: Launch your game and let it run until just before it typically crashes. Alt-tab back to PoolMon periodically.

Step 5: Watch for tags where allocated memory keeps climbing without ever decreasing. The tag name identifies the responsible component. For example, a tag starting with “ND” often relates to network drivers, while “Vi” tags may point to video drivers.

Step 6: Once you identify the leaking tag, search for that tag online along with “memory leak.” You will typically find forum threads pointing to a specific driver or service.

Step 7: Update or roll back the identified driver. If a Windows service is the culprit, check for Windows updates or temporarily disable the service.

Real-world example from the Tom’s Hardware forums: a user with 32 GB of RAM experienced persistent OOM crashes. PoolMon revealed that LAN drivers were leaking memory under the “NDnb” tag. Updating the network adapter driver resolved the issue completely.

Laptop-Specific Fixes: UMA Frame Buffer and Integrated Graphics

Laptop gamers face a unique OOM problem that desktop users never encounter. Many gaming laptops have both an integrated GPU (built into the CPU) and a dedicated GPU. The integrated GPU does not have its own VRAM, so it reserves a portion of your system RAM instead.

This reserved memory is controlled by the UMA Frame Buffer Size setting in your BIOS or UEFI. By default, many laptops reserve 512 MB to 2 GB of system RAM for the integrated GPU. That memory is unavailable to your games even when the dedicated GPU is doing all the rendering.

Here is how to reclaim that memory:

Step 1: Restart your laptop and enter BIOS or UEFI. This usually requires pressing F2, F10, F12, or Del during boot. The exact key depends on your manufacturer.

Step 2: Navigate to the Advanced or chipset settings section. Look for “UMA Frame Buffer Size,” “iGPU Memory,” or “Shared Video Memory.”

Step 3: Reduce the UMA Frame Buffer Size to the minimum available value, typically 64 MB or 128 MB. Since your games use the dedicated GPU, the integrated GPU does not need a large buffer.

Step 4: Save changes and exit BIOS. Your system will restart with more RAM available for gaming.

Be aware that some laptops lock this setting and do not allow changes. In that case, the fix is ensuring your games actually use the dedicated GPU. Right-click your game executable, select “Run with graphics processor” (NVIDIA) or check AMD Radeon Settings to force the dedicated GPU.

Another laptop issue: some laptops ship with single-channel memory (one RAM stick instead of two). Single-channel memory cuts bandwidth in half, which can cause games to struggle with memory-intensive operations even when capacity is sufficient. Upgrading to dual-channel memory can reduce OOM-related crashes.

When to Test Your Hardware with MemTest86?

If you have tried every software fix and your games still crash with memory errors, the problem might be physical. Failing RAM modules, unstable overclocks, and incompatible memory sticks can all produce crashes that look exactly like software OOM errors.

MemTest86 is the gold standard for hardware memory testing. It runs outside of Windows, so no background processes or drivers can interfere with the results.

Here is how to use it:

Step 1: Download MemTest86 from the PassMark website. You need a USB flash drive to create the bootable tool.

Step 2: Run the MemTest86 USB installer to create your bootable drive. This formats the USB drive, so back up any data on it first.

Step 3: Restart your computer and boot from the USB drive. You may need to change boot order in BIOS or press a boot menu key (F12, F8, or F11).

Step 4: MemTest86 will start automatically. Let it run through at least one full pass, which takes 30 minutes to 2 hours depending on your RAM capacity.

Step 5: Review the results. Any red entries or errors indicate a hardware problem with your RAM.

If MemTest86 finds errors, try these hardware fixes:

• Reseat your RAM modules by removing and reinstalling them firmly.

• Test each RAM stick individually to isolate the failing module.

• Disable any RAM overclocks or XMP profiles and test at default speeds.

• Check that all memory sticks are the same speed, capacity, and brand if running multiple sticks.

• Update your motherboard BIOS, as newer versions often improve memory compatibility.

Run MemTest86 after any RAM upgrade or system change. It is the fastest way to rule out hardware before spending hours on software troubleshooting.

Advanced Tips for Persistent Memory Crashes

If none of the standard fixes work, a few advanced techniques can resolve even stubborn OOM crashes.

Limit VRAM allocation in game config files. Some games have configuration files where you can manually cap VRAM usage. Check the game’s installation folder for .ini or .cfg files and look for memory-related settings. Capping VRAM slightly below your GPU’s maximum can prevent the game from over-committing.

Try the Windows Memory Diagnostic tool. Press Win + R, type “mdsched.exe,” and choose “Restart now and check for problems.” This built-in tool is less thorough than MemTest86 but catches obvious hardware faults without needing a USB drive.

Disable XMP profiles temporarily. XMP (Extreme Memory Profile) runs your RAM at faster-than-spec speeds. If your memory is unstable at XMP speeds, it can cause OOM-style crashes. Disable XMP in BIOS and test at default JEDEC speeds to see if crashes stop.

Check for motherboard BIOS updates. Intel 13th and 14th generation CPUs had well-documented memory instability issues that were partially resolved through BIOS microcode updates. If you are running one of these processors, check your motherboard manufacturer’s website for the latest BIOS.

Monitor temperatures. Overheating RAM or VRAM can cause the same symptoms as software memory errors. Use HWMonitor or MSI Afterburner to track memory temperatures during gaming. If temps exceed 50 degrees Celsius for DDR4 or 60 degrees for GDDR6, improve your system cooling.

FAQs

Conclusion: Fixing OOM Crashes for Good

Knowing how to fix games crashing with out-of-memory errors comes down to understanding what type of memory is actually running out. System RAM and VRAM are managed separately, and committed memory adds a third layer that most gamers never consider. Once you identify which of these is failing, the fix becomes straightforward.

Start with the quick fixes: close background apps, keep your page file enabled, update drivers, and lower texture settings. These alone resolve the vast majority of OOM crashes. If the problem persists, move to advanced diagnostics like PoolMon for leak detection and DDU for clean driver reinstalls.

If software fixes do not work, do not skip hardware testing. MemTest86 catches RAM failures that produce identical symptoms to software OOM errors. Reseating memory sticks, disabling overclocks, and updating your BIOS can make all the difference.

Remember that some OOM crashes are genuinely the game’s fault. Poorly optimized titles with real memory leaks may require patches from the developer. In those cases, lowering settings and keeping background usage minimal is your best option until a fix ships.

The most important takeaway: never disable your page file. That single setting change has caused more OOM crashes than any hardware limitation I have encountered. Keep it system-managed, keep your drivers clean, and your games will stay running.