April 2019
Kind regards,
Filip
April 2019
April 2019
The information we need:
We need Dxdiag, to see what Hardware and drivers you are using. ATTACHED
What did you do just before the crash happen? INSTALLED FIRESTORM UPDATE,
Does it happen in all game modes? MAINLY FIRESTORM
Does it always happen at the same action/place? RANDOM LAG, FRAME DROP, GAME CRASH
April 2019 - last edited April 2019
There is no way Dice do not have access to a PC that is exhibiting crashes with BF5, its so wide spread and is the same issue.
So I dont know why requests for info are being made, if dice are really bothered by this and literally have no other machines or way of replicating this, you can PM me and buy my 6mo old PC from me at todays cost price, AMD 2700x, MSI gaming X 1080ti, Asus 470x crosshair, 16GB Trident x Ram, ADATA 1tb NVME, NZXT x62 AIO, you can even buy my monitor for the same resolution (LC34J791WTUXEN)
Im in UK and ill buy another. you can have the newly installed OS with all latest drivers and updates with just BF5 installed as it currently is. It crashes to desktop guaranteed the first time you play about 15 mins in, then on 2nd load sometimes it plays a few matches sometimes not. Event system says KERNELBASE.dll error for BF5
Then you can diagnose until your hearts content and fix the issue. something says your not gonna though, and this is all kicking the can down the street until its no longer relevant and BF5 is no longer played.
P.S I'm serious about the offer to sell, this has gone on long enough with the developers playing the 'whats the issue we cant replicate it game'
April 2019
Sadly I have to agree with you @B3ATTS .....
I also spent money on upgrading my machine, till I reached a moment, where there is nothing old and I still cannot run the game normally..
Kind Regards
Daniel
April 2019
April 2019
April 2019
Just to confirm, after a few weeks of using older 417.01 drivers i’ve had no CTD at all. I originally used drivers from 416.xx era and had 400hrs without an issue since purchasing the game, so I used a driver close to them, hence 417.01. My first experience of a CTD was after updating my drivers to 419.xx, which always pointed to KERNELBASE.DLL in event viewer which triggers a few seconds after “nvlddmkm has stopped responding and has recovered”. Every driver i’ve used returns this same .dll in event viewer after a CTD.
After using 417.01 issue free I tried the latest 425.37, i experienced 2 CTD in 3 hours. So, there is something about 419.xx onwards that’s causing it. Possibly even 418.xx but don’t have time to test those. But for me at least, 417.01 works flawlessly with no problems..... I hope this helps.
April 2019