Wolfenstein: Youngblood

Wolfenstein: Youngblood

View Stats:
cratylus Jul 25, 2019 @ 8:07pm
Crash on start
GeForce GTX 1060 3gb
AMD Phenom II X4 830

Screen goes dark, as if the game is about to start, then before showing any text or graphics, it crashes, and an errorbox appears saying "Could not write crash dump"

I deleted game files and then reinstalled, no change.
I updated my nvidia drivers, no change.
I validated game files, all were ok.

Despite the message, I do see some kind of crash info in

c:\Users\me\Saved Games\MachineGames\Wolfenstein Youngblood\base

qconsole.log:
***************
CrashHandler: Storing data and writing local report.
WARNING: No address, error: 126
idStackTracer::GetSource: Failed
WARNING: No address, error: 126
idStackTracer::GetSource: Failed
CrashHandler: Complete.
ShowGameWindow: (0, 0) 1920 x 1080, windowed

and

Crash.MYCOMPUTER.99998.html
***************************************
<PRE>
Callstack Function(desc) Line Bytes File Process Address
--------------------------- ---- ----- ---- ------- -------
** UNKNOWN **(** FUNC_PARAM_ERROR **) ... + 0x9ac5f579 ?
** UNKNOWN **(** FUNC_PARAM_ERROR **) ... + 0x3a83126f ?

Register Info
---------------------------
EDI: 0x00000000DA016128 ESI: 0x00000000097A3733 EAX: 0x0000000000000010
EBX: 0xB714609A58888000 ECX: 0x00000000DA01C010 EDX: 0x0000000000000020
EIP: 0x00007FFB9AC5F579 EBP: 0x00000000097A2EA0 SegCs: 0x0000000000000033
EFlags: 0x0000000000010202 ESP: 0x00000000097A2D60 SegSs: 0x000000000000002B

Exception Info
---------------------------
ExpCode: 0xC000001D (Illegal Instruction)
ExpFlags: 0
ExpAddress: 0x00007FFB9AC5F579

Build & Runtime Info
---------------------------
User: cratylus
Version: 20190722-230838-105784_purple-iceberg
File Path: D:\Steam\steamapps\common\Wolfenstein Youngblood\Youngblood_x64vk.exe
System Time: 7/25/2019 22:58:30
Build String: 20190722-230838-105784_purple-iceberg
VT File Path:
VMTR Override: generated/pagefiles
Launch Command: "D:\Steam\steamapps\common\Wolfenstein Youngblood\Youngblood_x64vk.exe" +com_safemode 1 +r_allowComputePresent 0

Memory Info
---------------------------
In Use: 67%
MB Physical RAM: 8192
MB Physical Free: 2699
MB Paging File: 15104
MB Paging Free: 4487
MB User Address: 134217728
MB User Free: 134209472

CPU Info
---------------------------
Num Packages: 1
Num Cores: 4
Num Logical: 4
CPU ID: Generic
CPU MHz: 2793

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

User Info: cratylus
---------------------------
Repro Steps:


Details:

</PRE>



ANY HELP APPRECIATED
< >
Showing 1-7 of 7 comments
pidge2k Jul 26, 2019 @ 3:39am 
Are you using the latest R431.60 driver?
cratylus Jul 26, 2019 @ 10:14am 
yes, updated to 431.60, no change in the symptom
LapdogSalami Jul 26, 2019 @ 11:15am 
Did u fix it?
erikms Jul 26, 2019 @ 11:25am 
Originally posted by cratylus:
GeForce GTX 1060 3gb
AMD Phenom II X4 830

Screen goes dark, as if the game is about to start, then before showing any text or graphics, it crashes, and an errorbox appears saying "Could not write crash dump"

I deleted game files and then reinstalled, no change.
I updated my nvidia drivers, no change.
I validated game files, all were ok.

Despite the message, I do see some kind of crash info in

c:\Users\me\Saved Games\MachineGames\Wolfenstein Youngblood\base

qconsole.log:
***************
CrashHandler: Storing data and writing local report.
WARNING: No address, error: 126
idStackTracer::GetSource: Failed
WARNING: No address, error: 126
idStackTracer::GetSource: Failed
CrashHandler: Complete.
ShowGameWindow: (0, 0) 1920 x 1080, windowed

and

Crash.MYCOMPUTER.99998.html
***************************************
<PRE>
Callstack Function(desc) Line Bytes File Process Address
--------------------------- ---- ----- ---- ------- -------
** UNKNOWN **(** FUNC_PARAM_ERROR **) ... + 0x9ac5f579 ?
** UNKNOWN **(** FUNC_PARAM_ERROR **) ... + 0x3a83126f ?

Register Info
---------------------------
EDI: 0x00000000DA016128 ESI: 0x00000000097A3733 EAX: 0x0000000000000010
EBX: 0xB714609A58888000 ECX: 0x00000000DA01C010 EDX: 0x0000000000000020
EIP: 0x00007FFB9AC5F579 EBP: 0x00000000097A2EA0 SegCs: 0x0000000000000033
EFlags: 0x0000000000010202 ESP: 0x00000000097A2D60 SegSs: 0x000000000000002B

Exception Info
---------------------------
ExpCode: 0xC000001D (Illegal Instruction)
ExpFlags: 0
ExpAddress: 0x00007FFB9AC5F579

Build & Runtime Info
---------------------------
User: cratylus
Version: 20190722-230838-105784_purple-iceberg
File Path: D:\Steam\steamapps\common\Wolfenstein Youngblood\Youngblood_x64vk.exe
System Time: 7/25/2019 22:58:30
Build String: 20190722-230838-105784_purple-iceberg
VT File Path:
VMTR Override: generated/pagefiles
Launch Command: "D:\Steam\steamapps\common\Wolfenstein Youngblood\Youngblood_x64vk.exe" +com_safemode 1 +r_allowComputePresent 0

Memory Info
---------------------------
In Use: 67%
MB Physical RAM: 8192
MB Physical Free: 2699
MB Paging File: 15104
MB Paging Free: 4487
MB User Address: 134217728
MB User Free: 134209472

CPU Info
---------------------------
Num Packages: 1
Num Cores: 4
Num Logical: 4
CPU ID: Generic
CPU MHz: 2793

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

User Info: cratylus
---------------------------
Repro Steps:


Details:

</PRE>



ANY HELP APPRECIATED
AMD Phenom II X4 830
Do you really think it's possible to play modern games with a 70 Dollar CPU? You have a problem , not the game .You can not expect to play this game with this CPU.
cidyuk Jul 26, 2019 @ 11:31am 
try

+r_disablesteamOverlay 1

in launch options
helped me
cratylus Jul 26, 2019 @ 1:22pm 
Originally posted by erikms:
Do you really think it's possible to play modern games with a 70 Dollar CPU? You have a problem , not the game .You can not expect to play this game with this CPU.

This game isn't some sort of quantum leap in technology, and every other Wolfenstein runs like a champ. Yes I really think it should work. In any case, people with better specs have the same problem, so let's see if we can help them too, if you feel my machine is a lost cause.
cratylus Jul 26, 2019 @ 1:22pm 
Originally posted by cidyuk:
try

+r_disablesteamOverlay 1

in launch options
helped me

I just tried this. It did not change the symptom.
< >
Showing 1-7 of 7 comments
Per page: 1530 50

Date Posted: Jul 25, 2019 @ 8:07pm
Posts: 7