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

wildbam · July 30, 2019, 5:00pm

heheh check for dump files

C:\Users...\Documents\Battlefield V\crash_dumps

then you can run “!analyze -v” like @Pcidemocon did

for me it looks like my broken RAM is just causing this suddenly I had no issues at all until the 3. of may.. I dont know what kind of patch was released back then.. maybe this helps the devs to catch the exception:

Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64

Loading Dump File [C:\Users.…\Documents\Battlefield V\crash_dumps\CrashDump_2019.07.30_18.28.44.597.mdmp]

Comment: 'Frostbite MiniDump. Address: 0000000145C2FBFE (In Windbg type: .ecxr)

[EOF]’

User Mini Dump File: Only registers, stack and portions of memory are available

Path validation summary

Response Time (ms) Location

Deferred SRV…\windows software dev kit\SymCache*http://msdl.microsoft.com/download/symbols*

Symbol search path is: SRV…\windows software dev kit\SymCache*http://msdl.microsoft.com/download/symbols*

Executable search path is:

Windows 10 Version 17763 MP (8 procs) Free x64

Product: WinNt, suite: SingleUserTS

17763.1.amd64fre.rs5_release.180914-1434

Machine Name:

Debug session time: Tue Jul 30 18:28:44.000 2019 (UTC + 2:00)

System Uptime: not available

Process Uptime: 0 days 0:19:44.000

…

This dump file has an exception of interest stored in it.

The stored exception information can be accessed via .ecxr.

(1b1c.3eac): Access violation - code c0000005 (first/second chance not available)

ntdll!NtGetContextThread+0x14:

00007ff8`dcad0304 c3 ret

0:024> !analyze -v

Exception Analysis *

ERROR: Symbol file could not be found. Defaulted to export symbols for nvwgf2umx.dll -

ERROR: Module load completed but symbols could not be loaded for dbdata.dll

*** ERROR: Symbol file could not be found. Defaulted to export symbols for igo64.dll -**

ERROR: Symbol file could not be found. Defaulted to export symbols for poco.dll -

*** ERROR: Symbol file could not be found. Defaulted to export symbols for MessageBus.dll -**

ERROR: Symbol file could not be found. Defaulted to export symbols for GfeSDK.dll -

GetUrlPageData2 (WinHttp) failed: 12007.

KEY_VALUES_STRING: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start

Name:

Time: 2019-07-30T16:43:45.416Z

Diff: 901416 mSec

Timeline: Dump.Current

Name:

Time: 2019-07-30T16:28:44.0Z

Diff: 0 mSec

Timeline: Process.Start

Name:

Time: 2019-07-30T16:09:00.0Z

Diff: 1184000 mSec

DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT: (.ecxr)

rax=0000000000000000 rbx=000000000000000f rcx=00000000ffffffff

rdx=000000002ae9c5c0 rsi=000000000f000005 rdi=0000000034640000

rip=0000000145c2fbfe rsp=00000000344af890 rbp=0000000000000000

r8=0000000000000000 r9=0000000144503a80 r10=0000000000000000

r11=00000000344af690 r12=0000000032e94c78 r13=0000000144ac55e0

r14=0000000000000000 r15=0000000034630000

iopl=0 nv up ei pl nz na pe nc

cs=0033 =002b ds=002b es=002b fs=0053 gs=002b efl=00010202

bfv!fb::TwinkleFromJsEventEntity::c_TypeInfo+0x9411ce:

0000000145c2fbfe c7042500000000a7beadde mov dword ptr [0],0DEADBEA7h ds:0000000000000000=???

Resetting default scope

FAULTING_IP:

bfv!fb::TwinkleFromJsEventEntity::c_TypeInfo+9411ce

00000001`45c2fbfe c7042500000000a7beadde mov dword ptr [0],0DEADBEA7h

EXCEPTION_RECORD: (.exr -1)

ExceptionAddress: 0000000145c2fbfe (bfv!fb::TwinkleFromJsEventEntity::c_TypeInfo+0x00000000009411ce)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000001

Parameter[1]: 0000000000000000

Attempt to write to address 0000000000000000

DEFAULT_BUCKET_ID: NULL_POINTER_WRITE

FOLLOWUP_IP:

bfv!fb::TwinkleFromJsEventEntity::c_TypeInfo+9411ce

