Announcement

Collapse
No announcement yet.

Robo Recall Crashing When Choosing a Level

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [OCULUS] Robo Recall Crashing When Choosing a Level

    I'm running Robo Recall on Oculus

    i7 7700k
    GTX 1060 6GB
    16GB DDR3 RAM

    I submit a crash report each time the game crashes, however I'm not sure where they go, or if there's a knowledgebase being built around them. So, if a dev is listening, and if you could take a look, I'd appreciate it!

    Notable items from .dmp:

    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
    Online Crash Dump Analysis Service
    See http://www.osronline.com for more information
    Windows 8 Version 14393 MP (8 procs) Free x64
    Product: WinNt, suite: SingleUserTS
    kernel32.dll version: 10.0.14393.0 (rs1_release.160715-1616)
    Machine Name:
    Debug session time: Sat Mar 4 00:07:44.000 2017 (UTC - 5:00)
    System Uptime: not available
    Process Uptime: 0 days 0:14:30.000
    Kernel time: 0 days 0:00:28.000
    User time: 0 days 0:14:49.000
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\oca.ini, error 2
    TRIAGER: Could not open triage file : e:\dump_analysis\program\winxp\triage.ini, error 2
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\user.ini, error 2
    *** WARNING: Unable to verify timestamp for ntdll.dll
    *** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
    *******************************************************************************
    * *
    * Exception Analysis *
    * *
    *******************************************************************************

    *** WARNING: Unable to verify timestamp for RoboRecall-Core-Win64-Shipping.dll
    *** ERROR: Module load completed but symbols could not be loaded for RoboRecall-Core-Win64-Shipping.dll
    ***** OS symbols are WRONG. Please fix symbols to do analysis.

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\guids.ini, error 2
    Unable to load image C:\Windows\System32\ole32.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ole32.dll
    *** ERROR: Module load completed but symbols could not be loaded for ole32.dll
    *** WARNING: Unable to verify timestamp for LibOVRPlatform64_1.dll
    *** ERROR: Module load completed but symbols could not be loaded for LibOVRPlatform64_1.dll
    *** WARNING: Unable to verify timestamp for LibOVRP2P64_1.dll
    *** ERROR: Module load completed but symbols could not be loaded for LibOVRP2P64_1.dll
    *** WARNING: Unable to verify timestamp for LibOVRRT64_1.dll
    *** ERROR: Module load completed but symbols could not be loaded for LibOVRRT64_1.dll
    *** WARNING: Unable to verify timestamp for RoboRecall-PakFile-Win64-Shipping.dll
    *** ERROR: Module load completed but symbols could not be loaded for RoboRecall-PakFile-Win64-Shipping.dll
    *** WARNING: Unable to verify timestamp for nvwgf2umx.dll
    *** ERROR: Module load completed but symbols could not be loaded for nvwgf2umx.dll
    *** WARNING: Unable to verify timestamp for RoboRecall-Messaging-Win64-Shipping.dll
    *** ERROR: Module load completed but symbols could not be loaded for RoboRecall-Messaging-Win64-Shipping.dll
    *** WARNING: Unable to verify timestamp for d3d11.dll
    *** ERROR: Module load completed but symbols could not be loaded for d3d11.dll
    *** WARNING: Unable to verify timestamp for mctux.dll
    *** ERROR: Module load completed but symbols could not be loaded for mctux.dll
    *** WARNING: Unable to verify timestamp for RoboRecall-RenderCore-Win64-Shipping.dll
    *** ERROR: Module load completed but symbols could not be loaded for RoboRecall-RenderCore-Win64-Shipping.dll
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    *** The OS name list needs to be updated! Unknown Windows version: 10.0 ***

    FAULTING_IP:
    KERNELBASE+17788
    00007ff9`ac877788 488b8c24c0000000 mov rcx,qword ptr [rsp+0C0h]

    EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 00007ff9ac877788 (KERNELBASE+0x0000000000017788)
    ExceptionCode: 00000001
    ExceptionFlags: 00000000
    NumberParameters: 0

    PROCESS_NAME: RoboRecall-Win64-Shipping.exe

    ADDITIONAL_DEBUG_TEXT:

    Use '!findthebuild' command to search for the target build information.

    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    FAULTING_MODULE: 00007ff9af510000 ntdll

    DEBUG_FLR_IMAGE_TIMESTAMP: 58b4f989

    ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1

    EXCEPTION_CODE: (Win32) 0x1 (1) - Incorrect function.

    FAULTING_THREAD: 0000000000001bb8

    BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS_INVALID_POINTER_READ_AFTER_CALL

    PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS_AFTER_CALL

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS_AFTER_CALL

    IP_ON_HEAP: 00000003a8c1b000
    The fault address in not in any loaded module, please check your build's rebase
    log at \bin\build_logs\timebuild\ntrebase.log for module which may
    contain the address if it were loaded.

    FRAME_ONE_INVALID: 1

    LAST_CONTROL_TRANSFER: from 00000003a8c1b000 to 00007ff9ac877788

    STACK_TEXT:
    00000073`f24cc0f0 00000003`a8c1b000 : 00000000`00000400 00000073`f24cca70 00007ff9`6c4127b8 00000000`00000001 : KERNELBASE+0x17788
    00000073`f24cc0f8 00000000`00000400 : 00000073`f24cca70 00007ff9`6c4127b8 00000000`00000001 00000000`00000000 : 0x3`a8c1b000
    00000073`f24cc100 00000073`f24cca70 : 00007ff9`6c4127b8 00000000`00000001 00000000`00000000 00007ff9`ac877788 : 0x400
    00000073`f24cc108 00007ff9`6c4127b8 : 00000000`00000001 00000000`00000000 00007ff9`ac877788 00007ff9`00000000 : 0x73`f24cca70
    00000073`f24cc110 00000000`00000001 : 00000000`00000000 00007ff9`ac877788 00007ff9`00000000 00000000`00000000 : RoboRecall_Core_Win64_Shipping+0x3a27b8
    00000073`f24cc118 00000000`00000000 : 00007ff9`ac877788 00007ff9`00000000 00000000`00000000 00000000`00000001 : 0x1


    STACK_COMMAND: ~1s; .ecxr ; kb

    FOLLOWUP_IP:
    RoboRecall_Core_Win64_Shipping+3a27b8
    00007ff9`6c4127b8 ?? ???

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: roborecall_core_win64_shipping+3a27b8

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: RoboRecall_Core_Win64_Shipping

    IMAGE_NAME: RoboRecall-Core-Win64-Shipping.dll

    BUCKET_ID: WRONG_SYMBOLS

    FAILURE_BUCKET_ID: WRONG_SYMBOLS_AFTER_CALL_1_RoboRecall-Core-Win64-Shipping.dll!Unknown

    Followup: MachineOwner
    ---------
    Fatal error: [File:\Build\++RR\Sync\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp] [Line: 933] &nl;GameThread timed out waiting for RenderThread after 30.00 secs&nl;
    0

    4
    8
    1
    GenuineIntel
    Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
    NVIDIA GeForce GTX 1060 6GB
    Windows 10

    17105584128
    140737488224256
    65536
    16
    7415451648
    140729489027072
    2462547968
    4116914176
    7374536704
    7500308480
    0
    0
    0


    1
    0


    3++S++
    The operation completed successfully.
    3++S++
    3++S++
    Assertion failed: Assertion failed: [File:\Build\++RR\Sync\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp] [Line: 933]
    GameThread timed out waiting for RenderThread after 30.01 secs
    Fatal error: [File:\Build\++RR\Syn
    e\Runt
    D:\Build\++RR\Sync\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp
    Assertion failed:
    D:\Build\++RR\Sync\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp
    GameThread timedGameThread timed out waiting for RenderThread after 30.01 secs
    .&$]"D
    Microphone (Ri
    Audio)
    .{c24dde47-c798-4e6d-89b2-82d84e8af0d3}
    Microphone (Rift Audio)
    !ti>}gi?3
    \StringFileInfo\040904b0\FileVersion
    Eastern Standard Time
    Eastern Daylight Time
    10.0.14393.206 (rs1_release.160915-0644)
    dbgcore.amd64,10.0.14321.1024
    2\dbgc
    UE4CC-Windows-5FBB675D474830815C41EFB31F1B2DE9_0000

    #2
    My game also crashes during the loading screen whenever i select mission 1-2. Hoping I can find some info because the game was really fun so far. Very frustrating!

    Comment


      #3
      unreal process has crashed ue4-roborecall

      Originally posted by jbonez1983 View Post
      My game also crashes during the loading screen whenever i select mission 1-2. Hoping I can find some info because the game was really fun so far. Very frustrating!
      I too have the same error, does not load mission 1-2 "short circuit", but i can run 2 other unlocked missions I have, 1-1 and 2-1 . I uninstalled and reinstalled the game, but the error is still there,

      Comment


        #4
        Yea, with the new mods I can skip ahead so I know the other missions work (or at least most of them anyway) So its definitely something with that particular mission. With that said, while the mods are fun they shut off the leaderboards/score from being counted which obviously is also a big part of the games appeal. Really frustrating, its been almost 2 weeks no sign of it getting fixed, and it just so happens to be the best game on the entire platform.

        Comment


          #5
          Originally posted by jbonez1983 View Post
          Yea, with the new mods I can skip ahead so I know the other missions work (or at least most of them anyway) So its definitely something with that particular mission. With that said, while the mods are fun they shut off the leaderboards/score from being counted which obviously is also a big part of the games appeal. Really frustrating, its been almost 2 weeks no sign of it getting fixed, and it just so happens to be the best game on the entire platform.

          Honestly, that's good to know that you can skip ahead using the mods. I guess I'll have to rely on third party to get me into the next missions, since Unreal support is so abysmal lol.

          Comment

          Working...
          X