Project

General

Profile

Actions

Emulator Issues #10427

closed

Vulkan Crash in Starfox Adventures on NVIDIA Pascal with MSAA

Added by sam.brereton over 7 years ago. Updated over 7 years ago.

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

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:
5.0-5150

Description

Game Name?

Starfox Adventures

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

GSAE01

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

afb0306454b581e37a62170fdfd1de09

What's the problem? Describe what went wrong.

When using the Vulkan Backend, opening the main menu in Starfox Adventures results in the program becoming unresponsive and crashing to desktop, leaving the errors described below in the Event Viewer log. Switching backends to either OpenGL or DIrectX solve the issue.

What steps will reproduce the problem?

Use Vulkan Backend

Internal Res: 6K
Anti-Aliasing: 2x MSAA
Anisotropic FIltering: 1x

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-4772
5.0-4952

What are your PC specifications? (CPU, GPU, Operating System, more)
Intel Core i5-7600K
NVIDIA GeForce GTX 1070
Windows 10 Professional (Build 1703)

NVIDIA Driver Version: 384.94 WHQL (Tried lower versions as well)

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

The following errors are printed to the Windows Event Log

The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

\Device\Video4
Variable String too Large

the message resource is present but the message is not found in the string/message table
The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

\Device\Video4
Graphics Exception on GPC 2: 3D-CT KIND Violation. Coordinates: (0x10, 0x10)

the message resource is present but the message is not found in the string/message table
The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

\Device\Video4
Graphics Exception: ESR 0x500420=0x80000100 0x500434=0x0 0x500438=0x5001800 0x50043c=0x100db

the message resource is present but the message is not found in the string/message table

Files

Actions #1

Updated by Stenzek over 7 years ago

Do you get the same behavior with MSAA disabled? There was an issue with clears and MSAA causing the device to be lost on Pascal that I've seen before, although I was only able to reproduce that on Linux.

Actions #2

Updated by sam.brereton over 7 years ago

Stenzek wrote:

Do you get the same behavior with MSAA disabled? There was an issue with clears and MSAA causing the device to be lost on Pascal that I've seen before, although I was only able to reproduce that on Linux.

Interestingly enough, no. I turned off Anti-Aliasing all together and I did not get a crash.

Any ideas? Bug or Graphics Card issue?

Actions #3

Updated by Stenzek over 7 years ago

Potentially a driver issue, although I haven't verified that Dolphin isn't in the wrong here. It only seems to affect Pascal cards (potentially Maxwell, but I've only tested Kepler+Pascal as that's all I have): https://github.com/dolphin-emu/dolphin/pull/5478

Actions #4

Updated by Stenzek over 7 years ago

  • Subject changed from Vulkan Crash in Starfox Adventures to Vulkan Crash in Starfox Adventures on NVIDIA Pascal with MSAA
  • Status changed from New to Accepted
Actions #5

Updated by JMC4789 over 7 years ago

  • Status changed from Accepted to Fix pending
Actions #6

Updated by JMC4789 over 7 years ago

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

Also available in: Atom PDF