Attention: The August update to RIVEN updated the game to build 1.3.0., and players report this resolved crash issues. If you are still experiencing crashes after updating to build 1.3.0., please read and follow the directions in this FAQ below.
___

Cyan is working on a patch to alleviate this issue in RIVEN, but the issue is generally resolved by making the runtime adjustment workaround noted in the linked FAQ below.

If you’re on a Windows machine, specific CPUs have a hardware issue that cause a crash on startup or when loading.

“RAD has become aware of a problem that can cause Oodle Data decompression failures, or crashes in games built with Unreal. We believe that this is a hardware problem which affects primarily Intel 13900K and 14900K processors, less likely 13700, 14700 and other related processors as well. Only a small fraction of those processors will exhibit this behavior. The problem seems to be caused by a combination of BIOS settings and the high clock rates and power usage of these processors, leading to system instability and unpredictable behavior under heavy load.”

Unfortunately, this isn’t anything Cyan can fix on our end. You may have also encountered this in other games made with Unreal Engine 5. It’s about how your CPU interacts with software a part of Unreal, and as noted in linked FAQ above, Epic Games is aware of the issue and can only suggest the workarounds as the solve for this at this time.

You can find more information on the issue here, in addition to workarounds: https://cyan.com/docs/riven-launches-but-closes-never-gets-to-the-menu-sometimes-shows-an-error-message/

If you are unsatisfied with the workarounds, please reach out to your hardware manufacturer and Epic Games.

APP HANGS ON STARTUP: If you are experiencing a crash or hang on startup outside of the scenario described above, and if you have a customized or older VR setup with options you can’t recall whether or not you’ve turned on or off, please disable the “motion compensation layer” in your OpenXR backend settings. This applies to the game running in 2D mode as well. This appears to be an engine bug prevalent in our version of Unreal.