00000001`45c2fbfe c7042500000000a7beadde mov dword ptr [0],0DEADBEA7h

WRITE_ADDRESS: 0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000000

WATSON_BKT_PROCSTAMP: 5d2f3d7a

WATSON_BKT_PROCVER: 1.0.75.6509

PROCESS_VER_PRODUCT: Battlefield V

WATSON_BKT_MODULE: bfv.exe

WATSON_BKT_MODSTAMP: 5d2f3d7a

WATSON_BKT_MODOFFSET: 5c2fbfe

WATSON_BKT_MODVER: 1.0.75.6509

MODULE_VER_PRODUCT: Battlefield V

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

MODLIST_WITH_TSCHKSUM_HASH: 452a30bbc94c6f29a3ed91ce41c4b05341267a30

MODLIST_SHA1_HASH: cb8e67bfab2252f3c7b6298ce3c4e0268c18d5c3

COMMENT: Frostbite MiniDump. Address: 0000000145C2FBFE (In Windbg type: .ecxr)

[EOF]

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

DUMP_FLAGS: a2

DUMP_TYPE: 11

PROCESS_NAME: unknown

ANALYSIS_SESSION_HOST: DESKTOP

ANALYSIS_SESSION_TIME: 07-30-2019 18:43:45.0416

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

THREAD_ATTRIBUTES:

OS_LOCALE: DEU

BUGCHECK_STR: APPLICATION_FAULT_NULL_POINTER_WRITE_INVALID_POINTER_WRITE_AFTER_CALL

PRIMARY_PROBLEM_CLASS: APPLICATION_FAULT

PROBLEM_CLASSES:

ID: [0n313]

Type: [@ACCESS_VIOLATION]

Class: Addendum

Scope: BUCKET_ID

Name: Omit

Data: Omit

PID: [Unspecified]

TID: [0x3eac]

Frame: [0] : bfv!fb::TwinkleFromJsEventEntity::c_TypeInfo

ID: [0n286]

Type: [INVALID_POINTER_WRITE]

Class: Primary

Scope: BUCKET_ID

Name: Add

Data: Omit

PID: [Unspecified]

TID: [0x3eac]

Frame: [0] : bfv!fb::TwinkleFromJsEventEntity::c_TypeInfo

ID: [0n301]

Type: [NULL_POINTER_WRITE]

Class: Primary

Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)

BUCKET_ID

Name: Add

Data: Omit

PID: [0x1b1c]

TID: [0x3eac]

Frame: [0] : bfv!fb::TwinkleFromJsEventEntity::c_TypeInfo

ID: [0n111]

Type: [AFTER_CALL]

Class: Addendum

Scope: BUCKET_ID

Name: Add

Data: Omit

PID: [0x1b1c]

TID: [0x3eac]

Frame: [0] : bfv!fb::TwinkleFromJsEventEntity::c_TypeInfo

LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000145c2fbfe

STACK_TEXT:

00000000344af890 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : bfv!fb::TwinkleFromJsEventEntity::c_TypeInfo+0x9411ce

THREAD_SHA1_HASH_MOD_FUNC: 469d6ca7f6b417ff2fa393987dcef43fd058d25d

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 096f2aa1f684658fd89028017768c6286031c38c

THREAD_SHA1_HASH_MOD: f86e706f3881ff99410f64522468510881cb97a0

FAULT_INSTR_CODE: 2504c7

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: bfv!fb::TwinkleFromJsEventEntity::c_TypeInfo+9411ce

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bfv

IMAGE_NAME: bfv.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5d2f3d7a

STACK_COMMAND: ~24s ; .ecxr ; kb

FAILURE_BUCKET_ID: NULL_POINTER_WRITE_c0000005_bfv.exe!fb::TwinkleFromJsEventEntity::c_TypeInfo

BUCKET_ID: APPLICATION_FAULT_NULL_POINTER_WRITE_INVALID_POINTER_WRITE_AFTER_CALL_bfv!fb::TwinkleFromJsEventEntity::c_TypeInfo+9411ce

FAILURE_EXCEPTION_CODE: c0000005

FAILURE_IMAGE_NAME: bfv.exe

BUCKET_ID_IMAGE_STR: bfv.exe

FAILURE_MODULE_NAME: bfv

BUCKET_ID_MODULE_STR: bfv

FAILURE_FUNCTION_NAME: fb::TwinkleFromJsEventEntity::c_TypeInfo

BUCKET_ID_FUNCTION_STR: fb::TwinkleFromJsEventEntity::c_TypeInfo

BUCKET_ID_OFFSET: 9411ce

BUCKET_ID_MODTIMEDATESTAMP: 5d2f3d7a

BUCKET_ID_MODCHECKSUM: edb1582

BUCKET_ID_MODVER_STR: 1.0.75.6509

BUCKET_ID_PREFIX_STR: APPLICATION_FAULT_NULL_POINTER_WRITE_INVALID_POINTER_WRITE_AFTER_CALL_

FAILURE_PROBLEM_CLASS: APPLICATION_FAULT

FAILURE_SYMBOL_NAME: bfv.exe!fb::TwinkleFromJsEventEntity::c_TypeInfo

WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/unknown/1.0.75.6509/5d2f3d7a/bfv.exe/1.0.75.6509/5d2f3d7a/c0000005/05c2fbfe.htm?Retriage=1

TARGET_TIME: 2019-07-30T16:28:44.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-25 02: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: 3167a

ANALYSIS_SOURCE: UM

FAILURE_ID_HASH_STRING: um:null_pointer_write_c0000005_bfv.exe!fb::twinklefromjsevententity::c_typeinfo

FAILURE_ID_HASH: {7c2bad99-7bc8-2ac9-da22-044f914d38d0}

Followup: MachineOwner

============================================================================================================================================================================================================

Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64

Loading Dump File [C:\Users.…\Documents\Battlefield V\crash_dumps\CrashDump_2019.07.28_17.47.37.156.mdmp]

Comment: 'Frostbite MiniDump. Address: 0000000147AF84DF (In Windbg type: .ecxr)

[EOF]’

User Mini Dump File: Only registers, stack and portions of memory are available

Path validation summary

Response Time (ms) Location

Deferred SRV…\windows software dev kit\SymCache*http://msdl.microsoft.com/download/symbols*

Symbol search path is: SRV…\windows software dev kit\SymCache*http://msdl.microsoft.com/download/symbols*

Executable search path is:

Windows 10 Version 17763 MP (8 procs) Free x64

Product: WinNt, suite: SingleUserTS

17763.1.amd64fre.rs5_release.180914-1434

Machine Name:

Debug session time: Sun Jul 28 17:47:37.000 2019 (UTC + 2:00)

System Uptime: not available

Process Uptime: 0 days 3:13:39.000

…

This dump file has an exception of interest stored in it.

The stored exception information can be accessed via .ecxr.

(22a0.3214): Access violation - code c0000005 (first/second chance not available)

ntdll!NtGetContextThread+0x14:

00007ff8`dcad0304 c3 ret

