Solution: Fatal Application Exit fixed!! (finally)

[Thomas Anderson]

First of all, fix this Capcom. I'm about to give up on this game. The fact that it's been a month and a hotfix isn't out yet is ridiculous. When I 100% the achievements I plan on writing a review and if it isn't fixed, expect it to be negative.

Now to the point - if you're getting constant crashes every 2-3 minutes with that fatal application exit BS --

Turn off any and all over clocking. You don't need to under clock as some people here suggest. I don't mean just on your GPU - I mean on your CPU as well. What finally fixed it for me was going into BIOS (I have an ASUS) and turn off all OC profiles and literally going to the LOAD ALL DEFAULT settings.

This brought the board back to day 1 specs and turned everything off. That seems to have stopped MOST of the crashing. The game still crashes about once every couple of hours, but I can at least make some progress now.

(Be warned, if you have any other operating systems or dual boot, you'll be turning off other operating systems. If you're savvy enough to set it up though, you know which settings not to set back to stock.)

My suggestion is to set everything else back to stock settings.

Why Capcom made a PC GAME that doesn't do well when people over clock is beyond me. I'm even more flabbergasted that it isn't fixed yet and that there has been zero response over it. All I have to say now is this - if it isn't fixed soon, there will be other games I want to play and I will be returning to my old tuned settings. I'll be forever done with this game if this problem is still happening by then because I am not keeping my PC hobbled for just 1 game.

And that will reflect in my review.

[Shirakani]

So, problem exists with YOUR potato and you blame Capcom for it... Nice.

I'll make sure to mark your review as worthless.

[Thomas Anderson]

Not sure how you think my computer is causing the crashes that everyone else is reporting, but hey, whatever helps you sleep at night bucko. You can rest easy now knowing that you've laid the burden of everyone's crashes on to 1 bad review that hasn't even been posted yet. Excellent work.

[Shirakani]

Ok, so... according to you:

APPLICATION INSTABILITY DUE TO OVERCLOCKING, as proven by you is somehow CAPCOM'S fault?!?

I... I... I don't even...

We're totally utterly done here... Jeebus H Christ...

[Peelsepuuppi]

Originally posted by Shirakani:

So, problem exists with YOUR potato and you blame Capcom for it... Nice.

I'll make sure to mark your review as worthless.

Not going to be as crude as this, but I have to say that OCing was never known for it's 100% stability.

[Cypher]

Overclocking issues --- yep, definitely devs being incompetent...

[MarkedMarkyMark]

I had this error without an overclock, so i'm pretty sure this isn't ''really'' it. Granted I stopped having this error for...no reason, so shrugs.

[Thomas Anderson]

Originally posted by Shirakani:

Ok, so... according to you:

APPLICATION INSTABILITY DUE TO OVERCLOCKING, as proven by you is somehow CAPCOM'S fault?!?

I... I... I don't even...

We're totally utterly done here... Jeebus H Christ...

Lol good troll. Definitely 11/10

Yes. Let's not look to Capcom to fix an issue which anyone with a modicum of computer savvy has done to their computer. Not to mention other developers have zero problems with overclocked computers.

This from the guy who's a member of a group called "2B's Ass", "Hentai" and "noob frag"

LMAO yeah, we're definitely done my dude.

[Thomas Anderson]

LOL Oh no and look - Seems like the latest patch made things even worse.

NOT CAPCOMS FAULT, tho, mirite?

Get rekt.

[lolschrauber]

Overclocking fixes issues? Who could've known that operating Hardware outside of their officially supported Performance range could cause problems?

Genius.

[Thomas Anderson]

Well - ok, let's say it is overclocking issues.

Any explanation for the 150+ post thread about the latest issues after the patch? I mean, I'm running stock now, as well as many, many others. Seems like a Capcom issue to me

¯\_(ツ)_/¯

[MarkedMarkyMark]

Originally posted by Thomas Anderson:

Well - ok, let's say it is overclocking issues.

Any explanation for the 150+ post thread about the latest issues after the patch? I mean, I'm running stock now, as well as many, many others. Seems like a Capcom issue to me

¯\_(ツ)_/¯

It is not overclocking issues, it's also drivers, and yes low to mid end machines suffer from it (just leave effects at low and it usually fixes it) there's plenty of small issues that causes it.

This is not a perfect port, it's not bad i've seen worse, but people that go ''i have no issue'' is useless, you're not the problem, and not part of it right? It's like if you've got nothing constructive to add to the possible fixes, then just leave, those people need to understand that just cause it works for them dosent mean it works for everyone, it dosent erase the issue, it's a tad annoying i know.

That said it is kinda lame that you're stepping down to their level of maturity with the snark, which only causes more silly big ding dong measurements fights which is also not constructive at all.

[Thomas Anderson]

Originally posted by BBKSSorveteDeTentáculo:

Originally posted by Thomas Anderson:

Well - ok, let's say it is overclocking issues.

Any explanation for the 150+ post thread about the latest issues after the patch? I mean, I'm running stock now, as well as many, many others. Seems like a Capcom issue to me

¯\_(ツ)_/¯

It is not overclocking issues, it's also drivers, and yes low to mid end machines suffer from it (just leave effects at low and it usually fixes it) there's plenty of small issues that causes it.

This is not a perfect port, it's not bad i've seen worse, but people that go ''i have no issue'' is useless, you're not the problem, and not part of it right? It's like if you've got nothing constructive to add to the possible fixes, then just leave, those people need to understand that just cause it works for them dosent mean it works for everyone, it dosent erase the issue, it's a tad annoying i know.

That said it is kinda lame that you're stepping down to their level of maturity with the snark, which only causes more silly big ding dong measurements fights which is also not constructive at all.

