# Gaming tests w/kernel 7.3

**URL:** <https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261>\
**Category:** Gaming, sound and video\
**Created:** [November 1, 2026, 10:46pm UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261 "2026-11-01T22:46:48Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![ajgringo619](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ajgringo619/32/35599_2.png) [@ajgringo619](https://forum.endeavouros.com/u/ajgringo619)\
**Post date:** [November 1, 2026, 10:46pm UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261/1 "2026-11-01T22:46:48Z")

</div>

Running `xanmod-edge`, on version 7.3.1 (as of 2026-11-01), and `dmemcg-booster`.

First tested game: **Titan Quest 2**

This game consistently uses 5-6 GB of NVRAM, which pushes by RTX 4060 (w/ 8 GB) to the brink. The only way I could play before was to restart my PC, load basically nothing but **Steam**.

Today, I ran a fully-loaded system with TQ2. Not only was NVRAM never taxed (hit 7.3 GB briefly in one of the most graphically-intense areas, the Temple of the Moirai), there was absolutely no stuttering: never dropped below my FPS max limit of 90.

Next test will be **Cities: Skylines** , which has been a system killer unless I disabled almost all mods.

---

<div class="post-metadata">

**Author:** ![UncleSpellbinder](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/unclespellbinder/32/127055_2.png) [@UncleSpellbinder](https://forum.endeavouros.com/u/UncleSpellbinder)\
**Post date:** [November 1, 2026, 11:08pm UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261/2 "2026-11-01T23:08:24Z")

</div>

Still waiting for 7.3 on the stock and/or Zen kernels. Just had an update, but not to 7.3 yet…

`7.2.11.arch1-1 -> 7.2.14.arch1-1` and `7.2.11.zen1-1 -> 7.2.14.zen1-1`

---

<div class="post-metadata">

**Author:** ![ajgringo619](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ajgringo619/32/35599_2.png) [@ajgringo619](https://forum.endeavouros.com/u/ajgringo619)\
**Post date:** [November 1, 2026, 11:09pm UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261/3 "2026-11-01T23:09:59Z")

</div>

Hmmm…it hasn’t even hit `core-testing` yet.

---

<div class="post-metadata">

**Author:** ![Schlaefer](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/schlaefer/32/11917_2.png) [@Schlaefer](https://forum.endeavouros.com/u/Schlaefer)\
**Post date:** [November 1, 2026, 11:21pm UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261/4 "2026-11-01T23:21:43Z")

</div>

> [@ajgringo619](#):
>
> dmemcg-booster

Isn’t that mesa only (AMD/Intel)?

---

<div class="post-metadata">

**Author:** ![ajgringo619](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ajgringo619/32/35599_2.png) [@ajgringo619](https://forum.endeavouros.com/u/ajgringo619)\
**Post date:** [November 1, 2026, 11:28pm UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261/5 "2026-11-01T23:28:39Z")

</div>

According to this Reddit post (and subsequent Nvidia driver link), it’s now supported. How well it works is another story.

---

<div class="post-metadata">

**Author:** ![ajgringo619](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ajgringo619/32/35599_2.png) [@ajgringo619](https://forum.endeavouros.com/u/ajgringo619)\
**Post date:** [November 1, 2026, 11:32pm UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261/6 "2026-11-01T23:32:06Z")

</div>

My initial testing of **Cities: Skylines** was successful. Game never got above 7.2 GB of NVRAM, although I did notice a minor spike of ZRAM usage (\<10%). And this was with several mods, including **Move It** , which was notorious for killing my machine.

---

<div class="post-metadata">

**Author:** ![UncleSpellbinder](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/unclespellbinder/32/127055_2.png) [@UncleSpellbinder](https://forum.endeavouros.com/u/UncleSpellbinder)\
**Post date:** [November 2, 2026, 4:31am UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261/7 "2026-11-02T04:31:43Z")

</div>

Moved to 7.3 Xanmod via [**Chaotic AUR**](https://aur.chaotic.cx/packages?search=xanmod-edge).

```auto
─❯ uname -r
7.3.0-xanmod1-1-edge-x64v3
─❯

```

My GPU is a _ZOTAC Nvidia GeForce RTX 3060 Ti (8GB GDDR6 VRAM)_. My only issues were occasional stuttering in **Metro Exodus** and **X4: Foundations** the past several weeks. The past 90 minutes or so playing **Metro Exodus** have been stutter-free. Next weekend (this week at work will be a long week with little time to play games) I’ll test further. But so far, so good!

---

<div class="post-metadata">

**Author:** ![ajgringo619](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ajgringo619/32/35599_2.png) [@ajgringo619](https://forum.endeavouros.com/u/ajgringo619)\
**Post date:** [November 2, 2026, 5:09am UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261/8 "2026-11-02T05:09:23Z")

</div>

Chaotic must be behind. I’m on the following (from this afternoon):

```auto
linux-xanmod-edge-linux-bin-x64v3 7.3.1-1
linux-xanmod-lts-linux-bin-x64v3 6.18.60-1

```

---

<div class="post-metadata">

**Author:** ![UncleSpellbinder](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/unclespellbinder/32/127055_2.png) [@UncleSpellbinder](https://forum.endeavouros.com/u/UncleSpellbinder)\
**Post date:** [November 2, 2026, 5:12am UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261/9 "2026-11-02T05:12:19Z")

</div>

I didn’t even think to check for a `bin` version in the AUR.

---

<div class="post-metadata">

**Author:** ![ajgringo619](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ajgringo619/32/35599_2.png) [@ajgringo619](https://forum.endeavouros.com/u/ajgringo619)\
**Post date:** [November 2, 2026, 6:13am UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261/10 "2026-11-02T06:13:55Z")

</div>

After going through a crapload of kernel compiles during my time with Gentoo, I basically refuse to do that anymore.

---

<div class="post-metadata">

**Author:** ![HeinzDo1961](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/heinzdo1961/32/118845_2.png) [@HeinzDo1961](https://forum.endeavouros.com/u/HeinzDo1961)\
**Post date:** [November 2, 2026, 1:05pm UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261/11 "2026-11-02T13:05:16Z")

</div>

It feels like kernel upgrades (e.g., from 7.2 to 7.3) are arriving later and later.

---

<div class="post-metadata">

**Author:** ![chroot](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/c/90db22/32.png) [@chroot](https://forum.endeavouros.com/u/chroot)\
**Post date:** [November 2, 2026, 1:35pm UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261/12 "2026-11-02T13:35:27Z")

</div>

Try a bore or pds kernel. They are famous for better gaming performance.

---

<div class="post-metadata">

**Author:** ![ajgringo619](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ajgringo619/32/35599_2.png) [@ajgringo619](https://forum.endeavouros.com/u/ajgringo619)\
**Post date:** [November 3, 2026, 6:20am UTC](https://forum.endeavouros.com/t/gaming-tests-w-kernel-7-3/82261/13 "2026-11-03T06:20:15Z")

</div>

Another update. Played another 2+ hour session, went right to the NVRAM max, never slowed down in the slightest. Still got some of these messages:

```auto
Nov 02 22:14:49 kernel: NVRM: intermapRegisterDmaMapping: Failed to insert new mapping node for range 0xDF7E020000-0xDF7E0AFFFF!
Nov 02 22:14:49 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: NV_OK == status @ gpu_vaspace.c:4586
Nov 02 22:14:49 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: NV_OK == status @ gpu_vaspace.c:2080
Nov 02 22:14:49 kernel: NVRM: nvCheckFailedNoLog: Check failed: 0 == (pMapNode->gpuMask & gpuMask) @ gpu_vaspace.c:4503
Nov 02 22:14:49 kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Invalid argument to call [NV_ERR_INVALID_ARGUMENT] (0x0000001F) returned from _gvaspaceMappingInsert(pGVAS, pGpu, pVASBlock, vaLo, vaHi, flags) @ gpu_vaspace.c:2036
Nov 02 22:14:49 kernel: NVRM: nvCheckFailedNoLog: Check failed: NV_OK == status @ virt_mem_allocator_gm107.c:2563
Nov 02 22:14:49 kernel: NVRM: dmaAllocMapping_GM107: can't update VA space for mapping @vaddr=0x216a00000
Nov 02 22:14:49 kernel: NVRM: intermapRegisterDmaMapping: Failed to insert new mapping node for range 0xDF7E020000-0xDF7E0AFFFF!
Nov 02 22:14:49 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: NV_OK == status @ gpu_vaspace.c:4586
Nov 02 22:14:49 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: NV_OK == status @ gpu_vaspace.c:2080
Nov 02 22:14:51 kernel: NVRM: intermapRegisterDmaMapping: Failed to insert new mapping node for range 0xDF7E020000-0xDF7E0AFFFF!
Nov 02 22:14:51 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: NV_OK == status @ gpu_vaspace.c:4586
Nov 02 22:14:51 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: NV_OK == status @ gpu_vaspace.c:2080
Nov 02 22:15:01 kernel: NVRM: nvCheckFailedNoLog: Check failed: 0 == (pMapNode->gpuMask & gpuMask) @ gpu_vaspace.c:4503
Nov 02 22:15:01 kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Invalid argument to call [NV_ERR_INVALID_ARGUMENT] (0x0000001F) returned from _gvaspaceMappingInsert(pGVAS, pGpu, pVASBlock, vaLo, vaHi, flags) @ gpu_vaspace.c:2036
Nov 02 22:15:01 kernel: NVRM: nvCheckFailedNoLog: Check failed: NV_OK == status @ virt_mem_allocator_gm107.c:2563
Nov 02 22:15:01 kernel: NVRM: dmaAllocMapping_GM107: can't update VA space for mapping @vaddr=0x1f4600000
Nov 02 22:15:03 kernel: NVRM: intermapRegisterDmaMapping: Failed to insert new mapping node for range 0xDF7E020000-0xDF7E0AFFFF!
Nov 02 22:15:03 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: NV_OK == status @ gpu_vaspace.c:4586
Nov 02 22:15:03 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: NV_OK == status @ gpu_vaspace.c:2080

```

These would have been extremely noticeable before, even to the point of the game freezing until I could free up some NVRAM from other processes.