0:015> !analyze -v

Exception Analysis *

WARNING: Unable to verify timestamp for dbdata.dll

ERROR: Module load completed but symbols could not be loaded for dbdata.dll

*** ERROR: Symbol file could not be found. Defaulted to export symbols for igo64.dll -**

ERROR: Symbol file could not be found. Defaulted to export symbols for nvwgf2umx.dll -

*** ERROR: Symbol file could not be found. Defaulted to export symbols for poco.dll -**

ERROR: Symbol file could not be found. Defaulted to export symbols for MessageBus.dll -

*** WARNING: Unable to verify timestamp for GfeSDK.dll**

ERROR: Module load completed but symbols could not be loaded for GfeSDK.dll

KEY_VALUES_STRING: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start

Name:

Time: 2019-07-30T16:38:29.468Z

Diff: 175852468 mSec

Timeline: Dump.Current

Name:

Time: 2019-07-28T15:47:37.0Z

Diff: 0 mSec

Timeline: Process.Start

Name:

Time: 2019-07-28T12:33:58.0Z

Diff: 11619000 mSec

DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT: (.ecxr)

rax=a4b655fdba653c29 rbx=00000000a0f77bb0 rcx=00000001446e2c50

rdx=3a8ba8e7a5660450 rsi=3a8ba8e7046e88a0 rdi=00000001446e2c50

rip=0000000147af84df rsp=000000003414f6e0 rbp=5b49aa02e6923f87

r8=3ffffffffffffff8 r9=00000000a93d05d0 r10=0000000000000002

