Emulator Issues #12042

Dolphin fully freezes windows 10, requiring restart, when playing specific Donkey Kong Country Returns with D3D12 Backend

Added by Kirian 6 months ago. Updated 5 months ago.

% Done:


Operating system:
Issue type:
Relates to usability:
Relates to performance:
Relates to maintainability:
Regression start:
Fixed in:


Game Name?

Donkey Kong Country Returns

Game ID? (right click the game in the game list, Properties, Info tab)

SF8E01 (0001000053463845)

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)


What's the problem? Describe what went wrong.

(tested at native resolution, 3x resolution, synchronous (non-ubershaders) and synchronous ubershaders, tested with and without the HD graphics pack)
On Windows 10, when playing the game on Direct3D 12 the game will freeze on stage 1-5 (Canopy cannons), mostly after the first checkpoint, though there was one time when it froze before it. After the game freezes, attempting to stop the emulation will not work. After some time with the game frozen, windows system will completely stop (testes by being on discord audio channel while at my tests. I could hear other people talking for some seconds after the game freezes, but all audio will stop after some time). If attempting to "Ctrl + Alt + Dell" with the game frozen, but before windows completely stops, the screen will go black and nothing will happen until windows completely freezes. In any case, after windows freezes the machines is required to be reseted.

What steps will reproduce the problem?

1) Set graphics backend as Direct3D 12
2) Start Donkey Kong Country Returns
3) select the level 1-5 (Canopy cannons)
4) Slowly advance the stage
5) Some time after the start, mostly after the first checkpoint, the game will freeze.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

Yes, tested on 11832.

Is the issue present in the latest stable version?

Not tested on Dolphin 5.0 Stable

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool and anyone who is building Dolphin on their own can use git bisect.)

[(Not tested)]

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here:

[No Graphical Glitch]

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

System: Windows 10 1903 (compilation 18362.720)
CPU: Core Intel i7 3770k (running at default clocks)
GPU: GTX 970 (Drivers: 445.75)
Memory: 2x4GB (8GB) DDR3
Motherboard: Asus P8z77-V LX

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

Save file for the game, along with screenshots of the used configuration:
Video showing the issue:

2-3 months ago, when I was beating the game, I remember being on this stage for almost half an hour tryng to find a puzzle piece and there were no issues, but I don't remember if I was using D3D12 at the time. Still, there is a chance that this problem is from recent versions. I also tested this stage on D3D11, OpenGL and Vulkan and, although I didn't tested extensively, I managed to beat the stage in those backends.


#1 Updated by Miksel12 5 months ago

I played the level a few times with D3D12 without any problems. Using W10 1909, R5 3600, GTX1060 442.36.

#2 Updated by Kirian 5 months ago

Miksel12 wrote:

I played the level a few times with D3D12 without any problems. Using W10 1909, R5 3600, GTX1060 442.36.

I'm still having the problem. Dolphin 11967, Win10 1909, Gtx 970 "445.87". I'm only posting here because I have never encountered this kind of problem in any game before.

#3 Updated by JMC4789 5 months ago

It sounds like a driver crash if Windows 10 is crashing, which means it's likely out of our control.

Also available in: Atom PDF