Like I posted in the DX12 thread, would be wonderful if there could be a investigation why 007 First Light shows full performance under DX12 with Heaps, and the rest of the DX12 games are still showing the 25% perf delta (also reflected by lower power draw)
Hello,
Since the release of 610 drivers, I experiment black screen, and fans are ramping up to 100% on my 5090.
I made a side post with all the debug logs you may need.
Update: It’s a BIG problem as it happens at least one time per hour, and downgrading to 595 didn’t fix anything for me (it wasn’t happening before I updated to 610).
Thanks a lot
Please do share nvidia-bug-report to proceed further on this.
nvidia-bug-report.log.gz (2.0 MB) There it is
Someone with color pipeline enabled please share drm_info output. I can’t get it to show up.
nvidia-bug-report.log.gz (543.9 KB)
drm_info.txt (128.0 KB)
I’ve observed a 15-20% performance decline in Cyberpunk 2077 with 610 relative to 595 (which,of course, is 20-30% slower than windows). This is substantial, but given the lack of anyone else making this observation, it can’t be true across all configurations. I haven’t done rigorous comparisons due to the pain of switching drivers, but I’ll try and collect more data. I’m interested in other folks experience.
I’ll run the benchmarks on both drivers and report back later on it.
edit: well ■■■■ the diffs are crazy on Cyberpunk 2077.
| Field | 610.43.02 drivers | 595.71.05 drivers | Change |
|---|---|---|---|
| Average FPS | 51.49 | 64.71 | +13.22 / +25.7% |
| Min FPS | 29.61 | 45.12 | +15.51 / +52.4% |
| Max FPS | 75.96 | 85.92 | +9.97 / +13.1% |
| Frame count | 3309 | 4158 | +849 / +25.7% |
| Time | 64.2605s | 64.2514s | nearly identical |
benchmarks both ran from the cli (with the -benchmark arg), on the same exact settings, only the drivers version changed. NVIDIA 4070 Laptop + AMD Ryzen 7 8845HS, proton-cachyos-11.0-20260521-slr-x86_64_v3
The Black Myth Wukong Benchmark tool gave the same exact results for both drivers, so that’s not widespread across all DX12 games.
Greetings, please note the pinned forum thread: »»»»»»»»»» If you have a problem, PLEASE read this first ««««««««««
As noted in large, bold letters, please always include a copy of the nvidia-bug-report.log.gz file with any bug report, since this includes information to reproduce and diagnose a problem. This can be generated using the nvidia-bug-report.sh script.
Otherwise, as you are aware, no one will know what system you are on, what hardware you have, what game you are running, and so forth. Without this information, it can be nearly impossible to identify a specific problem.
Hello,
I still have the same issue with the GPU dropping the connection to the monitor after awhile.
System Information:
Operating System: CachyOS Linux
KDE Plasma Version: 6.6.91
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1
Kernel Version: 7.0.10-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
Memory: 96 GiB of RAM (94.2 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 4090
Manufacturer: ASUS
Issue:
The monitor I have, Asus PG32UCDM, has a built-in KVM switch. The GPU is connected to the monitor through DisplayPort. The KVM function mode on the monitor is through USB-B which connects to the CachyOS Desktop that has the GPU. When I connect my work laptop to the monitor’s USB-C connection, after awhile the GPU drops the connection to the monitor on DisplayPort/ Desktop CachyOS. The work laptop is functioning through the KVM USB-C mode on the monitor. Disconnecting laptop USB-C connection or switching back to DisplayPort results in a no signal detected output by monitor. The only way to recover from this is to disconnect the DisplayPort physically, wait for a few seconds, and then reinsert it. Sometimes, that does not even work as well as a power cycle of the monitor and I have to reboot the system.
Reproduce:
With an Asus monitor with a built-in KVM switch or my specific monitor, PG32UCDM, attach a Linux PC/laptop to the DisplayPort and put the monitor’s KVM switch mode into USB-B. Attach a Windows 11 PC/laptop and connect it to the monitor’s USB-C and put the monitor’s KVM switch mode to USB-C. Wait 10-20 minutes and then switch back to the DisplayPort.
Logs:
Journalctl of current session and time stamp of when I was trying to switch back to Linux PC.
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526] Removing connected display on bus 6
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773803] Emitting DDCA_Display_Status_Event[73696.773: DDCA_EVENT_DISPLAY_DISCONNECTED, card1-DP-2, dref: DDCA_Display_Ref[7], io_path:/dev/i2c-6, ddc working: false]
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773807] Starting 1 callback threads
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773842] libddcutil callback thread 0x7f0de00033c0 started
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773845] Started 1 event callback thread(s)
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773924] Udev event detected
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773959] Udev_Event_Detail
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773959] prop_subsystem: drm
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773959] prop_action: change
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773959] prop_connector: (null)
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773959] prop_devname: /dev/dri/card1
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773959] prop_devmode: (null)
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773959] prop_hotplug: 1
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773959] prop_major: 226
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773959] prop_minor: 1
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773959] sysname: card1
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773959] syspath: /sys/devices/pci0000:00/0000:00:03.1/0000:0a:00.0/drm/card1
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773959] attr_name: (null)
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 50635][73696.773984] Invoking callback function 0x7f0e15608970 for event DDCA_Display_Status_Event[73696.773: DDCA_EVENT_DISPLAY_DISCONNECTED, card1-DP-2, dref: DDCA_Display_Ref[7], io_path:/dev/i2c-6, ddc working: false] in this thread [ 50635]
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 48526][73696.773985] (dw_watch_display_connections) Time since last return from sleep = 73696649921189 ns = 73696650 ms
Jun 05 14:58:02 Home org_kde_powerdevil[32649]: [ 50635][73696.774009] Callback function 0x7f0e15608970 for event DDCA_Display_Status_Event[73696.773: DDCA_EVENT_DISPLAY_DISCONNECTED, card1-DP-2, dref: DDCA_Display_Ref[7], io_path:/dev/i2c-6, ddc working: false] complete
Jun 05 14:58:03 Home kded6[32563]: Failed to notify "Created too many similar notifications in quick succession"
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260666] Udev event detected
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260717] Udev_Event_Detail
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260717] prop_subsystem: drm
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260717] prop_action: change
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260717] prop_connector: (null)
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260717] prop_devname: /dev/dri/card1
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260717] prop_devmode: (null)
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260717] prop_hotplug: 1
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260717] prop_major: 226
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260717] prop_minor: 1
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260717] sysname: card1
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260717] syspath: /sys/devices/pci0000:00/0000:00:03.1/0000:0a:00.0/drm/card1
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260717] attr_name: (null)
Jun 05 14:58:07 Home org_kde_powerdevil[32649]: [ 48526][73702.260749] (dw_watch_display_connections) Time since last return from sleep = 73702136685037 ns = 73702137 ms
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526] Adding connected display with bus 6
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526] busno=6, Feature 0xdd should not exist but ddc_get_nontable_vcp_value() succeeds, returning mh=0x00 ml=0x01 sh=0x00 sl=0x01
Jun 05 14:58:08 Home kded6[32563]: Failed to notify "Created too many similar notifications in quick succession"
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.231817] Emitting DDCA_Display_Status_Event[73703.231: DDCA_EVENT_DISPLAY_CONNECTED, card1-DP-2, dref: DDCA_Display_Ref[8], io_path:/dev/i2c-6, ddc working: true]
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.231852] Starting 1 callback threads
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.231996] libddcutil callback thread 0x7f0de0012030 started
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232005] Started 1 event callback thread(s)
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 50670][73703.232043] Invoking callback function 0x7f0e15608970 for event DDCA_Display_Status_Event[73703.231: DDCA_EVENT_DISPLAY_CONNECTED, card1-DP-2, dref: DDCA_Display_Ref[8], io_path:/dev/i2c-6, ddc working: true] in this thread [ 50670]
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 50670][73703.232095] Callback function 0x7f0e15608970 for event DDCA_Display_Status_Event[73703.231: DDCA_EVENT_DISPLAY_CONNECTED, card1-DP-2, dref: DDCA_Display_Ref[8], io_path:/dev/i2c-6, ddc working: true] complete
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 32649] Quiescing libddcutil API...
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 32649] Quiesce libddcutil API complete
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 32649] Display redetection starting.
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232237] Udev event detected
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232287] Udev_Event_Detail
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232287] prop_subsystem: drm
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232287] prop_action: change
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232287] prop_connector: (null)
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232287] prop_devname: /dev/dri/card1
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232287] prop_devmode: (null)
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232287] prop_hotplug: 1
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232287] prop_major: 226
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232287] prop_minor: 1
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232287] sysname: card1
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232287] syspath: /sys/devices/pci0000:00/0000:00:03.1/0000:0a:00.0/drm/card1
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48526][73703.232287] attr_name: (null)
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 48525] recheck thread terminating because watch thread terminated
Jun 05 14:58:08 Home org_kde_powerdevil[32649]: [ 32649] Watch thread terminated.
Jun 05 14:58:10 Home org_kde_powerdevil[32649]: [ 32649] busno=6, Feature 0xdd should not exist but ddc_get_nontable_vcp_value() succeeds, returning mh=0x00 ml=0x01 sh=0x00 sl=0x01
Jun 05 14:58:10 Home org_kde_powerdevil[32649]: [ 32649][73705.336646] Time since library initialized: 73705.336646 seconds
Jun 05 14:58:10 Home org_kde_powerdevil[32649]: [ 32649][73705.336652] Extra delay starting dw_start_watch_displays: 0 millisec
Jun 05 14:58:10 Home org_kde_powerdevil[32649]: [ 32649] Watching for display connection changes, resolved watch mode = Watch_Mode_Udev, poll loop interval = 500 millisec
Jun 05 14:58:10 Home org_kde_powerdevil[32649]: [ 32649] initial_stabilization_millisec: 0, stabilization_poll_millisec: 100
Jun 05 14:58:10 Home org_kde_powerdevil[32649]: [ 32649] libddcutil recheck thread 0x55aa49a27d70 started
Jun 05 14:58:10 Home org_kde_powerdevil[32649]: [ 32649] libddcutil watch thread 0x55aa49a4cdd0 started
Jun 05 14:58:10 Home org_kde_powerdevil[32649]: [ 32649] Display redetection finished.
Jun 05 14:58:10 Home org_kde_powerdevil[32649]: [ 32649] Unquiescing libddcutil API...
Jun 05 14:58:10 Home org_kde_powerdevil[32649]: [ 50675][73705.342100] Recheck interval: Sleeping for 200 milliseconds
Jun 05 14:58:10 Home org_kde_powerdevil[32649]: [ 32649][73705.342103] (ddca_get_display_refs) Returned DDCA_Display_Ref list:
Jun 05 14:58:10 Home org_kde_powerdevil[32649]: [ 32649][73705.342124] DDCA_Display_Ref Display_Ref[9:bus /dev/i2c-6 @0x55aa49a83440]
Jun 05 14:58:10 Home kernel: usb 3-3: new high-speed USB device number 50 using xhci_hcd
Jun 05 14:58:11 Home kernel: usb 3-3: New USB device found, idVendor=0bda, idProduct=5411, bcdDevice= 0.03
Jun 05 14:58:11 Home kernel: usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 05 14:58:11 Home kernel: usb 3-3: Product: USB2.1 Hub
Jun 05 14:58:11 Home kernel: usb 3-3: Manufacturer: Generic
Jun 05 14:58:11 Home kernel: hub 3-3:1.0: USB hub found
Jun 05 14:58:11 Home kernel: hub 3-3:1.0: 6 ports detected
Jun 05 14:58:11 Home kernel: usb 4-3: new SuperSpeed USB device number 15 using xhci_hcd
Jun 05 14:58:11 Home kernel: usb 4-3: New USB device found, idVendor=0bda, idProduct=0411, bcdDevice= 0.03
Jun 05 14:58:11 Home kernel: usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 05 14:58:11 Home kernel: usb 4-3: Product: USB3.2 Hub
Jun 05 14:58:11 Home kernel: usb 4-3: Manufacturer: Generic
Jun 05 14:58:11 Home kernel: hub 4-3:1.0: USB hub found
Jun 05 14:58:11 Home kernel: hub 4-3:1.0: 3 ports detected
current_session.log (3.4 MB)
nvidia-bug-report.log.gz (963.0 KB)
Monitor’s OSD Pictures:
Hi @RyzenDew
You mean to say that you are seeing couple of issues with Halo Infinite.
-
It crashes sometimes
-
And when It doesn’t crashes, you observe performance loss in fps.
https://youtu.be/IZKzlsqwNj8 so here is the timecode normally in windows i would get around 200FPS but linux was 90-100fps 1440p maxed out but here as you can see it’s even worse now down to 56-60fps and worse now visual glitches and random massive freezing
Dropping a comment here. Just updated to the Nvidia Open 610.43 on Arch, causing Deadlock to just freeze when using an ability in the hideout. Very frustrating. Luckily, I had a timeshift backup that i could revert to, and it fixed all the freezes.
developers from wivrn have found an issue(still seems to happen on driver 610) where NVIDIA drivers limit the GPU to the P2 performance state during NVENC encoding.
This is very problematic for most VR users, as normally users will stream the game as video, encoding through nvenc, to the headset, losing performance in VR
the fix is mentioned there already. the application profile.
System information:
OS: Arch Linux 7.0.8-arch1-1
GPU: RTX 3080 12GB
Nvidia Driver: nvidia-open / nvidia-open-dkms
Adding an issue with 610 Driver. After updating from 595.71.05 to 610.43.02 on Arch Linux, games started to crash mid session with error in kernel log:
kernel: NVRM: Xid (PCI:0000:08:00): 109, pid=14122, name=MainThrd, channel 0x0000001a, errorString CTX SWITCH TIMEOUT, Info 0x3c024
Section of the log:
Jun 06 19:10:36 vallahost steam[2225]: ntsync: up and running.
Jun 06 19:10:36 vallahost steam[2225]: Adding process 13984 for gameID 1422450
Jun 06 19:10:36 vallahost steam[2225]: Adding process 13985 for gameID 1422450
Jun 06 19:10:36 vallahost steam[2225]: Adding process 13988 for gameID 1422450
Jun 06 19:10:36 vallahost steam[2225]: Adding process 13990 for gameID 1422450
Jun 06 19:10:36 vallahost steam[2225]: Adding process 13993 for gameID 1422450
Jun 06 19:10:36 vallahost steam[2225]: Adding process 14002 for gameID 1422450
Jun 06 19:10:38 vallahost steam[2225]: Adding process 14036 for gameID 1422450
Jun 06 19:10:38 vallahost steam[2225]: Adding process 14043 for gameID 1422450
Jun 06 19:10:39 vallahost steam[2225]: Adding process 14101 for gameID 1422450
Jun 06 19:10:39 vallahost steam[2225]: Adding process 14114 for gameID 1422450
Jun 06 19:10:40 vallahost steam[2225]: Adding process 14116 for gameID 1422450
Jun 06 19:10:40 vallahost steam[2225]: Adding process 14122 for gameID 1422450
Jun 06 19:10:44 vallahost steam[2225]: 06/06 19:10:44 minidumps folder is set to /tmp/dumps
Jun 06 19:10:44 vallahost steam[2225]: 06/06 19:10:44 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(20260601220446)/tid(14285)
Jun 06 19:10:44 vallahost steam[2225]: 06/06 19:10:44 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(14285)
Jun 06 19:10:46 vallahost wireplumber[2047]: spa.audioconvert: 0x7fc8b7c1c010: (0 suppressed) out of buffers on port 0 2
Jun 06 19:10:50 vallahost steam[2225]: 06/06 19:10:50 minidumps folder is set to /tmp/dumps
Jun 06 19:12:43 vallahost kernel: NVRM: GPU at PCI:0000:08:00: GPU-2d08b422-d213-e73e-2a1a-fe4419b9dbb7
Jun 06 19:12:43 vallahost kernel: NVRM: Xid (PCI:0000:08:00): 109, pid=14122, name=MainThrd, channel 0x0000001a, errorString CTX SWITCH TIMEOUT, Info 0x3c024
Jun 06 19:13:06 vallahost systemd[2034]: Started kitty child process: 17529 launched by: 17514.
Jun 06 19:13:07 vallahost systemd[2034]: Started kitty child process: 17609 launched by: 17605.
Jun 06 19:13:20 vallahost steam[2225]: pid 13986 != 13985, skipping destruction (fork without exec?)
Jun 06 19:13:20 vallahost steam[2225]: Game Recording - game stopped [gameid=1422450]
Jun 06 19:13:20 vallahost steam[2225]: Removing process 14122 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 14116 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 14114 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 14101 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 14043 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 14036 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 14002 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 13993 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 13990 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 13988 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 13985 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 13984 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 13983 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 13982 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 13887 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 13885 for gameID 1422450
Jun 06 19:13:20 vallahost steam[2225]: Removing process 13884 for gameID 1422450
This after 5 to 10 minutes of opening a game (tested with Deadlock, Backrooms: Escape Together, Cyberpunk 2077 and Crimson Desert) it will immediatly crash, without any behavior change between Proton versions (Proton and ProtonGE tested).
After changing it to nvidia-open-dkms, i could play a little longer (around 20 to 30 minutes) before the same issue happening
A rollback to the 595.71.05 driver version fixed this behavior.
I notice some new issues with object culling in Resident Evil 4 (2023).
Depending on the camera position and angle, some objects like crates, foliage, etc. get culled even if they shouldn’t. This wasn’t an issue with pre 610 drivers.
Look at the crates in front of the barrier:
Moving the camera just a little bit to the left causes the crates to get culled:
System:
Operating System: Bazzite 44
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1
Kernel Version: 7.0.9-ogc3.2.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600 6-Core Processor
Memory: 32 GiB of RAM (30.8 GiB usable)
Graphics Processor 1: NVIDIA GeForce RTX 5080
Graphics Processor 2: AMD Ryzen 5 7600 6-Core Processor
Manufacturer: ASRock
Product Name: B650M-HDV/M.2
NVIDIA Driver Version: 610.43.02
@Vyrolian We tried to repro the issue locally on Ubuntu 24.04 with 610.43.02 driver and RTX 4060 GPU but we couldn’t reproduce the issue locally.
Can you please help with the below details:
-
Is there any external display connected to your system, If yes what is the display resolution?
-
Please help with the game settings and steam launch option.
-
Proton version
-
Also please provide the nvidia bug report.
I have been trying for hours since reverting to 610, but so far somehow can’t reproduce either. FWIW it was highly inconsistent back then too - could be fine for hours then freeze, I’d restart and it would happen again very soon - maybe in 5-10 minutes. And it did not matter what I was doing - playing the game or used something else while the game was in background, I think once it happened in the main menu even.
All settings were on High except Medium for textures, with Reflex on. Using an external 240hz 1440p monitor connected directly to dGPU, and I forgot to mention I used Smooth Motion (more performant than DLSS FG on the 4060) and the latest DLSS on Performance. As I said also tried with and without heap, and Proton is latest CachyOS.
Also remembered that while playing GoW 2018 the same thing happened maybe two or three times during the entire 20-something hour playthrough, so it is probably not game specific (these were the only two games I played with 610 during that time). Will update with logs as soon as I catch a freeze again.