I won't justify myself when I do stuff like that, but I tend to give back what gets given to me.

Of course, had Mr Hentai over there been mature instead of dismissive, this could have been a constructive conversation. If someone is willing to have a real discussion, I can reciprocate.

Like hundreds (thousands?) of others that have been having the same issue I had been seeing and had NONE of the troubleshooting steps help, I just thought it'd be nice to share what finally fixed it for me.

Did I blame Capcom? Yup. And that's up for debate, but seeing as how so many other games don't (but some do) have issues with ports AND the fact that it definately wasn't just me seeing the error, I was more inclined to blame Capcom, as their is the ONLY game that wasn't working properly on my rig - for whatever reason.

[MarkedMarkyMark]

Originally posted by Thomas Anderson:

Originally posted by BBKSSorveteDeTentáculo:

It is not overclocking issues, it's also drivers, and yes low to mid end machines suffer from it (just leave effects at low and it usually fixes it) there's plenty of small issues that causes it.

This is not a perfect port, it's not bad i've seen worse, but people that go ''i have no issue'' is useless, you're not the problem, and not part of it right? It's like if you've got nothing constructive to add to the possible fixes, then just leave, those people need to understand that just cause it works for them dosent mean it works for everyone, it dosent erase the issue, it's a tad annoying i know.

That said it is kinda lame that you're stepping down to their level of maturity with the snark, which only causes more silly big ding dong measurements fights which is also not constructive at all.

I won't justify myself when I do stuff like that, but I tend to give back what gets given to me.

Of course, had Mr Hentai over there been mature instead of dismissive, this could have been a constructive conversation. If someone is willing to have a real discussion, I can reciprocate.

Like hundreds (thousands?) of others that have been having the same issue I had been seeing and had NONE of the troubleshooting steps help, I just thought it'd be nice to share what finally fixed it for me.

Did I blame Capcom? Yup. And that's up for debate, but seeing as how so many other games don't (but some do) have issues with ports AND the fact that it definately wasn't just me seeing the error, I was more inclined to blame Capcom, as their is the ONLY game that wasn't working properly on my rig - for whatever reason.

Hey what's wrong with a lil bit of hentai? that's in fact my job, what, are you some sort of hentaicist?

Jokes aside, yeah, the port is a bit rough, especially with denuvo, its a thing it wont matter for people with high end pcs but that like 5 fps matters for a pc that's struggling to run it at 60, not my case but i've been there.

But yeah, i'm POSITIVE this error is related to lighting effects, i used to get it consistently with cavaleire and furies, and royal guarding too, I lowered it down and it stopped, tho' I specifically made the settings ''default'' and only changed the effects. Also make sure it is NOT dx11, they say you get fps, BUT i'm pretty sure dx11 causes it to happen twice more. I'm saying as someone that did a lot of testing, these two things :

- Low Effects
- Keeping it dx12

Are exactly what fixed it for me. I spent a long time royal guarding cavaliere after doing that and it seemed to have fixed it. In fact I am now a cavaliere expert with royal guard.

[Thomas Anderson]

Originally posted by BBKSSorveteDeTentáculo:

Originally posted by Thomas Anderson:

I won't justify myself when I do stuff like that, but I tend to give back what gets given to me.

Of course, had Mr Hentai over there been mature instead of dismissive, this could have been a constructive conversation. If someone is willing to have a real discussion, I can reciprocate.

Like hundreds (thousands?) of others that have been having the same issue I had been seeing and had NONE of the troubleshooting steps help, I just thought it'd be nice to share what finally fixed it for me.

Did I blame Capcom? Yup. And that's up for debate, but seeing as how so many other games don't (but some do) have issues with ports AND the fact that it definately wasn't just me seeing the error, I was more inclined to blame Capcom, as their is the ONLY game that wasn't working properly on my rig - for whatever reason.

Hey what's wrong with a lil bit of hentai? that's in fact my job, what, are you some sort of hentaicist?

Jokes aside, yeah, the port is a bit rough, especially with denuvo, its a thing it wont matter for people with high end pcs but that like 5 fps matters for a pc that's struggling to run it at 60, not my case but i've been there.

But yeah, i'm POSITIVE this error is related to lighting effects, i used to get it consistently with cavaleire and furies, and royal guarding too, I lowered it down and it stopped, tho' I specifically made the settings ''default'' and only changed the effects. Also make sure it is NOT dx11, they say you get fps, BUT i'm pretty sure dx11 causes it to happen twice more. I'm saying as someone that did a lot of testing, these two things :

- Low Effects
- Keeping it dx12

Are exactly what fixed it for me. I spent a long time royal guarding cavaliere after doing that and it seemed to have fixed it. In fact I am now a cavaliere expert with royal guard.

I'll have to take your word that there's nothing wrong with a little bit of hentai. Or better yet, maybe I should do my own research so I'm not so ignorant on the subject? Any suggestions on where to begin? XD

I agree with you. I think that whatever is going on is related to something in the lighting effects. I've noticed most of the crashes seem to popup whenever that lens flare is called - but it has been other times as well. I've tried turning off most of the lighting effects, but the crashes are so random, it's hard for me to get a handle on whether or not it's happening because of a specific effect.

Since this new patch has knocked me back to square one, I'll try setting everything to potato quality and see if that makes a difference.

[Thomas Anderson]

It just occurred to me that I haven't given my specs here. Just in case someone is thinking I'm running a sup-par machine:

i7-4790k (now running stock speed - water cooled)
12GB GTX Titan X (latest drivers - also water cool - also stock speeds)
32 GB ram (stock speeds / timing if you want to be technical)
m.2 SSD Samsung 960 Pro on PCI-E lane
Win 10 (latest patches)