Forum Discussion
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.
- 7 years ago
Problem continues please fix this.
- 7 years ago
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. - 7 years agoI don't think it is BF5 software causing the problem. Or it could be a combination of Nvidia drivers 471.17 and 471.35 and BF5.
Not sure about 471.22 driver but I 471.01 NVidia driver works perfectly.
I reinstalled 471.01 and no longer have any issues.
https://www.nvidia.com/download/driverResults.aspx/140341/en-us - 7 years agoUnfortunately is not working for me.
- 7 years 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...
- 7 years ago
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.
- 7 years ago
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
- 7 years agoDon't give up just yet. Follow this guide to clear out BF5 cache. It has help me each time for a short period and then back to crashes. But it might do more for you and at least get the game running.
https://help.ea.com/en-us/help/faq/clear-cache-to-fix-problems-with-your-games/
If you do get it to open, try disabling RTX and DXR together, then if it runs turn one or the other back on and test,
I would do it but I just sent my card in for the step-up. - 7 years ago
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
- 7 years ago
Well, now I can't get BF5 working with the 980ti either. These people really destroyed this game for some.
- 7 years ago
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. - 7 years ago
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. - 7 years ago
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
- 7 years ago
Further notes on my system (see my previous post):
I tried rolling back the overclock on EVERYTHING (including the factory overclock on my 2080). It made no difference - I still crashed just as often with or without the OC.
Since I have this AIDA64 widget visible on my second monitor constantly, I'm 100% certain my temps never spiked above 80 on my CPU, sitting at 60 - 75 typically while in BF5. My GPU sits at a steady 72 - 75c while in BF5 for long enough. I water cool my CPU and air cool my GPU in an extremely well ventilated case that I regularly dust (including making sure there's negligible dust on the radiator / heatsinks). I was just showing off my computer to co-worker less than 2 weeks ago, and I very thoroughly dusted it off then.
I also used a second widget GPU-Z a few times to confirm the temps. I made sure the temp poll rate is fairly high to ensure it's not spiking crazy high when it's not polling (to get accurate numbers).
Here's my idle temps:
Here's my temps after running BF5 for about 5 minutes (capped at 75fps due to 75hz display with vsync on, so load was at like 85%):
On my CPU, throttling begins at 100c. According to GPU-Z, throttling begins at 83c on my 2080. So I'm not hitting the thermal limit on anything ever.
So all this being said, I can safely eliminate the possibility of my computer overheating being why the game is crashing. I know that's a very real possibility with all the computer novices that surely play this game (nothing against any of you), but it's not for me.
Incidentally, I also have my CPU "unparked". Basically this just disables a default feature that down-clocks your CPU when it thinks the computer is idle - I had problems with microstuttering in BF4 and BF1, which this resolved.
Two other possibilities that can be eliminated:
I had a 7 year old, but fully functional power supply I decided to replace since it was nearing it's end of lifespan. I replaced it with a newer modular one. I had general computer crashing problems shortly after, so I had that new one replaced under warranty. The replacement did the same thing. So I went to Best Buy and replaced my video card with an identical one, and the computer crashing problem ceased. Nvidia replaced the defective one under warranty. The computer crashing problem has not returned since then. So that's 3 different cards, if you're keeping track.
All 3 cards had the BF5 crashing problem described in this thread. I'm including the original 2080 since it was working fine for a couple months, except BF5 would crash. So the possibility of defective card (the best buy temp one plus this replacement) is all but eliminated. The only possibility that remains for that to be defective is if there's an extremely large batch of defective 2080's, or there's a major design flaw with the 2080's. Since people are reporting the problem on other cards, this seems very unlikely (unless my tensor core theory holds true).
All 3 power supplies have the BF5 crashing problem present. It's astronomically unlikely any of the 3 power supplies are defective since the BF5 crashing problem was present on all 3 equally (and AIDA 64 reports very healthy voltages on all rails). So that possibility can safely be eliminated.
Sorry for the TL;DR, but I want to provide as much data possible to prove to the devs this is not an isolated issue with people with crappy computers and viruses and whatnot. I work for level 3 tech support, so I know what it's like to escalate an issue to the devs and have them bounce it back because they can't recreate the issue. This issue is 100% on BF5's side and / or Nvidia's side. Regardless, since BF5 is the only game that crashes, DICE needs to fix the issue, or work with Nvidia to identify a design flaw with their RTX cards. - 7 years ago
With as many people with different configurations and different video cards and different rig set up’s, I am absolutely convinced that it is a software issue with dice. The preposterous part of this whole scenario is that Dice will not even respond and I have sent them no less than 100 crash reports. I have consulted an attorney and we are proceeding with putting together a class action lawsuit. During the discovery phase of the lawsuit, Dice will be required to supply the name and email address of every single person that has ever purchased the game to include them in the class-action suit. At that point I would think that losing millions of dollars might give them the kick in the * to get off their lazy * and FINALLY ADDRESS THE PROBLEM!
- 7 years agoTDC has been happening for almost 2 months for me and friends I associate with in BF5. Its absolutely not a hardware issue. It’s the buggy game Dice put out as a finished product when In actuality it is a beta version at best.
- 7 years ago
ASUS Prime x470
R7 2700x
16 GB Trident Z 3600 Mhz @ 3600 Mhz
Sapphire Nitro+ Vega64 (updated from RX 580 to 2070 to Vega64)
So, i did buy a new nvme ssd and decided to reinstall everything from scratch.
But this time i did it different then i do usually.
Instead of downloading my drivers for the Mainboard and Onboard stuff from ASUS i did only install a clean windows and let windows grab all drivers for me.
The only thing i downloaded was the GPU driver since it was newer.
Then i made a Disk Image!
I installed Origin, downloaded BF5 and had about 5h BFV without any crash.
I made a DiskImage.
I installed the drivers provided by the ASUS website. BFV crashed when opened
I restored the DiskImage
So i moved forward to installed MSI Afterburner + AIDA64 and enabled the OSD, BFV started crashing when connecting to a server.
I restored the DiskImage
I installed Teamspeak with Overwolf, BFV crashed when opened
I restored the DiskImage
I installed the Discord and enabled the OSD, BFV crashed midgame.
I restored the DiskImage
I had about 15h of crash free BFV.
Moved the DiskImage to a smaller SSD.
I have no clue if it helps, but somehow OSD + Hardwaremonitoring seems to interfere.
I now have a SSD only to play BFV.
- 7 years ago
I found this in event viewer a week or two ago along with the Nvidia driver crash/recovery followed three seconds later with BF5.exe program fault/crash. The was a reoccurring event time after time after BF5 update and logged in Event Viewer consistently. It was also fairly consistent that five minutes into gamming that the crash would repeat. With the second 20gb BF5 update the crashes were random anywhere from startup to several minutes into the game.
BF5 worked perfectly, along with my other games until two updates occurred around the same time. One was Nvidia driver update (believe it was 417.35) and then the first BF5 update in early Jan. Reinstalling earlier versions of Nvidia drivers does not correct crashes leading me to conclude it cant be anything other than BF5.
The image below may point to BF5 code interfering with Windows operating system.
And of course I have yet to hear back from Origin on the matter.
- 7 years ago
this Just start happening to me as well.. last few days... i have 427 hours into the game alone... and just recently happening.
I am not OC on anything hardware all stock out of box.. No overheating issues
Ryzen 2700x
16GB RAM
on SSD Drive
GTX 980 -- Driver 417.71
Win 10 Pro- 1803
all game modes.. did everything same as other poster ( uninstall..reinstall... safe mode.. yada yada...)
no over lays.. i do not run anything else on PC. again this just start happening after last update
Faulting application name: bfv.exe, version: 1.0.69.20852, time stamp: 0x5c487dbc
Faulting module name: bfv.exe, version: 1.0.69.20852, time stamp: 0x5c487dbc
Exception code: 0xc0000005
Fault offset: 0x00000000089bbfe5
Faulting process id: 0x2414
Faulting application start time: 0x01d4b9dc5a70c43e
Faulting application path: G:\Program Files (x86)\Origin Games\Battlefield V\bfv.exe
Faulting module path: G:\Program Files (x86)\Origin Games\Battlefield V\bfv.exe
Report Id: 361ac459-64c8-4090-a4eb-efcaa39df710
Faulting package full name:
Faulting package-relative application ID:Fault bucket 1862081543290474840, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0Problem signature:
P1: bfv.exe
P2: 1.0.69.20852
P3: 5c487dbc
P4: bfv.exe
P5: 1.0.69.20852
P6: 5c487dbc
P7: c0000005
P8: 00000000089bbfe5
P9:
P10: - 7 years ago
this Just start happening to me as well.. last few days... i have 427 hours into the game alone... and just recently happening.
I am not OC on anything hardware all stock out of box.. No overheating issues
Ryzen 2700x
16GB RAM
on SSD Drive
GTX 980 -- Driver 417.71
Win 10 Pro- 1803
all game modes.. did everything same as other poster ( uninstall..reinstall... safe mode.. yada yada...)
no over lays.. i do not run anything else on PC. again this just start happening after last update
Faulting application name: bfv.exe, version: 1.0.69.20852, time stamp: 0x5c487dbc
Faulting module name: bfv.exe, version: 1.0.69.20852, time stamp: 0x5c487dbc
Exception code: 0xc0000005
Fault offset: 0x00000000089bbfe5
Faulting process id: 0x2414
Faulting application start time: 0x01d4b9dc5a70c43e
Faulting application path: G:\Program Files (x86)\Origin Games\Battlefield V\bfv.exe
Faulting module path: G:\Program Files (x86)\Origin Games\Battlefield V\bfv.exe
Report Id: 361ac459-64c8-4090-a4eb-efcaa39df710
Faulting package full name:
Faulting package-relative application ID:Fault bucket 1862081543290474840, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0Problem signature:
P1: bfv.exe
P2: 1.0.69.20852
P3: 5c487dbc
P4: bfv.exe
P5: 1.0.69.20852
P6: 5c487dbc
P7: c0000005
P8: 00000000089bbfe5
P9:
P10: - 7 years ago
minorly off topic... but with the anthem demo going on, do you guys have the same problem there? I know I did.... Maybe its something about the frost engine, not the individual developers...
- 7 years ago
Crashes are more frequent now than ever.
Thank you very much Dice.
And Thanks again for NOT Making this a Top priority.
- 7 years ago
I wanted to report back:
I left DX12 on, but disabled Ray-Tracing in BF5.
I played for 2 - 3 hours with zero crashes. I will play some more in a bit, but I expect I will experience more of the same. For me, it seems to be ray-tracing related. I also noticed I stopped getting 2 - 3 microstutters per minute after I disabled ray tracing. - 7 years ago
Well, at least it’s still working for you
My game won’t even launch, The blue loading screen shows up for a few seconds then auto close. I wish i could see the game menu
Anyway, i never play with DX12 or DXR on, the game was very smooth before the January updates, it’s totally dead now. In their recent Quality of Life commitment, no Crash/Launch issue was mentioned, that means they do not care about it, sadly
Flick through the forum, i saw some recommendations from Community managers, all of them are useless and rarely work (clear cache, ccleaner...), and they are repeatedly used (copy & paste) to answer all issue related to Crash/Launch problems, nothing innovative there.
- 7 years ago
so, an update for me.. i un installed just the nvidia HDMI audio after booting from safe mode..and all of the other "fluff" ... i was getting other errors with realtec audio so it may have been conflicting. so far no crashes since.
About Battlefield V
Recent Discussions
- 11 hours ago
- 2 days ago
- 2 days ago