- Feb 13, 2016
- 770 (0.59/day)
- Buenos Aires, Argentina
|System Name||Ryzen Monster|
|Processor||Ryzen 5 2600X|
|Motherboard||Asus ROG Crosshair Hero VII WiFi|
|Cooling||Corsair H100i RGB Platinum|
|Memory||Corsair Vengeance 32GB (4x8GB) 2400Mhz|
|Video Card(s)||Asus ROG Strix RX580 OC 8Gb|
|Storage||250Gb Samsung EVO SSD, OCZ 500Gb SSD WD M.2 500Gb, plus three spinners up to 1.5Tb|
|Display(s)||Samsung C27F591 curved monitor 27" with FreeSync|
|Case||Cooler Master Storm Trooper|
|Audio Device(s)||Supreme FX on board|
|Power Supply||Corsair RM850X full modular|
|Keyboard||Corsair Strafe RGB Silent|
|Software||Windows 10 x64 Start 10|
|Benchmark Scores||3DMark Time Spy 4532|
Both Wolfenstein II: The New Colossus and No Man's Sky (NMS) will not launch unless I delete the following registry key:
This key contains the following:
"C:\\Program Files (x86)\\Steam\\steamapps\\common\\ActionRecorder\\vulkan_x64\\MirillisActionVulkanLayer.json"=dword:00000000
"C:\\Program Files (x86)\\Steam\\steamapps\\common\\FPS Monitor\\tools\\fpsmonvk64.json"=dword:00000000
"C:\\Program Files (x86)\\Bandicam\\bdcamvk64.json"=dword:00000000
"C:\\Program Files (x86)\\Steam\\SteamOverlayVulkanLayer64.json"=dword:00000000
"C:\\Program Files (x86)\\Steam\\SteamFossilizeVulkanLayer64.json"=dword:00000000
If the key is present I receive the Crash Dump Error in Wolfenstein and in NMS, no error message at all.
I have a Ryzen 2600X and RX580 rolled back to Adrenaline 19.5.2 (stable), but even the latest version 19.8.1produces the same error. I also use DDU for clean driver installs and back up the registry before deleting the key.
Deleting the key basically disables Bandicam, Action!, Steam Overlay, FPS Monitor and any other related overlays or monitoring programs related to that key. That's a bit like a mechanic looking at your car because it won't start and disabling the aircon, the radio and other features so that it will start. Overlays and game recording will cease to function with the key deleted.
I have a similar PC with an FX8350 and an Nvidia GTX960 and don't get any of these errors with either game, so I can only conclude that it's an AMD /Vulkan issue at play.
I've reported the problem in the AMD Community forums and Steam, so am posting here in case someone is aware of a fix.