(SOLUTION)How to Fix BFV Crash on PC. Like no error, just takes you to desktop *atleast works for me

Battlefield V PC
41

I got this random crash with no error a few times since the latest patch and update. I get it randomly when I’m not expecting it but it’s rare more than anything.

I reckon it’s to do with the game interacting with Windows 10 probably RAM related. I have as much stuff in Windows 10 disabled or turned off (Game Mode, Telemetry, etc). Anyone know where the BF5 client logs are so I can understand what’s causing these random crashes?

I also get client freezes in game, randomly for about half a second. Not sure what is causing this. I suspect it is to do with Standby RAM usage in Windows 10 but again, it’s difficult to prove it.

42
43

I finally found a fix for my specific PC.

For some reason my i5-9600k doesn’t like 4.6Ghz, this caused numerous stability issues so I locked the max frequency via the BIOS to 4.5Ghz, never had these crashes again. I have no idea why but yeah, it’s working so far. Took me about a week of numerous tests and solutions to figure this one out. Weird. Hope this helps?

44

can only be solved from DICE , u got no way to solved it in most case/bug we are encountering currently, like game crash, it’s not raised from the game or PC, i tested from last bFV updates,but it raised from origin updated

45

Hey all,

I’ve been having the exact same issue as all of you with good hardware.
I’ve just managed to fix it for myself it seems:

Set your GPU clock to Nvidia’s reference clocks. For example the Aorus GTX1080Ti should be set to 1582MHZ Boost Clock and 11008MHZ Memory Clock. For me, even with these set in my GPU GUI it still goes over these limits. It seems to have stopped BF5 from crashing.
I’m still using DX11 and have the hardware restrictions to off.

46

It seems like the issue is that the second the GPU usage even skims 100% BF5 crashes. Looked a lot at the data and tweaked it slightly above the reference clocks to sit at around 80-90% usage. Quite lame if you ask me and a bit of a shame. Would like to know if anyone has the same experience, so the EA peeps can look into it and hopefully fix it for everyone.

47

Hmmm…interesting. I experienced that crash last night. When i ready to play the third round of mp conquest, suddenly close and return to desktop without any notification.
Thanks for sharing the solution

48

What worked for me was putting settings to ultra and resolution scale to 120 I do have a high end pc but this fixed my crashing problem Just put your settings up as higher as resolution up higher

49

With the same display size as monitor?
I am running 3440x1440 @ 120Hz

50

I play 2 k 165 MHz monitor etc 2080 ti i9900k 32 g ram no what I mean is the resolution scale to 120 in the video settings in bfv settings definitely works for me

51

Please help !!!

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\MrRobot\Documents\Battlefield V\crash_dumps\CrashDump_2019.06.29_22.06.27.386.mdmp]
Comment: ‘Frostbite MiniDump. Address: 00007FFCBE535299 (In Windbg type: .ecxr)
[EOF]’
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Version 17763 MP (16 procs) Free x64
Product: WinNt, suite: SingleUserTS
17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Debug session time: Sat Jun 29 22:06:27.000 2019 (UTC - 7:00)
System Uptime: not available
Process Uptime: 0 days 0:07:29.000
…
…
…
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(1474.750): Unknown exception - code 887a0005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007ffc`c22d0304 c3 ret
0:014> !analyze -v

*** Exception Analysis ***

WARNING: Unable to verify timestamp for igo64.dll
*** WARNING: Unable to verify timestamp for nvwgf2umx.dll

KEY_VALUES_STRING: 1

Key : Timeline.Process.Start.DeltaSec
Value: 449

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start
Name:
Time: 2019-06-30T09:39:55.686Z
Diff: 16408686 mSec

Timeline: Dump.Current
Name:
Time: 2019-06-30T05:06:27.0Z
Diff: 0 mSec

Timeline: Process.Start
Name:
Time: 2019-06-30T04:58:58.0Z
Diff: 449000 mSec

DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT: (.ecxr)
rax=dfdfdfdfdfdfdfdf rbx=0000000038027410 rcx=dfdfdfdfdfdfdfdf
rdx=dfdfdfdfdfdfdfdf rsi=00000000887a0005 rdi=00000000347beab8
rip=00007ffcbe535299 rsp=00000000347be100 rbp=00000000347be2e0
r8=dfdfdfdfdfdfdfdf r9=dfdfdfdfdfdfdfdf r10=dfdfdfdfdfdfdfdf
r11=dfdfdfdfdfdfdfdf r12=0000000143b3ced0 r13=00000000000003ff
r14=00000000380263e0 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0033 =002b ds=002b es=002b fs=0053 gs=002b efl=00000206
KERNELBASE!RaiseException+0x69:
00007ffc`be535299 0f1f440000 nop dword ptr [rax+rax]
Resetting default scope

