Additional to @IIPrest0nII, please also provide a DxDiag in text file format and post it with your next reply.
You can do that with the "choose file" button at the bottom right corner of the reply window.
Your DxDiag is full with "RADAR_PRE_LEAK_64" warnings for several different games and application, but not BF1.
Still, I think it is possible that the error in BF1 is related.
"RADAR_PRE_LEAK_64" is a memory leak warning, and the error you get is an error that also (not only) occurs if the system would run out of memory.
Try this:
Go here and use the guide to set your pagefile to "32660" minimum and maximum. (Also set it to your SSD, if it is not already set there.) > Reboot > see if it is any better.
I tried but I still getting this error.
Ok, that is a different error.
Run the Windows System File Checker Sfc /scannnow and post the concluding message.
Also create a new DxDiag in text file format, also go to your Reliability monitor (Press the windows key and "R" at the same time and copy or type "perfmon /rel" (without the quotes) in > ENTER and look if it has BF1 entries.
If yes double click at the last one, copy it to the clipboard, (Bottom left corner) save it to a text file and load it up together with the DxDiag.
You can do that with the "Browse" button at the bottom right corner of the reply window.
Here is the all things.
DICE TeamHey @xXanaphia I took look on that log and yeah DX is crashing (d3d11.dll) hense why Battlefield 1 stops working. When did you do a windows update last time?
If its all update I recommend that you try making new windows user on your pc as Admin and try to play BF1 on there.
/Atic
Do you use Reshade?
If not try to switch to DX12.
On the new user account, did it crash with the same error message?
If that not helps, there is a newer driver available for the 1070.
Install the graphic driver this way:
• Download DDU:
• Install (if you have profiles for games, back them up using "NVIDIA inspector")
• run DDU > save mode > NVIDIA Software and Drivers > Clean and Restart
• shut down your virus scanner.
• Run the installation EXE > install only the GPU Driver and the PHYSX software.
(don't deselect components you need even if the have the same version number, the installation program will deinstall them if you do)
• Reboot > test.
No I don't using Reshade.
Yes it was same error message (Battlefield1 has stopped working) on the new user account as adminstrator.
I tried every thing up there. First I closed my antivirus and restarted pc with save mode. I reinstalled new driver after wipe everything with DDU. I installed just Driver and Phsyx.
But it worked just for 1 hour. And agter that, again I get same crash error
On the software side we did a lot by now, lets take a look at the hardware.
Here is the hwinfo. I played for around 1.5 hours and after game crashed with same error.
https://www.dropbox.com/s/6odn7pcfw0e7p2j/system%20sensors%20summary2.CSV?dl=0
Ok, the log looks good so fare.
The interesting points are this:
As you can see the Virtual Memory usage (Note: In HWinfo that is the entire accessible memory space.) spikes at the end of the log without an increase in physical memory usage.
That means there is no classic memory leak, but I assume that this sudden increase in memory load is the reason for the crash. (In your second DxDiag BF1 crashes with an access violation code.)
The problem is that this is not really helping to localize the problem.
This behaviour can have any number of reasons. (The BIOS, the OS, third party applications or services [Did you tried the clean boot @IIPrest0nII suggested] the game or memory issues.
Yes I tried clean boot for pc and it didn't worked. Also I upgraded BIOS on official page on MSI 3 months ago and it didn't worked too.
What should I do with this problem. This is really annoying.
@xXanaphia wrote:
What should I do with this problem. This is really annoying.
It depends on how fare you want to go.
First lets try the last "easy" troubleshooting step I can think of here.
Create a new Windows user account (Administrator) > reboot > logon to the new account > test.
Here is what you can do (unless you know someone who can perform some serious debugging on your machine on side.) if that also don't works: (Test after each step)
If that all fails you need to lock at the hardware side. Start with MemTest.
