Skip to content

Random occasional video freezes (Xid 62) with no other errors #1017

@NoTuxNoBux

Description

@NoTuxNoBux

NVIDIA Open GPU Kernel Modules Version

590.48.01

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.

  • I confirm that this does not happen with the proprietary driver package.

Operating System and Version

Arch Linux

Kernel Release

6.18.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 24 Jan 2026 00:47:39 +0000 x86_64 GNU/Linux

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.

  • I am running on a stable kernel release.

Hardware: GPU

GPU 0: NVIDIA GeForce RTX 4090 Laptop GPU (UUID: GPU-31eda2d2-5404-a711-e1a7-1be574d4a03e)

Describe the bug

At random times on my work account I will get a full video freeze on my secondary monitor attached to my NVIDIA GPU. Linux itself stays running since if music is playing, it keeps on playing, but at that point it's impossible to drop to a TTY, nor can I get the primary display (hooked to the AMD GPU) to work any more by unplugging the cable.

To Reproduce

Wait. Might be related to WebGL loads being run in Firefox or Unity, but that is uncertain (see above).

Bug Incidence

Sometimes

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

On my work account I usually work with Unity and WebGL, and so far I've only had this happen when WebGL and/or Unity were open. This might be coincidence or not, but I haven't experienced this on my home account which drives games that max out the GPU. There may be some specific load that triggers it.

Probably most importantly, this shows up in the logs:

NVRM: Xid (PCI:0000:01:00): 62, 32344000 00006768 00000000 202e8674 202e7308 202e7466 202e5bb4 202e621c
NVRM: GPU at PCI:0000:01:00: GPU-31eda2d2-5404-a711-e1a7-1be574d4a03e

There appear to be no other related errors; most hits for this issue have other issues being logged but mine never does. Also, the log is always identical, as in: the parameters after the 62 remain the same, as if some assertion is being hit somewhere.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions