Re: Game Keeps Crashing don't know what to do HELP!

Thank you for the info @K3rberoZ We'll be on standby to hear the results.

We're doing our best to narrow down what's been causing this and everyone here has been exceptionally helpful providing all the steps they've tried and PC specifications. For that I truly want to thank everyone. I've played PC games growing up and know this stuff can be extremely tiresome to deal with. We completely understand the frustration that stems from it.

We always throw out the basic troubleshooting steps first because it really does help fix the majority of technical issues out there. Even the more complicated technical solutions won't work every time for everyone else as well, so we just need to see what sticks to help you get back into the game as soon as possible.

Like @K3rberoZ mentioned, there's a possibility it's program related. I've already seen threads where the GeForce Experience program will automatically download PC drivers for those that are playing on a laptop. Users have been able to fix it by manually installing the mobile version drivers from Nvidia's website.

I just stumbled across another thread involving ASUS setups here that's worth a look: https://answers.ea.com/t5/Technical-Issues/Help-Battlefield-V-blank-home-screen-PC/m-p/7214068#M3849

We tend to recommend a clean boot first to see if it's a program silently running in the background that's causing the game to fail. Discord caused a technical error for Origin a while back. It was fixed, but nonetheless it was unexpected.

We'll continue to dive a little deeper into this. Thank you all so much for hanging in there with us. 

/Blueberry

@K3rberoZ unfortunately your only source is your friend and you might be right for her/his problem it could be program related. However for me it isn't I tried reinstalling windows, clean boot, play on low res, future frames on or off, and whatever the ea community managers recommended. It doesn't make a difference. Like one of the people in this thread said a couple of weeks ago, i beleive it is the engine something fundamental not playing ball with windows 10 which makes the game crash without error. 

It's in no way my hardware, as the game plays buttery smooth on 100 frames on 1440p high settings. But after 10 minutes I get a ctd and no error message. I even tried playing the game on the first version of windows 10 without updating w10. It made me play roughly 10 minutes more on average but I would still crash, but however I would received a windows error which surprised me. But the error code etc was the same. 

I feel sorry for the people that paid 60$ for a game that can't even run on their pc. 

Can you explain why this is happening specially after a "Patch" 

I mean what did we download 17 Gyg for , its worst than bevore .

I get random Crashes for no reason at all? 

 @K3rberoZ.... I'm pretty sure none of us want to have "pitchforks" out.  But when you spend your money on something, you expect it to work.  And when it doesn't work for weeks and there's no solution/timeline to get fixed, well these things will happen... especially when most retailers will not let you refund the game after you've opened the package.  Not to mention EA has a pretty bad reputation for quality issues at launch.

It's like buying a car, finding out the engine breaks down every block and the dealer keeps telling you to wait.  Would you be happy spending hours of your personal time trying to fix it for them?  Because that's what many in this thread are really doing testing combos and combos of settings, reinstalling, some doing OS wipes, trying to get a workaround.  People paid for a fun experience of a QA'ed game... not hours of troubleshooting.  If they can't repro in house, it's not too difficult to have a engineer get permission to contact some people in the thread that are crashing pretty much non stop and get a valid crash dump they can analyze.  But yeah reproducible crashes should be a P1 issue listed on the "known issues" list.

So it's not like we want to give the community managers/EA/Dice a hard time... but we've been pretty darn patient (waiting since release and through this first big patch) and one thing we do expect as consumers is at least we have a working product which we paid for.

Thanks for the official response @EA_Blueberry.  I think many of us just want to know what the timeline will be of a resolution.  Please let us know as soon as you can.

@MethicsI also tried everything on her PC. If it was a problem with Windows 10 , i would have the same crashes, but i don't. (we're even on the same windows 10 version (1803))

And it can't be the game by itself, since almost everyone (including myself) would have these crashes. Out of my 9 friends i play with, only one gets these crashes. I did too, but only two times sionce release.

Also my source is my own research done and help provided on reddit and my experience as a former microsoft AnswerDesk agent.

Also for everyone, after i upgraded her chipset drivers to the latest version, the crashes seemed to stop (we only had ~1 - 1,5 hours to playtest, so take that with a grain of salt since the crashes are very random). Will test more tomorrow. Cheers!

@EA_Blueberry thanks for the reply. I hope my testing will bring us a little bit closer to the conclusion. Although i have a feeling that there might not be a one-for-all solution.

@EA_Blueberry I had my issue fixed by rolling back to older drivers. However, DICE/EA now require the latest drivers just to launch the game, which means I am back to crashing every 15 min just to play. This only happens in MP, as I was able to one-shot the new SP story. I am still convinced it has something to do with how RTX play on older hardware, as the older drivers I used were pre-RTX. 

@V--FENRIR--VKeep in mind that i have two completely identical systems to test. One PC has regular crashes, my personal PC doesn't have it.

The only difference is the user / the software on that machine.

So it can't be directly hardware related.

@K3rberoZ - You must have meant to address someone else because I NEVER said that it was hardware related. I was pretty clear in blaming the SOFTWARE when I said that they had access to the hardware. They had the ability to test across multiple hardware setups and conclude that the hardware is NOT the problem and that it was their SOFTWARE.