Website: elexgame.com Follow us:
Follow @NordicGamesAT Follow
Close

Results 1 to 3 of 3

Thread: ELEX Crash

  1. #1
    Registered User
    Join Date
    Dec 2017
    Posts
    6

    Exclamation ELEX Crash

    Occasionally ELEX (v1.0.2847.0 Steam) PC crashes to desktop. Text version of Dump follows below.

    Also; on this run, when I loaded [Continue] the game the Quick Slot Bar was not working correctly (showed only Slot 1 and 4 as having assignments), had to Quick-Save, Quick-Load to get it back.

    Any ideas


    ========DUMP=================

    ELEX Dump - Crash 20171215
    ELEX v1.0.2847 on Win7 Pro 64bit desktop, nVidia GTX 770

    Analysis Summary

    Error

    Description Recommendation

    WARNING - DebugDiag was not able to locate debug symbols for C:\Windows\System32\KERNELBASE.dll, so the information below may be incomplete.

    In ELEX-423220-EDWARD-PC-20171215-091143.dmp the Module C:\Windows\System32\KERNELBASE.dll has caused an access violation exception (0xC0000005) when trying to write to memory location 0x40b03778 on thread 0
    Please follow up with the vendor of this Module, Microsoft Corporation, for further assistance with this issue.

    Analysis Details

    CrashHangAnalysis

    Report for ELEX-423220-EDWARD-PC-20171215-091143.dmp

    Type of Analysis Performed Combined Crash/Hang Analysis
    Machine Name
    Operating System Windows 7Service Pack 1
    Number Of Processors
    Process ID 8428
    Process Image D:\Steam\steamapps\common\ELEX\system\ELEX.exe
    Command Line
    System Up-Time 00:00:00
    Process Up-Time 00:27:23
    Processor Type X64
    Process Bitness 64-Bit

    Top 5 Threads by CPU time

    Note - Times include both user mode and kernel mode for each thread
    Extended thread information (including thread CPU times) is unavailable in this dump

    CLR Information

    Thread Report

    •Thread 5
    •6
    •7
    •8
    •18
    •19
    •20
    •21
    •22

    9 Threads (34% of all threads) have this same call stack.
    Note: Grouping of identical threads can be disabled in the 'Preferences' tab of the Analysis Options

    Thread 5 - System ID 8972

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    Thread 6 - System ID 7480

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    Thread 7 - System ID 8576

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    Thread 8 - System ID 8716

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    Thread 18 - System ID 9832

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    Thread 19 - System ID 6304

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    Thread 20 - System ID 9060

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    Thread 21 - System ID 7816

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    Thread 22 - System ID 3220

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwWaitForSingleObject+a
    KERNELBASE!WaitForSingleObjectEx+9c
    nvwgf2umx!OpenAdapter12+1d1edf
    nvwgf2umx!OpenAdapter12+1d1ddf
    nvwgf2umx!NVAPI_Thunk+4886c7
    nvwgf2umx!NVAPI_Thunk+48886e
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    •Thread 1
    •2

    2 Threads (7% of all threads) have this same call stack.
    Note: Grouping of identical threads can be disabled in the 'Preferences' tab of the Analysis Options

    Thread 1 - System ID 9796

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    Thread 2 - System ID 8592

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwWaitForSingleObject+a
    KERNELBASE!WaitForSingleObjectEx+9c
    ELEX+1e480
    ELEX+1fc80
    ELEX+2b6b5
    ELEX+2b6d9
    msvcr110!beginthreadex+107
    msvcr110!endthreadex+192
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    •Thread 11
    •12

    2 Threads (7% of all threads) have this same call stack.
    Note: Grouping of identical threads can be disabled in the 'Preferences' tab of the Analysis Options

    Thread 11 - System ID 636

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    Thread 12 - System ID 9336

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!NtWaitForKeyedEvent+a
    ntdll!RtlSleepConditionVariableCS+d4
    kernel32!SleepConditionVariableCS+28
    binkw64!BinkOpenXAudio28+54f5
    binkw64!BinkDoFrameAsyncWait+7ca
    binkw64!BinkWaitStopAsyncThreadsMulti+d1
    binkw64!BinkDoFrameAsyncWait+589
    binkw64!BinkOpenXAudio28+5122
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    Thread 0 - System ID 10916

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwGetContextThread+a
    KERNELBASE!local_unwind+108b1
    0x0012e030
    0x00000001
    0x908f89e0

    Thread 3 - System ID 10900

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwWaitForSingleObject+a
    KERNELBASE!WaitForSingleObjectEx+9c
    ELEX+1e3b0
    ELEX+5a7746
    msvcr110!beginthreadex+107
    msvcr110!endthreadex+192
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    Thread 4 - System ID 10052

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwWaitForSingleObject+a
    KERNELBASE!WaitForSingleObjectEx+9c
    nvwgf2umx!OpenAdapter12+1498f9
    nvwgf2umx!OpenAdapter12+1489ad
    nvwgf2umx!OpenAdapter12+140f8d
    nvwgf2umx!NVAPI_Thunk+a224a
    nvwgf2umx!NVAPI_Thunk+4886c7
    nvwgf2umx!NVAPI_Thunk+48886e
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    Thread 9 - System ID 9908

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwWaitForMultipleObjects+a
    ntdll!TpIsTimerSet+9f7
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    Thread 10 - System ID 5936

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwWaitForMultipleObjects+a
    KERNELBASE!GetCurrentProcess+40
    kernel32!WaitForMultipleObjects+b0
    nvwgf2umx!NVAPI_Thunk+83296
    nvwgf2umx!NVAPI_Thunk+a224a
    nvwgf2umx!NVAPI_Thunk+4886c7
    nvwgf2umx!NVAPI_Thunk+48886e
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    Thread 13 - System ID 9032

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwWaitForWorkViaWorkerFactory+a
    ntdll!RtlValidateHeap+155
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    Thread 14 - System ID 10880

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwWaitForSingleObject+a
    KERNELBASE!WaitForSingleObjectEx+9c
    ELEX+1e480
    ELEX+2abaac
    ELEX+2abd24
    msvcr110!beginthreadex+107
    msvcr110!endthreadex+192
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    Thread 15 - System ID 9896

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwWaitForSingleObject+a
    KERNELBASE!WaitForSingleObjectEx+9c
    ELEX+1e480
    ELEX+2abaac
    ELEX+2abd03
    msvcr110!beginthreadex+107
    msvcr110!endthreadex+192
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    Thread 16 - System ID 10956

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwWaitForMultipleObjects+a
    KERNELBASE!GetCurrentProcess+40
    kernel32!WaitForMultipleObjectsEx+b3
    user32!GetScrollBarInfo+1dd
    user32!MsgWaitForMultipleObjectsEx+2e
    MMDevAPI!Ordinal9+1d96
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    Thread 17 - System ID 10156

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!NtWaitForKeyedEvent+a
    ntdll!RtlSleepConditionVariableCS+d4
    kernel32!SleepConditionVariableCS+28
    binkw64!BinkOpenXAudio28+54f5
    binkw64+3e28
    binkw64!BinkOpenXAudio28+5122
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    Thread 23 - System ID 664

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwDelayExecution+a
    KERNELBASE!SleepEx+b3
    fmod64!FMOD_File_SetDiskBusy+ce9a
    fmod64!FMOD_File_SetDiskBusy+417a
    fmod64!FMOD_File_SetDiskBusy+cca6
    fmod64!FMOD::SystemI::createMemoryFile+18d7b
    fmod64!FMOD::SystemI::createMemoryFile+18f22
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21


    Thread 24 - System ID 10096

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwWaitForSingleObject+a
    KERNELBASE!WaitForSingleObjectEx+9c
    fmod64!FMOD_File_SetDiskBusy+11e0b
    fmod64!FMOD_File_SetDiskBusy+4161
    fmod64!FMOD_File_SetDiskBusy+cca6
    fmod64!FMOD::SystemI::createMemoryFile+18d7b
    fmod64!FMOD::SystemI::createMemoryFile+18f22
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    Thread 25 - System ID 10752

    This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

    ntdll!ZwWaitForSingleObject+a
    KERNELBASE!WaitForSingleObjectEx+9c
    ELEX+1e480
    ELEX+27210c
    ELEX+1579f
    msvcr110!beginthreadex+107
    msvcr110!endthreadex+192
    kernel32!BaseThreadInitThunk+d
    ntdll!RtlUserThreadStart+21

    Exception Information

    WARNING - DebugDiag was not able to locate debug symbols for C:\Windows\System32\KERNELBASE.dll, so the information below may be incomplete.

    In ELEX-423220-EDWARD-PC-20171215-091143.dmp the Module C:\Windows\System32\KERNELBASE.dll has caused an access violation exception (0xC0000005) when trying to write to memory location 0x40b03778 on thread 0

    Module Information

    Image Name: C:\Windows\System32\KERNELBASE.dll Symbol Type: Export
    Base address: 0x00000003`00905a4d Time Stamp: Wed Sep 13 08:30:50 2017
    Checksum: 0x00000000`00000000 Comments:
    COM DLL: False Company Name: Microsoft Corporation
    ISAPIExtension: False File Description: Windows NT BASE API Client DLL
    ISAPIFilter: False File Version: 6.1.7601.23915 (win7sp1_ldr.170913-0600)
    Managed DLL: False Internal Name: Kernelbase
    VB DLL: False Legal Copyright: © Microsoft Corporation. All rights reserved.
    Loaded Image Name: KERNELBASE.dll Legal Trademarks:
    Mapped Image Name: C:\Windows\System32\KERNELBASE.dll Original filename: Kernelbase
    Module name: KERNELBASE Private Build:
    Single Threaded: False Product Name: Microsoft® Windows® Operating System
    Module Size: 424 KBytes Product Version: 6.1.7601.23915
    Symbol File Name: KERNELBASE.dll Special Build: &

  2. #2
    Registered User
    Join Date
    Dec 2017
    Posts
    6

    Update

    I am now in Chapter 3 and have had 2 more crashes as stated in original post.

    I now recognize this type of crash, it's what I call an "Object Collision" crash, from games in the past.

    Object Collision Crash:

    This crash is caused when a game generates 2 or more objects at the same coordinates. This can happen is very high performance systems.

    REF: My rig; Win7 Pro 64bit, Intel Core i5 (quad core) @ 3.50GHz, Memory 8 gigabyte DDR3 high speed, 4 terabyte hybrid SATA hard drive with SSHD buffer, nVidia GeForce GTX 770 with 2k Memory & 1536CUDA Cores, 1046MHz clock

    With these high speed specs, which includes the SSHD that acts as a buffer, means everything runs in memory, which means very fast.

    This results that games that do not have very good code to prevent this type of system from generating objects at the same coordinates can do so and cause a crash.

    The only way around this (verified) is do not use Sprint in areas where NPCs can pop up and use for short periods, and walking is best in outdoor environments.

  3. #3
    Registered User
    Join Date
    Dec 2017
    Posts
    2

    Crashes after last update

    Hey.
    I'm getting crashes every time at launch, right after intros. Reinstalled game, vcredist directory, drivers and still crashing.
    Specs: Win 10 64bit, core-i5 2500k, 8gb ram, gtx1070. GeForce exp. not installed, tried to disable all overlays.
    https://www.dropbox.com/s/7l1cfjs27j...71650.dmp?dl=0 - latest dump file

    It's pretty annoying, because i became a legat just before the patch -_-
    Any thoughts how to fix it?

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •