Project

General

Profile

Emulator Issues #10482

Direct3D 11 requires platform update on Windows 7, but this is not explained to the user

Added by newhacker1746 almost 3 years ago. Updated about 1 year ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
Windows
Issue type:
Bug
Milestone:
Current
Regression:
Yes
Relates to usability:
Yes
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
5.0-4657
Fixed in:
5.0-10738

Description

Game Name?

Any Game

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

Any Game, I tested RMCE01 (Mario Kart Wii NTSC) RMGP01 (Super Mario Galaxy PAL) and SB4E01 (Super Mario Galaxy 2 NTSC)

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

RMCE01: 390375058c5820597df0059311558e49 RMGP01: 4a7379f93369f3335cfdae90cdac2f96 SB4E01: 7a22942b14cb1dbdd63a09b4fd77f718

What's the problem? Describe what went wrong.

Upon starting any game with the direct3d11 backend, dolphin crashes. (or from before a certain point, gives me error dialog boxes and then crashes)

What steps will reproduce the problem?

Open any game (I think, 3 games crashing in the same way from different regions makes me think it applies universally) and watch as dolphin crashes, as long as you have selected the direct3d11 backend.

It is important to make sure the bug hasn't already been fixed. Please tell us what the latest version you've verified the bug on.

5.0-5209 (latest as of August 19th at 5:00PM UTC-05:00 Eastern Time)

Is the issue present in the latest stable version?

No. Dolphin 5.0 (non developer release)

If the issue isn't present in the latest stable version, which is the first broken version?

There are 2 types of crashes I noticed while hunting for the first broken version. The first type of crash, starting on dolphin 4657, is that on starting any game the error is "Failed to initialize Direct3D. Make sure your video card supports at least D3D 10.0" and after clicking ok on that dialog box, a "Warning" dialog box says "Failed to create D3D device." and then dolphin crashes. This type of crash occurs for several releases. Starting on dolphin 4687, dolphin just crashes with no error dialog box. (i.e the "dolphin.exe has stopped working" dialog from windows itself appears with no messages from dolphin before that) This type of crash continues up to the current dev build, 5.0-5209.

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

(This is not a graphical issue)

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

