Emulator Issues #10348
closed
FrameBufferManager crash when change internal resolution on Mario Kart Wii
0%
Description
Game Name?
Mario Kart Wii
Game ID? (right click the game in the game list, properties, info tab)
RMCP01
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
b43c4b93211278259e7dca8ba20cf926
What's the problem? Describe what went wrong.
After change some times internal resolution (5 times between native and 5x ), I got a crash of dolphin with an avertissement pop-up before.
What steps will reproduce the problem?
Launch Mario Kart Wii, go to save selection screen, change IR many times.
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?
5.0-4432
What are your PC specifications? (CPU, GPU, Operating System, more)
Intel Core i7 - 3630QM | AMD Radeon HD 7500M/7600M Series | Windows 10 x64
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
Screenshot in attachment
Files
Updated by xerxes over 7 years ago
- File 69-GW7E-James Bond__3a__ Agent Under Fire.gci 69-GW7E-James Bond__3a__ Agent Under Fire.gci added
The same bug happens in 007 Agent Under Fire (GW7E69). I switched over to D3D11 from OpenGL to do performance comparisons on the driving stage Dangerous Pursuit, and that stage seems to always lock up Dolphin with the same message, but "hr=0x887a0005". It's a pretty terrible crash as when it happens not only does Dolphin completely crash but my whole PC freezes for a moment and Windows gives me a notification that it also crashed the graphics driver, but it self recovered. The driver Windows gives is "Display driver NVIDIA Windows Kernel Mode Driver, Version 378.49" (my GPU is an NVIDIA GeForce GTX 1060 6GB). I tried to bisect, but D3D still doesn't work on builds going as far back as the 4.0-2000s. OpenGL works fine, however.
Below are pictures of Dolphin's and Windows' error messages. I attached a save with the stage unlocked in case it's needed as well.
https://i.gyazo.com/a2ac92db0a241fedd6ca8bc5d3c5aee9.png
https://i.gyazo.com/5972943053565921bcb084e136bf2d95.png
Updated by JMC4789 about 7 years ago
- Assignee set to Stenzek
This is a graphics driver crash that I haven't been able to reproduce yet. I can assign this to stenzek, but as he's busy there's no guarantee that he'll get to it anytime soon.
Updated by xerxes about 7 years ago
As an update to my comment, Windows 10 recently forced an upgrade and it seems to have come with new graphics drivers which are now avoiding the crash. However, playing Dangerous Pursuit on D3D still crashes Dolphin with the same message, it just doesn't also crash the graphics driver in the process anymore.
Updated by JMC4789 about 2 years ago
- Status changed from New to Fixed
- Assignee deleted (
Stenzek)
This should be fixed by now on supported graphics cards. I'm not sure if those graphics cards count as supported based on their feature support.