I have a problem with Nvidia drivers 535.129.3

I have a problem with Nvidia drivers 535.129.3 in this current update (and with the bad “rolled back” driver too) bad performance in games, Steam overlay not working, bad fps drops unplayable gameplay, Steam overlay not working.

I used a TimeShift snapshot from two weeks ago and it fixed the issues. 535.113.01 has no issue.

I still have same issue as before with the latest Nvidia drivers.

I have the same Problem.
Cyberpunk crashes the entire PC.
I found the problem here.

journalctl | grep Xid                                                                                   0|1 ✘ 

Nov 17 00:04:00 weingeist-PC kernel: NVRM: Xid (PCI:0000:03:00): 31, pid=5889, name=GameThread, Ch 00000086, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0xffff9190_00001000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ
Nov 17 04:00:13 weingeist-PC kernel: NVRM: Xid (PCI:0000:03:00): 31, pid=1743, name=GameThread, Ch 0000007e, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0x3bb0_00001000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ
Nov 17 20:44:36 weingeist-PC kernel: NVRM: Xid (PCI:0000:03:00): 31, pid=2008, name=GameThread, Ch 00000089, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0x250_00001000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ
Nov 17 21:42:23 weingeist-PC kernel: NVRM: Xid (PCI:0000:03:00): 31, pid=2874, name=GameThread, Ch 0000008b, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0xffffd410_00001000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ
Nov 17 22:16:59 weingeist-PC kernel: NVRM: Xid (PCI:0000:03:00): 31, pid=4122, name=GameThread, Ch 00000086, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0x2ea0_00001000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ
Nov 17 22:43:17 weingeist-PC kernel: NVRM: Xid (PCI:0000:03:00): 31, pid=1812, name=GameThread, Ch 00000089, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0xffffb5d0_00000000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ
Nov 17 23:03:07 weingeist-PC kernel: NVRM: Xid (PCI:0000:03:00): 31, pid=3124, name=GameThread, Ch 00000091, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0x34d0_00000000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ
Nov 17 23:26:46 weingeist-PC kernel: NVRM: Xid (PCI:0000:03:00): 31, pid=1731, name=GameThread, Ch 00000087, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0xfffff630_00000000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ
Nov 18 01:08:49 weingeist-PC kernel: NVRM: Xid (PCI:0000:03:00): 31, pid=3156, name=GameThread, Ch 0000008f, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0xfffffd60_00000000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ

View this

Nvidia 545.x is in unstable …

Yes it is, not sure why you’re pointing that out.

1 Like

What problem?

Which is? The testing branch went from 535.113.01 > 535.129.3 > 545.29.02 > 535.129.3.

What issue?

Not for me wth 545.29.02-1. :man_shrugging:

…because you never specifically mentioned you tried the 545 series, maybe? :wink:

I will refer you to your featured topic in your profile. C’mon, you know better. Help us help you.

1 Like

545 is not in stable

You’re right. @omano is using testing and I’m using unstable. Are you lost? :wink:

Also to be fair I didn’t open a support thread, two post I made from two different announcement thread were merged in this thread.

Your profile gives us your system info, so we have that:

Branch: Testing
DE / WM: KDE Plasma
CPU: Ryzen 5 3600
GPU: GTX 1060
GPU Driver: Nvidia

Now, which games are giving you these performance issues?
Many of us are also gamers and usually own similar (if not the same) games.

Cyberpunk worked great for me and since the last update i get major stutters(especially after a few hours of playing).
535.129.03

i see it wasn’t updated on the 13.11 ,so I’m not sure what’s the culprit.

I updated the system again from my snapshot, and it seems to work OK now. Not sure what happened as it is the same driver that was problematic before (not same revision though). I also switched to kernel 6.6 and removed 6.5.

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.