How to post a Bug Report

Bug Reports
20

Handling hyperion related solutions

NOTE: This text has been drawn from ‘Hyperion related solutions’ - for the original post, see here: https://devforum.roblox.com/t/hyperion-related-solutions/2322367

The document reads as follows:

"This short write-up is an attempt to have a centralized document that we can link to when guidance is needed.

Mini Q&A:

Q: Why is my Roblox player crashing?

A: There are basically two major categories of crashes:

  1. Crashes due to bugs in the Roblox player.

  2. Crashes induced by Hyperion due to the detection of unusual access to the Roblox player process.

Q: How can I distinguish between a Hyperion crash and a crash caused by Roblox player bugs?
A: Hyperion-induced crashes happen typically rather quickly right after starting the Roblox player.

If you suspect a Hyperion crash, what should you do?

Hyperion is rather strict when other processes attempt to access the address space belonging to the Roblox player, as this sort of behavior is typically a hallmark of malicious software. However, there is quite a high number of programs that are generally not malicious but demand unreasonable access rights to the process space of our Roblox player.

A typical example is tools simply needing to query statistics from processes in the system but, rather than opening the process with humble PROCESS_QUERY_LIMITED_INFORMATION access rights, attempting to open the process with PROCESS_ALL_ACCESS.

It is important to point out that proper digitally signed software is not subject to limited access. The keyword here is “proper,” as signatures can be outdated or otherwise invalid. In other words, the simple presence of a signature is not necessarily a guarantee that the signature is accepted.

To find the offending process, there are several strategies:

Strategy one:

  1. Terminate all processes and Windows services that are not absolutely necessary and try to rerun the Roblox player again.

  2. If the Roblox player runs, try starting the usual programs and Windows services one by one until the Roblox player crashes again.

Strategy Two:

Perform a clean boot as described by Microsoft and rerun the Roblox player.

support.microsoft.com

How to perform a clean boot in Windows - Microsoft Support

Describes how to use the clean boot process to troubleshoot a problem in Windows 8.1, Windows 8, Windows 7, or Windows Vista.

Strategy Three:

Enable full crash dump for the Roblox crash uploader by following these simple steps:

  1. Create a file %LOCALAPPDATA%\Roblox\Versions<your-current-client-version-here>\ClientSettings\ClientAppSettings.json.

  2. Open the newly created file and add the following: {"DFIntWriteFullDmpPercent": 100}

  3. Rerun the Roblox player and let it crash.

  4. File a bug report as outlined here and attach the crash report as well as all log files to the report.

Strategy Four:

Use ProcDump to create a crash dump by following these steps:

  1. Download and extract ProcDump: ProcDump - Sysinternals | Microsoft Learn 25.

  2. Create a folder called dumps (e.g., C:\dumps).

  3. Open an elevated command prompt where you extracted procdump and run this command: procdump -ma -i C:\dumps. Click Yes if any prompts appear.

  4. Now run Roblox player again, and it will automatically create a crash dump in C:\dumps. You can send us one of the dumps that are created there (there will likely be two of the same crash).

We hope this helps, and as always, please don’t hesitate to reach out to us. Thank you for your patience."

371 Likes