Bug 34511 - Nvidia current 570.172.08 cause several steam games to crash or freeze at launch
Summary: Nvidia current 570.172.08 cause several steam games to crash or freeze at launch
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 34523
Blocks:
  Show dependency treegraph
 
Reported: 2025-07-26 06:08 CEST by Didier Le Gloanic
Modified: 2025-08-06 05:49 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
steam log of an exemple of crash (352.81 KB, text/plain)
2025-07-27 11:10 CEST, Didier Le Gloanic
Details

Description Didier Le Gloanic 2025-07-26 06:08:02 CEST
Description of problem:
with that update some games crash or hang... (expedition 33,cyberpunk...)
while some seem to work corectly (portal rtx)
i've tried several proton version with same result before downgrading to the previous current version of the drivers (550.163.01).
Everything work fine after the downgrade.

i wasn't using the "all" metapackage, but i doubt that the lack of 32bits libraries is the culprit
i however was already using the open dkms and initramfs options when i uprgaded

Version-Release number of selected component (if applicable):
570.172.08

How reproducible:
crash every launch on the affected game
Comment 1 Didier Le Gloanic 2025-07-26 06:14:54 CEST
i did not grabbed steam logs ,i should have, i know, but i'm short on time this weekend. i will run more test when next week...
Comment 2 Didier Le Gloanic 2025-07-27 11:05:06 CEST
just in case it's matter : i'm on X11 plasma and my gpu is a rtx 4070

after reinstalling version 570.172.08 i runned a few more test.
Unlike bug 34512 (https://bugs.mageia.org/show_bug.cgi?id=34512) straight vulkan doesn't seem affected. Neither is dxvk apparently. 

But all VKD3D games i launched crashed.

expedition 33 crash with an error message :

the message is actually given by wine c++ runtime library
"
 assertion failed!
 
 program:(path to the program)
 
 file: ../src-wine/dlls/winevulkan/loader.c
 line 392
 
 expression: "!status"
"

in the steam log the first warning concerning vulkan is :
"warn:  OpenXR: Unable to get required Vulkan instance extensions size"

i will attach the full log in case it's giving an hint to the problem
Comment 3 Didier Le Gloanic 2025-07-27 11:10:42 CEST
Created attachment 15052 [details]
steam log of an exemple of crash
Comment 4 Cyril Levet 2025-07-27 12:52:25 CEST
I confirm the bug. Probably linked to Bug 34514

CC: (none) => cyril.levet0780

Stéphane Pontier 2025-07-27 13:56:04 CEST

CC: (none) => stephane.pontier

Morgan Leijström 2025-07-29 10:54:03 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=34514

Mike Rambo 2025-07-29 17:17:03 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=34515

Comment 5 Lewis Smith 2025-07-29 20:44:20 CEST
See the linked bugs. There is no doubt that this Nvidia update is flawed:
> downgrading to the
> previous current version of the drivers (550.163.01).
> Everything work fine after the downgrade.

Assignee: bugsquad => kernel
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=34512

Comment 6 Didier Le Gloanic 2025-07-31 08:07:37 CEST
revision 3 (570.172.08-3) in update testing have solved that issue.
everything seem fine ...
i think that at least this bug could be closed
Comment 7 Giuseppe Ghibò 2025-07-31 09:02:27 CEST
(In reply to Didier Le Gloanic from comment #6)

> revision 3 (570.172.08-3) in update testing have solved that issue.
> everything seem fine ...

which game? card? framerate?

CC: (none) => ghibomgx

Comment 8 Didier Le Gloanic 2025-07-31 11:08:17 CEST
(In reply to Giuseppe Ghibò from comment #7)
i use X11,Plasma 5, my card is a rtx 4070 but i used to have a 3060 until recently so i lack a little bit a frame of reference. I also tend to limit the power to 160 W (default 200)  with a little overclock (the goal is to undervolt, no other way on linux+nvidia). I use a 1080p monitor.

I tested a variety of opengl, vulkan and the compatibility layers that use it (dxvk and vkd3d) : expedition 33, cyberpunk 77, portal rtx, supertuxkart, alien swarm... vkcube and glxspheres aswell
No crash, freeze, or visual glitch that wasn't there before.

When it's come to the framerate, i usually cap it at a rate depending of the game, usualy 60 for demanding games (those with ray tracing for example) and i haven't kept benchmark result of the previous driver... But something meaningfull is experimenting with cyberpunk 77's pathtracing (with dlss balanced, transformer model, limited power draw), performance seem at least as good as before. In fact, as far as i recall it seem improved with something like 45 to 50 fps most of the time in one of the most demanding area of the game, where i recall sometime dipping in the 30's last time i tested. When out of city centre the performance rise and even reach my frame cap.
I only experimented a little with that card and never used a specific methodology to accurately evaluate it's performance, so my impressions are, of course, to be taken with a grain of salt.
But anyway at that point it seem to me that we are talking of the performance quality of nvidia drivers themselves, not of the adequacy of the packages.
I haven't encountered some of the bugs that others described, so all i could say is : this bug (vkd3d games crashing) doesn't affect my rig anymore , i haven't tested things i don't have much experience with like gpu hw video encoding or cuda for example, but what i did test work.
Comment 9 Cyril Levet 2025-07-31 22:08:19 CEST
Don't have time to make more tests today, but I confirm that the 570.172.08-3 fixes startup crashes with my games too : Victoria 3, Crusader King 3. I can test other games this weekend.
Morgan Leijström 2025-08-01 00:30:59 CEST

Depends on: (none) => 34523

Comment 10 katnatek 2025-08-06 05:49:04 CEST
Closing

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.