"Battlefield 4 Has Stopped Working"

[JB780]

I recently decided to get back into Battlefield 4, I bought the game at launch and was fortunate enough not to experience most of the issues that others were having during this infamous past year in which I put about 150 hours into BF4. With the much hyped fall patch and final DLC coming out I started playing BF4 again with no issues, and then the fall patch was released. As soon as I had the fall patch installed my games started crashing on average every 20 minutes, sometimes 5 or 10 minutes but rarely longer than 20 minutes would go by before I would crash.

 

It's always the same, the game just stops and I get the infamous "Battlefield 4 has stopped working" notification window. No error code or anything specific, and it's only the game that crashes not my computer. Eventually I grew tired of crashing all the time and contacted EA Help, and they were about as helpful as you would expect, none of their recommended steps have fixed my problem. I even went so far as to uninstall/re-install the game but i'm still crashing. EA Help has said that they have forwarded my case to one of their "Specialists" so I'll have to wait and see if/when anything happens. 

 

Does anyone have any ideas what the issue may be?

 

Is anyone else experiencing the same problem?

 

I've made no changes to software or hardware recently and the problem corresponds to immediately, and I do mean the first time I played, after the fall patch

 

Specs are:

Windows 8.1 64 bit

HD7950 Crossfire

i5 3570K (OC @ 4.5ghz)

8gb ram

750 watt PSU

 

150 hours with no major problems and NOW this!

[olback]

"Battlefield 4 Has Stopped Working"

 

Dont worry m8. 

 

Its normal. Its 100% fine

 

#BlameDICE

[JB780]

"Battlefield 4 Has Stopped Working"

 

Dont worry m8. 

 

Its normal. Its 100% fine

 

#BlameDICE

 

I know I'm in the majority here, but still. The game has been out for a year and they're still breaking it? In the meantime on battlelog they put up a post about how great the patch is and include positive feedback from people who haven't been screwed over by the patch.

Don't get me wrong, I have no problem with the gameplay changes, my problem is not being able to play the game for more than 20 minutes at a time. It sucks crashing in the middle of a match and then having to wait in line to get back into a full 64 player server.

[Tro]

Reinstalling worked for me, this happened to me like 3 times the last 2 weeks.

[olback]

I know I'm in the majority here, but still. The game has been out for a year and they're still breaking it? In the meantime on battlelog they put up a post about how great the patch is and include positive feedback from people who haven't been screwed over by the patch.

Don't get me wrong, I have no problem with the gameplay changes, my problem is not being able to play the game for more than 20 minutes at a time. It sucks crashing in the middle of a match and then having to wait in line to get back into a full 64 player server.

i have the same problem..

[JB780]

Reinstalling worked for me, this happened to me like 3 times the last 2 weeks.

I re-installed a couple days ago. After the 18 hour download (THANKS SHAW!) I still had the same problems.

 

 

i have the same problem..

I feel your pain my friend.

[JB780]

After looking into the event viewer for all my recent crashes it looks like they all have Exception code: 0xc0000005 

 

Doing some searches brings up this: 

Exception code 0xc0000005 is an Access Violation. An AV at fault offset 0x00000000 means that something in your service's code is accessing a nil pointer. You will just have to debug the service while it is running to find out what it is accessing. 

 

I know nothing about programming and don't pretend too, does anyone know if this is legit? And if so WTF?

[JB780]

I'm still working away at trying to fix this. Over the weekend I used DDU to uninstall and remove any remnants of old AMD drivers and then did a clean install of 14.9. I also disabled crossfire. I ran the game and after some time crashed, I checked event viewer and it changed since my previous crashes. I got two seperate events from the crash.

 

First:

 

Faulting application name: bf4.exe, version: 1.3.2.15221, time stamp: 0x541a1598

Faulting module name: bf4.exe, version: 1.3.2.15221, time stamp: 0x541a1598

Exception code: 0xc000001d

Fault offset: 0x000000000001dd40

Faulting process id: 0xb30

Faulting application start time: 0x01cffba5e9ce1c74

Faulting application path: F:\Origin\Battlefield 4\bf4.exe

Faulting module path: F:\Origin\Battlefield 4\bf4.exe

Report Id: 3bb7eb6d-67a7-11e4-805c-d43d7e488c57

Faulting package full name:

Faulting package-relative application ID:

 

The second event:

 

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 4™ because of this error.

Program: Battlefield 4™

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

 

I ran CHKDSK and no errors were found. I've also run the game a few more times and this is the same event that keeps coming up when I crash now.