Battlefield 4 has stopped working

by F1erZ
Reply

Original Post

Battlefield 4 has stopped working

[ Edited ]
★ Novice

Will get this error after 5-7 minutes of gameplay. Have tried to downgrade drivers. Did work for 1 hour with 331.40 but now same problem.

 

Have updated punkbuster, directx and many more stuff.

 

But still the game is crashing about 2-7 minutes.

 

Here is the event viewer if that helps?

 

Faulting application name: bf4.exe, version: 1.0.0.0, time stamp: 0x52668dcb
Faulting module name: bf4.exe, version: 1.0.0.0, time stamp: 0x52668dcb
Exception code: 0xc0000005
Fault offset: 0x0000000000b17f5b
Faulting process ID: 0x8c8
Faulting application start time: 0x01ced416fed61b6d
Faulting application path: D:\Program Files (x86)\Origin Games\Battlefield 4\bf4.exe
Faulting module path: D:\Program Files (x86)\Origin Games\Battlefield 4\bf4.exe
Report ID: 25ba280f-400b-11e3-be86-d43d7e32225e
Faulting package full name:
Faulting package-relative application ID:

 

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

Problem signature:
P1: bf4.exe
P2: 1.0.0.0
P3: 52668dcb
P4: bf4.exe
P5: 1.0.0.0
P6: 52668dcb
P7: c0000005
P8: 0000000000b17f5b
P9:
P10:

Attached files:
C:\Users\Johan\AppData\Local\Temp\WERA6C7.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_bf4.exe_a1c346e57674c6ee71ae18e44c511199d49fa_e718be99_08addf5c

Analysis symbol:
Rechecking for solution: 0
Report ID: 25ba280f-400b-11e3-be86-d43d7e32225e
Report Status: 0
Hashed bucket: 145f80ea66702c3de3bd9f0dc1db140c

 

Message 1 of 21 (3,951 Views)

Re: Battlefield 4 has stopped working

[ Edited ]
★★★ Newbie

I get this same exact issue.  Runs fine for 2-7 minutes and then it stops working.  I'm running the lastest BETA version of my AMD driver as of 10/25.  I actually took the time to reformat and reinstall everything fresh on my gaming machine to avoid issues.  BF3 was running fine last night but BF4 crashes consistently.

 

Adding my App Launcher details:

 

Description
Faulting Application Path: C:\Program Files (x86)\Origin Games\Battlefield 4\bf4.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: bf4.exe
Application Version: 1.0.0.0
Application Timestamp: 52668dcb
Fault Module Name: bf4.exe
Fault Module Version: 1.0.0.0
Fault Module Timestamp: 52668dcb
Exception Code: c0000005
Exception Offset: 0000000000b17f5b
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 4502
Additional Information 2: 4502f2508e1e8ee8c6fafa2879648263
Additional Information 3: f7c1
Additional Information 4: f7c15348a9a6d434280ee03f6780a412

Message 2 of 21 (3,841 Views)

Re: Battlefield 4 has stopped working

★★★ Newbie

So I waited in line last night for 40 minutes to speak to a live chat person only to be told I should use the "Call Me" option...  Going to try that this evening and see what happens.  I'll post an update to this thread if they help me address the problem.

Message 3 of 21 (3,751 Views)

Crash to desktop in BF4 within minutes

[ Edited ]
★★★ Novice

I'm getting crashes in BF4 with 4 different version of graphics drivers and reinstalling DirectX many times. I can never stay in the game for more than 5 or 10 minutes before the issue is presented. I have tried:

 

Latest WHQL and 3 versions back (clean install each time)

Both with SLI enabled and with it Disabled on each driver version. 

Windowed and FullScreen on each driver version. 

 

No matter what, I get this EXACT exception. 

 

I can run any other games for hours, from FarCry to Blops II, and from Just Cause 2 to anything else and they all work flawlessly without any issues. I was in the BF4 BETA but was never able to play because it would constantly crash to desktop. That's right, I didn't get to play AT ALL because it crashed constantly. I figure all would work out as people would address these kinds of crashes before the game came out. Nope!

 

