Game is randomly crashing. Sometimes it's at the end of missions, other times it's randomly during gameplay

Warhammer: Vermintide 2 Technical Support
1

Issue Type (Required):

Crash - During Play

Issue Description (Required):

Game is crashing out randomly during gameplay and frequently after hitting return to keep. Unable to capture error message due to copy to clipboard failing to capture the information and the window quickly closing.

[PC] Do You Use Mods? (Optional):

No, I don’t use mods

Reproduction Rate (Required):

Often (<75%)

Platform (Required):

Steam (PC)

[PC] Crash Report (Optional):

I have tried uninstalling and reinstalling the game, clearing appdata, and uninstalling reinstalling EAC.

GUID: e38e0256-2ffc-4b01-9856-20797e171df8

Log File:
Info Type:

[Script Error]: foundation/scripts/util/error.lua:32: [StatisticsDatabase] Failed fetching statistic using parameters: completed_career_levels, we_thornsister, pat_bay_tzeentch_path2, hard

UPDATE: 4/18

Just got this error and “Out of Memory”
GUID: 28487a59-c502-4466-a4e9-2a402f6acc4f
Log File:
Info Type:

[Engine Error]: Not enough memory reserved for heap lua_heap, size: 2025848832ll, reserved: 1073741824ll, required: 2235564032ll

At D:\a\d\vt2-stingray\vt2\release\release_hon_2025_05_12_event_level\runtime\foundation\memory\heap_allocator.cpp:221 in function stingray::HeapAllocator::resize_heap

These errors ONLY OCCUR ON VERMINTIDE 2. I have just played through Clair Obscur, Silent Hill f, and Resident Evil 4 Remake, without any crashes. It is not a hardware failure.

[PC] Upload Console Log & vermintide2_launcher.log (Optional):

console-2026-04-17-22.33.15-62735574-a891-468a-90e6-1ecdeb3b8f2a.log (566 KB)vermintide2_launcher.log (679 KB)console-2026-04-17-22.27.33-286577ec-a4e5-47fa-a8f8-c6a7bd542b52.log (474 KB)

2

Just got this one:

GUID: 36683651-2414-4e56-a558-e09318c99716
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build c8e433747fa706ef4968750e872bc2ffd1571437

accessing address 000000003600C007 from 00007FFB41001CEE

3

Sorry to hear this @Azureliske

The crashes are varied, and it’s difficult to pinpoint the root cause here. Some general things I recommend to try:

Failing the above, please run through our other general crash solutions here:

https://support.fatshark.se/hc/en-us/articles/360021422873--PC-How-to-Resolve-Crashes-in-Vermintide-2

4

None of this common troubleshooting worked. I’d attempted over half of it before even making a post here, and just now crashed trying to join a game.

5

Still happening

GUID: 8b65d4bf-9241-452c-83ea-9a1ef2aab020
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build c8e433747fa706ef4968750e872bc2ffd1571437

accessing address 0000430000000005 from 00007FFBA13AB8F7

6

GUID: 2072f558-e255-4e19-b406-c22d32b4cae1

Log File:
Info Type:

[Script Error]: foundation/scripts/util/error.lua:32: [StatisticsDatabase] Failed fetching statistic using parameters: completed_career_levels, dr_ironbreaker, magnus, cataclysm

7

The most frequent moment for crashing is joining a game invitation.

8

GUID: a89489c1-165a-47b8-b153-423f447e9a12

Log File:
Info Type:

[Script Error]: foundation/scripts/util/error.lua:32: [StatisticsDatabase] Failed fetching statistic using parameters: completed_career_levels, es_huntsman, pat_mines_tzeentch_path4, harder

9

GUID: cea6414a-46a6-48df-bc26-4954531a67df

Log File:
Info Type:

[Script Error]: foundation/scripts/util/error.lua:32: [StatisticsDatabase] Failed fetching statistic using parameters: completed_career_levels, wh_bountyhunter, pat_bay_tzeentch_path1, hardest

10

Thanks for the added crash reports @Azureliske

I’ve shared these with the development team and I’m waiting to hear back. I’ll let you know as soon as I receive any updates.

11

@Azureliske though the crashes are referencing data failing to fetch, this doesn’t appear to be a backend-related issue from what we can tell.

Unfortunately, we have no immediate solutions to these crashes. I’ve raised them in our database and our developers will need to investigate deeper into this in future.

Apologies for the inconvenience.

12

GUID: 3d980c8d-06e7-40ae-b8eb-23c3d35ffaf6

Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build c8e433747fa706ef4968750e872bc2ffd1571437

accessing address 000000003C0607CF from 00007FF80F971CEE

13

GUID: 6bfa7e2f-cb1b-4a4d-9a54-644d154f3988

Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build c8e433747fa706ef4968750e872bc2ffd1571437

accessing address 000000009CC6234B from 00007FF80F971CEE

14

GUID: 0f3e6092-c11f-4339-accd-68b11d6a1684

Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build c8e433747fa706ef4968750e872bc2ffd1571437
accessing address 00000000000000A8 from 000001936229B8B8

The issue could be related to the following modules found in the stack trace:
module ‘unknown_module’.

15

GUID: 9421a7fd-edab-4fce-8af0-846313cdb095

Log File:
Info Type:

[Script Error]: scripts/ui/ui_renderer.lua:612: bad argument #3 to ‘Vector2’ (number expected, got no value)

16

GUID: b573fb45-7541-42a6-9db7-f33536bcfba5

Log File:
Info Type:

[Script Error]: foundation/scripts/util/error.lua:32: [StatisticsDatabase] Failed fetching statistic using parameters: completed_career_levels, es_questingknight, sig_crag_nurgle_path1, cataclysm

17

Hi @Azureliske

Our developers have reviewed the crashes, and unfortunately they suspect they are occurring due to hardware degradation/failure (which is a known issue with 13th/14th gen Intel CPUs), as your CPU appears to be failing to unwrap and run lua code - which we are unable to do anything about on our end.

It could be worth checking if your BIOS is up-to-date, as outdated BIOS can also cause instability, though we advise caution and to do so at your own risk; and we can’t guarantee this will resolve the issue.