[WIP] How to fix issues using the game.crash file

This little guide gives some tipps on a few error lines from the game.crash file. Though it is always first recommended to check the game.log file. I've made a guide on that already, which can be found here:
https://steamcommunity.com/sharedfiles/filedetails/?id=2345183857

When to use the game.crash file

Basically, the game.crash file is very usefull if the game.log file doesn't show a clear reason for the crash. In cases like these the game.crash file can give more information as to what might be the cause of it.

Various error lines and how to solve it

Out of memory

When you are out of memory (aka RAM) you will see this in your game.crash file:

AvailMEM Virt:134206320 Phys:10096 Total:5

You can find this line below where your GPU is being reported.
If you are out of RAM then the game will crash. In the example above at the time of the crash only 5MB of RAM were available which is way too less. You can fix this by making sure that your page file/swap file setting is set to "System managed size". Here is an article describing how to do it:
https://www.tomshardware.com/news/how-to-manage-virtual-memory-pagefile-windows-10,36929.html
However, instead of making a custom size you have to activate "System managed size". That is all you need to change. Confirm that change and restart your PC.
If you have still the same issue after that, first make sure that the setting has actually saved. If it did you should check if the health of your RAM is still good using a programm for that (I will not recommend any programms here though).

Kernal base

Kinda infamous as it this is the error line:

Fault address: 00007FFEEE754D8C 0001:00063D8C C:\WINDOWS\System32\KERNELBASE.dll

Unless you have the "Out of memory" issue above (please check this first) this error is in 99% of cases pointing to mods. Which also means that you shouldn't be here but looking at your game.log file to find the mod(s) that is/are causing issues.

Dead beef

No, this is not something to eat but another error:

Fault address: 00000000 DEAD:BEEF0002 

This one is generally caused by the Discord overlay. If you have it active then you should deactivate it.

ntdll

If you have this line in your game.crash file:

Fault address: 00007FF9C2D67820 0001:00036820 C:\WINDOWS\SYSTEM32\ntdll.dll

Then you have corrupted system files. But not to worry, this can be fixed. For that you need to run the system file checker. Here are the instructions:
https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e

Asus Aura

Introduction
Error line
To fix that either update your Asus Aura and Razor Chroma software or change the following lines in the config (or config.cfg) file:

uset cf_asus_aura "1"
uset cf_razer_chroma "1" 

Change the "1" to "0" and save it.

You can find the config (or config.cfg) file in your documents in the ETS2 folder.

GPU issue

Any issues regarding the GPU will look like this:

Fault address: 00007FFD9AF19C10 0002:00007C10 C:\WINDOWS\SYSTEM32\d3d11.dll

This issue should generally also be visible in the game.log file as DX11 errors. For that either update your GPU driver (make a clean install of it by uninstalling the previous driver first), make sure your GPU is not overclocked (neither manually nor by factory) or make a clean reinstall of the GPU drivers using DDU (if you never used DDU then please first watch a tutorial and make notes).
Of course this is assuming that your GPU supports DX11.1. If it doesn't then switching to OpenGL is the solution.

Wheel driver

A wheel can also cause crashes:

Fault address: 0000000010002413 0001:00001413 C:\Windows\USB_Vibration\3333\EZFRD64.dll

(This also counts if the error line states anything with Vibration or Force Feedback)
If you get this then update the driver of your wheel (make sure the drivers are 64bit). If you can not find any 64bit driver for your wheel then you should deactivate Force Feedback.

But what if there is no game.crash file?

If there is no game.crash file then the game didn't crash. Every time the game is crashing a game.crash file will be generated. So if there is none then something on your PC forced the game to close. That can be a lot of things so you have some investigating to do.

[Wolfgang]

@Nimir-Raj: I will keep that in mind. So far, I have pretty much only seen that fault adress with the Discord overlay being the issue.

[Nimir-Raj]

Fault address: 00000000 DEAD:BEEF0002

Dead:Beef isn't a specific cause, it's often used when the crash cause is unknown but always related to the graphics card or drivers in some way. It's basically a catch all.

[Issa]

:like:

[Wolfgang]

Work in progress guide for now. Some text is subject to change but most of the error stuff should be correct.