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

Comments

  • Mhill2029
    111 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1, Battlefield V Member
    I downgraded the nvidia 430.64 driver back to 425.31 and my imminent crashing when spectating seems to have vanished. Can anyone else try this maybe ?

    the crashing almost never happens on anything before 418.xx from what I've tested, apart from that recent CTD which is the first 1 in months on early drivers. I do know though if you use anything around 419.xx onwards you'll get 3 or 4 CTD's a day depending on how long you play for.

  • DJDeon0
    2 postsMember, Battlefield 3, Battlefield 4, Battlefield Hardline, Battlefield, Battlefield 1, Battlefield V Member
    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?
  • GVlXxf
    433 postsMember, Battlefield 3, Battlefield 4, Battlefield Hardline, Battlefield, Battlefield 1, Battlefield V Member
    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
  • lVlangoo
    3 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1, Battlefield V Member
    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.
  • lVlangoo
    3 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1, Battlefield V Member
    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.

  • Worst_Rookie
    2 postsMember, Battlefield, Battlefield 1, CTE, Battlefield V Member
    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
  • vipermonkey
    14 postsMember, Battlefield 3, Battlefield 4, Battlefield Hardline, Battlefield, Battlefield 1, BF1IncursionsAlpha, Battlefield V Member
    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
  • lVlangoo
    3 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1, Battlefield V Member
    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
    With the same display size as monitor?
    I am running 3440x1440 @ 120Hz
  • vipermonkey
    14 postsMember, Battlefield 3, Battlefield 4, Battlefield Hardline, Battlefield, Battlefield 1, BF1IncursionsAlpha, Battlefield V Member
    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
  • Pcidemocon
    5 postsMember, Battlefield, Battlefield 1, Battlefield V Member
    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: <blank>
        Time: 2019-06-30T09:39:55.686Z
        Diff: 16408686 mSec

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

    Timeline: Process.Start
        Name: <blank>
        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: 
    00000000`347be100 00000001`41f138a3 : 00000000`2af2f488 00000000`38027410 00000000`887a0005 00000000`303048b0 : KERNELBASE!RaiseException+0x69
    00000000`347be1e0 00000001`4a7753bc : 00000000`380353f0 00000000`380353f0 00000000`380353f0 00000030`00000000 : bfv!fb::TwinkleJSBundleManager::getFailedVersion+0x3645f3
    00000000`347bf3c0 00000001`422b886e : 00000000`30b5f468 00000000`00000000 00000000`00000120 00000000`1bf1dd60 : bfv!fb::ScriptEngineAllocator::realloc+0xeaaec
    00000000`347bf520 00000001`45e88f58 : 00000001`00000000 00000000`00000018 00000000`380353f0 00000000`380353f0 : bfv!fb::ScriptEngineAllocator::getMallocAllocatorName+0x9a14e
    00000000`347bf560 00000001`45e8873f : 00000001`270fbca8 00000000`347bf679 00000000`fdea0a70 00000000`00000000 : bfv!fb::JsObject::setScriptObject+0x64b68
    00000000`347bf5b0 00000000`00000000 : 00000001`270fbca8 00000000`347bf679 00000000`fdea0a70 00000000`00000000 : 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
    00000001`41f138a3 7a6f            jp      bfv!fb::TwinkleJSBundleManager::getFailedVersion+0x364664 (00000001`41f13914)

    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}

    Followup:     MachineOwner
    ---------



  • Pcidemocon
    5 postsMember, Battlefield, Battlefield 1, Battlefield V Member
    believe i know computers and this crash is not normal... is not hardware related....
  • Rombibombii
    573 postsMember, Battlefield 3, Battlefield 4, Battlefield Hardline, Battlefield, Battlefield 1, CTE, BF1IncursionsAlpha, Battlefield V Member
    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.
  • Pcidemocon
    5 postsMember, Battlefield, Battlefield 1, Battlefield V Member
    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.


    Take it eas&, just trying to get some help that's all!
  • Pcidemocon
    5 postsMember, Battlefield, Battlefield 1, Battlefield V Member
    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

  • FlexHo
    1 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1, BF1IncursionsAlpha, Battlefield V Member
    Chiming in on this problem also. Started since the mid june patch. I'm able to play an hour then it crashes.

    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

    How do you @Pcidemocon view your crash dumpfiles?
  • luqiano01
    1 postsMember, Battlefield 3, Battlefield 4, Battlefield Hardline, Battlefield, Battlefield 1, Battlefield V Member
    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
  • Pcidemocon
    5 postsMember, Battlefield, Battlefield 1, Battlefield V Member
    FlexHo wrote: »
    Chiming in on this problem also. Started since the mid june patch. I'm able to play an hour then it crashes.


    Pcidemocon said:
    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


    How do you @Pcidemocon view your crash dumpfiles?
    FlexHo wrote: »
    Chiming in on this problem also. Started since the mid june patch. I'm able to play an hour then it crashes.


    Pcidemocon said:
    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


    How do you @Pcidemocon view your crash dumpfiles?

    Microsoft debugging tool .
  • Xx-Mythril-xX
    23 postsMember, Battlefield 3, Battlefield 4, Battlefield Hardline, Battlefield, Battlefield 1, Battlefield V Member
    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 ;)
  • cyberfredcobra
    34 postsMember, Battlefield 3, Battlefield 4, Battlefield Hardline, Battlefield, Battlefield 1, Battlefield V Member
    the same for me today :( 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)
  • wildbam
    1 postsMember, Battlefield 3, Battlefield 4, Battlefield Hardline, Battlefield, Battlefield 1, Battlefield V Member

    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 ;)


    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

    Copyright (c) Microsoft Corporation. All rights reserved.



    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: <blank>

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

        Diff: 901416 mSec


    Timeline: Dump.Current

        Name: <blank>

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

        Diff: 0 mSec


    Timeline: Process.Start

        Name: <blank>

        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:

    00000001`45c2fbfe c7042500000000a7beadde mov dword ptr [0],0DEADBEA7h ds:00000000`00000000=????????

    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:  

    00000000`344af890 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 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

    Copyright (c) Microsoft Corporation. All rights reserved.



    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: <blank>

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

        Diff: 175852468 mSec


    Timeline: Dump.Current

        Name: <blank>

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

        Diff: 0 mSec


    Timeline: Process.Start

        Name: <blank>

        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:

    00000001`47af84df 488b7a08        mov     rdi,qword ptr [rdx+8] ds:3a8ba8e7`a5660458=????????????????

    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:  

    00000000`3414f6e0 00000001`446e4120 : 00000001`4044c7eb 00000001`446e41b0 00000000`6ec754a8 00000001`446e2c50 : bfv+0x7af84df

    00000000`3414f6e8 00000001`4044c7eb : 00000001`446e41b0 00000000`6ec754a8 00000001`446e2c50 00000001`4120d6ec : bfv+0x46e4120

    00000000`3414f6f0 00000001`446e41b0 : 00000000`6ec754a8 00000001`446e2c50 00000001`4120d6ec 00000000`a679d380 : bfv+0x44c7eb

    00000000`3414f6f8 00000000`6ec754a8 : 00000001`446e2c50 00000001`4120d6ec 00000000`a679d380 00000001`4120d6b2 : bfv+0x46e41b0

    00000000`3414f700 00000001`446e2c50 : 00000001`4120d6ec 00000000`a679d380 00000001`4120d6b2 00000000`a0f77bb0 : 0x6ec754a8

    00000000`3414f708 00000001`4120d6ec : 00000000`a679d380 00000001`4120d6b2 00000000`a0f77bb0 5b49aa02`e6923f87 : bfv+0x46e2c50

    00000000`3414f710 00000000`a679d380 : 00000001`4120d6b2 00000000`a0f77bb0 5b49aa02`e6923f87 00000000`a0f77bc0 : bfv+0x120d6ec

    00000000`3414f718 00000001`4120d6b2 : 00000000`a0f77bb0 5b49aa02`e6923f87 00000000`a0f77bc0 00000001`47af08f6 : 0xa679d380

    00000000`3414f720 00000000`a0f77bb0 : 5b49aa02`e6923f87 00000000`a0f77bc0 00000001`47af08f6 00000001`446e2c50 : bfv+0x120d6b2

    00000000`3414f728 5b49aa02`e6923f87 : 00000000`a0f77bc0 00000001`47af08f6 00000001`446e2c50 00000000`00000158 : 0xa0f77bb0

    00000000`3414f730 00000000`a0f77bc0 : 00000001`47af08f6 00000001`446e2c50 00000000`00000158 00000000`a0f77bc0 : 0x5b49aa02`e6923f87

    00000000`3414f738 00000001`47af08f6 : 00000001`446e2c50 00000000`00000158 00000000`a0f77bc0 00000001`b48523c8 : 0xa0f77bc0

    00000000`3414f740 00000001`446e2c50 : 00000000`00000158 00000000`a0f77bc0 00000001`b48523c8 00000001`446e2c30 : bfv+0x7af08f6

    00000000`3414f748 00000000`00000158 : 00000000`a0f77bc0 00000001`b48523c8 00000001`446e2c30 00000001`45c3dacb : bfv+0x46e2c50

    00000000`3414f750 00000000`a0f77bc0 : 00000001`b48523c8 00000001`446e2c30 00000001`45c3dacb e4ba4333`36c222fc : 0x158

    00000000`3414f758 00000001`b48523c8 : 00000001`446e2c30 00000001`45c3dacb e4ba4333`36c222fc e4ba4333`36c222fc : 0xa0f77bc0

    00000000`3414f760 00000001`446e2c30 : 00000001`45c3dacb e4ba4333`36c222fc e4ba4333`36c222fc 00000000`00000158 : 0x00000001`b48523c8

    00000000`3414f768 00000001`45c3dacb : e4ba4333`36c222fc e4ba4333`36c222fc 00000000`00000158 00000000`a0f77bc0 : bfv+0x46e2c30

    00000000`3414f770 e4ba4333`36c222fc : e4ba4333`36c222fc 00000000`00000158 00000000`a0f77bc0 00000001`d9d56768 : bfv+0x5c3dacb

    00000000`3414f778 e4ba4333`36c222fc : 00000000`00000158 00000000`a0f77bc0 00000001`d9d56768 00000001`469ac296 : 0xe4ba4333`36c222fc

    00000000`3414f780 00000000`00000158 : 00000000`a0f77bc0 00000001`d9d56768 00000001`469ac296 e4ba4333`36c222fc : 0xe4ba4333`36c222fc

    00000000`3414f788 00000000`a0f77bc0 : 00000001`d9d56768 00000001`469ac296 e4ba4333`36c222fc 00000000`00000d18 : 0x158

    00000000`3414f790 00000001`d9d56768 : 00000001`469ac296 e4ba4333`36c222fc 00000000`00000d18 00000001`d9d8c620 : 0xa0f77bc0

    00000000`3414f798 00000001`469ac296 : e4ba4333`36c222fc 00000000`00000d18 00000001`d9d8c620 00000001`b4852330 : 0x00000001`d9d56768

    00000000`3414f7a0 e4ba4333`36c222fc : 00000000`00000d18 00000001`d9d8c620 00000001`b4852330 00000001`435af2a0 : bfv+0x69ac296

    00000000`3414f7a8 00000000`00000d18 : 00000001`d9d8c620 00000001`b4852330 00000001`435af2a0 00000000`00000000 : 0xe4ba4333`36c222fc

    00000000`3414f7b0 00000001`d9d8c620 : 00000001`b4852330 00000001`435af2a0 00000000`00000000 00000001`b48522c0 : 0xd18

    00000000`3414f7b8 00000001`b4852330 : 00000001`435af2a0 00000000`00000000 00000001`b48522c0 00000001`4047beb5 : 0x00000001`d9d8c620

    00000000`3414f7c0 00000001`435af2a0 : 00000000`00000000 00000001`b48522c0 00000001`4047beb5 00000001`b4852330 : 0x00000001`b4852330

    00000000`3414f7c8 00000000`00000000 : 00000001`b48522c0 00000001`4047beb5 00000001`b4852330 00000000`00000000 : 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

    ---------


Sign In or Register to comment.