Make the crash report specific
Nixxes says crash reports are collected and passed to developers, and asks players to describe when/where the crash occurred in the report comment. Its pinned guidance also points to file verification and current game/driver updates before support contact.
| Report item | Useful detail | Privacy check |
|---|---|---|
| Trigger | Location, menu/action, repeatability and last step | Do not include unrelated personal details |
| Build | Game version and storefront | Do not assume another patch behaved the same |
| Recent change | Update, driver, overlay, resolution or mod if applicable | State it as timing, not proven cause |
| Evidence | Crash-report comment and support-request files if requested | Review usernames, paths and account identifiers |
References: Nixxes: Horizon Zero Dawn Remastered PC support request guidance · Nixxes/Guerrilla: Horizon Zero Dawn Remastered PC patch notes
Follow the PC support sequence
Keep each check reversible. Use the currently linked Nixxes support documentation for file verification and platform-specific driver steps; avoid deleting saves, disabling security software globally or applying a forum fix for a different patch.
- Record OS, game build/storefront, hardware basics, location/action and exact crash timing.
- When the crash-report window appears, describe the reproducible context in its comment field as Nixxes requests.
- Verify installed game files using the storefront's current feature and update the game/driver as the pinned support note directs.
- Restart and reproduce the same action once if safe; note whether the crash report reappears.
- Check current Nixxes patch notes for a matching known issue and platform/build before trying a workaround.
- If unresolved, submit a focused request with only support-requested files and redact personal paths/account data.
References: Nixxes: Horizon Zero Dawn Remastered PC support request guidance · Nixxes/Guerrilla: Horizon Zero Dawn Remastered PC patch notes · Horizon Zero Dawn Remastered Steam Discussions
Before you play
- PC Remastered scope confirmed.
- Crash trigger and build recorded.
- Crash-report comment describes when/where.
- Official file verification/update checks completed.
- Files reviewed for private identifiers before sharing.
Frequently asked questions
Does crash reporting mean support has fixed the problem?
No. Nixxes says reports inform the developers; the player still needs to follow support steps and verify the outcome.
Should I upload an entire save folder?
Only provide the files Nixxes requests and inspect them for personal information first.
Does this tool submit a crash report?
No. It is a local issue worksheet, not a crash handler or upload form.
Sources & revision notes
Editorial revision: November 7, 2026; not a gameplay test date. The reference notes identify source limits and version differences.
- Nixxes: Horizon Zero Dawn Remastered PC support request guidance (Official)
Pinned developer post says PC crash reports are collected and asks for contextual comments; it directs support requests to verify files/update game and drivers and request relevant evidence. This is specific to the PC Remastered community page.
- Nixxes/Guerrilla: Horizon Zero Dawn Remastered PC patch notes (Official)
Developer announcements document dated PC fixes, including Steam Input/controller changes, crashes and support escalation. The cited fixes are historical and build-specific; check the current patch notes before changing settings.
- Horizon Zero Dawn Remastered Steam Discussions (Community)
External user-generated PC discussion. Match patch, controller path, storefront and hardware; community reports are not official fixes.
November 7, 2026: first publication, organized Nixxes' PC crash-report guidance into a reproducible and privacy-aware checklist. No crash or support ticket was submitted.
How we research and correct guidesNo affiliate links or paid placement. Commercial disclosure.