It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hi everyone !

I recently worked a lot on find a solution about Frostpunk crashes. I had a lot, no matter I updated newest drivers, changed configuration, installed all packages and updates, etc.

But, I finally found a solution !

I have a computer with SSD and HDD inside, I usally dispatch my files on them to optimize my work. It's known that you have to disable Windows' Vitual Memory management when using SSD.
I tried to reactivate it, then the game worked perfectly.

My advice is that people having this issue check that setting.
Go on the appropriate panel and do not disable the virtual memory to play Frostpunk. It's a game that seem to require it a lot.
I can't tell witch setting to set, I'm not enough qualify at this.

Hope it can help some people !

Bye.
avatar
Eliepse: It's known that you have to disable Windows' Vitual Memory management when using SSD.
No, it's wrong. You should never disable Windows' Vitual Memory.

First, if you use "modern PC" with "a lot of RAM" you should decrease size of pagefile and set min/max to the same value (2048 MB is ok).

Second, if you have both SSD and HDD you can move this pagefile to HDD.
avatar
Eliepse: Hi everyone !

I recently worked a lot on find a solution about Frostpunk crashes. I had a lot, no matter I updated newest drivers, changed configuration, installed all packages and updates, etc.

But, I finally found a solution !

I have a computer with SSD and HDD inside, I usally dispatch my files on them to optimize my work. It's known that you have to disable Windows' Vitual Memory management when using SSD.
I tried to reactivate it, then the game worked perfectly.

My advice is that people having this issue check that setting.
Go on the appropriate panel and do not disable the virtual memory to play Frostpunk. It's a game that seem to require it a lot.
I can't tell witch setting to set, I'm not enough qualify at this.

Hope it can help some people !

Bye.
I strongly advise either closing the browser, or demanding the company start checking return values for malloc and then crashing controlled identifying that it ran out of RAM.

I do have to ask, though: why would you have to disable virtual memory swapping for SSDs? I know it's healthy for the SSDs, but why would it be absolutely necessary?
Post edited June 27, 2018 by kohlrak
avatar
Eliepse: It's known that you have to disable Windows' Vitual Memory management when using SSD.
avatar
Lexor: No, it's wrong. You should never disable Windows' Vitual Memory.

First, if you use "modern PC" with "a lot of RAM" you should decrease size of pagefile and set min/max to the same value (2048 MB is ok).

Second, if you have both SSD and HDD you can move this pagefile to HDD.
My bad, I didn't manage that setting well (bad advices from websites I trusted, or more certainly some bad understanding from my side...) and thank you for the information. I'll configure it better now.

Anyway, it saves most of crash (which apparently some other few people also has) with this game. I think some other have a wrong virtual memory config, that's why I posted it here. :)
avatar
Eliepse: Hi everyone !

I recently worked a lot on find a solution about Frostpunk crashes. I had a lot, no matter I updated newest drivers, changed configuration, installed all packages and updates, etc.

But, I finally found a solution !

I have a computer with SSD and HDD inside, I usally dispatch my files on them to optimize my work. It's known that you have to disable Windows' Vitual Memory management when using SSD.
I tried to reactivate it, then the game worked perfectly.

My advice is that people having this issue check that setting.
Go on the appropriate panel and do not disable the virtual memory to play Frostpunk. It's a game that seem to require it a lot.
I can't tell witch setting to set, I'm not enough qualify at this.

Hope it can help some people !

Bye.
avatar
kohlrak: I strongly advise either closing the browser, or demanding the company start checking return values for malloc and then crashing controlled identifying that it ran out of RAM.

I do have to ask, though: why would you have to disable virtual memory swapping for SSDs? I know it's healthy for the SSDs, but why would it be absolutely necessary?
Yes, I close the browser. I have 12GB of RAM, the problem didn't come from there. I built this computer myself so... I learn from my mistakes !

Thank you for your answers !
Post edited June 28, 2018 by Eliepse