Mad Max crashes after an update of Origin

I have precisely the same problem with Mad Max from this weekend. Played more than 15 hours without a problem and now ia not possible to srartup. Also tried un/install game and Origin as well .

Until now there had been at least 2 Origin updates, but the issue persists. I even tried booting my laptop as 'Safe mode with network available', launched Origin and uninstalled Mad Max, then installed it again. After more than 1 and half an hour, the download was complete but a popup window came up "Error. The VC++ runtime redistributable package was not installed successfully. Setup cannot continue. (1601)"

And then another window of Origin said (in Korean, my language) "Unexpected error. Try again later. Error: 327684:1"

I wouldn't blame EA for what I just tried, as it's not an official reply or suggestion but was from a user on the Internet.

However, this issue persists for more than a week and it's not dealt with yet. What the hell is happening? Literally I've tried everything I could, there doesn't seem to be anything else I may try. After writing here, I had submitted UO Trace info to Korean branch as well, though I couldn't understand why I had to. (I was pretty sure it's not the network, but progamming can involve a problem from an unexpected source, so I just submitted it, with downloading an external program provided by EA.)

Hey @sengda2000, as Mad Max is a non-EA title then the level of support that we can offer is limited. I tested the game there and was able to launch and play it without issue so it could be a system issue that you are seeing.

Let's start by gabbing a DxDiag so that we can take a look at your system: https://help.ea.com/en/help/pc/how-to-gather-dxdiag-information/

Darko

Hello @EA_Darko, a few hours ago I contact EA Support of the U.S. Until now I've contact EA Support of my country 6 times online, and called them 4 times but my issue wasn't solved.

I was advised to update the graphics driver, so I tried this but it didn't help. Removed the graphics driver along with GeForce Experience, downloaded the installers, turned off antivirus to make sure it doesn't interfere, then launched installers as Admin. Then, manually downloaded update installer and updated the graphics driver and GeForce Experience, again with antivirus turned off and as Admin. Still, the issue persists.

I tried downloading another game through Origin (Syndicate(1993)) and it works perfectly well. Have no idea how to solve this matter.

Anyway, I attach DxDiag along wth msinfo, just in case. Both are newly updated after updating graphics driver.

Thank you for your concern.

@EA_Darko I had attached MSInfo as well, just in case anyone needs it. But I just realized the previous MSInfo was not in English. I attach the English version for it. DxDiag was in English, so no need to change that.

Hey @sengda2000 would it be possible to rerun the DxDiag in English?

While I love Korean cinema I can only speak about 4 words of it and read even less. 

From what I can see and understand your DxDiag is showing a number of issues so its no harm to use the System File Checker tool to repair missing or corrupted system files: https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

Darko

@EA_Darko for about 1 or 2 days I didn't notice you replied here again. I checked DxDiag and found a few expressions written in Korean. I added English translations for each Korean expression like 오전 -> 오전(morning) so that English speakers can understand this.

I just tried the link you provided on Wednesday, it says the corrupted files were repaired but when I launch the game it still crashes. I gave it a last chance, by uninstalling the game and Origin client and then reinstalling Origin and the game. It still doesn't work.

I've decided to stop trying to solve this issue, for 4 weeks as of today I haven't been able to play this game. I've contacted EA Korea about 12 times (including phone calls) and EA U.S. 4 times. I also contacted NVidia and WB Games (the latter hasn't replied yet, for 5 days) but the issue still persists. EA provided some suggestions but now I'm just told to contact WB Games.

I strongly believe that EA is responsible for this issue, this happened after the Origin update which was on around 24th or 25th of January (in my country it was 25th, but in Western countries it can be 24th). I can assure I didn't install or update anything, as long as there's any program which updates itself without any notification. Today I tried installing Origin and Mad Max on another desktop, but it didn't work in the same way like my laptop, surprisingly enough. If my laptop was the only one suffering, then it's on my side, but from the trial with another desktop I can see it's not on me. Still, EA's final standpoint after weeks of support was that WB Games is responsible, as it's not from EA but is from a 3rd party.

I'm pretty much disappointed about this, I was playing Mad Max through Origin Access, by this subscription EA earns the profit, users don't pay directly to those 3rd party publishers. Based on the official reply I got directly from EA U.S., EA is not responsible for the issue(s) regarding 3rd party publisher. In such a case like this, EA would not provide any compensation but I need to demand WB Games for that. When payment is made to EA and EA earns the commission, EA is not responsible. How impressive.

My Origin Access is valid until Mar 1st, but I cannot see when this issue will be solved. Even if WB Games or EA announces the issue is solved, what if I discover it actually isn't? I pay for Origin Access only to discover it's just the same? I've been given so many steps to try but none of them helped me. Even in such a situation, it is me who has to decide whether to extend the subscription or not.

I will not pay for the Origin Access in the future. Also, I would not pay for 3rd party games published through Origin. If I ever pay, that definitely will be games published by EA.

EA_Darko, you can stop paying attention to my case. EA will not support this case anymore and I don't expect EA to deal with this. Thank you for your dedication, though.