Your first CRASQ diagnosis: session, report and support
Published 22 October 2026. Steps for collecting evidence; results depend on your installation and the profile coverage.
1. Choose a game and check profile coverage
After installation, open the library and choose a game. Check whether its profile is developed or preliminary. Basic local diagnostics does not require an account; telemetry is optional.
2. Reproduce the issue with monitoring
Start the game and note what leads to the issue. Review the session result after exiting. If CRASQ asks for confirmation, report the actual outcome: normal exit, crash or instability. Missing temperature or FPS data alone does not indicate a failure.
3. Review evidence and choose a next step
Open the report and check confidence and limitations. Back up files before making changes. For support, include the CRASQ version, game, issue time and reproduction steps.
Share reviewed content only
A diagnostic package is created locally. Open and review it before sending, even though private data masking is applied. Do not include passwords, tokens, keys or private correspondence. Use the Support section to contact the project.
Continue
Download and release status · Contact support · Privacy policy