I can stress test and benchmark my CPU and GPU all day long without a single issue as well.  BF4 is the ONLY game that I have an issue with. 

 

DXDiag Output: http://cl.ly/SDLf

 

I enabled user-mode dumps and the trace is always the same. The fault appears to be in the opus_decoder if the frames are to be believed. I have the whole dump (1.7 GB) if it would help someone see what is happening here I can upload it: (it removed some "html" from the output of WinDBG, so things might be out of place, but the analysis is still there)

 

Event Viewer throws two events (one from WER and one generic Application Failure):

 

1.)

Faulting application name: bf4.exe, version: 1.0.0.0, time stamp: 0x52668dcb
Faulting module name: bf4.exe, version: 1.0.0.0, time stamp: 0x52668dcb
Exception code: 0xc0000005
Fault offset: 0x0000000000b17f5b
Faulting process id: 0x31e4
Faulting application start time: 0x01ced4d7e39d125f
Faulting application path: C:\Program Files (x86)\Origin Games\Battlefield 4\bf4.exe
Faulting module path: C:\Program Files (x86)\Origin Games\Battlefield 4\bf4.exe
Report Id: 29effe1d-40cc-11e3-befc-60a44ca93716
Faulting package full name:
Faulting package-relative application ID:

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

 

2.)

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

Problem signature:
P1: bf4.exe
P2: 1.0.0.0
P3: 52668dcb
P4: bf4.exe
P5: 1.0.0.0
P6: 52668dcb
P7: c0000005
P8: 0000000000b17f5b
P9:
P10:

Attached files:
C:\Users\Paronity\AppData\Local\Temp\WERA72F.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Paronity\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_bf4.exe_a1c346e57674c6ee71ae18e44c511199d49fa_360bd8bf

Analysis symbol:
Rechecking for solution: 0
Report Id: 29effe1d-40cc-11e3-befc-60a44ca93716
Report Status: 0
Hashed bucket: 145f80ea66702c3de3bd9f0dc1db140c

 =====END OF EVENTS THROWN=====

 

 

Contents from the WER file listed above:

