#RTX 5090 Xid 31 FAULT_PDE ACCESS_TYPE_VIRT_READ

2 messages · Page 1 of 1 (latest)

hoary flint
#

Hello,

I'm trying to debug this Xid 31 error I got from playing No Rest For The Wicket.
I've been playing this game on my older PC with omarchy with no issue (RTX 2060 Super)

Then I installed omarchy on my newer PC with RTX 5090 and after about 10 mins of gameplay the game lagged and didn't recover so I had to kill it.

Then I looked at the logs:

Mon 2025-12-15 19:20:02.934763 PST [s=dd0f1ee84d8a48d3b0a0955714b63c7a;i=6db8;b=26b9db60606f4470a8e4abed9131dadd;m=cb273473;t=6460934187feb;x=37d752fc1ffa9a02]
    _MACHINE_ID=1f33a11de93c46c39fc5711a9456b247
    _HOSTNAME=mystery
    _RUNTIME_SCOPE=system
    _TRANSPORT=kernel
    SYSLOG_FACILITY=0
    SYSLOG_IDENTIFIER=kernel
    PRIORITY=4
    _BOOT_ID=26b9db60606f4470a8e4abed9131dadd
    _SOURCE_BOOTTIME_TIMESTAMP=3408380018
    _SOURCE_MONOTONIC_TIMESTAMP=3408380018
    MESSAGE=NVRM: Xid (PCI:0000:01:00): 31, pid=11720, name=NoRestForTheWic, channel 0x00000017, intr 00000000. MMU Fault: ENGINE GRAPHICS HUBCLIENT_PD faulted @ 0x9_600bc000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ
#

I don't think its the application since the game works fine out of the box on my 2060 PC.
I'm thinking it could be either the driver for 5090 or the hardware because I bought the PC pre-built from falcon northwest and one thing I noticed is that they have an AI overclocked set to EXPO1