The “Low Level Fatal Error” screen. A freeze that locks your entire system. The game drops to desktop before the title screen even finishes rendering. If Star Wars Zero Company is crashing, the culprit is often not your graphics card or your drivers. It is your pagefile. Virtual memory is the invisible reserve tank for your system RAM, and when the game exhausts both physical RAM and a tiny default pagefile, it dies without a warning.
Most troubleshooting guides shuffle through the same tired checklist. Update drivers. Verify the game files. Disable overlays. These fixes work when the problem is corruption or interference. They do nothing when the problem is capacity. Star Wars Zero Company is a modern release that consumes RAM aggressively during shader compilation and asset streaming. A system with 16 GB of RAM and a Windows default pagefile that shrinks and grows on demand is a ticking time bomb. The fix is to stop letting Windows manage virtual memory and assign the game a dedicated, fixed reserve of space on your fastest drive.
What Virtual Memory Actually Does for Your Game
RAM holds everything the CPU needs right now. When those needs exceed your physical sticks, Windows moves idle data from RAM to a file on your storage drive called the pagefile. This is virtual memory. For a game like Star Wars Zero Company, the pattern is predictable. The game loads a level, streams in textures, compiles shaders in the background, and suddenly your 16 GB of RAM is full. The system starts swapping data to the pagefile. If that pagefile is set to a small, dynamic size, the system stalls. Then it crashes.
The mistake is treating virtual memory as a performance enhancer. It is not. It is a stability mechanism. Your game will not run faster with a bigger pagefile. It will simply stop freezing and crashing when the memory pressure spikes. Most crash reporters for Zero Company trigger because the system ran out of commit charge, the combined total of physical RAM and the pagefile. When the commit limit is hit, Windows cannot allocate more memory, and the application ends abruptly.
The default Windows setting is a system-managed pagefile. Windows grows it when needed. The problem is that growth does not happen instantly. The game requests memory, the system allocates the pagefile, and during that delay, the game’s internal watchdog timer trips and kills the process. That delay is exactly what produces the crash reporter on startup and the GPU crash dump errors that point at your graphics card when your graphics card is innocent.
The Defensible Stance: Set a Fixed Pagefile on Your Fastest Drive
Automatically managing paging file size for all drives is the default setting. Change it. The fix is fixed. Set a custom size and do not let Windows touch it again.
Here is the process for a system with 16 GB of RAM, the minimum realistic specification for Star Wars Zero Company.
Open the Start menu and search for “Advanced System Settings.” Click on the “Advanced” tab. Under Performance, click “Settings.” Click the “Advanced” tab, then under Virtual Memory, click “Change.”
Uncheck “Automatically manage paging file size for all drives.” Select your fastest storage drive. If your game is installed on an NVMe SSD, that is the drive to use. If the drive is nearly full, clear space first. The pagefile will need to reserve room like any other file.
Select “Custom size.” Set the initial size and the maximum size to the same number. For 16 GB of RAM, set both fields to 24576 MB. That is 24 GB, or 1.5 times your physical RAM. For 32 GB of RAM, use 32768 MB. Formula: take your RAM in GB, multiply by 1.5, convert to MB. That is the number to type twice.
Click “Set,” click “OK,” and restart your PC. The fixed pagefile prevents the system from spending time resizing it under memory pressure. It eliminates the delay that causes the crash. It is the single most direct fix for “Low Level Fatal Error” crashes in this game.
Why the “Just Add More RAM” Counterargument Fails
The strongest argument against this approach is that the real fix is to install more physical RAM. If you have 16 GB and the game needs more, buy a 32 GB kit. That closes the gap entirely. The pagefile is a band-aid, not a cure.
That argument sounds logical. It is wrong for most players.
First, the cost and compatibility problem. Laptop owners often cannot upgrade RAM at all because the modules are soldered to the motherboard. A desktop user with an older platform may need to replace existing sticks, and mismatched modules cause instability worse than the crashes they are trying to fix. Second, the pagefile still matters even with more RAM. Windows allocates virtual memory for every process, and applications request commit charge well above their actual working set. The crash reporter in Zero Company is tied to commit charge failure, not just physical RAM exhaustion. A fixed pagefile gives the system headroom it cannot get from hardware alone. Third, you do not buy hardware to fix a software configuration problem. The pagefile is free, takes five minutes to configure, and works universally.
Step-by-Step: Virtual Memory Configuration That Stabilizes Zero Company
Step 1: Check Your Current Pagefile Size
Open Task Manager with Ctrl + Shift + Esccodecodecodecodecodecode. Click the Performance tab. Select Memory. Look at the bottom of the window. The “Paged pool” and “Non-paged pool” numbers tell you how much memory is being consumed, but the critical number is “Committed.” If the commit charge is close to the “Commit limit,” your system is about to crash. The commit limit equals physical RAM plus the current pagefile size. A small gap between the charge and the limit means the pagefile is undersized.
Step 2: Free Space on the Target Drive
Do not set a 24 GB pagefile on a drive with 12 GB of free space. The system will ignore your setting or produce an error. Clear temporary files with Disk Cleanup. Uninstall games you are not playing. Move screenshots and captured video to another drive. Then configure the pagefile.
Step 3: Disable the “Automatically Manage” Setting and Set Custom Sizes
Follow the Advanced System Settings path described above. When you set the pagefile on your fastest drive, also set a pagefile on your secondary drive. Do not set it to “No paging file” on the system drive. Windows needs a pagefile on the boot drive to write kernel crash dumps. Keep a small one there, 1024 MB minimum, and set the large fixed one on the game drive.
Step 4: Verify the Change Took Effect
After restarting, navigate back to the Virtual Memory settings window. The list of drives should show “Custom” next to the chosen drive with your MB values. Then launch Star Wars Zero Company. The first load may feel the same. Play for two hours. Play during a firefight with multiple explosions. The crash reporter should stay away.
Step 5: Adjust the Shader Cache Afterward
A corrupted DirectX shader cache can still cause problems even with healthy virtual memory. Open Disk Cleanup, select your game drive, and check “DirectX Shader Cache.” Clear it. The next launch of the game will take longer because shaders need to recompile. That is expected. The shader cache is separate from virtual memory, but if you are chasing stability, do that clean-up right after the pagefile change.
When the Pagefile Is Not the Only Problem
If you set a fixed pagefile and the game still crashes, the issue is elsewhere.
Check the GPU driver. Use the manufacturer’s tool: Nvidia App for Nvidia cards, Adrenalin for AMD, and the Intel Arc Control for Intel. A corrupted driver will crash the game during shader compilation, which looks identical to a memory failure. Update the driver, restart, and test.
Then verify the game files. On Steam, right-click Star Wars Zero Company, select Properties, go to Installed Files, and click “Verify Integrity of Game Files.” The process scans and repairs damaged files. Run it even if you verified last week.
If the crash persists and your system has both integrated and dedicated graphics (common in laptops), ensure the game uses the high-performance GPU. Go to Settings > System > Display > Graphics, find the Zero Company executable, and select “High Performance.” A game running on integrated graphics will run out of memory much faster because it shares system RAM for video memory.
FAQ
Why does the crash reporter say GPU Crash Dump Triggered if the issue is virtual memory?
The game’s crash reporter points at the GPU because that is where the rendering thread stopped. When the system runs out of commit charge, memory allocations fail mid-frame. The graphics thread receives an invalid or null resource and reports a GPU crash. The actual trigger was the memory manager, not the hardware.
Should I set the pagefile to “System Managed” or a custom size?
Set a custom size. System managed works for office productivity, but games like Zero Company allocate memory in large bursts. The dynamic resizing introduces latency at the exact moment the game is demanding memory. Fixed custom sizes eliminate the resize operation entirely.
Does a larger pagefile hurt performance?
No, not if you set it on a fast SSD. The pagefile only gets used when physical RAM is full. A fixed size does not consume system resources. The space is reserved but idle until needed. The game does not perform worse because the pagefile exists.
My SSD has limited space. Can I put the pagefile on a slower HDD instead?
You can, but the game will stutter hard when it swaps data to the HDD. SSD to HDD latency is orders of magnitude longer. If you must use a HDD, set the pagefile to 24576 MB anyway. Stability beats speed when the choice is a slow game versus a crashing game.
How do I know if my RAM is actually the problem?
Open Task Manager while playing. If Memory usage sits at 95-100% and the game crashes, your RAM is exhausted. A fixed pagefile still provides the necessary commit charge headroom, but if you have a desktop with available slots, adding identical matched RAM sticks is the better long-term fix.
The Edge Case: Multiple Drives and Hidden Pagefile Conflicts
Here is the part that most guides miss. If you have multiple drives, Windows historically placed a pagefile on each drive when “Automatically manage” was enabled. If you disable that setting, you must deliberately configure every drive. Windows will not create a fallback pagefile on another drive unless you tell it to. If your single configured pagefile drive fails, the game has nowhere to spill. Configure a small pagefile on your system drive and the fixed large one on the game drive. That redundancy covers you in both directions: kernel dump requirements on the boot drive, and game memory capacity on the fast drive.
Virtual memory is not glamorous. It does not boost frame rates and it does not appear in benchmark graphs. It is raw insurance against a specific failure mode: the moment your game requests more memory than the system can provide. Star Wars Zero Company crashes at that exact moment. Set the pagefile. Restart. Then spend your time playing the game instead of fighting the crash reporter.
