Battlefront randomly crashes in game every 20 mins or so

Hmmmm, This is my gfx card. I think it's factory over clocked. I've never over clocked any of my hardware. 

http://www.amazon.co.uk/gp/product/B0146YLI24?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00

Ill try the clean install option as I haven't done than. I've been uninstalling and using DDU then express reinstalling.

Will see how this goes.

Thanks!

As you said, your gfx is factory over clocked. I think this kind of over clock is not an issue. And DDU is very similar to "clean install" procedure, in fact, DDU unistall and delete every single piece/trace of gfx. Sorry dude, but i think my suggestions will not help you anyway!

Ahhh lame. 😛 I've just gone through what you've suggested anyway. I'm going to give it ago. 

I've been having same issue and been following the forum. I just recently set my cpu performance to standard instead of performance via ASUS suite II and toggled the gpu boost on my mobo off. So far so good without any crashing.

A few people in Battlefield 4+3 had problems with their pre overclocked graphics cards and this game uses the same type of graphics engine, you might just want to try and underclock your graphics card with like 15% and see if the error occours.

Since Battlefield 3 / 4, the new Frostbite-Engine reacts very, very sensitive to overclocking. Regardless of whether CPU or GPU! So if anybody have trouble with Battlefront, first try do downclock your graphic card to factory standards.

Ok cool. I'll give that a try. Am I correct in thinking I will be able to do this with EVGA PrecisionX 16? My gfx card is Nvidia chip set but EVGA manufactured.

Attached is EVGA PrecisionX 16 screen shot.

Thanks

OK, So my gfx cards gpu clock is currently at 135mhz. take 15% away from that and its 114.75mhz. I just want to clarify before doing this as I don't have a clue when it comes to clock speeds, Things and stuff.

Thanks!

Actually the previous is obviously wrong. 135 is my current GPU clock speed when on idle. 😛 I think I'm going to need some assistance with this.

At "GPU CLOCK OFFSET" slide to all left

At "MEM CLOCK OFFSET" slide to left too (not all left).

Then click APPLY.

Then give game a try!

I think we are barking up the wrong tree here. My machine is a totally different set of hardware to his and we are both having the same issues. My GPU is factory settings.

I think there is a problem with these NVIDIA Drivers and maybe a certain range of cards or a certain build within Windows.

I'm sitting at 60FPS the whole time I get to play and the card is humming nicely at 64 degrees, it can't be the card to blame. Sometimes the game crashes and sometimes I get BSOD.

I've even had it watching movies through Plex. 

SFC is clean. Windows Re-Installed (Keeping Older FIles). Ive installed the NVIDIA drivers and removed them more times than I can imagine... 

I'm out of ideas 🙂

I'm kind of with you on this. Though I'm willing to give this a try because..... well... why not? 

I've made the following changes as shown in the image. 

I've gone down by about 20. Will return with results.

Is nvwgf2umx.dll still crashing? Maybe dll is corrupted. Before doing next step, DON'T FORGET TO BACKUP NVWGF2UMX.DLL IN CASE SOMETHING GOES WRONG (make a copy to your desktop, for example). Try deleting dll from windows/system32 and reinstall vga driver again. If reinstalling vga driver does not put dll back to where is was, use backup you did before to restore that.

I haven't had the Nvidia NVWGF2UMX.DLL crash since yesterday. But that could change.

The last crash I had which was 5 mins ago was due to MSVCR120.dll.

I mostly see these crop up when it crashes.

- NVWGF2UMX.dll

- MSVCR120.dll

- starwarsbattlefront.exe

These all crop up on the "P4" section of the problem signature in the event viewer.

Under clocking it does not fix the issue either. I went down in increments of 10 with no resolve. ☹️

Just crashed again with:

Fault bucket 120365981911, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: starwarsbattlefront.exe
P2: 1.0.4.24147
P3: 564dcc69
P4: starwarsbattlefront.exe
P5: 1.0.4.24147
P6: 564dcc69
P7: c0000005
P8: 0000000003f67b40
P9: 
P10: 

Attached files:
C:\Users\AutoLiMax\AppData\Local\Temp\WERB23B.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_starwarsbattlefr_ce4a5277a6c4f5a34bef4a8e759b3c544123f31_2b272c15_1cd6bc0e