r11=000000003414f740 r12=0000000000000000 r13=00000000301a5bc0

r14=df41fee4bed3c4e9 r15=0000000000000000

iopl=0 nv up ei pl nz na pe nc

cs=0033 =002b ds=002b es=002b fs=0053 gs=002b efl=00010202

bfv+0x7af84df:

0000000147af84df 488b7a08 mov rdi,qword ptr [rdx+8] ds:3a8ba8e7a5660458=???

Resetting default scope

FAULTING_IP:

bfv+7af84df

00000001`47af84df 488b7a08 mov rdi,qword ptr [rdx+8]

EXCEPTION_RECORD: (.exr -1)

ExceptionAddress: 0000000147af84df (bfv+0x0000000007af84df)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff

DEFAULT_BUCKET_ID: INVALID_POINTER_READ

FOLLOWUP_IP:

bfv+7af84df

00000001`47af84df 488b7a08 mov rdi,qword ptr [rdx+8]

READ_ADDRESS: ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

WATSON_BKT_PROCSTAMP: 5089d1b5

WATSON_BKT_MODULE: bfv.exe

WATSON_BKT_MODSTAMP: 5d2f3d7a

WATSON_BKT_MODOFFSET: 7af84df

WATSON_BKT_MODVER: 1.0.75.6509

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

MODLIST_WITH_TSCHKSUM_HASH: 011e9b605ce7fe831d67d36676c64327346213c5

MODLIST_SHA1_HASH: 6cbd07f2760294ca32c46092ecc4a0356bda1cb8

COMMENT: Frostbite MiniDump. Address: 0000000147AF84DF (In Windbg type: .ecxr)

[EOF]

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

DUMP_FLAGS: a2

DUMP_TYPE: 11

PROCESS_NAME: unknown

ANALYSIS_SESSION_HOST: DESKTOP

ANALYSIS_SESSION_TIME: 07-30-2019 18:38:29.0468

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

THREAD_ATTRIBUTES:

OS_LOCALE: DEU

BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ

PRIMARY_PROBLEM_CLASS: APPLICATION_FAULT

PROBLEM_CLASSES:

ID: [0n313]

Type: [@ACCESS_VIOLATION]

Class: Addendum

Scope: BUCKET_ID

Name: Omit

Data: Omit

PID: [Unspecified]

TID: [0x3214]

Frame: [0] : bfv

ID: [0n285]

Type: [INVALID_POINTER_READ]

Class: Primary

Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)

BUCKET_ID

Name: Add

Data: Omit

PID: [Unspecified]

TID: [0x3214]

Frame: [0] : bfv

LAST_CONTROL_TRANSFER: from 00000001446e4120 to 0000000147af84df

STACK_TEXT:

000000003414f6e0 00000001446e4120 : 000000014044c7eb 00000001446e41b0 000000006ec754a8 00000001446e2c50 : bfv+0x7af84df

000000003414f6e8 000000014044c7eb : 00000001446e41b0 000000006ec754a8 00000001446e2c50 000000014120d6ec : bfv+0x46e4120

000000003414f6f0 00000001446e41b0 : 000000006ec754a8 00000001446e2c50 000000014120d6ec 00000000a679d380 : bfv+0x44c7eb

000000003414f6f8 000000006ec754a8 : 00000001446e2c50 000000014120d6ec 00000000a679d380 000000014120d6b2 : bfv+0x46e41b0

000000003414f700 00000001446e2c50 : 000000014120d6ec 00000000a679d380 000000014120d6b2 00000000a0f77bb0 : 0x6ec754a8

000000003414f708 000000014120d6ec : 00000000a679d380 000000014120d6b2 00000000a0f77bb0 5b49aa02e6923f87 : bfv+0x46e2c50

000000003414f710 00000000a679d380 : 000000014120d6b2 00000000a0f77bb0 5b49aa02e6923f87 00000000a0f77bc0 : bfv+0x120d6ec

000000003414f718 000000014120d6b2 : 00000000a0f77bb0 5b49aa02e6923f87 00000000a0f77bc0 0000000147af08f6 : 0xa679d380

000000003414f720 00000000a0f77bb0 : 5b49aa02e6923f87 00000000a0f77bc0 0000000147af08f6 00000001446e2c50 : bfv+0x120d6b2

