Hello Same on HP Omen 15-en0004AX
Spec Ryzen 7 4800H ,2x512gb Nvme drive, Nvidia GTX 1650 Ti, 16GB RAM
OS: Arch Kernel 5.8
Nvidia Diver: 450.66
Session KDE Plasma Xorg
None of the solution worked so far. I am getting this error when Ideling and on Regular usage (more frequently in Idelling). Suddenly CPU may got 100 percentage mouse will work for few seconds no commands or logging mentioned here will work on this state, after that entire system crash no ssh nothing, need to restart to recover.
Frequency hack mentioned here can delay it some what , But it very frequent for me the longest stretch i am able to use desktop is about 2:30 hours
Hello Amrits,
Thanks for the 450.66 update. I have not encountered the xid61 error since I updated to this driver version 3-4 days ago.
I am on Mobo: ASUSTeK model: ROG STRIX X570 -F GAMING AMD Ryzen 9 3950X GeForce RTX 2080 SUPER
Regards
just as an update - I never had a single Xid 61 lockup on ubuntu with the clock hack we settled on,since I wrote about it in message 214 June 9.
I just installed the newer driver (450.66) and took off the hack - can confirm that the gpu clock is now running idle at much more sane speeds which is nice to be honest. I will report back if the new driver has fixed anything.
I also noticed from here:
that the additional information tab mentions some other workarounds for bugs I hadnāt heard of:
- Disable flipping in nvidia-settings (uncheck "Allow Flipping" in the "OpenGL Settings" panel)
- Disable UBB (run 'nvidia-xconfig --no-ubb')
- Use a composited desktop
Update
Changing to xanmod kernal and updating grub with kernal parameter āpci=nommconfā fix this i think xanmod doesnt have any effect though.
For me PCIe bus fail on this issue rendering my system unusable.(no ssh , display sound hard disk mount wifi etc. It seems that everyone in the pcie bus goes missing when this happens but enabling āpci=nommconfā has done something which kind of fix this. ) Anybody have any idea why this configuration fix for me.
Hi elialbert,
thanks for coming back and reporting! I also installed 450.66 now and disabled our clock-fix workaround. I will let it run now for some time to see if the Xid-61 occurs again.
Any confirmation on if this āfixā was pushed to the WIndows Driver?
Not had the issue myself on WIndows since locking the card at Prefer Maximum Performance, but that also locks my card at maximum frequency 24/7 which also means constant heat.
Iāve updated to 450.66, and Iām still experiencing the Xid 61 error.
Hardware:
MB: Asus ROG STRIX X570-E Gaming (latest BIOS)
GPU: Asus Phoenix GeForce GTX 1650 Super
CPU: Ryzen 3900XT
OS: Fedora 32 (latest updates)
My situation is a little different than others.
After installing the proprietary driver (450.66) and with no other customization, it would predictably hang within a few minutes of starting the system. Every time. When hanging, the mouse cursor would move, but nothing else changed on the screen, Xid 61 was visible in the dmesg output, and nvidia-smi would show the ERR output.
With the nouveau driver, I didnāt have any issues (but I only used it for a few hours).
After applying the suggested fixes, nvidia-smi -pm ENABLED and nvidia-smi -lgc 1000,1740, stability improved dramatically, but it still froze again in less than 24 hours.
At this point, Iāve locked the frequency with nvidia-smi -lgc 1740,1740, and Iāve made the suggested PowerMizer āPreferred Modeā change.
I have a couple hours of uptime since my last hang, and I have my fingers crossedā¦ (I will report back.)
(And a huge thanks to all those whoāve helped with the workarounds! Without you, I wouldnāt have been able to type this message without experiencing a crash.)
I can confirm that after upgrading to the 450.66 driver I have not experienced an Xid 61 error (uptime about 4-5 days now). I am still locking the GPU frequencies to (700,1680) to keep it out of the lowest power state (P8, I believe); if I need to reboot again soon I will leave the frequencies alone and see what happens.
Previously I would encounter 1-2 Xid 61 errors per day, requiring 1-2 reboots to free up the graphics system. Whatever the change in the driver, that seems to at least be preventing the error from occurring in my system.
System:
ASRock X470 Gaming-ITX/ac with 32GB of memory (no overclock or XMP)
Ryzen 3700X (hyperthreading enabled, no overclock)
ā¦ and, at just over 2.3 hours of uptime, Iāve had it hang again. I had walked away from the machine (it was idle), and when I returned, I found it frozen. I was still able to connect to it via SSH, confirm the Xid 61, and see the ERR in the nvidia-smi output.
Iām currently investigating a theory that my Xid 61 errors are related to my motherboardās SOC voltage setting. The voltage was automatically increased when I selected the DOCP for my 3600 MHz RAM. Iāve now overridden the SOC voltage to a lower value, and Iām seeing significantly improved stability. Iāll follow up in a few daysā¦
@services_nvidia1, you were certainly on to something with the RAM speed! :) Before I first posted the other day, I had read your post along with all the others in this thread. When I now look back at your post, Iām sorry I didnāt give enough credit to its second half, i.e., āAND lowering main memory speed.ā I had focused on the ānvidia-smiā patch.
After lowering the SOC voltage (and not applying any other workarounds), my system, which would previously consistently encounter an Xid 61 error within a couple minutes of booting, has now been running for 11 hours. In the kernel logs, I should also note my CPU was reporting an error every few hours, e.g.,
Congrats! btw 3466 sorted out the clocks for me plus game me higher performance in graphics (games), it was tested by good sources to have 2x higher MIN_fps perf (which matters for stutters) vs 3600. Is it true? Well, at least it helps stability. Blabbed about the divider here.
Now the nvidia issuefest is shrinking in size, and issues leave the party as time goes on, i found 2 more solutions: [Status][Priority]Issue:Notes
[OK][High] Freezefest with Xid61: fix is to reduce clock or limit min PCI mode with nvidia-smi
[OK][High] blackscreen after login or resume - can be fixed with nvidia-settings advanced resolution settings, trying combinations, and sync it with desktop manager.
[KO][Medium] some windows empty after resume - cannot be fixed, you need to maximize window to refresh each time
[KO][Low] Waylandfreeze - have to wait few more years, but itās ok, stay with X11 and wait
[OK][High] framerate drop in firefox after resume: this was top priority as scrolling was poor, fix is to set layout.frame_rate to your target fps
Remaining issues were reproduced on 10 distros, driver 440,450,455, kernel 5.4,5.5,5.6,5.7,5.8. No, thereās no lucky distro #Distrofest :)
@thecakemaster From your system specs, we have the same MB and nearly the same processor. I have a Ryzen 9 3900XT. Iām curious whether youāve looked at the VDDCR SOC voltage in the BIOS?
