[GH-ISSUE #3988] [GAME BUG]: Taiko no Tatsujin: Drum Session! (CUSA11183) - Crash: Access Violation (0x10c1c00000) on Boot and Music Select #1195

New issue

Open

opened 2026-02-27 21:10:27 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 21:10:27 +03:00

Owner

Originally created by @LuisFellp on GitHub (Feb 2, 2026).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3988

Checklist (we expect you to perform these steps before opening the issue)

I have searched for a similar issue in this repository and did not find one.
I am using an official build obtained from releases or updated one of those builds using its in-app updater.
I have re-dumped the game and performed a clean install without mods and the issue is still present.
I have disabled all patches and cheats and the issue is still present.
I have all the required system modules installed.

Describe the Bug

The game is unstable and crashes with a critical signal error ("Unreachable code") resulting in an Access Violation at address 0x10c1c00000.

This crash occurs in two distinct scenarios:
Boot/Loading: The emulator crashes during the initial loading phase while loading system modules (e.g., libSceFontFt.sprx).

Music Select: If the game boots successfully, it consistently crashes when navigating to the "Music Select" menu. The log shows this happens following sceKernelMapNamedFlexibleMemory operations.

Reproduction Steps

Launch Taiko no Tatsujin: Drum Session! (CUSA11183) on shadPS4 v0.13.0.
Scenario A: Observe crash during the initial loading screen.
Scenario B: If the game reaches the main menu, navigate to the "Music Select" option.
The emulator will trigger a SignalHandler error and terminate immediately.

Specify OS Version

EndeavourOS / 6.18.7-zen1-1-zen

CPU

AMD Ryzen 7 5700X3D 8-Core Processor

GPU

AMD Radeon RX 9070 XT

Amount of RAM in GB

32GB

Amount of VRAM in GB

16GB

Log File

shad_log.txt

Originally created by @LuisFellp on GitHub (Feb 2, 2026). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3988 ### Checklist (we expect you to perform these steps before opening the issue) - [x] I have searched for a similar issue in this repository and did not find one. - [x] I am using an official build obtained from [releases](https://github.com/shadps4-emu/shadPS4/releases) or updated one of those builds using its in-app updater. - [x] I have re-dumped the game and performed a clean install without mods and the issue is still present. - [x] I have disabled all patches and cheats and the issue is still present. - [x] I have all the required [system modules](https://github.com/shadps4-emu/shadPS4/wiki/I.-Quick-start-%5BUsers%5D#4-dumping-firmware-modules) installed. ### Describe the Bug The game is unstable and crashes with a critical signal error ("Unreachable code") resulting in an Access Violation at address **0x10c1c00000**. This crash occurs in two distinct scenarios: Boot/Loading: The emulator crashes during the initial loading phase while loading system modules (e.g., libSceFontFt.sprx). Music Select: If the game boots successfully, it consistently crashes when navigating to the "Music Select" menu. The log shows this happens following **sceKernelMapNamedFlexibleMemory** operations. ### Reproduction Steps 1. Launch Taiko no Tatsujin: Drum Session! (CUSA11183) on shadPS4 v0.13.0. 2. Scenario A: Observe crash during the initial loading screen. 3. Scenario B: If the game reaches the main menu, navigate to the "Music Select" option. 4. The emulator will trigger a SignalHandler error and terminate immediately. ### Specify OS Version EndeavourOS / 6.18.7-zen1-1-zen ### CPU AMD Ryzen 7 5700X3D 8-Core Processor ### GPU AMD Radeon RX 9070 XT ### Amount of RAM in GB 32GB ### Amount of VRAM in GB 16GB ### Log File [shad_log.txt](https://github.com/user-attachments/files/24997926/shad_log.txt)

kerem commented

2026-02-27 21:10:27 +03:00

Author

Owner

@StevenMiller123 commented on GitHub (Feb 2, 2026):

This is an exception in our GPU thread, as is clear when looking at the error message.

[Debug] <Critical> signals.cpp:86 SignalHandler: Unreachable code!
Unhandled access violation in thread 'shadPS4:GpuComm' at code address 0x7f287c17b96e: Read from address 0x10b7400000

@StevenMiller123 commented on GitHub (Feb 2, 2026): This is an exception in our GPU thread, as is clear when looking at the error message. ``` [Debug] <Critical> signals.cpp:86 SignalHandler: Unreachable code! Unhandled access violation in thread 'shadPS4:GpuComm' at code address 0x7f287c17b96e: Read from address 0x10b7400000 ```

kerem commented

2026-02-27 21:10:27 +03:00

Author

Owner

@LuisFellp commented on GitHub (Feb 2, 2026):

Thanks for the clarification. Since it's an exception in the GPU thread, I have some additional context regarding the timing and memory addressing that might help narrow down the cause:

Timing/Execution Speed Dependency:
I've observed that the time-to-crash correlates directly with how fast I interact with the game.

-If I navigate menus/select songs slowly, the game runs for a significantly longer duration before crashing.
-If I navigate quickly or attempt to restart a song immediately, the crash happens much sooner.

Variable Fault Address:
While the error type (Unhandled access violation in shadPS4:GpuComm) remains the same, the specific address being accessed is changing slightly between sessions.

-Previous Log: Read from 0x10bd40000
-Current Log: Read from 0x10b7400000

This suggests the code is attempting to access a GPU buffer or texture that is either mapped inconsistently, corrupted over time, or subject to a race condition that is sensitive to execution speed.

shad_log.txt

@LuisFellp commented on GitHub (Feb 2, 2026): Thanks for the clarification. Since it's an exception in the GPU thread, I have some additional context regarding the timing and memory addressing that might help narrow down the cause: 1. Timing/Execution Speed Dependency: I've observed that the time-to-crash correlates directly with how fast I interact with the game. -If I navigate menus/select songs slowly, the game runs for a significantly longer duration before crashing. -If I navigate quickly or attempt to restart a song immediately, the crash happens much sooner. 2. Variable Fault Address: While the error type (Unhandled access violation in shadPS4:GpuComm) remains the same, the specific address being accessed is changing slightly between sessions. -Previous Log: Read from 0x10bd40000 -Current Log: Read from 0x10b7400000 This suggests the code is attempting to access a GPU buffer or texture that is either mapped inconsistently, corrupted over time, or subject to a race condition that is sensitive to execution speed. [shad_log.txt](https://github.com/user-attachments/files/24998107/shad_log.txt)