000000003414f728 5b49aa02e6923f87 : 00000000a0f77bc0 0000000147af08f6 00000001446e2c50 0000000000000158 : 0xa0f77bb0

000000003414f730 00000000a0f77bc0 : 0000000147af08f6 00000001446e2c50 0000000000000158 00000000a0f77bc0 : 0x5b49aa02`e6923f87

000000003414f738 0000000147af08f6 : 00000001446e2c50 0000000000000158 00000000a0f77bc0 00000001b48523c8 : 0xa0f77bc0

000000003414f740 00000001446e2c50 : 0000000000000158 00000000a0f77bc0 00000001b48523c8 00000001446e2c30 : bfv+0x7af08f6

000000003414f748 0000000000000158 : 00000000a0f77bc0 00000001b48523c8 00000001446e2c30 0000000145c3dacb : bfv+0x46e2c50

000000003414f750 00000000a0f77bc0 : 00000001b48523c8 00000001446e2c30 0000000145c3dacb e4ba433336c222fc : 0x158

000000003414f758 00000001b48523c8 : 00000001446e2c30 0000000145c3dacb e4ba433336c222fc e4ba433336c222fc : 0xa0f77bc0

000000003414f760 00000001446e2c30 : 0000000145c3dacb e4ba433336c222fc e4ba433336c222fc 0000000000000158 : 0x00000001`b48523c8

000000003414f768 0000000145c3dacb : e4ba433336c222fc e4ba433336c222fc 0000000000000158 00000000a0f77bc0 : bfv+0x46e2c30

000000003414f770 e4ba433336c222fc : e4ba433336c222fc 0000000000000158 00000000a0f77bc0 00000001d9d56768 : bfv+0x5c3dacb

000000003414f778 e4ba433336c222fc : 0000000000000158 00000000a0f77bc0 00000001d9d56768 00000001469ac296 : 0xe4ba4333`36c222fc

000000003414f780 0000000000000158 : 00000000a0f77bc0 00000001d9d56768 00000001469ac296 e4ba433336c222fc : 0xe4ba4333`36c222fc

000000003414f788 00000000a0f77bc0 : 00000001d9d56768 00000001469ac296 e4ba433336c222fc 0000000000000d18 : 0x158

000000003414f790 00000001d9d56768 : 00000001469ac296 e4ba433336c222fc 0000000000000d18 00000001d9d8c620 : 0xa0f77bc0

000000003414f798 00000001469ac296 : e4ba433336c222fc 0000000000000d18 00000001d9d8c620 00000001b4852330 : 0x00000001`d9d56768

000000003414f7a0 e4ba433336c222fc : 0000000000000d18 00000001d9d8c620 00000001b4852330 00000001435af2a0 : bfv+0x69ac296

000000003414f7a8 0000000000000d18 : 00000001d9d8c620 00000001b4852330 00000001435af2a0 0000000000000000 : 0xe4ba4333`36c222fc

000000003414f7b0 00000001d9d8c620 : 00000001b4852330 00000001435af2a0 0000000000000000 00000001b48522c0 : 0xd18

000000003414f7b8 00000001b4852330 : 00000001435af2a0 0000000000000000 00000001b48522c0 000000014047beb5 : 0x00000001`d9d8c620

000000003414f7c0 00000001435af2a0 : 0000000000000000 00000001b48522c0 000000014047beb5 00000001b4852330 : 0x00000001`b4852330

000000003414f7c8 0000000000000000 : 00000001b48522c0 000000014047beb5 00000001b4852330 0000000000000000 : bfv+0x35af2a0

THREAD_SHA1_HASH_MOD_FUNC: 5acdeb3ce06d60c8359b3fb9b3eed6ba8b9678dc

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f66e08f0d02982bb9fe36935dff309f0141cd24a

THREAD_SHA1_HASH_MOD: 5acdeb3ce06d60c8359b3fb9b3eed6ba8b9678dc

FAULT_INSTR_CODE: 87a8b48

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: bfv+7af84df

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bfv

IMAGE_NAME: bfv.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5d2f3d7a

STACK_COMMAND: ~15s ; .ecxr ; kb

FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_bfv.exe!Unknown

BUCKET_ID: APPLICATION_FAULT_INVALID_POINTER_READ_bfv+7af84df

