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

Can you guys enable crash dump for bfv,exe - follow the below instriongs:

Tell Windows to automatically collect a crash dumps and store it in "%LOCALAPPDATA%\CrashDumps" by running the following commands in an administrator command prompt :

reg add "HKLM\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps\bfv.exe" /v DumpType /d 1 /t REG_DWORD

Use ur application as usually to reproduce the crash, once crash occurs let all Windows crash dialogs finish processing.
Go to "%LOCALAPPDATA%\CrashDumps" and locate the latest dump file. Once you have the dump file you can rar it and attach it to ur next post, or upload it to some file-hosting cloud/server and give us a link.

You can run the following command to revert back dump collection to its original state:

reg delete "HKLM\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps\bfv.exe" /f

(You can read more about Windows user-mode dump collection here: https://docs.microsoft.com/en-us/windows/desktop/wer/collecting-user-mode-dumps )

Then once you have 2-3 mini dumps ccreated afte tthe game crahes, upload them somewhere so I can  download them and look into the kernel debugger. I want to correlate if these are all related to what I think it is.

Was able to get a couple rounds of squad conquest in this morning and halfway through the 4th round it crashed. Haven't played in a couple weeks and I can't say that I'm surprised it's still absolutely

f

u

c

k

e

d

Having the same problem... thank you MS NV and EA

Faulting application name: bfv.exe, version: 1.0.68.64411, time stamp: 0x5c3644c4
Faulting module name: bfv.exe, version: 1.0.68.64411, time stamp: 0x5c3644c4
Exception code: 0xc0000005
Fault offset: 0x0000000001a26476
Faulting process id: 0xd5c
Faulting application start time: 0x01d4b11a9f312a30
Faulting application path: C:\Program Files (x86)\Origin Games\Battlefield V\bfv.exe
Faulting module path: C:\Program Files (x86)\Origin Games\Battlefield V\bfv.exe
Report Id: 4ceb75f0-26ff-4e76-82c0-6ca9927193aa
Faulting package full name:
Faulting package-relative application ID:

before the update: 

Windows: lowering RAM to 2133 mhz made it work 

Linux: the game runs with 15-20% less performance (but buttersmooth) then windows but with full 3600mhz clocked ram due to emulation / translation 

after the update last week:

Windows :  the game startes has massive fps drops and then closes after connecting to a game. 

Linux: the game starts fine, has high fps but lots of stutters and then closes midgame. 

Overall great update. 

Got my first crash in menu while changing weapon's look 😃

Hey all, another player was able to fix crashes to desktop via this:

" I meant to mark your post as fix, not mine....

Fix was discord. Uninstalled the Asus quick charge app and then used ccleaner and all was good!"

Source: https://answers.ea.com/t5/Technical-Issues/Random-game-crashing-to-desktop/m-p/7358826#M8614 

I neither have Discord nor Asus QuickCharge installed - yet having the same kind of crash.

and now?

I'm having the same issues still in January 2019. I don't use discord don't have Asus quick charge. Pointing fingers at so many other things, sharing fake fixes, not addressing an apparently widespread issue is real lame of EA. Why am I a premier subscriber when I can't play their top tier games? Now the Anthem demo has been completely unplayable.

Specs:

Ryzen 5 1600 

Rtx 2080

16gb G. Skill ripjaws 3200

Evga 800w psu. 

I keep coming back here just to see if there has been an actual fix and not pointing fingers at other companies. All my friends that were playing have since stopped since the latest update, it's not like the game even ran properly for them anyways. So at this point I'm not even mad, just put this behind you ladies and gents and don't buy their other games from now on! Most useless company ever!

Like many of you here, I've been struggling with this issue to various degrees.  I've had some luck turning off XMP profiles on my memory and turning off overclocks of any kind in general, but it's always bugged me that I can't play my PC the way it's meant to be setup and really take advantage of what the game has to offer (DXR, DX12, ect).  

After pulling memory sticks, swapping GPUs, re-installing Windows 10 with no change in performance (still hard crashing to desktop mid game). I checked Gigabyte's website for a BIOS update and they released an update to my board just about a week ago touting "performance and stability improvements".

Turning XMP back on and applying my old overclock settings and I'm happy to say the game seems to be running better for me.

Long story short, even if like me, you've recently checked for a BIOS update, check again!  

Similar case for me when running into the crash mid game. Finally found the dmp files created ( feel like an idiot that it took me so long )

DMP files indicated that the game was trying to talk to bad RAM locations. I knew my RAM wasn't bad ( memtest86 for 6 hours without error )

However on a previous build from a few years ago I ran into a similar problem, under normal circumstances my PC ran fine.. but under extreme loads it would crash to desktop, and sometime reboot. Problem was the default value being used for my RAM voltage was too low... I nudged it up 1 tick at a time until I had a stable machine under stress...

Why does this matter? RAM runs entirely off of electricity... if there isn't enough to keep it fully powered it loses its information, and when the application that was using that area of the RAM tries to hit it again the information is no longer there and Windows says you cant have it.

Please be careful with this information as I wouldn't want you to fry your PC...

Wow!

After the 29.01.2019 Patch it even Crashes to Desktop in the Main Menu.

Congratulations.

Problem continues please fix this.

I thought maybe this had been fixed after the recent patch. I played for about 15 mins with no problems, then the usual CTD.

Total stab in the dark: Maybe the tensor cores in the RTX cards are getting hotter than what the actual sensors are reading. Like maybe there is no probe on a part of the card that is getting so hot that it's unstable and crashes the game. It would only appear in games that take advantage of the tensor cores, which would only be this game so far.

I have a second monitor going showing that my card and my entire system is handling the huge load from this game very well (and NO other game crashes ever), so it's not my hardware.

To be clear, my CTDs only started about a month ago.

Please check your the crash dmp file created at MyDocuments\BFV\Temp

If you are like me and don't know how to parse them, upload them to:

http://www.osronline.com/page.cfm?name=Analyze

And if you are really a glutton for punishment you use procmon and parse those logs (nightmare)

For me the problem was too low of voltage for my RAM... all of the BF games I have had this issue on new build... PC works wonderful on everything until I do multiplayer battlefield... even single player battlefield would work wonderful...

My card also started to crash again after a day using 417.01 so I figured I would try installing 4017.71. I also worked for a day and started to crash again.

My step-up started today so I'm sending my 2080 xc back and I installed my old 980ti. Guess what, no crashes using 417.71. I have to think the RTracing has been corrupted or some other component specific to RTX.

Mt 980ti is actually working quit well.

I also use a RTX card (2080ti) and BFV run flawlessly til last week, the game suddently crashed to desktop and i cannot get it work again, tried everything (incl. clean reinstall windows) with no luck, the other games work fine, only BFV refuses to start

i think it is something wrong with the game, maybe it does not like RTX card anymore. Using newest nvidia driver or rollback to the old one does not help, the game keep crashing on startup

I’m going to give up on this game, what a waste of money

Thanks dc8flyer, Clearing cache did not work for me unfortunately

I read in battlefield forum that people using RTX card also have crash problem with battlefield V, especially factory OC versions

It’s not the card fault, the game may be too sensitive with OC RTX card at the moment and really needs a fix from DICE & EA. I have a factory OC version so i think it should be the problem

That may be the reason why your 980ti can run the game but not your RTX card

Well, now I can't get BF5 working with the 980ti either. These people really destroyed this game for some.

I noticed that the first time I play the game, it tends to last a lot longer before it crashes. I get like 60 mins in or more sometimes. Then when I try to persist in playing it after the first crash, the subsequent crashes get closer and closer together until it crashes once ever 2 or 3 minutes.

The fact that it gets worse lends itself to my theory that it may be the tensor cores don't have a well placed temp diode (or none at all), and they're overheating. Reminder: the temps reported by the stock thermometer(s) are great even under a stress test (75c max).

I will repeat (since people keep offering ideas / solutions that don't make sense): This is the ONLY game that crashes at all. I have many other games that use a ton of RAM (Cities Skylines is a supreme example), so the "my min  RAM voltage isn't enough" almost certainly doesn't apply to me. I have a ton of other games that max out my GPU usage and use a similar amount of vRAM. The only wildcards here are BF5 and ray tracing.

There are no crash logs generated; my BF5/Temp folder exists, but is empty.

Maybe there's more common hardware that exists between us than we realize. Here's a list:

7700k OCed to 4.9ghz
RTX 2080 OCed to +65mhz GPU / +675mhz vRAM
Gigabyte z170 Gaming 5
32GB RAM @ 3200mhz
Windows 10 Pro 1809
417.71 driver

Edit 6:40pm MST: I played about 5 mins before it crashed. I got about 2 or 3 micro-stutters per minute. I feels like it goes into a microstutter that just doesn't recover.

I noticed that the first time I play the game, it tends to last a lot longer before it crashes. I get like 60 mins in or more sometimes. Then when I try to persist in playing it after the first crash, the subsequent crashes get closer and closer together until it crashes once ever 2 or 3 minutes.

The fact that it gets worse lends itself to my theory that it may be the tensor cores don't have a well placed temp diode (or none at all), and they're overheating. Reminder: the temps reported by the stock thermometer(s) are great even under a stress test (75c max).

I will repeat (since people keep offering ideas / solutions that don't make sense): This is the ONLY game that crashes at all. I have many other games that use a ton of RAM (Cities Skylines is a supreme example), so the "my min  RAM voltage isn't enough" almost certainly doesn't apply to me. I have a ton of other games that max out my GPU usage and use a similar amount of vRAM. The only wildcards here are BF5 and ray tracing.

There are no crash logs generated; my BF5/Temp folder exists, but is empty.

Maybe there's more common hardware that exists between us than we realize. Here's a list:

7700k OCed to 4.9ghz
RTX 2080 OCed to +65mhz GPU / +675mhz vRAM
Gigabyte z170 Gaming 5
32GB RAM @ 3200mhz
Windows 10 Pro 1809
417.71 driver

I played about 5 mins before it crashed. I got about 2 or 3 micro-stutters per minute. I feels like it goes into a microstutter that just doesn't recover.

RTX 2070 OC for me... so slightly different enough that I cant discount your theory... however, of note is that everything in my case is air cooled, I am unsure of your config

AMD 2700x, stock speed, air cooled only

zotac RTX 2070 AMP extreme core edition, air cooled only

Asus ROG strix b450-f

16 gig RAM @ 3000 (capable of 3200 but I had stability issues, not in just bf5)

win pro 10 1809

417.71 driver

Basic 650 watt power supply (evga) with single 12v rail

Im always up for discussion in origin as well if anyone wants to chat offline...

other items of note: (please don't disable these if you are not familiar with the ramifications)

win firewall disabled

win defender disabled

UAC disabled