Analysis symbol: 
Rechecking for solution: 0
Report Id: a6ab4dc8-447e-44f9-8293-b6f1f90f122b
Report Status: 1
Hashed bucket: 18454b752835bf3bef3f76ec4a4d5790

This time starwarsbattlefront.exe is the cause. So the event viewer says. And this is the case for the past 3 crashes.

I haven't received the nvidia NVWGF2UMX.dll crash today. Which maybe due to under clocking my gpu, Though I haven't tested extensively so I do not know for sure.

I am not shure, but MSVCR120.dll belongs to VCREDIST (Microsoft Visual C++). There is a subdirectory with those libraries inside Star Wars Battlefront. Install them again.

ok, I've unistalled the reinstalled VCREDIST in the bf redist folder. I'm going to try again play again after work. See what goes down.

Thanks

Just seen this;

https://forums.geforce.com/default/topic/900924/geforce-drivers/geforce-hotfix-driver-359-12-for-geforce-860m-notebook-gpus-released-12-2-15-/1/

Nvidia published a fix to our problem but not for my card or yours but at least they are aware and we can probably say that the driver is definitely to blame!!

So turns out the driver supports all notebook cards;

I installed using DDU in Safemode to remove then install excluding the 3D Vision driver as so many recommended.

http://nvidia.custhelp.com/app/answers/detail/a_id/3812

Ran SW: Battlefront and got 2 crashes in first 20 mins of play, no blue screen though which is slight progress.

Ok, So I've made a post on the Nvidia forums linking to these forums. Hopefully something will come of this.

https://forums.geforce.com/default/topic/902335/geforce-drivers/gtx-950-crashing-on-battlefront-every-20-mins/

Also going to mention that I've been in contact with EA who have pretty much said I've tried everything that they would have already suggested so go and talk to Nvidia about the issue.

As well as the above post I'm going to go in live chat to see what they say. Will post the outcome.

Hey buddy, I feel for ya. This is very frustrating, so I haven't read all the posts, but from those I read I didn't see anyone post this. Sorry if this is a repeated step, just trying to help you too.

Start up command promt with admin privileges and write the following.

sfc /scannow (this might take a while, but let it go through, usually takes 30 or so minutes)

DISM.exe /Online /Cleanup-image /Scanhealth (after the scan hit this in, note the spaces, let it finish)

DISM.exe /Online /Cleanup-image /Restorehealth (once the previous command has finished, type this afterwards)

Then I would suggest you restart your computer and hope for the best.

I too hope this works out for you or it does something that might bring you closer to a solution.

Sorry once again if this has already been posted.

Good luck!!

- Dave

Right peoples. I have just come off live chat with Nvidia. It is a known bug that EA have reported to Nvidia and they are working on getting it sorted. Now I'm not sure if this is the truth because EA would have said something when I was in live chat with them. So if it is the truth then yay, it's being looked in to. If it's not the truth then he didn't have a clue about fixing the issue and was fobbing it off because he couldn't be bothered to look in to it.

Though saying that one of the previous posts mentions a hot fix for another Nvidia GPU so there's a chance it is the truth. Who knows?

All I know is when I was first line and it was the end of my shift, saying "It's a known issue and it's being looked in to" was the easiest way to get out of doing something you really cba to do at that time. 

I did ask for details of the bug in which he replied "It's confidential" which is strange because it is a piece of hardware I own, so surely I have the right to know what's going wrong with it? I don't know the rules so there you go.

I also asked if there's an ETA on when they are looking to get it sorted. "No" This is a weird one because surely different impacts have different severity's which surely must have some sort of aim to be fixed by time? And again I do not know the rules or the infrastructure of how they work so speculating is only making me think of more questions.... which does not help the issue at hand.

Long story short: It's a known bug and it's being looked in to. No ETA and no other information.

I guess we will just have to wait.

Don't hate...... because we all know where that leads.

Hi Dave, I've done sfc /scannow but I have not done the steps following. The previous post states I have spoken to Nvidia about the issue and that they are looking in to it. But trying what you've suggested is worth it if I can get a couple hours of game play out of it.

Thanks