Crashing Again (Menus?)

[GenericName]

Issue Type (Required):

Crash - During Play

Issue Description (Required):

Hello,

I am crashing pretty much constantly, and I can reliably reproduce the crash within 10 minutes of the game starting by simply exploring menus. This has occurred almost every single time while I am in a menu, but, once, when I deliberately ignored every single possible menu, it occurred when I finished a Chaos Wastes level (presumably because the end of level reward display uses menu GFX).

I have previously had crashing issues resulting from my Nvidia drivers being too up-to-date. I have since rolled back to a version from November 2024, which stopped the crashes. I am dearly hoping this is not yet another issue with my GPU.

The integrity of the game files has already been verified. The game was doing just fine for weeks. My only guess is that this is something introduced as a result of the skull event ending, but what do I know?

Let me know what else I can do to resolve this.

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

Yes, and I’ve tried disabling them

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

Steam (PC)

Player ID (Optional):

Steam Community :: GenericName

[PC] Crash Report (Optional):

GUID: 6b9306e3-0700-4770-a6f0-43556e34ad8a
Log File:
Info Type:

[Script Error]: foundation/scripts/util/error.lua:26: [UIAtlasHelper] Atlas texture settings do not exist: “W??\15”

GUID: 112916f5-9b95-45e7-b22c-c9a7e88afebb
Log File:
Info Type:

[Script Error]: scripts/ui/ui_passes.lua:134: Material tab_menu_glow not found in Gui.

GUID: 5147a121-8bfd-49ee-bc5e-48e7ecce92f2
Log File:
Info Type:

[Script Error]: scripts/ui/ui_renderer.lua:1589: Material menu_frame_09 not found in Gui.

GUID: 14cf4948-bc93-41fb-baaa-84e2f42bdf88
Log File:
Info Type:

[Script Error]: scripts/ui/ui_renderer.lua:1605: Material button_frame_01 not found in Gui.

[FatsharkLev]

Sorry to hear this @GenericName

These crashes are all very unusual, with only a handful of unique occurrences. If you are using any mods can you please try disabling them and check if the crashes persist?

Otherwise, next, to rule out an issue with the installation please try a clean reinstall of Vermintide 2 which involves deleting your AppData (please note any custom settings e.g. graphics, keybinds etc. will be reset):
https://support.fatshark.se/hc/en-us/articles/360034118394--PC-How-to-Perform-a-Clean-Re-Installation-of-Vermintide-2-or-Darktide

Please let me know how this goes.

[GenericName]

Okay, I did a clean reinstall and the issue persists. I crashed four times, twice on loading screens, twice in menus. Here’s one of the crash codes I got:

GUID: 22b9c1aa-a7d6-4068-84e3-837dc16ed0bf
Log File:
Info Type:

[Script Error]: scripts/ui/ui_passes.lua:134: Material button_glass_02 not found in Gui.

[GenericName]

GUID: 74d8823f-421b-4c7b-9032-791f54fc9506
Log File:
Info Type:

[Script Error]: scripts/ui/ui_renderer.lua:1801: Material button_frame_01 not found in Gui.

[GenericName]

Hey there, if it helps, I sometimes get an error that I do not have enough memory to run Vtide2, which causes it to crash on start up. I can get past this by lowering my launcher settings to medium and then back up to ultra in game, but I should not have to. I have 64Gb RAM, a 4070Ti, and 50 Gb of available space on the SSD the game is stored on. Maybe that is related?

GUID: 297c7699-0368-4421-9c35-e126c4af0a91
Log File:
Info Type:

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

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

---

[FatsharkLev]

Sorry to hear this @GenericName

These crashes are highly unusual, and fall into a category we can only describe as “impossible crashes”, that can only be explained by hardware failure. I’ve spoken with our engine developers and they noted you have an i9 14900k CPU, and informed me that this may have felled victim to hardware degradation common with 13th and 14th series i7/i9 CPU.

For more information on the possible underlying issue, please refer to:

Intel Core 13th and 14th Gen Desktop Instability Root Cause Update

There are BIOS updates available to mitigate/resolve issues for 13th/14th Gen CPU’s, so I would recommend checking that your BIOS is up-to-date. Though, we advise caution when performing firmware updates, and to do so at your own risk.

[GenericName]

Hey there. I checked out the article you sent. I have updated my BIOS previously because of issues with this CPU, but that was in August 2024, and this article was in the following month. Seeing that, I updated my BIOS again, to a patch from May 2025 this time. I cannot tell if this fixed my in-game issues, because now the crashing on start up is so prevalent I cannot get the game to open any more at all. I have tried lowering my graphics settings to lowest, disabling all mods, going from DirectX 12 to 11, starting in fullscreen instead of borderless windowed, verified integrity of game files… Nothing works. This is so infuriating because the game was running fine with zero crashes (after I rolled back my Nvidia drivers anyway) for a few weeks. It’s like my computer somehow became dependent on the skull event and having them removed has made the game unplayable. I don’t know. Anything else I can do?

Since you said the CPU might have been damaged, I ran a diagnostic to see if it was. I am not a hardware engineer, but the diagnostic tool says it has a clean bill of health. For the record, I have had this CPU for less than a year as I had a replacement from the incredibly, very broken ones in August 2024 (when I updated my BIOS the first time).

