Independent community database.

Grand Theft Auto V

Issues

PPSA04264 · Windows · Los Santos open-world Story save: three 420-second runs without the previously reproduced HDD Streamer crash when Relinker framing is explicitly enabled

Current conclusion

Windows main c8d34aa8f with merged PR #5640 and the explicit Relinker --frame-red-zone option was tested on GTA V PPSA04264 Story Mode: three 420-second Los Santos open-world runs on Windows 11/RTX 4090 finished without the formerly repeatable HDD Streamer crash, despite 1,030–1,186 resumed write faults in each run.

This is a controlled, opt-in main-source result, not behavior of the v0.1.3 tagged release or a default unframed conversion; unrelated game blockers and full-game completion remain untested.

The 23 October merged voice-worker PR #9730 separately reached the North Yankton prologue at 22–27 presents per ten seconds, and an older experimental fork recorded 21.4 FPS; those environments must not be mixed.

Grand Theft Auto VPS5
Grand Theft Auto V — promotional gameplay screenshot

Platform test results

Windows · North Yankton prologue gameplay on older testing branch

Issues

An older experimental branch enters the North Yankton bank sequence with dialogue, music, HUD and rendered world; the reporter observed roughly 27–28 FPS in the bank.

Build: gta-v/testing (based on main before #639); distinct current-main run d70b899
Report: Oct 9, 2026

Windows branch and current-main comparison ↗

Windows · Story Mode gameplay with correct rendering on experimental 21.4 FPS POC

Issues

On one prototype stack, Story Mode renders correctly with an average 21.4 FPS over 66 seconds (21.1–21.6 FPS per 10-second slice). Intermediate steps separately measured 8.4, 12.0, 15.3 and 17.9 FPS; these include graphics-mode and implementation changes, so the 1-to-21 FPS progression is not a stock-main comparison.

Build: tibzejoker/AnyPS5 gtav-next11-poc34: main plus PRs #757, #448 port, #1186, #1189 and unreleased local GPU/CPU optimizations
Report: Oct 16, 2026

Windows GTA V Story FPS optimization comparison (Oct 16; updated Oct 17) ↗

Windows · Story Mode open-world save loads in Los Santos; HDD Streamer crashes from resumed memory write fault

Issues

On main f6ce8e34a an open-world Story Mode save triggers over 400 resumed write faults, including about 60 in GTA V's zlib code, and crashes on all seven tested runs with an unhandled 0xc0000005 access violation in [RAGE] HDD Streamer.

The reporter traced a resumed fault corrupting stack red-zone bytes that inflate_fast later reloads as pointers.

An Oct 17 main revision showed zero such resumed faults during 240 s. Disabling deferred settles on a separate Oct 21 main revision removed zlib faults and avoided a crash for 150 s, but other memory faults remained and this is a targeted diagnostic A/B, not an upstream cure.

Build: Unmodified Windows main f6ce8e34a (20 Oct): 7/7 crashes; main 275e89679 (21 Oct): further resident faults; 17 Oct main 47a266cf9 control ran 240 s without crash. Temporary diagnostic instrumentation used to count resumed faults.
Report: Oct 21, 2026

October 21 GTA V Windows main red-zone crash and fault-count bisect (#9136) ↗

Windows · Main+PR #9730 reaches title, Resume Story and North Yankton player movement; later open-world crash remains

Issues

Six Story Mode test runs of 600–900 s compared main and PR candidate. Main fails at sceVoiceSetThreadsParams with priority 700 and affinity 0x7f for three workers: 2/2 runs stopped at 271 s cold caches or 14 s warm caches.

With PR #9730's validated range handling the title starts, presents its main menu, resumes Story and allows scripted player movement in North Yankton at 22–27 presents per 10 s.

The separate red-zone/write-watch fault tracked in issue #9136 can still occur in the prologue on that machine; the PR is not an open-world fix.

Build: main 7e2ba73e4 versus same main + PR #9730, merged into main at 2026-10-23 01:01 UTC; PR branch A/B, not v0.1.3
Report: Oct 23, 2026

23 October GTA V Windows voice worker A/B against main, with unresolved #9136 follow-on crash ↗

Windows · Los Santos open-world Story save: three 420-second runs without the previously reproduced HDD Streamer crash when Relinker framing is explicitly enabled

Issues

Three repeats from the same open-world save ran for 420 seconds each without an HDD Streamer crash despite 1,030, 1,166 and 1,186 resumed write faults; at least 15, 16 and 16 respectively were logged in inflate_fast. Relinker reported 243 framed leaves out of 991 candidates. The issue was closed after this retest. Earlier unframed builds could crash following a single such resumed fault.

Build: upstream main c8d34aa8f including merged PR #5640 (d01070d6c3) and #9159; Relinker --windows --to-intel --frame-red-zone (opt-in, not default); local per-RIP fault log for diagnosis; APS5_MIMALLOC=1
Report: Oct 24, 2026

24 October current-main Windows --frame-red-zone retest and issue closure ↗

Known issues

Windows · North Yankton prologue gameplay on older testing branch

  • Current main alone stops at boot; open PRs reach first startup frames but then stop at a bindless material-table image read.
  • Ray-tracing modes render only at a few FPS on the older branch.

Windows · Story Mode gameplay with correct rendering on experimental 21.4 FPS POC

  • The prototype uses local experimental changes and an upstream PR stack, not the tagged release or unmodified main; its author reports occasional DEVICE_LOST when registry refresh is enabled.
  • Most of the 21.4 FPS gain depends on proposed recording threads, shader math choices and memory/TLS changes that are not deployed as one production-ready patch.

Windows · Story Mode open-world save loads in Los Santos; HDD Streamer crashes from resumed memory write fault

  • Windows write-watch fault resumption can overwrite a title's x86-64 stack red-zone state and crash the streaming thread after an open-world save loads.
  • The reporter associates the new armed ranges with #6678 and #7473 and still has unexplained remaining faults; no fully validated merged fix or stable-release confirmation is documented.

Windows · Main+PR #9730 reaches title, Resume Story and North Yankton player movement; later open-world crash remains

  • The fix handles only valid priority/affinity request values; no actual voice workers or host scheduling are implemented.
  • The source still reproduces the open-world red-zone/write-watch crash (#9136) on the patched test setup, so current merged main is not officially Playable or complete.

Windows · Los Santos open-world Story save: three 420-second runs without the previously reproduced HDD Streamer crash when Relinker framing is explicitly enabled

  • The protection requires --frame-red-zone when converting for Windows; older unframed executables remain susceptible. The tagged v0.1.3 predates merged PR #5640.
  • Only three bounded open-world runs were checked. Some leaf functions are skipped by framing and other gameplay or rendering regressions were not validated as fixed.

Test environments

Platform
Windows
Game version
01.005
Hardware / tools
Windows 11 Pro; Ryzen 5 7600; RTX 5080; NVIDIA 32.0.16.1074
Platform
Windows
Game version
PPSA04264 PS5 Story Mode; Performance graphics mode
Hardware / tools
Windows; Core i9-13900K; RTX 4090 (NVIDIA 616.92); 2560x1440 internal / 4K output; warm caches
Platform
Windows
Game version
PPSA04264; exact content build not stated
Hardware / tools
Windows 11 build 26200; Intel Core i9-13900K; RTX 4090, NVIDIA 616.92; WinLibs GCC 15.2.0 r7; Release; write watch enabled
Platform
Windows
Game version
01.005.000
Hardware / tools
Windows 11 Pro; Intel Core i9-14900K; NVIDIA RTX 5080 driver 32.0.16.1742; WinLibs GCC 15.2.0 Release
Platform
Windows
Game version
PPSA04264 Story Mode; content version not specified for this retest
Hardware / tools
Windows 11; Intel Core i9-13900K; NVIDIA RTX 4090, driver 616.92

PPSA04264 PS5 Story Mode. The October 23 #9730 A/B uses content 01.005.000 on Windows main with a single voice-port patch; earlier #9136 uses a Los Santos Story save on a different Windows main revision, and the older 21.4 FPS run is a separate experimental fork. No GTA Online result is implied.