Forum Discussion
Microsoft (R) Windows Debugger Version 10.0.19494.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\ventu\OneDrive\Documenti\Battlefield V\crash_dumps\CrashDump_2019.10.11_19.43.44.011.mdmp]
Comment: 'Frostbite MiniDump. Address: 00007FF9E4A3A839 (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*
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: SingleUserTS
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Debug session time: Fri Oct 11 19:43:44.000 2019 (UTC + 2:00)
System Uptime: not available
Process Uptime: 0 days 0:30:34.000
................................................................
................................................................
.................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(2b10.302c): Unknown exception - code 887a0006 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007ff9`e779de54 c3 ret
0:014> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 97
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-KP1KK6Q
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 124
Key : Analysis.Memory.CommitPeak.Mb
Value: 3413
Key : Analysis.System
Value: CreateObject
Key : Timeline.Process.Start.DeltaSec
Value: 1834
COMMENT: Frostbite MiniDump. Address: 00007FF9E4A3A839 (In Windbg type: .ecxr)
[EOF]
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
CONTEXT: (.ecxr)
rax=0000474e55485f45 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=00000000378a63e0 rdi=00000000887a0006
rip=00007ff9e4a3a839 rsp=00000000340bc580 rbp=00000000340bc760
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=00000000378b2390 r13=00000000378a63e0
r14=000000014399f628 r15=00000001439a5ed8
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
KERNELBASE!RaiseException+0x69:
00007ff9`e4a3a839 0f1f440000 nop dword ptr [rax+rax]
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff9e4a3a839 (KERNELBASE!RaiseException+0x0000000000000069)
ExceptionCode: 887a0006
ExceptionFlags: 00000000
NumberParameters: 0
PROCESS_NAME: bfv.exe
ERROR_CODE: (NTSTATUS) 0x887a0006 - La GPU non risponde a pi comandi. probabile che sia stato passato un comando non valido dall'applicazione chiamante.
EXCEPTION_CODE_STR: 887a0006
DETOURED_IMAGE: 1
STACK_TEXT:
00000000`340bc580 00000001`41f9e666 : 00000001`4399f628 00000000`00000000 00000000`340bc760 00000000`378a63e0 : KERNELBASE!RaiseException+0x69
00000000`340bc660 00000001`41fb0384 : 00000000`00000002 00000000`03b09a00 00000000`00000000 00000000`00000000 : bfv!fb::ScriptEngineAllocator::getUsedMemory+0x53e46
00000000`340bdf30 00000001`41fa0a3c : 00000001`439a5ec8 00000001`439a5ed8 00000001`439a5ed8 00000000`340bf5a9 : bfv!fb::ScriptEngineAllocator::getUsedMemory+0x65b64
00000000`340bf510 00000001`41f9ef30 : 00000000`2abdb9c0 00000000`378c0660 00000000`378c0650 00000000`378a63e0 : bfv!fb::ScriptEngineAllocator::getUsedMemory+0x5621c
00000000`340bf610 00000001`41f0f656 : 00000000`00000000 00000000`00000000 00000000`340bf840 00000000`37893bb0 : bfv!fb::ScriptEngineAllocator::getUsedMemory+0x54710
00000000`340bf740 00000001`48c0d162 : 00000000`337580c0 00000000`37893bb0 00000000`33571230 00000000`337580c0 : bfv!fb::JsMessageListener::onJSRegister+0x3535c6
00000000`340bfa10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : bfv!fb::Twinkle::getLayout+0xb7a512
SYMBOL_NAME: bfv!fb::ScriptEngineAllocator::getUsedMemory+53e46
MODULE_NAME: bfv
IMAGE_NAME: bfv.exe
STACK_COMMAND: ~14s ; .ecxr ; kb
FAILURE_BUCKET_ID: APPLICATION_FAULT_887a0006_bfv.exe!fb::ScriptEngineAllocator::getUsedMemory
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {50269fac-5900-b2c2-579f-ee550fd50576}
Followup: MachineOwner
---------
Looks like a driver is causing various crashes.
Looks like its trying to send faulty memory instructions giving you error of corruption and causing your gpu to not respond.
Would help of you posted your spec and a dxdiag as well.
Try something simple like clearing the origin cache. For some reason origin is involved in more crashes than anything else. lol And disable all overlays, including discord, steam, origin, while playing bfv. Somethimes they interfere with drivers causing these crashes.
Also in general you should make sure you try different drivers, first the newest possible and if that doesnt work try an older one. Since the GPU hangs its most likely the gpu driver causing this.
But updating all drivers including chipset driver doesnt hurt. Also updating or reinstalling your bios might fix something here or turn on or off xmp.
Maybe more people could help if your crash dump was entirely in english and and not having some error messages in italian (?)
Anyways I hope one of the simple solutions work for you so you do not need to go through the entire update everything route.
- 7 years ago
@3DiE9djua2 ha scritto:Looks like a driver is causing various crashes.
Looks like its trying to send faulty memory instructions giving you error of corruption and causing your gpu to not respond.
Would help of you posted your spec and a dxdiag as well.
Try something simple like clearing the origin cache. For some reason origin is involved in more crashes than anything else. lol And disable all overlays, including discord, steam, origin, while playing bfv. Somethimes they interfere with drivers causing these crashes.
Also in general you should make sure you try different drivers, first the newest possible and if that doesnt work try an older one. Since the GPU hangs its most likely the gpu driver causing this.
But updating all drivers including chipset driver doesnt hurt. Also updating or reinstalling your bios might fix something here or turn on or off xmp.
Maybe more people could help if your crash dump was entirely in english and and not having some error messages in italian (?)
Anyways I hope one of the simple solutions work for you so you do not need to go through the entire update everything route.
I tried deleting local app data and disabling overlays from various programs.
i tried putting my rams in auto instead of xmp profile.
and it seems work!never got crashes!
I’ll try to put xmp profile to see if it will still crash or not!
I’ll let you know