Wolfenstein: Youngblood

Wolfenstein: Youngblood

Ver estatísticas:
Aesu 25/abr./2021 às 18:58
Vulkan device lost (GPU stalled/hung/crashed). AMD CPU + NVIDIA GPU crashing with RTX enabled.
I am using an Asus G733 with AMD Ryzen 9 5900HX and Nvidia GeForce RTX 3080 16GB GDDR6, 1545MHz boost clock, 130W TGP

Without RTX enabled, this game works... I can play.
With RTX enabled, it crashes.

The game loads, but as soon as I enable RTX and run the benchmark, it crashes after 3 ~ 4 sec with the error: There was an error while initializing the graphics driver. Vulkan device lost (GPU stalled/hung/crashed). The game will exit when you click OK.

Without RTX enabled, it works... I can play. With RTX, crash.

I have tried everything...
1. https://www.reddit.com/r/BethesdaSoftworks/comments/f2g9l5/wolfenstein_youngblood_error_game_crashed_crash/
2. https://help.bethesda.net/app/answers/detail/a_id/47979/~/what-should-i-do-if-wolfenstein%3A-youngblood-crashes-while-playing-through-steam%3F
3. Several guides here on steam

Here is the crash content:

Callstack Function(desc) Line Bytes File Process Address
--------------------------- ---- ----- ---- ------- -------
** UNKNOWN **(** FUNC_PARAM_ERROR **) ... + 0xc3ce6cbc ?
** UNKNOWN **(** FUNC_PARAM_ERROR **) ... + 0xc3cd2437 ?
** UNKNOWN **(** FUNC_PARAM_ERROR **) ... + 0x65646168 ?
** UNKNOWN **(** FUNC_PARAM_ERROR **) ... + 0x006b636f ?

Register Info
---------------------------
EDI: 0x0000000000003FFE ESI: 0x000000000A6734E0 EAX: 0x0000000000000014
EBX: 0x000000000A672AA0 ECX: 0x0000000000000020 EDX: 0x000000007FFFFFFF
EIP: 0x00007FF8C3CE6CBC EBP: 0x000000000A672B40 SegCs: 0x0000000000000033
EFlags: 0x0000000000010283 ESP: 0x000000000A672928 SegSs: 0x000000000000002B

Exception Info
---------------------------
ExpCode: 0xC0000005 (Access Violation)
ExpFlags: 0
ExpAddress: 0x00007FF8C3CE6CBC

Build & Runtime Info
---------------------------
User: x
Version: 20201019-143815-107336_brown-magenta
File Path: C:\Program Files (x86)\Steam\steamapps\common\Wolfenstein Youngblood\Youngblood_x64vk.exe
System Time: 4/25/2021 21:20:16
Build String: 20201019-143815-107336_brown-magenta
VT File Path:
VMTR Override: generated/pagefiles
Launch Command: "C:\Program Files (x86)\Steam\steamapps\common\Wolfenstein Youngblood\Youngblood_x64vk.exe"

Memory Info
---------------------------
In Use: 18%
MB Physical RAM: 32177
MB Physical Free: 26321
MB Paging File: 37041
MB Paging Free: 24663
MB User Address: 134217728
MB User Free: 134212662

CPU Info
---------------------------
Num Packages: 1
Num Cores: 8
Num Logical: 16
CPU ID: Generic
CPU MHz: 3294

Forge Info
---------------------------
Binary Name:
Package Name:
Candidate Name:
Runtime UUID:

User Info: x
---------------------------
Repro Steps:


Details:

Also there is another file called Qconsole which has errors:

CrashHandler: Storing data and writing local report.
WARNING: No address, error: 126
idStackTracer::GetSource: Failed
WARNING: No address, error: 126
idStackTracer::GetSource: Failed
WARNING: No address, error: 126
idStackTracer::GetSource: Failed
WARNING: No address, error: 126
idStackTracer::GetSource: Failed
CrashHandler: Complete.
< >
Exibindo comentários 115 de 31
Aesu 29/abr./2021 às 4:57 
ahhh the lack of response is a real testament to the care and love of developers for their creation
asklepion 29/abr./2021 às 7:53 
Yup, but to remind u. The game ist currently in the cheap bargain corner
Aesu 20/mai./2021 às 18:42 
yeah true :) but I prefer a working game none the less...
green.nifta 27/mai./2021 às 8:20 
Disabling the Nvidia overlay seemed to help some people...
CaptainGeoluread 9/jul./2021 às 12:14 
Having this problem too, driving me mad.
papalazarou 10/jul./2021 às 13:25 
just my 50p ..latest nv driver, i would guess a driver issue. windows updates, maybe try leaving msi afterburner off and rtss
Última edição por papalazarou; 10/jul./2021 às 13:25
CrAzYLuKe 17/set./2021 às 5:06 
I‘ve got an 3900x & 3060ti which is over clocked with MSI Afterburner. By quitting the tool, I got no crashes!
Liloes 19/out./2021 às 16:55 
I have the same problem, disabling Nvidia In-Game Overlay does not resolve the issue. Nvidia GTX 1660 Ti :DSTskull: Btw. all my drivers and OS are up to date.
Mang 23/jul./2022 às 17:40 
Would love to get a fix for this. I have tried everything suggested but still no cigar.
bechdrak 20/set./2022 às 14:26 
Nvidia drivers 497.29 solves the problem.
Dragoth01 20/out./2022 às 11:49 
Any Fix to this yet. I can't get past the first boss. The explosion through the bullet proof glass crashes my game every single time. Graphics card can't initialize hung up etc...RTX 3080Ti.
Dragoth01 20/out./2022 às 13:14 
Escrito originalmente por bechdrak:
Nvidia drivers 497.29 solves the problem.
sucks that I have to install a previous version of the driver to play a game.
longshanks66 3/nov./2022 às 4:44 
Same prob here. Nothing has worked thus far. Came close, tho. I stayed at the bottom of the Metro station stairs and lurked the kwazy krauts to me and snarfed them one at at time. When I ran out of victims to shoot I carefully made my way to the objective and I ALMOST made it before the game crashed. I know this is not a 'fix' but it is a close as I came. If one can figure out what exactly is triggering the crash, that may halp more.
adenders 30/nov./2022 às 11:00 
Was having this problem (crash fighting the first boss, received the Vulkan error) and also could not find a real solution anywhere, but got it to work, at least for now, by: turning off RayTracing and DLSS in game settings, and changing the NVIDIA Control Panel setting "Vulkan/OpenGL present method" to "Prefer native". I've only tested the same boss fight so far and it no longer crashed, but uncertain if this a permanent solution. Will try to update if anything else comes up. Drivers are most current as of 11.30.22, 526.98 updated 11/16/22. Good luck and hope it runs for you!
Sheol 17/dez./2022 às 13:11 
I would like to say that this issue suddenly appeared for me. Already completed the game and now just spending time completing achievements after 60 hours of perfect play this error is now present during any explosive scenes. Tried turning Ray tracing off but made no difference. I have a 3060ti, but just very confused on why it suddenly appeared or how to get around it
< >
Exibindo comentários 115 de 31
Por página: 1530 50