Intermittent Crashes

My dxdiag

Can anyone help? I'd really like to play this game I bought...

The error log would suggest an Nvidia component being to blame. So I would completely uninstall all Nvidia drivers. Then run DDU to remove it completely:

http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

then install the latest driver.

Thank you for the advice, I did all of that and used DDU to fully remove everything. Fresh install and it crashed after about 3 minutes playing.

Faulting application name: bf1.exe, version: 1.0.9.47594, time stamp: 0x57f64c72
Faulting module name: nvwgf2umx.dll, version: 21.21.13.7306, time stamp: 0x57f00c9b
Exception code: 0xc0000005
Fault offset: 0x0000000000337d7e
Faulting process id: 0x26c4
Faulting application start time: 0x01d22a5b32a09f95
Faulting application path: D:\Program Files (x86)\Battlefield 1\bf1.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3baaab0007230109\nvwgf2umx.dll
Report Id: 5e3e5a4d-2dd8-4265-9b58-0dad11ba901a
Faulting package full name:
Faulting package-relative application ID:

Are there any EA support people on this forum? It's been days and I still cannot play this game. 

Answers HQ is a place where gamers help each other, there are EA people on here but it's not direct customer support like on help.ea.com.

Have you tried disabling Origin in game and running a clean boot?

https://help.ea.com/en/help/faq/how-to-clean-boot-your-pc/

Actually I am beginning to suspect a hardware issue. Going to try that route.

@dirtloves

There is a possibility that this is a Windows permissions issue. Something easy to try is to start the game by right clicking the desktop link and 'Run as Administrator'. Give that a try and let us know how you get on, thanks.

OK, so I ran this with Admin privileges and I've completely replaced my GPU. I've run CHKDSK now and everything seems OK.

Failed again, but with a more interesting error..  two events in the log:

Faulting application name: bf1.exe, version: 1.0.9.53998, time stamp: 0x58077d90
Faulting module name: nvwgf2umx.dll, version: 21.21.13.7563, time stamp: 0x580af2e9
Exception code: 0xc0000096
Fault offset: 0x0000000000367f7f
Faulting process id: 0x1ebc
Faulting application start time: 0x01d22e5cec5195c6
Faulting application path: D:\Program Files (x86)\Battlefield 1\bf1.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_49b226e6441043f1\nvwgf2umx.dll
Report Id: b764b0a6-e38e-4d6b-947b-3aa930d6ee4a
Faulting package full name:
Faulting package-relative application ID:

----------------------------------------------

Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Battlefield™ 1 because of this error.

Program: Battlefield™ 1
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0

@dirtloves

Additionally, running System File Checker to ensure the integrity of your Windows System files is definitely something to try, if only to confirm no issue there:

http://support.microsoft.com/kb/929833