Cities: Skylines Crash Calculator
Analyze why your Cities: Skylines game crashes and get optimization recommendations
Crash Analysis Results
Comprehensive Guide: Fixing Cities: Skylines Crashes (2024)
Cities: Skylines is one of the most popular city-building simulations, but many players experience frustrating crashes, especially with large cities or heavy mod usage. This expert guide covers all aspects of diagnosing and fixing crashes in Cities: Skylines, including the new Cities: Skylines II.
Understanding the Root Causes of Crashes
Game crashes in Cities: Skylines typically fall into several categories, each with distinct causes and solutions:
- Memory-related crashes: The most common issue, occurring when the game exceeds available RAM or VRAM
- Mod conflicts: Incompatible or poorly coded mods can destabilize the game
- Asset overload: Too many custom assets strain the game engine
- CPU bottlenecks: Complex simulations overwhelm processor capabilities
- Graphics driver issues: Outdated or corrupt GPU drivers cause instability
- Corrupted game files: Damaged installation files lead to unpredictable behavior
Memory Management: The #1 Crash Culprit
Cities: Skylines is notorious for memory leaks, particularly in long play sessions. The game’s 32-bit architecture (in the original version) limits it to ~3.5GB of RAM usage, while 64-bit versions can use more but still face memory management challenges.
| System Configuration | Maximum Stable Population | Recommended Mod Count | Recommended Asset Count |
|---|---|---|---|
| 8GB RAM, 4-core CPU, 2GB VRAM | 20,000-30,000 | 10-20 | 200-500 |
| 16GB RAM, 6-core CPU, 4GB VRAM | 50,000-80,000 | 30-50 | 500-1,000 |
| 32GB RAM, 8-core CPU, 8GB VRAM | 100,000-200,000 | 50-80 | 1,000-2,000 |
| 64GB RAM, 12-core CPU, 12GB VRAM | 200,000-500,000 | 80-120 | 2,000-5,000 |
Note: These are approximate guidelines. Actual performance depends on mod quality, city layout complexity, and other factors.
Step-by-Step Crash Diagnosis
-
Check Windows Event Viewer
- Press Win+X and select “Event Viewer”
- Navigate to Windows Logs > Application
- Look for errors with “Cities” or “Unity” in the source
- Error codes like 0xc0000005 indicate memory access violations
-
Monitor Resource Usage
- Use Task Manager (Ctrl+Shift+Esc) to monitor:
- Memory usage (should stay below 90% of physical RAM)
- GPU memory usage (VRAM)
- CPU usage (shouldn’t max out single cores for extended periods)
-
Test Without Mods
- Disable all mods and assets via the content manager
- Load your city and observe if crashes persist
- If stable, re-enable mods in batches to identify culprits
-
Verify Game Files
- Steam: Right-click game > Properties > Installed Files > Verify Integrity
- Epic Games: Click three dots > Verify
- Update Everything
Advanced Solutions for Persistent Crashes
1. Pagefile Optimization
Windows pagefile (virtual memory) settings can significantly impact stability:
- Press Win+Pause/Break > Advanced system settings
- Under Performance, click Settings > Advanced tab
- Under Virtual memory, click Change
- Uncheck “Automatically manage paging file size”
- Select Custom size and set:
- Initial size: 1.5 × your physical RAM (e.g., 24GB for 16GB RAM)
- Maximum size: 3 × your physical RAM (e.g., 48GB for 16GB RAM)
- Set the pagefile on your fastest drive (preferably SSD)
- Click Set, then OK, and restart your computer
2. Launch Options for Stability
Add these launch options in Steam (right-click > Properties > Launch Options):
Explanation:
-force-d3d11: Forces Direct3D 11 (more stable than D3D9)-cpu-count:4: Limits CPU cores (adjust to your core count minus 1)-noWorkshop: Disables Steam Workshop integration (can cause issues)
3. Mod Management Best Practices
Poorly managed mods account for ~60% of crashes in modded games:
- Use Conflict Detector to identify mod conflicts
- Avoid “asset replacer” mods that modify core game files
- Prioritize mods with high subscription counts and recent updates
- Regularly clean unused assets with Clean It!
- Consider using Mod Manager for better control
4. Graphics Settings Optimization
| Setting | Low-End PC | Mid-Range PC | High-End PC |
|---|---|---|---|
| Resolution | 1280×720 | 1920×1080 | 2560×1440 or 4K |
| Anti-aliasing | FXAA | TAA | TAA or SMAA |
| Anisotropic Filtering | 2x | 4x | 8x or 16x |
| Level of Detail | Low | Medium | High |
| Shadow Quality | Low | Medium | High |
| Draw Distance | Short | Medium | Far |
| Ambient Occlusion | Off | Low | Medium/High |
| Depth of Field | Off | Low | Medium |
| Motion Blur | Off | Off | Personal preference |
Cities: Skylines II Specific Solutions
The sequel introduces new challenges with its improved simulation depth:
- Citizen System: Each citizen is now fully simulated, dramatically increasing CPU load. Cities over 50,000 population require careful optimization.
- New Rendering Engine: Uses Unity’s DOTS system, which can cause crashes on older GPUs that don’t fully support Vulkan/DX12.
- Modding Framework Changes: Many CS1 mods aren’t compatible, and new mods may have unstable APIs.
For CS2 crashes:
- Ensure you meet minimum system requirements
- Disable the new “Citizen Units” option if experiencing stuttering
- Use the built-in “Graphics Presets” and select one below your actual hardware level
- Monitor VRAM usage – CS2 uses significantly more than CS1
When All Else Fails: Nuclear Options
For completely unplayable situations:
-
Clean Windows Install
- Backup important files
- Create USB install media from Microsoft’s official site
- Perform clean install (select “Custom” and format drive)
- Install only essential drivers and software before testing game
-
Game Reinstall with Selective Content
- Uninstall game completely (including all workshop content)
- Delete remaining files in:
- C:\Users\[YourUsername]\AppData\Local\Colossal Order\Cities_Skylines
- C:\Users\[YourUsername]\AppData\LocalLow\Colossal Order\Cities_Skylines
- Reinstall game without subscribing to any workshop items
- Gradually add back content while testing stability
- Hardware Diagnostics
Preventative Maintenance for Long-Term Stability
Regular maintenance can prevent many crashes before they occur:
- Monthly Tasks:
- Verify game files
- Update all mods and assets
- Run Disk Cleanup (cleanmgr)
- Defragment HDDs (not needed for SSDs)
- Before Major Sessions:
- Close all background applications
- Disable antivirus real-time protection
- Set power plan to “High Performance”
- Restart your computer
- Save Game Management:
- Keep multiple save slots
- Use the “Save As” function periodically
- Consider AutoSave mod for regular backups
- Avoid saving during peak traffic hours in-game
Expert Resources and Further Reading
For advanced users seeking deeper technical understanding:
- Microsoft System Error Codes – Official documentation for Windows error messages
- Unity Performance Optimization – Technical guide to Unity engine limitations (Cities: Skylines uses Unity)
- OpenGL Error Reference – Helpful for diagnosing graphics-related crashes
- Windows Bug Check Code Reference – For analyzing blue screen crashes
The official Paradox forums and r/CitiesSkylines subreddit are excellent community resources for specific crash scenarios.
Final Thoughts: Balancing Ambition with Stability
Cities: Skylines pushes hardware to its limits in ways few other games do. The most stable cities often result from:
- Realistic expectations about your hardware capabilities
- Strategic use of mods that enhance without overloading
- Regular maintenance and monitoring
- Willingness to compromise on visual fidelity for stability
Remember that even with perfect optimization, extremely large cities (200,000+ population) will eventually hit engine limitations. The game simply wasn’t designed for infinite scalability. For these cases, consider:
- Starting a new city with lessons learned
- Using the “Move It” mod to split your city into districts
- Accepting that some crashes may be unavoidable at extreme scales
With the right approach, you can build and maintain thriving cities that push the boundaries of what’s possible in Cities: Skylines while minimizing crashes and frustration.