6 years ago
Analize crash Dump
Hi
I've had CTD for the longest time I've always done a quick fix of deleting origins cache. But it's becoming annoying lately that I wish to find a permanent solution. I have a copy of the crash dump, but I don't know how to read this, maybe some of you can analyze it and give me the solution. Crash dumb can be seen below:
Microsoft (R) Windows Debugger Version 10.0.19494.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\MADZAK\Documents\Battlefield V\crash_dumps\CrashDump_2019.11.20_22.35.14.158.mdmp] Comment: 'Frostbite MiniDump. Address: 00000001459A35C2 (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 18362 MP (8 procs) Free x64 Product: WinNt, suite: SingleUserTS 18362.1.amd64fre.19h1_release.190318-1202 Machine Name: Debug session time: Wed Nov 20 22:35:15.000 2019 (UTC + 8:00) System Uptime: not available Process Uptime: 0 days 0:28:53.000 ................................................................ ................................................................ ........... This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (2ffc.2d4c): Access violation - code c0000005 (first/second chance not available) For analysis of this file, run !analyze -vntdll!NtGetContextThread+0x14: 00007ffa`a135de54 c3 ret 0:023> !analyze -v ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* KEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullPtr Key : AV.Fault Value: Write Key : Analysis.CPU.Sec Value: 178 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on MADZAK Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 206 Key : Analysis.Memory.CommitPeak.Mb Value: 5813 Key : Analysis.System Value: CreateObject Key : Timeline.Process.Start.DeltaSec Value: 1733 COMMENT: Frostbite MiniDump. Address: 00000001459A35C2 (In Windbg type: .ecxr) [EOF] NTGLOBALFLAG: 0 PROCESS_BAM_CURRENT_THROTTLED: 0 PROCESS_BAM_PREVIOUS_THROTTLED: 0 CONTEXT: (.ecxr)rax=0000000000000000 rbx=0000000035080000 rcx=00000000ffffffff rdx=000000002b425a20 rsi=00000000337d4af8 rdi=0000000033794e40 rip=00000001459a35c2 rsp=0000000034f2f8d0 rbp=0000000033fc79c0 r8=0000000000000000 r9=00000001440c9980 r10=000000002ac7f338 r11=000000002ab51d78 r12=0000000000000000 r13=000000000316f258 r14=0000000000000000 r15=0000000035070000 iopl=0 nv up ei pl nz na po nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206 bfv!fb::Twinkle::getKeyValueStorage+0x3df72: 00000001`459a35c2 c7042500000000a7beadde mov dword ptr [0],0DEADBEA7h ds:00000000`00000000=???????? Resetting default scope EXCEPTION_RECORD: (.exr -1)ExceptionAddress: 00000001459a35c2 (bfv!fb::Twinkle::getKeyValueStorage+0x000000000003df72) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000001 Parameter[1]: 0000000000000000 Attempt to write to address 0000000000000000 PROCESS_NAME: bfv.exe WRITE_ADDRESS: 0000000000000000 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000001 EXCEPTION_PARAMETER2: 0000000000000000 STACK_TEXT: 00000000`34f2f8d0 00000001`405c6e40 : 00000000`3046f6e0 00000000`33fc79c0 00000000`3046f6e0 00000000`33fc79c0 : bfv!fb::Twinkle::getKeyValueStorage+0x3df72 00000000`34f2f9e0 00000001`41c77090 : 00000000`33fb6200 00000000`33fb629c 00000000`33e55330 00000000`33fc79c0 : bfv!fb::TwinkleOverlayManager::getState+0x28cf0 00000000`34f2fa40 00000001`48a8682a : 00000000`33fb6200 00000000`00000000 00000000`00000000 00000000`00000000 : bfv!fb::JsMessageListener::onJSRegister+0xf28f0 00000000`34f2fa80 00000001`41c7b41f : 00000000`00000000 00000000`33fb2400 00000000`00000000 00000000`00000000 : bfv!fb::Twinkle::getLayout+0x6357fa 00000000`34f2fb20 00000001`48a9d40f : 00000001`4469d3b0 00000000`34f2fdf0 00000001`4469cd01 00000001`4450a1d0 : bfv!fb::JsMessageListener::onJSRegister+0xf6c7f 00000000`34f2fce0 00000001`48a9cbfa : 00000000`2c3e38f0 00000001`4469cd90 00000000`00000000 00000000`00000001 : bfv!fb::Twinkle::getLayout+0x64c3df 00000000`34f2fdc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : bfv!fb::Twinkle::getLayout+0x64bbca SYMBOL_NAME: bfv!fb::Twinkle::getKeyValueStorage+3df72 MODULE_NAME: bfv IMAGE_NAME: bfv.exe STACK_COMMAND: ~23s ; .ecxr ; kb FAILURE_BUCKET_ID: NULL_POINTER_WRITE_c0000005_bfv.exe!fb::Twinkle::getKeyValueStorage OS_VERSION: 10.0.18362.1 BUILDLAB_STR: 19h1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {b33f1dbb-46cb-a1b3-ff30-313bca5c0e3f} Followup: MachineOwner --------- 0:023> lmvm bfvBrowse full module liststart end module name 00000001`40000000 00000001`4e92b000 bfv (export symbols) bfv.exe Loaded symbol image file: bfv.exe Mapped memory image file: F:\GAMES\Battlefield V\bfv.exe Image path: F:\GAMES\Battlefield V\bfv.exe Image name: bfv.exe Browse all global symbols functions data Timestamp: Wed Oct 23 01:16:25 2019 (5DAF3969) CheckSum: 0E38A2DB ImageSize: 0E92B000 File version: 1.0.77.40679 Product version: 1.0.77.40679 File flags: 1 (Mask 17) Debug File OS: 4 Unknown Win32 File type: 0.0 Unknown File date: 00000000.00000000 Translations: 0409.04b0 Information from resource tables: CompanyName: EA Digital Illusions CE AB ProductName: Battlefield™ V ProductVersion: 1, 0, 77, 40679 FileVersion: 1, 0, 77, 40679 FileDescription: Battlefield™ V LegalCopyright: Copyright © 2018 EA Digital Illusions CE AB. All rights reserved.
Thank You, and you can help.
@MADZAK66 Can we try starting up your PC in a clean boot to see if that helps? If there's anything else running in the background that might be causing these crashes that may help narrow down the cause.
For more info on how to set up a clean boot check out https://help.ea.com/en/help/faq/how-to-clean-boot-your-pc/
/Kent