Emulator

Game Name?

Metroid Prime Trilogy (MP3: Corruption)

Game ID? (right click the game in the game list, properties, info tab)

R3ME01

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

823df1c3c425f1383529f368f6479359

What's the problem? Describe what went wrong.

Direct3D 12 Backend: Started a new game and reached the GFS Olympus Save Room without a crash, though there was persistently heavy Shader Compilation Stuttering on the way. I can now load this saved game, and while in D3D12, I can run around the Flag Bridge Room, shoot at most stuff with no problem. However, the game will crash if I (1) pull up the map screen by pressing the '1' button, or if I (2) shoot multiple power beam shots at the door that's sealed with a Blast Shield Lock (it's located in the 'Lift Access' corridor that you enter when you leave the Save Room). This is the type of door that deflects the beam shots back at Samus. Sometimes it takes only one shot at this door to crash the game, other times it may take up to 6-8 shots in quick succession, but it crashes reliably every time I've tried this in D3D12.

Direct3D 11 Backend: After D3D12 crashed a few times, I decided to try D3D11. The game crashed immediately (before the Wii remote advisory screen) the first 3-4 times that I tried D3D11. So I tried OpenGL (worked fine), then went back to D3D11, and suddenly D3D11 started to work perfectly. I've now loaded my saved game 5-6 times in D3D11 with no problems. Nothing I now do while playing the game in D3D11 will crash the game.

OpenGL Backend: Loads up without a problem. As with D3D11, nothing I do while playing will crash the game.

What steps will reproduce the problem?

Select Direct3D12 (other settings shown in screenshots). Exit GFS Olympus Save Room (thus entering the 'Lift Access' corridor) and shoot at the 'Blast Shield Lock' door on your right. Shoot at it multiple times with the energy beam so that several of the shots are deflected back at Samus. This causes the game crash. Alternatively, you can (2) press the '1' button to pull up the map. This will also produce a crash.

Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?

The above tests were all done in Dolphin 5.0. I initially encountered the crashes in D3D12 while using 5.0-240. As the crashing started (as described above), I reverted to 5.0. That's when I started testing D3D11 and OpenGL (in addition to re-testing D3D12).

What are your PC specifications? (CPU, GPU, Operating System, more)

CPU: Intel i7 3770K @ 4533 MHz
GPU: AMD Radeon 7970 (Core @ 1171 MHz & Memory @ 1650 MHz)
GPU Driver: Crimson 16.7.2
OS: Windows 10 Build 10586.494
RAM: 16GB DDR3 @ 1854 MHz

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

See Attached.