FAILURE_EXCEPTION_CODE: c0000005

FAILURE_IMAGE_NAME: bfv.exe

BUCKET_ID_IMAGE_STR: bfv.exe

FAILURE_MODULE_NAME: bfv

BUCKET_ID_MODULE_STR: bfv

FAILURE_FUNCTION_NAME: Unknown

BUCKET_ID_FUNCTION_STR: Unknown

BUCKET_ID_OFFSET: 7af84df

BUCKET_ID_MODTIMEDATESTAMP: 5d2f3d7a

BUCKET_ID_MODCHECKSUM: edb089b

BUCKET_ID_MODVER_STR: 1.0.75.6509

BUCKET_ID_PREFIX_STR: APPLICATION_FAULT_INVALID_POINTER_READ_

FAILURE_PROBLEM_CLASS: APPLICATION_FAULT

FAILURE_SYMBOL_NAME: bfv.exe!Unknown

TARGET_TIME: 2019-07-28T15:47:37.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-25 02: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: 2b080

ANALYSIS_SOURCE: UM

FAILURE_ID_HASH_STRING: um:invalid_pointer_read_c0000005_bfv.exe!unknown

FAILURE_ID_HASH: {5ed0a69c-603d-a86c-09e8-233e39078c55}

Followup: MachineOwner

ApexAEF · July 31, 2019, 2:09am

Hi guys,

Just revisiting this old thread to see if there has been any solutions/luck from anyone with this issue.

It’s been many months now, basically more than half a year has passed, and I’ve not been able to play a single match of this game.

Cheers all, happy gaming!

JDjitsu · August 1, 2019, 1:29am

