[2.0.32][PC] Crash on startup and memory errors

[atee86]

Today when i tried to start up the game at the cropping bitmap stage it crashed with
Error Util.cpp:95: Unexpected error occurred. If you're running the latest version of the game you can help us solve the problem by posting the contents of the log file on the Factorio forums.
Please also include the save file(s), any mods you may be using, and any steps you know of to reproduce the crash.

After that i did a file verification on steam, all file are in good conditions. Tried to start again the game, it crashed again.
Error Util.cpp:81: Failed to create a texture.

Screenshot 2025-02-19 140142.png (2.16 MiB) Viewed 591 times

For the third time the game started without issues, however i can't load the save from yesterday. A new game loads fine.

2.845 Loading 3D bitmaps.
2.919 Texture processor created (2048). GPU accelerated compression Supported: yes, Enabled: yes/yes. Test passed. YCoCgDXT PSNR: 35.83, BC3 PSNR: 33.82
2.930 Parallel sprite loader initialized (threads: 15, bitmaps: 4569)
13.420 Error ParallelSpriteLoader.cpp:67: Parallel sprite loading failed, falling back to normal sprite loading. bad allocation: __base__/graphics/entity/artillery-wagon/artillery-wagon-base-8.png
RAM: 16632/32655 MB, page: 37529/37655 MB, virtual: 8514/134217727 MB, extended virtual: 0 MB
21.291 Sprites loaded
21.303 Generated mipmaps (4) for atlas [2] of size 16384x7424
21.314 Generated mipmaps (3) for atlas [5] of size 8192x5632
21.326 Generated mipmaps (3) for atlas [6] of size 4096x1792
21.336 Generated mipmaps (3) for atlas [7] of size 16384x6288
21.348 Generated mipmaps (3) for atlas [8] of size 4096x2960
21.377 Generated mipmaps (3) for atlas [9] of size 4096x3088
21.388 Generated mipmaps (5) for atlas [10] of size 8192x2480
21.400 Generated mipmaps (3) for atlas [14] of size 8192x2352
21.416 Custom mipmaps uploaded (2113)
21.429 Video memory usage: 1608.57 MB (Atlases: 1597.03 MB, Textures: 11.54 MB)
22.606 Factorio initialised
22.610 Steam Storage Quota: 23466/23841
1023.705 Loading map C:\Users\atee8\AppData\Roaming\Factorio\saves\lazy20.zip: 17267796 bytes.
1023.834 Loading level.dat: 67411577 bytes.
1023.838 Info Scenario.cpp:153: Map version 2.0.32-0
1025.694 Loading blueprint storage: Local timestamp 1739629338, Cloud timestamp 1739629337
1027.331 Warning Map.cpp:857: Map loading failed: bad allocation
1028.570 Error AppManagerStates.cpp Out of memory
1272.259 Loading map C:\Users\atee8\AppData\Roaming\Factorio\saves\lazy20.zip: 17267796 bytes.
1272.372 Loading level.dat: 67411577 bytes.
1272.376 Info Scenario.cpp:153: Map version 2.0.32-0
1274.326 Loading blueprint storage: Local timestamp 1739629338, Cloud timestamp 1739629337
1275.272 Warning Map.cpp:857: Map loading failed: bad allocation
1276.331 Error AppManagerStates.cpp Out of memory
1319.409 Loading map C:\Users\atee8\AppData\Roaming\Factorio\saves\lazy20.zip: 17267796 bytes.
1319.521 Loading level.dat: 67411577 bytes.
1319.525 Info Scenario.cpp:153: Map version 2.0.32-0
1321.498 Loading blueprint storage: Local timestamp 1739629338, Cloud timestamp 1739629337
1322.455 Warning Map.cpp:857: Map loading failed: bad allocation
1323.552 Error AppManagerStates.cpp Out of memory

Also yesterday during gameplay it gave me a message that it cannot autosave. Manual save worked, but when i tried to load it back, it said Out of memory. However i checked i had more than 100 GB free space on my OS disk and 43% of the RAM was also not used which means approx 16 GB of memory. When i retried to load it several times the game eventually loaded and was able to play along, the autosaves were working fine too before and after this incident.

Screenshot 2025-02-19 141003.png (1.51 MiB) Viewed 589 times

[Loewchen]

The page file is full and the os refused the memory allocation, nothing the game can do about it.

[atee86]

The page file is full and the os refused the memory allocation, nothing the game can do about it.

Interesting, but more than half of my RAM is free, why would it want to use the page file? Also I can start a new game without any problems, only if i want to load the save this is when the error happens. Plus i have 142 GB free on the drive C, where the page file is located.

[Bilka]

Interesting, but more than half of my RAM is free, why would it want to use the page file?

That's just how Windows works, it refuses to allocate RAM sometimes when you have a full page file. The game has no influence on this. Restart your computer and Windows should empty the page file.

[Muche]

Plus i have 142 GB free on the drive C, where the page file is located.

According to https://learn.microsoft.com/en-us/troub ... of-windows, the pagefile limit might be the capacity of that drive / 8? Which would suggest your C drive is about 300GB?

[atee86]

Plus i have 142 GB free on the drive C, where the page file is located.

According to https://learn.microsoft.com/en-us/troub ... of-windows, the pagefile limit might be the capacity of that drive / 8? Which would suggest your C drive is about 300GB?

Yes, the C is a 500gb ssd.

Thank you guys, i've extended the page file to the regular hard disk D which has 4 TB capacity and i allowed the OS to manage it on both drives.. After these settings and a restart, the game starts without errors. Let's see how it goes. Apparently i have learned something new about the page file, because back then on Windows 7, when i had tons of ram i even completely disabled the page file and my machine was running faster. Seems like this approach doesn't work in new versions anymore.

[Rseding91]

Thank you guys, i've extended the page file to the regular hard disk D which has 4 TB capacity and i allowed the OS to manage it on both drives.. After these settings and a restart, the game starts without errors. Let's see how it goes. Apparently i have learned something new about the page file, because back then on Windows 7, when i had tons of ram i even completely disabled the page file and my machine was running faster. Seems like this approach doesn't work in new versions anymore.

It works... until it doesn't, and you get cryptic errors/issues like this.

[NineNine]

https://learn.microsoft.com/en-us/troub ... ion-errors

This seems to me to be an extremely serious issue that should be fixed right away. Instead, it goes back to Windows 10. Yikes!

I suggest this as a workaround: https://www.linuxmint.com/