Pentium G3258 @ 4.0Ghz, GTX 760, Windows Embedded Standard 7 64 bit (it's just Windows 7 rebranded so this should not be an issue)

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

For the first crash, i.e. the warnings and then crash:

First crash dialog box
First crash second dialog box
First crash debug info

The text of the crash is as follows:

Problem signature:
Problem Event Name: APPCRASH
Application Name: Dolphin.exe
Application Version: 0.0.0.0
Application Timestamp: 5962d13b
Fault Module Name: Dolphin.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 5962d13b
Exception Code: c0000005
Exception Offset: 000000000070e2eb
OS Version: 6.1.7601.2.1.0.320.65
Locale ID: 1033
Additional Information 1: bbe3
Additional Information 2: bbe3a01dfbe759adbab43cfc05b1227c
Additional Information 3: 8ede
Additional Information 4: 8edea9bc016bfef9c990ea495d0824a0

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

For the second crash, i.e. when dolphin crashes without any other warning dialogs:
Second crash debug info

The text of the crash is as follows:

Problem signature:
Problem Event Name: APPCRASH
Application Name: Dolphin.exe
Application Version: 0.0.0.0
Application Timestamp: 5963233b
Fault Module Name: dxgi.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7c631
Exception Code: c0000005
Exception Offset: 000000000002cebc
OS Version: 6.1.7601.2.1.0.320.65
Locale ID: 1033
Additional Information 1: 3a2b
Additional Information 2: 3a2b036725aac4cfeeb433a7283a162a
Additional Information 3: 1d2b
Additional Information 4: 1d2b38b4853c3fde96360648b7ca9288

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

Note that the second crash references dxgi.dll while the first crash references dolphin itself. I combed through changelogs to find the ones pertaining to the versions that introduced crashes and did find something: https://github.com/dolphin-emu/dolphin/pull/5697 which is the pull request that became dolphin 5.0-4657, and there is someone else with the same issue, which leads to the pull request for 5.0-4687. (comment is from July 8) The pull request mentions that the proposed changes to the d3d11 backend would break its compatibility with Vista, but I am not using Vista (Windows NT 6.0 is Vista, Windows NT 6.1 is Win7/derivatives) and the proposed changes should not break anything. Here's the pull request that became 5.0-4687: https://github.com/dolphin-emu/dolphin/pull/5771 ironically this pull request was supposed to fix the aforementioned D3D initialization error but it breaks D3D even more for me. (and nobody that may have experienced the second crash I mentioned has reported it anywhere I looked)

If any other logs/info is required I will be glad to provide it.

error1.PNG (25.1 KB) error1.PNG First crash dialog box newhacker1746, 08/19/2017 08:19 PM
aftererror1.PNG (20.6 KB) aftererror1.PNG First crash second dialog box newhacker1746, 08/19/2017 08:20 PM
aftererror1crash.PNG (42.9 KB) aftererror1crash.PNG First crash debug info newhacker1746, 08/19/2017 08:20 PM
error2crash.PNG (42.9 KB) error2crash.PNG Second crash debug info newhacker1746, 08/19/2017 08:22 PM
yes.PNG (44.3 KB) yes.PNG D3DCompiler file properties newhacker1746, 08/20/2017 01:43 PM
6270
6271
6272
6273
6277

History

#1 Updated by newhacker1746 almost 3 years ago

a

#2 Updated by newhacker1746 almost 3 years ago

Sorry I accidentally submitted. I wanted to mention that my OS is fully updated and so there should be no issues there.

#3 Updated by newhacker1746 almost 3 years ago

Wanted to note that all the md5 hashes are from games compressed with wbfs

#4 Updated by Stenzek almost 3 years ago

  • Status changed from New to Questionable

Sounds like another Win7 issue.

Have you installed the platform update (check the file versions if you don't have it listed): https://support.microsoft.com/en-us/help/2670838/platform-update-for-windows-7-sp1-and-windows-server-2008-r2-sp1
And the D3DCompiler update (check for the presence of d3dcompiler_47.dll): https://support.microsoft.com/en-us/help/4019990/update-for-the-d3dcompiler-47-dll-component-on-windows

I'm not sure if these are applicable to the edition of win7 you have listed.

#5 Updated by newhacker1746 almost 3 years ago

I had not installed the platform update.But I had installed the D3DCompiler update because dolphin itself told me it was needed...D3DCompiler file properties Note the file version. The D3DUpdate had separate downloads for Windows Embedded and Win7 x64 (I googled the update on google to find the standalone update download page) but I doubted that the files were any different, so I downloaded both versions (WinEmb and Win7x64) and the files were identical! So I went ahead and installed the platform update (for Win7x64) and yes it works. (The update appears to only check for Windows NT 6.1 and not a specific windows 7 derivative or maybe that's just how .msu standalone updates work) Thanks for your help! But since certain computers are set to not automatically install updates ahead of time (or haven't installed that specific update) wouldn't it be useful to add a warning to dolphin to inform you if you need to install the platform update? So that this issue is solved more permanently.

#6 Updated by newhacker1746 almost 3 years ago

6277

Looks like the screenshot didn't go through so here's the D3Dcompiler file info D3DCompiler file properties

#7 Updated by Stenzek almost 3 years ago

What about the platform update? The failed to initialize Direct3D error suggests that either the device is failing to create (unlikely), or one of the calls to create the swap chain is failing.

#8 Updated by newhacker1746 almost 3 years ago

Applying the platform update fixed the issue. I'm not sure what you mean.

#9 Updated by newhacker1746 almost 3 years ago

I think that the fix would be to warn a user when the platform update is not detected, as it is not listed as a requirement anywhere to run dolphin versions > 5.0-4657

#10 Updated by Stenzek almost 3 years ago

  • Status changed from Questionable to Working as intended

As the platform update should be delivered via windows update, I think it's a reasonably safe assumption that most users will have it installed. That said, the error message could be changed to indicate this, similar to the D3DCompiler error.

#11 Updated by JosJuice almost 3 years ago

  • Subject changed from Dolphin crashes when using Direct3D11 backend to Direct3D 11 requires platform update on Windows 7, but this is not explained to the user
  • Status changed from Working as intended to New
  • Milestone set to Current
  • Regression changed from No to Yes
  • Relates to usability changed from No to Yes
  • Regression start set to 5.0-4657
  • Operating system Windows added
  • Operating system deleted (N/A)

Re-opening as an issue about there not being any information about the update being required.

#12 Updated by JMC4789 about 2 years ago

  • Status changed from New to Won't fix

D3D11 backend no longer works on Windows 7 as far as I know due to the missing update that we use for proper LogicOp support...

#13 Updated by JosJuice about 2 years ago

  • Status changed from Won't fix to New

We should still tell the user about it instead of showing some generic error messages that don't explain anything.

#14 Updated by Silent about 1 year ago

I'll see what I can do about it. I have access to Windows 7 with "good enough" hardware so that should suffice.

#15 Updated by Silent about 1 year ago

This pull request will implement a warning when using D3D11 on Windows 7 and will also make logic op graphical artifacts less jarring:

https://github.com/dolphin-emu/dolphin/pull/8258

I'm currently rolling back a Win7 SP1 Platform Update so I can verify if Dolphin still crashes without it.

#16 Updated by JosJuice about 1 year ago

  • Status changed from New to Fix pending

#17 Updated by JosJuice about 1 year ago

  • Fixed in set to 5.0-10738
  • Status changed from Fix pending to Fixed

https://dolphin-emu.org/download/dev/dea2b9c509b96cb58182b883c1df9f9f7f9234bf/

Dolphin should now avoid crashing, and has a warning about the logic ops problem. (I think there still isn't a warning about what updates are required, but Windows 7 is EoL soon and we already have a warning about the D3D11 backend for other reasons, so...)

Also available in: Atom PDF