Greetings,

This game ran fine on my last build (2700x /x470/ 1080 Ti /Sound BlasterX AE-5/ 16GB ram / Windows 10.) I just built a new system:

5900X
6900 XT
x470 (Asus)
32GB RAM (3600Mhz)
Sound Blaster AE-9
Windows 10
OS and drivers fully updated.

Mad Max now crashed during the splash screen, right before it updates to show company involvement. I lowered my RAM speed to 3200MHz and the game then ran perfectly at 4k with everything cranked up. After power down / power on, the game crashes again at any RAM speed setting. Using a program called dxcpl-directx-11-emulator.exe and checking "Force warp" gets the game to load to the menu, but CPU utilization is between 90-100% and it runs so slow that I can't select any options.

Event viewer offers this:

Information:

Fault bucket 120368807500, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: MadMax.exe
P2: 1.0.3.0
P3: 5628a448
P4: MadMax.exe
P5: 1.0.3.0
P6: 5628a448
P7: c0000094
P8: 0000000002f5c46e
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A7.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER534.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER545.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER545.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER565.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MadMax.exe_73d5b63053fc77261d5c7aba5a752ac49ce 5b2_cf0f2102_36df1eca-d455-411b-8839-9fc07e974893

Analysis symbol:
Rechecking for solution: 0
Report Id: 3ef3a16c-5901-4980-b34f-2d58e610900c
Report Status: 268435456
Hashed bucket: 538c0177f6255afad0763bcca4be9769
Cab Guid: 0

Error:

Faulting application name: MadMax.exe, version: 1.0.3.0, time stamp: 0x5628a448
Faulting module name: MadMax.exe, version: 1.0.3.0, time stamp: 0x5628a448
Exception code: 0xc0000094
Fault offset: 0x0000000002f5c46e
Faulting process id: 0x33ec
Faulting application start time: 0x01d7e332f2d44d8e
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Mad Max\MadMax.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Mad Max\MadMax.exe
Report Id: 3ef3a16c-5901-4980-b34f-2d58e610900c
Faulting package full name:
Faulting package-relative application ID:

I read random posts across the internet where a handful of people have the same issue, and I can't figure out what it is. I hope to solve it or have someone solve it, because this is a great game and I would like to finish it.

Try and cap the framerate with RivaTuner Statistics Server or Radeon Chill. Maybe make a game profile in the Radeon software and lower the GPU frequency.

Testing that RAM would be a good idea too.

Having the same issue. Just upgraded to a 3000 series video card and the game crashes to desktop after a brief loading screen appearance. Working perfectly with old 1000 series card.

So, an update. I deleted the game, and all save files/cloud and tried to reinstall. There must be an issue with my Galaxy as it refused to repair or download the game without error - even offline installers. I manually downloaded the latest offline installer and launched that. The game now runs.

Additional odd thing, the main menu options menu has only one item - game. The options are there as I can hear them get selected, but the text isn't visible. You have to get into the game and adjust the settings from there.

I have the same Issue...

The Game just don*t start. I also tried the DirectX Emulator with Force Warp

My problem returned, it seems to be a scaling issue though. 2 solutions to this for Nvidia on Win11:

Under Manage 3D Settings:
For the Mad Max (madmax.exe) profile change Image Scaling to on.

or

Under Desktop Size and Position:
Change Perform Scaling on to Display

Overriding DPI scaling via the shortcut failed to do anything for me.

Sorry to necro this, but I hope this can help someone.

This crash issue (Exception code: 0xc0000094), is caused by the game trying to divide by zero, when retrieving the current screen's refresh rate.

The GoG version can be fixed quite easily, I wrote an open-source launcher for the game that fixes this specific issue, you can find it on GitHub - github.com/x0reaxeax/MadMaxCrashFix

If someone wants to patch it themselves, the `div` instruction at static address `0x140F17E5E` can be replaced with a `MOV r32, imm32` instruction, where `EAX` is the destination, and `imm32` holds the value of the target screen's refresh rate in Hz.

Unfortunately, the Steam version to this day uses Denuvo, so the fix is not applicable.

Hope this helps.

Worked for me, many thanks.