Here’s a window that opened one of the times I tried to open it. Maybe it helps?

More crash logs:
GUID: 1dd802cb-42c8-42b6-ade5-07a94629b8a4
Log File:
Info Type:

[Script Error]: not enough memory

GUID: e1332b18-3800-41bf-9369-c1445dfd3bd6
Log File:
Info Type:

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

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

---

[FatsharkLev]

@GenericName I see, thanks for the update! I ran the new crash reports by our engine developers but they are equally stumped by this.

They informed me that 1.4gb memory is trying to be allocated incorrectly, but they haven’t been able to uncover any clues from the logs as to why; and simply told me that something is very broken and to disable any mods if you are using them - though from the logs it doesn’t appear that you are?

Unfortunately, I’m unsure of what else to suggest here. It’a an extreme measure, but perhaps to try repairing/reinstalling Windows in case of a deeper issue. I can’t say if this will help with any certainty though

[GenericName]

The horrors persist. I am sorry to continue to put you through this nonsense, but at this point I have thoroughly fallen for the sunk cost fallacy. I ran a whole bunch of OS repair commands through CMD:
1: scf /scannow
2: chkdsk
3: DISM.exe restore health
4: Windows memory diagnostic

Only #1 actually detected any issues. I tested immediately after with no change as far as I could tell. So, if my OS is damaged, I have no idea how or why. I hope it is not, i have not had this computer yet two years.

Then, I had an epiphany. I have two storage devices; why not try to move it? So I did: I moved the game from my C: drive to my D: drive, my SSD to my HDD. I tested it again immediately after, and the game actually started this time, mods, high graphics quality, and all. I played for maybe two hours and suffered two additional crashes, which is unfortunate, but at least they’re of a different error type than the previous lua / menu errors. Do you recognize anything from this?

GUID: ffa6f5ec-33a5-496c-b40d-44532d257069
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build 4ebf911a8dad50ea32d18e541eebdc2ab4cadc55
accessing address 000000004300000C from 00007FFCB8491CEE

[GenericName]

Update:

Moved the game back to my C: drive just to experiment. Game ran fine until I got the same crash error, in a loading screen to a level, that I got on my D: drive.

GUID: 6dbcb63f-7672-4b77-b46b-6c51394f8240
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build 4ebf911a8dad50ea32d18e541eebdc2ab4cadc55
accessing address 000000003000090C from 00007FFCF0BC1CEE

[GenericName]

Update to update: I am going on a one week vacation tomorrow and will not be able to access my computer; please do not let this thread die, as I rely on it to try and fix my issues. For Vermintide 2, that is.

[FatsharkLev]

Interesting - thanks for the updates! I’ve passed these new crash reports on to our engine developers to see if they have any insight. With a busy release week ahead, this may not get looked at immediately but I’ll let you know once I’ve heard back from them!

I’ve adjusted the topic timer to close after 3 weeks now, so not to worry about the thread closing

[GenericName]

Understood, thanks so much!

[Riku]

@FatsharkLev

and they noted you have an i9 14900k CPU

i have the exact same CPU, and the gist is that this particular CPU comes overclocked from the factory, unless you have a great cooling solution, it runs at high temperatures even in low stress, the moment you open applications that increase stress it shuts down out of self-preservation.
i remember being puzzled as to why crashes happend for no apparent reason, so perhaps its worth a shot.

the Core Ratio is set to 60x i recommend 44x for top tier performance or 38 for safety.
you can edit the clocking with -Intel Extreme Utility-
Open the “advanced Tuning” tab, if it wont let you, its because the “Speed Optimizer” is Active, disable it. that will allow you to edit manually.
once youre on the advanced tuning tab scroll down until you see the core ratio section, on default it should look like this:

im going to use my personal setting, you may be able to squeeze out more or less depending on your cooling setup

1:

i dont use it but if you want to fine tune you can use the “thermal velocity Boost” option.
think of it as a break, once a temperature is reached it will lower the core ratio by the set amount,

basically “if core reaches 85 degrees, lower core ratio by 2, if the core reaches 90 degrees lower it by 4.” its a failsafe feature, as i dont plan to ever letting my system get close to these temps ill dont use it.
if you wanna use the feature you gotta enable it here:

anyway i use 42 on P cores and 38 on E cores:

since this CPU has a very high core count running it on a comparatively low clock can still yield you great performance, so don’t be distraught, i barely notice the difference, and the boost in stability is worth it.

[GenericName]

Hey, thanks so much for this reply! You can always rely on the inexplicable tech-god to show up in forums like this.

I am familiar with the Extreme Tuning Utility, since I had to use it as a stop-gap before I got the CPU replaced with my current one that was supposed to not have any issues. More accurately, I suppose, it has fewer issues. I did the changes as you’ve described them, and I have not crashed since after ~4 hours of play. I am still puzzled as to why this only became an issue relatively recently, as the game was running fine for some time before, but I do not care as much as the issue being properly fixed, which I think it is. Occasionally, I have stability issues with some other games, but it is only a rare few, and I am looking forward to testing if those function now.

Again, thank you so much!!

[Riku]

@GenericName

I am still puzzled as to why this only became an issue relatively recently,

Are you living in the Northern Hemisphere? Might be the summer adding a couple degrees that tipped it over the edge.
anyway great news.