Windows Heap Size tweak, for increased stability in Stalkersoup

Author: kd6dm

How to increase the IRPStackSize value in the registry

One thing I always do, in all my Windows installs, is to increase the Heap size, which requires editing the Registry

Though this is not universally accepted by technicians, back in the 90's when I was a full time network admin, we always increased the heap size on new NT Servers

But this may be worth a try if you're experiencing instability, and are comfortable messing with the Registry
-----------------------------------------------------------
1. Run regedit.

2. Navigate to the following key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters

3. In the right pane, double-click the IRPStackSize value

NOTE: If the IRPStackSize value does not already exist, use the following procedure to create it:

a. In the Parameters folder of the registry, right-click the right pane

b. Point to New, and then click DWord (32-bit) Value

c. Type IRPStackSize and press Enter

IMPORTANT: Type "IRPStackSize" exactly as it is displayed here because the value name is case-sensitive


4. Right click on this, click Modify, and change the Base to 'Decimal'

5. In the Value Data box, type a value that is larger than the value already listed.

If you created the IRPStackSize value using the procedure described in step 4, the default value will be 15. Whatever it is, increase it by 3. So if the previous value was 11, type 14, then click OK

6. Close the Registry Editor, and restart the computer

If the problem persists after you complete the preceding procedure, try to increase the value of IRPStackSize even more. The maximum value for Windows 2000 was 50 (0x32 hex)

As a general guide, I usually increase my IRPStackSize to 30

kd6dm

this does work for versions of windows before win10h1 but it appears to cause startup issues that freeze the screen and need to shut down the computer and restart, it seems to be random though.
This next release will also update the engine to be large address aware which has improved stability and reduces out of memory crashes. This may make the above change unnecessary so unless you are experiencing memory ctds you may not want to do this as right now windows is going through some real changes which may conflict but you can always start in safe mode to remove the change if you experience startup screen freezes.

I agree, after having problems with the initial level of 1.10019.5 after a very stable 2+ years playing 1.10019.1

Running the latest version of Windows 10, and having reduced and then removed the tweaked IRPStackSize entry from my registry, the game is a little more stable now

TecnoBacon wrote:

this does work for versions of windows before win10h1 but it appears to cause startup issues that freeze the screen and need to shut down the computer and restart, it seems to be random though.
This next release will also update the engine to be large address aware which has improved stability and reduces out of memory crashes. This may make the above change unnecessary so unless you are experiencing memory ctds you may not want to do this as right now windows is going through some real changes which may conflict but you can always start in safe mode to remove the change if you experience startup screen freezes.

It seems Windows 11 may have more running errors, in my opinion, than Windows 10 according to a site I follow.
However, as I have commented before, stability can also be linked to the synchronisation between graphic card and monitor especially frame rate speeds. My card and monitor both can operate up to 240fps. They use Nvidia's synchronisation software and frequent CTDs became virtually zero for me, imo, once the monitor/graphic card were constantly synchronised.
I mention this here because I have not experienced any problems of the topic at all.