Version=1
EventType=APPCRASH
EventTime=130275467382557097
ReportType=2
Consent=1
UploadTime=130275467398433187
ReportIdentifier=29effe1e-40cc-11e3-befc-60a44ca93716
IntegratorReportIdentifier=29effe1d-40cc-11e3-befc-60a44ca93716
NsAppName=bf4.exe
Response.BucketId=145f80ea66702c3de3bd9f0dc1db140c
Response.BucketTable=4
Response.LegacyBucketId=138547795
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=bf4.exe
Sig[1].Name=Application Version
Sig[1].Value=1.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=52668dcb
Sig[3].Name=Fault Module Name
Sig[3].Value=bf4.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=1.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=52668dcb
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0000000000b17f5b
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.2.9200.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=08a6
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=08a675e6bb88cc949ac8af35291f63e0
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=b05e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=b05ebc22c93a6d36891b0bf259e53e55
UI[2]=C:\Program Files (x86)\Origin Games\Battlefield 4\bf4.exe
UI[3]=Battlefield 4™ has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\Origin Games\Battlefield 4\bf4.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\system32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\system32\KERNELBASE.dll
LoadedModule[4]=C:\Program Files (x86)\Origin Games\Battlefield 4\Core\Activation64.dll
LoadedModule[5]=C:\WINDOWS\system32\WS2_32.dll
LoadedModule[6]=C:\WINDOWS\SYSTEM32\WINHTTP.dll
LoadedModule[7]=C:\WINDOWS\system32\PSAPI.DLL
LoadedModule[8]=C:\WINDOWS\system32\USER32.dll
LoadedModule[9]=C:\WINDOWS\system32\ADVAPI32.dll
LoadedModule[10]=C:\WINDOWS\system32\SHELL32.dll
LoadedModule[11]=C:\WINDOWS\system32\ole32.dll
LoadedModule[12]=C:\WINDOWS\system32\OLEAUT32.dll
LoadedModule[13]=C:\WINDOWS\system32\SHLWAPI.dll
LoadedModule[14]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[15]=C:\WINDOWS\system32\RPCRT4.dll
LoadedModule[16]=C:\WINDOWS\system32\NSI.dll
LoadedModule[17]=C:\WINDOWS\system32\msvcrt.dll
LoadedModule[18]=C:\WINDOWS\SYSTEM32\combase.dll
LoadedModule[19]=C:\WINDOWS\SYSTEM32\sechost.dll
LoadedModule[20]=C:\WINDOWS\system32\GDI32.dll
LoadedModule[21]=C:\WINDOWS\SYSTEM32\WINNSI.DLL
LoadedModule[22]=C:\WINDOWS\system32\IMM32.DLL
LoadedModule[23]=C:\WINDOWS\system32\MSCTF.dll
LoadedModule[24]=C:\WINDOWS\system32\nvinitx.dll
LoadedModule[25]=C:\Program Files (x86)\Origin\igo64.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\MSVCR100.dll
LoadedModule[27]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[28]=C:\WINDOWS\system32\apphelp.dll
LoadedModule[29]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[30]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\cfgmgr32.dll
LoadedModule[32]=C:\WINDOWS\system32\DEVOBJ.dll
LoadedModule[33]=C:\WINDOWS\system32\urlmon.dll
LoadedModule[34]=C:\WINDOWS\system32\iertutil.dll
LoadedModule[35]=C:\WINDOWS\system32\WININET.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\MSVCP110.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\MSVCR110.dll
LoadedModule[39]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\DINPUT8.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[42]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[43]=C:\WINDOWS\SYSTEM32\d3d11.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\DSOUND.dll
LoadedModule[45]=C:\WINDOWS\SYSTEM32\POWRPROF.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\XINPUT9_1_0.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\dbghelp.dll
LoadedModule[48]=C:\WINDOWS\SYSTEM32\WSOCK32.dll
LoadedModule[49]=C:\WINDOWS\system32\USP10.dll
LoadedModule[50]=C:\WINDOWS\system32\bcryptprimitives.dll
LoadedModule[51]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[52]=C:\Program Files (x86)\Stardock\Start8\Start8_64.dll
LoadedModule[53]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[54]=C:\WINDOWS\SYSTEM32\shcore.dll
LoadedModule[55]=C:\Program Files (x86)\Origin Games\Battlefield 4\Engine.BuildInfo_Win64_retail.dll
LoadedModule[56]=C:\WINDOWS\SYSTEM32\profapi.dll
LoadedModule[57]=C:\WINDOWS\SYSTEM32\DXGIDebug.dll
LoadedModule[58]=C:\WINDOWS\SYSTEM32\nvapi64.dll
LoadedModule[59]=C:\WINDOWS\system32\SETUPAPI.dll
LoadedModule[60]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[61]=C:\WINDOWS\SYSTEM32\WINSTA.dll
LoadedModule[62]=C:\WINDOWS\SYSTEM32\HID.DLL
LoadedModule[63]=C:\WINDOWS\system32\WINTRUST.dll
LoadedModule[64]=C:\WINDOWS\system32\CRYPT32.dll
LoadedModule[65]=C:\WINDOWS\system32\MSASN1.dll
LoadedModule[66]=C:\WINDOWS\system32\nvspcap64.dll
LoadedModule[67]=C:\WINDOWS\SYSTEM32\nvwgf2umx.dll
LoadedModule[68]=C:\WINDOWS\system32\mswsock.dll
LoadedModule[69]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[70]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[71]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[72]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[73]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[74]=C:\WINDOWS\SYSTEM32\clbcatq.dll
LoadedModule[75]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[76]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
LoadedModule[77]=C:\WINDOWS\SYSTEM32\avrt.dll
LoadedModule[78]=C:\WINDOWS\SYSTEM32\wdmaud.drv
LoadedModule[79]=C:\WINDOWS\SYSTEM32\ksuser.dll
LoadedModule[80]=C:\WINDOWS\SYSTEM32\msacm32.drv
LoadedModule[81]=C:\WINDOWS\SYSTEM32\MSACM32.dll
LoadedModule[82]=C:\WINDOWS\SYSTEM32\midimap.dll
LoadedModule[83]=C:\WINDOWS\system32\NLAapi.dll
LoadedModule[84]=C:\WINDOWS\system32\napinsp.dll
LoadedModule[85]=C:\WINDOWS\system32\pnrpnsp.dll
LoadedModule[86]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule[87]=C:\WINDOWS\System32\winrnr.dll
LoadedModule[88]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[89]=C:\Windows\System32\rasadhlp.dll
LoadedModule[90]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[91]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
LoadedModule[92]=C:\Program Files (x86)\Origin Games\Battlefield 4\EAWebKit64.dll
LoadedModule[93]=C:\Program Files (x86)\Origin Games\Battlefield 4\pb\pbcl.d64
LoadedModule[94]=C:\Users\Paronity\AppData\Local\PunkBuster\BF4\pb\pbag.d64
LoadedModule[95]=C:\WINDOWS\SYSTEM32\d3d9.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Battlefield 4™
AppPath=C:\Program Files (x86)\Origin Games\Battlefield 4\bf4.exe
NsPartner=windows
NsGroup=windows8

