Emulator Issues #11320
closedDolphin application quits without error when running Direct3D 11 backend on Intel HD 615 running latest July 10 2018 graphics drivers
0%
Description
Game Name?
Metroid Prime E
Metroid Prime v1.00 U
Mario Kart Wii E
Game ID? (right click the game in the game list, properties, info tab)
GM8P01
GM8E01
RMCP01 (00010004524d4350)
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
GM8P01 - b1379c44e0ebc521e18215de3e5dbeea (compressed to .gcz)
GM8E01 - eeacd0ced8e2bae491eca14f141a4b7c (no compression or alteration)
GM8E01 - 0d2ba934eec6a59ee1e155e0d039f194 (widescreen patched and frustum hex-edited, trimmed via Gamecube ISO Tool)
RMCP01 - bef977cb912d9caa0828219a18d72cd1 (compressed to .gcz)
What's the problem? Describe what went wrong.
On my GPD Win 2 using Intel HD 615 graphics and the Direct3D 11 backend, some games are prone to crashing or poor performance at specific spots, depending on the Intel graphics driver installed.
The nature of the crash is that Dolphin will quit completely with no error message.
Issues occur regardless of any other graphics settings tried, only reproducible variables have been the use of Direct3D 11, and certain graphics drivers.
When using older drivers (Version 23.20.16.4944 / Build Date February 8, 2018), affected parts may be very slow, running at half or quarter speed.
When using newer drivers (Version 24.20.100.6194 / Build Date July 10, 2018), affected parts may either run full speed without impact, or cause Dolphin to quit unexpectedly regardless of using Syncronous (not Ubershaders) or Asynchronous Shader Compilation (Ubershaders)
What steps will reproduce the problem?
- All issues occur when using Direct3D 11 graphics backend, not on OpenGL
For Metroid Prime (both EU and US)
- Start a new save game
- Intro text is drawn on screen: "Unidentified distress beacon has been tracked to derelict space vessel in orbit above Tallon IV."
- On old drivers, performance is not quite 100%, dipping to about 40FPS in gameplay. Syncronous or asyncronous shader compilation does not make any difference.
- On new drivers, after text is drawn then faded out, just before the fade-in to the opening scene, Dolphin quits unexpectedly.
- If you load a savegame that gets past this crash, performance is mostly 100%
For Mario Kart Wii
- With no save file, issue does not occur until creating the first license/save slot
- With pre-existing save file, issue can occur on title screen
- On old drivers, severe slowdown occurs in-menu but resolves itself when reaching character selection screen
- On new drivers, Dolphin quits unexpectedly
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
5.0-8494
5.0-8512
Is the issue present in the latest stable version?
Issue does not occur in stable 5.0 release with clean Dolphin Emulator config folder in My Documents.
On newest drivers, no crash will occur.
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: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
FIFO recording not possible due to emulator quitting upon reproduced issue
What are your PC specifications? (CPU, GPU, Operating System, more)
- GPD Win 2 / Windows 10 Home v1803
- Intel(R) Core(TM) m3-7y30 CPU @ 1.00GHz 1.61GHz
- Intel HD 615 Graphics
- 8.00 GB RAM
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Video example of Metroid Prime quitting before game intro:
https://www.youtube.com/watch?v=I8RhJb-KxQA
Video example of Mario Kart Wii quitting on new license screen:
https://www.youtube.com/watch?v=XHymfwY4WHI
See also attached Dolphin.ini file from my GPD Win 2
Files
Updated by Rupeeclock over 5 years ago
I'd like to add that I can test a variety of other Gamecube and Wii games if any further testing is required, and can co-operate with an investigation if the issue is not reproducible on your own hardware.
Updated by JMC4789 over 5 years ago
These sound like driver issues and not something caused by Dolphin. What you can do if you want to see if there's something we can fix it setup Dolphin to run from visual studio (aka, compile Dolphin yourself,) and run with a debugger attached. Then, when it crashes, it'll give you a bunch of information about what went wrong and we can see if there's something we can change on our side in order to avoid whatever's breaking the driver.
Updated by Rupeeclock over 5 years ago
- File dolphin-emu debugging frame not in module.png dolphin-emu debugging frame not in module.png added
- File dolphin-emu igc64.pdb not loaded.png dolphin-emu igc64.pdb not loaded.png added
Using Visual Studio I was able to successfully compile a DolphinD.exe debug build of 5.0-8545. Running this by itself it would crash at the same points as described enough.
I'm not familiar with debugging via Visual Studio itself, after building the binary, when starting debugging (F5), after launching Metroid Prime it would continuously break at exceptions like these:
Exception thrown at 0x0000024A099C507D in DolphinD.exe: 0xC0000005: Access violation writing location 0x0000024D4B606434.
Ignoring those I continued until the point of crash in Metroid Prime or in Mario Kart Wii, and this error occurred.
igc64.pdb not loaded:
Unhandled exception at 0x00007FFC2AB311E8 (igc64.dll) in DolphinD.exe: 0xC0000005: Access violation reading location 0x0000000000000018.
When this occurred, debugger could not continue.
igc64.dll is the Intel Graphics Shader Compiler for Intel(R) Graphics Accelerator, file version 24.20.100.6194, modified 10-Jul-18 15:59
So this at least suggests it is a shader bug with the Intel HD drivers, and would explain why the crash does not occur on 5.0 stable which has not had the extensive ubershaders development.
Hope this is of any help to you.
Updated by Rupeeclock over 5 years ago
The graphics drivers for this device were recently updated.
August 7, 2018
Driver Version 24.20.100.6229
These continue to experience crashes in the same way.
Updated by JMC4789 over 5 years ago
It's possible whatever feature they implemented is still broken. I don't have any other ideas as there've been no further reports of issues with the D3D backend.
Updated by Rupeeclock over 5 years ago
More recent graphics drivers updates for Intel HD 615 appear to have resolved this issue, including the most recent being version 25.20.100.6471 released December 20th 2018.
https://forums.intel.com/s/question/0D50P0000490URuSAM/dolphin-emulator-vulkan-crash?language=en_US
Specific issue is no longer reproducible on Dolphin 5.0-9213.
Updated by JMC4789 over 5 years ago
- Status changed from New to Fixed
Awesome to hear. Thanks for the update.