It you didn’t try the super easy stuff like turn off any overclocking of CPU, GPU and memory, making sure you don’t have hardware acceleration on in your browser then make sure you have Origin or BFV running in Admin Mode. Even if the box isn’t ticked when you right click on Origin or BF .exe icon, sometimes it can be turned on in the Registry. Go to your Registry(Hit Start/Run then type in regedit then enter. Your Reg should then open up and go to “HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers” and delete any origin or BF games listed to the right. That’s what worked for me. Somehow it was running in Admin Compatibility Mode and I think that was the culprit for my crashes. GLHF

Mhill2029 · August 4, 2019, 2:50pm

No problems for a long time, and suddenly after updating Windows 10 with KB4505903 I CTD after a few matches. It’s only happened the once, so maybe an isolated bug. But i’m not having a lot of faith with Windows 10’s updates. Since most of these CTD’s have always arised suddenly after an update.

InFlames_nn · August 4, 2019, 6:15pm

After Win10 latest patch (04 August) and switching to dx12, i didn’t experienced those crushes on desktop without error. Besides i have cpu and ram overclock and didn’t want to go lower, and now it’s fine.

PrOdyh · August 4, 2019, 7:39pm

Yes, very nice news. Directx 12 work fine in my i5 8600k + 1070

Mhill2029 · August 5, 2019, 2:32am

Also just noticed in the last day or so that there has been a major security flaw in all nvidia drivers. That causes all sorts of issues, so it’s recommended to update to 431.60. Just a heads up…

Not sure if it has any baring on BFV, but some of the problems I read are pretty extensive.

CanSwe22 · August 11, 2019, 1:00pm

Hi guys,
I have also been having the same problem with BFV crashing to desktop on startup. I have tried everything you all have said (I am on day three now…) but I figured out (from the Event Viewer) that Overwolf is my problem. I searched and found this happens with other games too. https://www.reddit.com/r/Overwolf/comments/b3b4iq/overwolf_causes_games_to_crash/

I disabled BFV in Overwolf and it seems to work now. I don’t know if this helps anyone but it can’t hurt!

oneCelph · August 12, 2019, 10:20pm

Fyi.

Started for me today, can confirm.

JVF_CON · August 14, 2019, 1:44am

Im experiencing random freeze in bfv. However i manage to fix it by lowering the cpu usage. On game setting I lower my frame limiter to 60fps. On windows nvdia config i choosed vsync daptive half screen refresh rate, optimal power, change the default physics as Gpu . On the power setting max cpu usage at 100% and minimum to 5%.

RudyMentally · August 15, 2019, 11:20am

I can play for hours without a crash, but if I decide to go spectate (some suspicious player or whatever), it crashes within a minute, sometimes even before the players start to move properly within 10 seconds and relaunching and spectating again will just crash just as quickly, so it is reproducable … please fix it, feel free to contatct me to get the crash dump. This is the only game that has the problem.

Overwolfqa · August 16, 2019, 2:47pm

Hey CanSwe22,

I’m from Overwolf’s team and I came across your post.
I’m sorry to hear that your game had been crashing while you were using Overwolf. Our team puts users’ game performance as a top priority, so it’s important to us to get to the bottom of your issue and understand how these crashes happened.
If you could please contact us through this support request form, I will make sure that we get back to you as soon as possible.

Thank!

g0merpile · September 29, 2019, 1:24pm

follow my advice problem solved hopefully forums.battlefield.com/en-us/discussion/194530/battlefield-v-poor-performance-solutions#latest

bigdaddygonutz · September 29, 2019, 7:20pm

Thnx … but I am on win 1803 win locked-n-updates … and it was 100% perfect until the recent patch = immediately after this patch …crash crash crash…

pootisstyle123 · October 1, 2019, 9:30pm

After the latest patch, my game started to randomly close again … I tried repair, clear cache and other bullsh*t they say, but it still crashes NOW RIGHT AFTER I LAUNCH THE GAME.. Why can’t we get a single patch that doesn’t break up our game ?? They called it Hotfix but this only gave more bugs ..

S1n31ra · October 2, 2019, 5:42am

It’s even worse now after the patch. 3 times in 2h. Ridiculous.

Pcidemocon · October 2, 2019, 12:25pm

](https://ibb.co/dQCTvv4)
Check BFV DBUG FILE you’ll see what is causing the crashing.
In my case i’d found out RTX SLI water block terminal flow was impacting heat dissipation .

Gunboat2000 · October 4, 2019, 5:21pm

Game crashes directly after launch.

Solution: UNINSTALL AND NEVER BUY A EA GAME AGAIN!

MrMassiveLoad · October 17, 2019, 9:45pm

After an hardware upgrade to a Ryzen 7 3700X, Gigabyte X570 AORUS ELITE and 16 GB G-Skill Ripjaws V I also suffert from randomly CTD. Every five minutes, once an hour or after two.

After 2 weeks of research, investigation and tons of different settings (every hint i found in this forum) i was finaly able to
reproduce my crashes respectively what causes they.

My solution:

Regardless the fact that my RAM is certified as an 3200 mhz RAM (F4-3200C16D-8GVKB DDR4-3200MHz CL16-18-18-38 1.35V), it has still an regular SPD speed of 2133m mhz. Depends on the Mainboard and cpu configuration this RAM is able (!!!) to reach 3200 mhz with timings at CL16-18-18-38 in XMP mode. In my case, it wasn´t. It also causes some errors in HCI MemTest. So even if everything else worked fine with this settings, it´s still faulty.

By keeping this timings AND the XMP profil I had to reduce the Frequency to 3066 mhz (1533mhz). No errors. No crashes in BF V anymore.

So it doesn´t mean BF V always reacts petty to XMP profils. In my case, BF V just showed me - regardless of every other software doesn´t -
that this settings are not working properly. The HCI MemTest just confirmed this.

I hope this informations are helpfull to other people as well.

(I used the DRAM-Calculator-for-Ryzen Tool to start the MemTest. Because it starts automaticly several instances to fill up the RAM entirely)

OskooI_007 · October 17, 2019, 11:53pm

Yup, most crashes and random reboots are due to DDR memory errors.

Sometimes you need to downclock the memory. Sometimes you need to increase memory voltage (risky).

Sometimes you need to increase the memory controller voltage on the CPU die (even more risky).

Even leaving voltage settings on ‘auto’ in the BIOS is risky. I made that mistake while overclocking my 8700k and it ‘auto’ increased voltages for my CPU to unsafe levels. I’m pretty sure the CPU got damaged and degraded a little. That’s why I’d never buy a used CPU off eBay.

Upgrading your BIOS can also help with DDR memory stability. Motherboard manufacturers add new memory profiles with BIOS updates.

Finally, the best way to avoid DDR memory problems is to buy memory off the Qualified Vendors List (QVL) for your motherboard. You can usually find the QVL list under the support section on the motherboard manufacturer’s website.