======END of WER File=====

 

Since these errors are generic, I decided to take a look at the user-mode dump which gave the below details:

 

WinDBG Analysis:

FAULTING_IP: 

bf4!opus_decoder_destroy+4a4bdb
00000001`40b17f5b c0660f70 shl byte ptr [rsi+0Fh],70h

EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000140b17f5b (bf4!opus_decoder_destroy+0x00000000004a4bdb)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000010
Attempt to write to address 0000000000000010

PROCESS_NAME: bf4.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000010

WRITE_ADDRESS: 0000000000000010

FOLLOWUP_IP:
bf4!opus_decoder_destroy+4a4bdb
00000001`40b17f5b c0660f70 shl byte ptr [rsi+0Fh],70h

MOD_LIST: <ANALYSIS/>

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

FAULTING_THREAD: 0000000000003170

BUGCHECK_STR: APPLICATION_FAULT_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_WRITE

PRIMARY_PROBLEM_CLASS: NULL_CLASS_PTR_DEREFERENCE

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from 0000000140b18339 to 0000000140b17f5b

STACK_TEXT:
00000000`4b2cfa60 00000001`40b18339 : 00000000`a1217c80 00000000`00000000 00000000`42aa0000 00000000`42aa6cc0 : bf4!opus_decoder_destroy+0x4a4bdb
00000000`4b2cfbd0 00000001`40c39959 : 00000000`c5ea01e0 00000000`0000d789 00000000`c5e9ec30 00000001`40c3a89f : bf4!opus_decoder_destroy+0x4a4fb9
00000000`4b2cfd10 00000001`40c38d03 : 00000000`c5d58780 00000000`3f000b9a 00000000`00000000 00000000`3f000b9a : bf4!opus_decoder_destroy+0x5c65d9
00000000`4b2cfd50 00000001`40c3a027 : 00000000`c5d58780 00000000`42aa0320 00000000`42aa5230 00000000`42aa5230 : bf4!opus_decoder_destroy+0x5c5983
00000000`4b2cfda0 00000001`40c399aa : 00000000`00000000 00000000`00000000 0000a80d`00000000 00000000`00000000 : bf4!opus_decoder_destroy+0x5c6ca7
00000000`4b2cfe70 00000001`40670a8e : 00000001`42355cc0 00000000`42aa6e70 00000000`00000103 00000000`4aa69460 : bf4!opus_decoder_destroy+0x5c662a
00000000`4b2cfea0 000007fb`3d9a3fef : 00000001`42355cc0 00000000`42aa6e70 00000000`00000000 00000000`00000000 : bf4+0x670a8e
00000000`4b2cff00 000007fb`3d9a4196 : 000007fb`3da41db0 00000000`00000000 00000000`00000000 00000000`00000000 : msvcr110!beginthreadex+0x107
00000000`4b2cff30 000007fb`70541832 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msvcr110!endthreadex+0x192
00000000`4b2cff60 000007fb`70d6d609 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a
00000000`4b2cff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d


STACK_COMMAND: ~6s; .ecxr ; kb

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: bf4!opus_decoder_destroy+4a4bdb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bf4

IMAGE_NAME: bf4.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 52668dcb

FAILURE_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE_c0000005_bf4.exe!opus_decoder_destroy

BUCKET_ID: X64_APPLICATION_FAULT_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_WRITE_bf4!opus_decoder_destroy+4a4bdb

WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/bf4_exe/1_0_0_0/52668dcb/bf4_exe/1_0_0_0/52668dcb/c0000005/00b1...

Followup: MachineOwner

 =====END OF WINDBG ANAYLSIS=====

Message 4 of 21 (6,822 Views)

Re: Crash to desktop in BF4

★★★★★ Novice

I have the same problem.

Message 5 of 21 (6,743 Views)

Re: Crash to desktop in BF4 within minutes

★★★★★ Novice

Unfortunately same happens to me. Random game crashes to desktop and/or getting time out of the servers... Even singleplayer crashes. And that doesn't happen only to a few people. I was watching a stream with like 6-7 guys on teamspeak and every like 20-30 minutes one or more of em were getting random game crashes. Even the streamer himself got 2 crashes in a short period of time.

Message 6 of 21 (6,717 Views)

Battlefield 4 has stopped working

★ Novice

First, I had the annoying Direct X error telling me my driver was crashing, I use the latest nvidia driver not beta, official driver 

now when I play around, 20-30min my game crash, battlefield 4 has stoped working, anyone have this issue or fixed it?

 

Re-installed PB didnt work either.. ugh I just wanna play..

Message 7 of 21 (3,744 Views)

Re: Battlefield 4 has stopped working

★ Novice

Since this has been pushed way back and I think its need to be addresed, bump

Message 8 of 21 (3,706 Views)

Re: Battlefield 4 has stopped working

[ Edited ]
★★ Apprentice

First I had the DirectX issue, then PB compatibility client/server issues, and now after 20-30 mins, I get this bad error. It just crashes to desktop saying "Battlefield has stopped working".

 

My EventViewer:

Faulting application name: bf4.exe, version: 1.0.0.0, time stamp: 0x52668dcb
Faulting module name: bf4.exe, version: 1.0.0.0, time stamp: 0x52668dcb
Exception code: 0xc0000005
Fault offset: 0x0000000000089bc7
Faulting process id: 0xcc8
Faulting application start time: 0x01ced56a2e3ec000
Faulting application path: C:\Program Files (x86)\Origin Games\Battlefield 4\bf4.exe
Faulting module path: C:\Program Files (x86)\Origin Games\Battlefield 4\bf4.exe
Report Id: 9d4373e2-415e-11e3-bf33-10bf48bd0706
Faulting package full name:
Faulting package-relative application ID:

 

Temps are fine, around 60...I will underclock the GPU by 15% to see if it helps...

 

We're getting there ever so slowly...

Message 9 of 21 (3,693 Views)

Re: Crash to desktop in BF4 within minutes

★★ Novice

Same problem here:

 

Faulting application name: bf4.exe, version: 1.0.0.0, time stamp: 0x52668dcb
Faulting module name: nvwgf2umx.dll, version: 9.18.13.3165, time stamp: 0x52676b0b
Exception code: 0xc0000005
Fault offset: 0x0000000000338e98
Faulting process id: 0x1460
Faulting application start time: 0x01ced5bc9743cc2d
Faulting application path: E:\Program Files\Origin Games\Battlefield 4\bf4.exe
Faulting module path: C:\Windows\system32\nvwgf2umx.dll
Report Id: 3d429d9b-41b1-11e3-a175-30469a97fc33

 

Could nvwgf2umx.dll be to blame/Can we replace it/I really want to play for more than 20 mins.

 

Bump 

Message 10 of 21 (6,145 Views)