Report the exact crash
Add an anonymous platform signal or confirm that Version 4.4 works normally.
Open pageFrameReady news
Honkai: Star Rail 4.4 Crashes on Videos and Cutscenes: Live Report Tracker
Honkai: Star Rail Version 4.4 launched July 15. Several players report that the game crashes when it tries to play event, banner, or story media. HoYoverse had not acknowledged one shared cause in the official source checked at review time.
Bottom line
This is a real cluster of matching player reports, but its size and cause are not confirmed. Reports mention the event screen, Travel Log, banner animation, and an early story cutscene. Some PC crash logs point to media playback components, while at least one PlayStation 5 player describes freezing. There is no confirmed fix yet.
Evidence status
multiple community reports: FrameReady keeps news claims tied to sources so updates do not drift into guesses.
Current status
FrameReady is separating the official Version 4.4 release from the community-reported crash. A live game service does not prove every client can play the new media correctly.
| Check | Status |
|---|---|
| Version 4.4 | Officially live on July 15, 2026 |
| Matching crash reports | Yes, across several community posts |
| HoYoverse acknowledgement | None found for this specific crash at review time |
| Confirmed fix | None found |
| FrameReady tracker | Open for anonymous platform confirmations |
Sources: Official Version 4.4 information, FrameReady live tracker.
Where players say it crashes
The reports point to media playback rather than one normal combat scene. That is a useful pattern, but it does not prove the exact component or establish that every crash has the same cause.
- Opening the Version 4.4 event or Travel Log screen.
- Playing a banner animation.
- Starting an early Version 4.4 story cutscene.
- Logging back into a story sequence that immediately reaches the same crashing media.
- One report describes PlayStation 5 freezing while matching PC reports describe a client crash.
What to do without making it worse
There is no publisher-confirmed repair to prescribe. Preserve the crash evidence and avoid destructive troubleshooting while the trigger appears tied to new patch content.
- Do not delete game saves or edit the Windows registry.
- Record your platform, the exact screen or cutscene, and whether the game returns to the same crash after login.
- Use the launcher repair option only if you understand that matching reports continued after ordinary repair attempts.
- If the rest of the game remains usable, consider pausing the affected event or story content until HoYoverse publishes guidance.
- Send the game crash log through HoYoverse support. Do not post personal paths or account information publicly.
Why FrameReady is collecting reports
The live tracker can show whether reports cluster by platform and whether working-normal responses rise after a hotfix. It cannot inspect private crash logs or prove a root cause.
- Reports are optional and anonymous.
- The public page shows aggregate responses, not private notes or identifiers.
- Publisher acknowledgement stays separate from FrameReady community data.
- Small hardware and regional cohorts remain hidden.
Related next steps
Sources
- official: HoYoverse Version 4.4 update information. Confirms Version 4.4 content and its July 15 release. It did not acknowledge this crash in the source checked.
- inferred: Event and cutscene crash reports. Several players describe crashes around event, banner, and story video playback.
- inferred: Matching Unity crash reports. Independent report and replies describing the same post-update media trigger.
- inferred: Travel Log crash report. Matching community report from a separate subreddit.