FAULTING_IP:
KERNELBASE!RaiseException+69
00007ffc`be535299 0f1f440000 nop dword ptr [rax+rax]

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffcbe535299 (KERNELBASE!RaiseException+0x0000000000000069)
ExceptionCode: 887a0005
ExceptionFlags: 00000000
NumberParameters: 0

DEFAULT_BUCKET_ID: APPLICATION_FAULT

PROCESS_NAME: bfv.exe

ERROR_CODE: (NTSTATUS) 0x887a0005 - The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.

EXCEPTION_CODE: (HRESULT) 0x887a0005 (2289696773) - The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.

EXCEPTION_CODE_STR: 887a0005

WATSON_BKT_PROCSTAMP: 5d080454

WATSON_BKT_PROCVER: 1.0.74.11040

PROCESS_VER_PRODUCT: Battlefield™ V

WATSON_BKT_MODULE: KERNELBASE.dll

WATSON_BKT_MODSTAMP: c3164c39

WATSON_BKT_MODOFFSET: 55299

WATSON_BKT_MODVER: 6.2.17763.1

MODULE_VER_PRODUCT: Microsoft® Windows® Operating System

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

MODLIST_WITH_TSCHKSUM_HASH: 888b6af2b4f3e7b3b92169cceaae77de22df2ec9

MODLIST_SHA1_HASH: 3d0d9a69db4488568d609db580d82e5da6b111dd

COMMENT: Frostbite MiniDump. Address: 00007FFCBE535299 (In Windbg type: .ecxr)
[EOF]

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

DUMP_FLAGS: a2

DUMP_TYPE: 11

ANALYSIS_SESSION_HOST: DESKTOP-FM08AAQ

ANALYSIS_SESSION_TIME: 06-30-2019 02:39:55.0686

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

THREAD_ATTRIBUTES:
OS_LOCALE: ENU

BUGCHECK_STR: APPLICATION_FAULT

PRIMARY_PROBLEM_CLASS: APPLICATION_FAULT

PROBLEM_CLASSES:

ID: [0n320]
Type: [APPLICATION_FAULT]
Class: Primary
Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
BUCKET_ID
Name: Add
Data: Omit
PID: [Unspecified]
TID: [Unspecified]
Frame: [0]

LAST_CONTROL_TRANSFER: from 0000000141f138a3 to 00007ffcbe535299

STACK_TEXT:
00000000347be100 0000000141f138a3 : 000000002af2f488 0000000038027410 00000000887a0005 00000000303048b0 : KERNELBASE!RaiseException+0x69
00000000347be1e0 000000014a7753bc : 00000000380353f0 00000000380353f0 00000000380353f0 0000003000000000 : bfv!fb::TwinkleJSBundleManager::getFailedVersion+0x3645f3
00000000347bf3c0 00000001422b886e : 0000000030b5f468 0000000000000000 0000000000000120 000000001bf1dd60 : bfv!fb::ScriptEngineAllocator::realloc+0xeaaec
00000000347bf520 0000000145e88f58 : 0000000100000000 0000000000000018 00000000380353f0 00000000380353f0 : bfv!fb::ScriptEngineAllocator::getMallocAllocatorName+0x9a14e
00000000347bf560 0000000145e8873f : 00000001270fbca8 00000000347bf679 00000000fdea0a70 0000000000000000 : bfv!fb::JsObject::setScriptObject+0x64b68
00000000347bf5b0 0000000000000000 : 00000001270fbca8 00000000347bf679 00000000fdea0a70 0000000000000000 : bfv!fb::JsObject::setScriptObject+0x6434f

THREAD_SHA1_HASH_MOD_FUNC: a7b18d79d216d2b2cde3604d340192318b466ad8

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 24eda7304232dd2358be29c53e53f3e2bf8a9a9d

THREAD_SHA1_HASH_MOD: 1ffc373d331743ecd185846907abab412ac9a3c3

FOLLOWUP_IP:
bfv!fb::TwinkleJSBundleManager::getFailedVersion+3645f3
0000000141f138a3 7a6f jp bfv!fb::TwinkleJSBundleManager::getFailedVersion+0x364664 (0000000141f13914)

FAULT_INSTR_CODE: 19206f7a

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: bfv!fb::TwinkleJSBundleManager::getFailedVersion+3645f3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bfv

IMAGE_NAME: bfv.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5d080454

STACK_COMMAND: ~14s ; .ecxr ; kb

FAILURE_BUCKET_ID: APPLICATION_FAULT_887a0005_bfv.exe!fb::TwinkleJSBundleManager::getFailedVersion

BUCKET_ID: APPLICATION_FAULT_bfv!fb::TwinkleJSBundleManager::getFailedVersion+3645f3

FAILURE_EXCEPTION_CODE: 887a0005

FAILURE_IMAGE_NAME: bfv.exe

BUCKET_ID_IMAGE_STR: bfv.exe

FAILURE_MODULE_NAME: bfv

BUCKET_ID_MODULE_STR: bfv

FAILURE_FUNCTION_NAME: fb::TwinkleJSBundleManager::getFailedVersion

BUCKET_ID_FUNCTION_STR: fb::TwinkleJSBundleManager::getFailedVersion

BUCKET_ID_OFFSET: 3645f3

BUCKET_ID_MODTIMEDATESTAMP: 5d080454

BUCKET_ID_MODCHECKSUM: ed28dc8

BUCKET_ID_MODVER_STR: 1.0.74.11040

BUCKET_ID_PREFIX_STR: APPLICATION_FAULT_

FAILURE_PROBLEM_CLASS: APPLICATION_FAULT

FAILURE_SYMBOL_NAME: bfv.exe!fb::TwinkleJSBundleManager::getFailedVersion

WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/bfv.exe/1.0.74.11040/5d080454/KERNELBASE.dll/6.2.17763.1/c3164c39/887a0005/00055299.htm?Retriage=1

TARGET_TIME: 2019-06-30T05:06:27.000Z

OSBUILD: 17763

OSSERVICEPACK: 1

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 256

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt SingleUserTS

USER_LCID: 0

OSBUILD_TIMESTAMP: 2023-11-24 17:28:01

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 4200b

ANALYSIS_SOURCE: UM

FAILURE_ID_HASH_STRING: um:application_fault_887a0005_bfv.exe!fb::twinklejsbundlemanager::getfailedversion

FAILURE_ID_HASH: {a0b6be02-5327-11f8-b064-0ace3cb906a9}

Link to section: Followup: MachineOwnerFollowup: MachineOwner

52

believe i know computers and this crash is not normal… is not hardware related…

53

This thread was made at launch when loads of people were crashing and having BSODs.

Last Tuesday, a patch came that made sure that this thread has become relevant again as the SAME BLOODY THING is happening YET AGAIN.

54

Take it eas&, just trying to get some help that’s all!

55

On Sun 6/30/2019 1:54:42 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20190630-0154.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF802587DD9B0)
Bugcheck code: 0x193 (0x804, 0xFFFFFFFFC01E0009, 0x308, 0xFFFFF802587DD9B0)
Error: VIDEO_DXGKRNL_LIVEDUMP
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e2b434c15f781143\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 431.18
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 431.18
Bug check description: A livedump triggered by dxgkrnl occurred. You may have problems with your graphics driver or hardware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 431.18 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_DXGKRNL_LIVEDUMP

56

Chiming in on this problem also. Started since the mid june patch. I’m able to play an hour then it crashes.

How do you @Pcidemocon view your crash dumpfiles?

57

After the early july update my bfv after opening it for a few seconds it will work then it crashed,no error.To fix it,in my case i went to origin,clicked on my library,clicked bfv,and right next to play button theres a settings button,click it and youll have the option to repair the game.It doesnt take much,about 5 minutes,if this doesnt work then idk

58

Microsoft debugging tool .

59

Well I too have just had a CTD with no error message. I have to be honest and say I’m yet to have one single crash with BF5. This is the first. I very much doubt it’s hardware related, more like a bug that’s been brought in. Any news on a fix or is this something else DICE will just ignore :wink:

60

the same for me today :frowning: I had no crach since many weeks (even with a computer overclocked)
and today , one CTD , without any message , even in windows event viewer.
I know when it s hardware related , u find message in event viewer (WHEA error , Driver diplay has crashed etc etc..)
But when there s no message , I think it s only a bug of the game.

Now I play since 3 hours without any problem ( even with overclocked computer)