Game crashes with Access violation (0xc0000005)

Since yesterday I have frequent crashed when playing. Usually crashing in the first 2 minutes or so of being in a game.

console.log show Access violation (0xc0000005) but not much more that I can find.

Windows was freshly reinstalled, VC redist too.

Playing with some sanctioned mods, but had been since forever and I had not had this problem before.

Any help is appreciated

console-2022-09-05-16.21.41-0721d8f6-abf4-4f3e-a545-03a8472dcccb.log (436.7 KB)

crash_dump-2022-09-05-16.21.41-0721d8f6-abf4-4f3e-a545-03a8472dcccb.dmp (742.9 KB)

1 Like

For this to occur so suddenly and without a patch, there may be a driver or hardware-related culprit. Can you think what could have changed on your PC around that time?

Otherwise, it’s always worth cleanly reinstalling your GPU drivers: https://support.fatshark.se/hc/en-us/articles/360021233554--PC-How-to-Perform-a-Clean-Re-Installation-of-Your-NVIDIA-GPU-Drivers

Driers were freshly installed.

Yesterday I took some time to perform the annual-but-forgotten-last-year-or-the-year-before-or-how-long-was-it-again cleaning, complete with disseating graphics card (which was absurdly hot) and a full blown compressed air in every nook and cranny.

Was able to play 2 maps without issues after that (then I stopped playing, not crashed), so I guess overheating was at least an aggravating factor, and hardware cause seems plausible.

I guess you can close the ticket and if something new happens in the next 7 days I’ll keep you posted.

Thanks for your help.

Folks : Clean your PCs insides regularly.

1 Like

OT-ish: This is a good reminder. An electric duster (blower) is a great investment and often on sale.

Pro tip: Hold the fans before blowing through them, don’t stick your finger in after the blower has it spinning at light speed.

Holy Sigmar, bless this ravaged finger!

1 Like

Unfortunately, that did not go as planned, I suffered another crash right now, after mere seconds in play, so overheating is not a viable culprit here.

Drivers are up to date. Memtest OK too so RAM is clean.

Any adviceon how to test presumed faulty GPU maybe ?

crash_dump-2022-09-08-15.56.50-b8483ef7-b2aa-4cc6-970b-122d895c7bc5.dmp (778.4 KB)
Uploading: console-2022-09-08-15.56.50-b8483ef7-b2aa-4cc6-970b-122d895c7bc5.log…

Update : tried furmark stress test.

About 2min at 100% power and GPU usage, nothing happened, temperature was stable at 70C for the whole duration. so … :person_shrugging:

furmark benchmark seems fine. Well I don’t know sh*t about that but nothing burst into flames so I guess that’s good

If RAM and GPU are good, what other HW issue might cause this AccesViolation ? Network ? CPU ?

I’ll try running some other ressource hungry game to see if the problem is specific to V2 or not … Will keep you posted

You might want to double check your RAM, timings and voltage.

Try setting a framerate cap in the game’s settings.

If that doesn’t work, try lowering the worker threads in the settings.

Your ‘Worker Thread’ count can be changed using the ‘Settings’ menu within the Vermintide 2 launcher.

If your current ‘Worker Thread’ count exceeds 6, please lower it to 6.

A higher-than-average ‘Worker Thread’ count may result in stability issues; the reason for this is currently unknown.

Source: [PC] How to Resolve Most Crashes.

Got back to installing some drivers for my mobo and so far so good.

I installed drivers for

  • Network card
  • Intel chipset
  • Intel RST

If I had to guess, I’d say the Intel RST was the missing one causing the issues, but :person_shrugging:

Don’t know why I was crashing prior to reinstalling windows though, but eh, got it working so I won’t complain (much).

Thanks for your advice, I feel like I won’t be posting back in the next 7 days :hand_with_index_finger_and_thumb_crossed:

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.