⨯ Every article tag can be clicked to get a list of all articles in that category. Every article tag also has an RSS feed! You can customize an RSS feed too!
Games accessing the hard drive unmounts it and the game crashes
Dwinn Nov 25, 2022
Hi, im relative new to linux and usually look up errors by my self. But now i don`t know any further than to write by myself now.
The problem is a lot of my games i trie to play crashes after a certain amount of time. Sometimes i get the error that it isn´t possible to connect to the nvme. If i close the game and look into dolphin the disks aren´t mounted anymore. Remounting in Terminal fails. Only solution is to restart the hole computer than everything works fine.
It does not happen on smaler games like Walking Simulator or How to survive. And it only happens if the game access the harddisk. This happens in Witcher 2, Hitman and lately in Cities Skylines(Autosave).
It happens on Nvme and SSD, on Boot drive or additional drive. And it happens on Proton, ProtonGE and as i sadly recognized today, on Native too.
I am on Manjaro, but it happend in Mint too.
I do not know how to create usefull logs. The basic steam logs don´t help. Maybe there is a way to create usefull logs and someone can help me, or has any idea how this happens?
peta77 Nov 25, 2022
Had a somewhat similar problem a while ago on a little bit older workstation where the nvme was rather slow and disappearing after a while (randomly) and only reboot brought it back. For me it was: I used a PCIe-controller / adapter to include it into the system as there was no nvme slots on the mainboard. Putting it into a different PCIe slot with higher rating solved it for me.
If that doesn't help, maybe try using a different nvme-slot on the mainboard, if you have or try a different sata-port for the ssd.
I think it's rather a hardware (compatibility) problem than anything with any software....

Regarding logs: maybe 
  dmesg has something useful included in its output.
Dwinn Nov 26, 2022
Thank you for your answer.
I don´t think it's a hardware problem because i tried installing the games on nvme(pcie) on slot 1, another nvme (pcie) on slot 2 and even on sata ssd. Only the drive the game is installed got unmounted. I can only think of that it has to do something with the motherboard drivers (x470). But as far as i know nvme-pcie and sata use diffrent drivers. So i rule that out.
I will try dmesg after a unmount and see if the drive is still visible.

Dmsg logs following the moment it crashes(shortend)
Spoiler, click me
process 'steamapps/common/Cities_Skylines/Cities.x64' started with executable stack
[26. Nov 14:01] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
[ +0,000006] nvme nvme0: Does your device have a faulty power saving mode enabled?
[ +0,000002] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
[ +0,053662] nvme0n1: Read(0x2) @ LBA 325110304, 256 blocks, Host Aborted Command (sct 0x3 / sc 0x71)
[ +0,000000] nvme0n1: Read(0x2) @ LBA 325110048, 256 blocks, Host Aborted Command (sct 0x3 / sc 0x71)
[ +0,000009] I/O error, dev nvme0n1, sector 325110048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[ +0,000001] I/O error, dev nvme0n1, sector 325110304 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2
[ +0,059619] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[ +0,000105] nvme nvme0: Removing after probe failure status: -19
[ +0,026572] nvme0n1: detected capacity change from 2000409264 to 0
[ +0,181253] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000056] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000043] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,050700] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000052] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000047] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,372611] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #51773442: lblock 0: comm QThread: error -5 reading directory block
[ +0,000031] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #51773442: lblock 0: comm QThread: error -5 reading directory block
[ +0,000019] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #51773442: lblock 0: comm QThread: error -5 reading directory block
[ +0,000014] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #51773442: lblock 0: comm QThread: error -5 reading directory block
[ +5,445204] Aborting journal on device nvme0n1p1-8.
[ +0,000004] Buffer I/O error on dev nvme0n1p1, logical block 124813312, lost sync page write
[ +0,000002] JBD2: Error -5 detected when updating journal superblock for nvme0n1p1-8.
[ +24,869431] EXT4-fs warning: 7 callbacks suppressed
[ +0,000002] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000025] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000019] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000017] EXT4-fs error (device nvme0n1p1): ext4_journal_check_start:83: comm CIPCServer::Thr: Detected aborted journal
[ +0,000002] EXT4-fs (nvme0n1p1): Remounting filesystem read-only
[ +0,000218] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000022] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000018] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[26. Nov 14:02] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000041] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000031] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,050884] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000041] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000031] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +30,731886] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000031] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000024] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,050697] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000051] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000030] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[26. Nov 14:03] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000033] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000025] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000322] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000029] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000023] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +30,727697] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000041] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000031] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000385] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000035] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000030] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[26. Nov 14:04] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000032] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000023] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000244] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000027] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000022] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +1,743285] EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1663: inode #51789299: comm Cities.x64: reading directory lblock 0
[ +0,000029] EXT4-fs error (device nvme0n1p1): __ext4_find_entry:1663: inode #51789299: comm Cities.x64: reading directory lblock 0
[ +28,984011] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000027] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000020] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,050789] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000041] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000031] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[26. Nov 14:05] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000034] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000024] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,050824] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000028] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000019] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +30,608377] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000033] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000023] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,050771] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000025] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000018] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[26. Nov 14:06] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000032] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000024] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,050887] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000025] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +0,000019] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block
[ +18,744909] audit: type=1701 audit(1669467992.497:231): auid=1000 uid=1000 gid=1001 ses=2 subj=unconfined pid=4253 comm="Cities.x64" exe="/mnt/nvme/Samsung1TB/SteamLibrary/steamapps/common/Cities_Skylines/Cities.x64" sig=7 res=1
[ +0,005166] audit: type=1334 audit(1669467992.501:232): prog-id=32 op=LOAD
[ +0,000051] audit: type=1334 audit(1669467992.501:233): prog-id=33 op=LOAD
[ +0,000016] audit: type=1334 audit(1669467992.501:234): prog-id=34 op=LOAD
[ +0,037008] audit: type=1130 audit(1669467992.541:235): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=systemd-coredump@0-5750-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ +12,323007] EXT4-fs warning (device nvme0n1p1): htree_dirblock_to_tree:1072: inode #2: lblock 0: comm CIPCServer::Thr: error -5 reading directory block

Is it a power problem because of the faulty power saving mode?

Last edited by Dwinn on 26 November 2022 at 1:10 pm UTC
peta77 Nov 26, 2022
Do you have any power saving for hard disks enabled? They usually don't make much sense for flashdrives like SSD and nvme. Won't hurt to try to turn it off. And to try to set those values mentioned in the dmesg-log. Only the first few lines are relevant. The remaining stuff is just a consequence of the nvme not being correctly available anymore.

Does the nvme still show up as a device? Look at "/dev/nvm....". You can look up the id by looking at /etc/fstab and if it's referred by uuid then there should be a link in "/dev/disk/by-uuid" which points to something in "/dev". If it's still there, then at least it doesn't get disconnected.

When there's a general power problem I'd assume you'd rather notice it by graphical issues or something, but it would be surprising if the storage would loose power first. But surely depends on the layout of the mainboard and how the PSU distributes power.
But to rule it out, do you have a bigger PSU available just for trying? Or are there any (power demanding) internal devices you could temporarily remove? Or external like harware connecte via USB that don't have their own power supply? Or put those USB devices into a separately powered USB-Hub.

Last edited by peta77 on 26 November 2022 at 1:41 pm UTC
Dwinn Nov 27, 2022
As far as i know there is now power saving feature enabled. I looked in bios and in system settings. Is there a not listend energy saving like in windows?

Its an 850watt "Gold" rated PSU so enough headroom for anything. But i don't have anything connected other than mouse keyboard and sound.

The nvme doesn't show up after the crash in /dev/disk/by-uuid and i don't have /dev/nvme... only dev/disk

How can i apply "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off"? Is it a file like fstab but called nvme_core?
peta77 Nov 27, 2022
The desktop environments usually have some power settings and there might be global settings too... I usually only fiddle with those of the desktop environment as they apply to the currently logged in user..

Yes, PSU should be more than good enough for any single gpu setup...

/dev/nvme<num> would be a file, not a directory... like normal disks and ssds showing up as /dev/sda, sdb, sg0, sg1, etc.

Don't know where those options are specified... Maybe as kernel parameters on boot? At least that's what the first matches on a web search suggest, excerpt:
if you're using grub, add those to variable GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, run update-grub and reboot
or you could also specify them in the boot menu, if you have that activated...
BlackBloodRum Nov 27, 2022
I'm not an expert but.. a few things that may be worth checking:

1) Temperatures, how hot is your drive getting when this occurs? Some nvme's can have issues when they get too hot.
2) Which NVMe do you have exactly? Some are known to have firmware issues that cause problems on Linux, Kingston for example may require a firmware update to prevent it locking up under Linux. You can easily check which device it is with "smartctl --all /dev/nvme0"

(replace 0 with your drives number)

3) Double check again the hardware using data from the above output, important things to look for:

- Error Information Log Entries: Ideally should be 0
- Warning Comp. Temperature Time: If above 0, it indicates the drive has spent time overheating.
- Critical Comp. Temperature Time: Same as above. If you have either of these, look into providing better airflow or cooling for the device.
Dwinn Nov 27, 2022
Thank you BlackBloodRum but Temperatures are not a problem. Drive never gets over 60°C

Its an SAMSUNG MZVLB1T0HALR and had same problems with a kingston sa2000 and and crucial ssd

Error Log on Samsung says
Error Information Log Entries: 2.125
Num ErrCount SQId CmdId Status PELoc LBA NSID VS
0 2125 0 0x0004 0x4004 - 0 0 -
Critical Warning: 0x00
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0

As far as i understand this is not a problem but refers to initialisation error, which is an error to be exprected if the drive is unmounted in an unusual way. At least thats what i found searching for this error.

Thank you peta77. I added this and will test.
BlackBloodRum Nov 28, 2022
Firstly, the Kingston A2000 is a known one for issues with Linux on its older firmware, I actually have one of these, and had to update the firmware on it to resolve it (from Linux).

Couple of next steps - rule out the motherboard and/or controller errors by temporarily placing the NVMe into another computer if you can and placing a similar load onto it.

Secondly; this may be useful for you:
https://wiki.archlinux.org/title/Solid_state_drive/NVMe#Troubleshooting

I know it's Arch Linux; but much of the Arch Linux documentation can be applied to most distro's with relatively minor tweaks.

Hope it helps!

Last edited by BlackBloodRum on 28 November 2022 at 3:13 am UTC
whizse Nov 28, 2022
There's a quite similar issue described in this reddit post. Unfortunately that turned out to be a faulty PSU.

You should absolutely try the kernel parameters suggested, but this does sound like a hardware issue.
Dwinn Nov 28, 2022
Ok some development: I tried my old Rx580 and couldn't get it to crash. But i although couldn't get it to the same condition with 2x 4k Monitors one 60hz one 144hz. It only managed, after some cable tampering, to get it to 2x 60hz. So i thought it is a driver problem with two different Hertz settings and switched back to my 6900. I tried 2times 60hz with cities skylines and no crash after an hour. Usually it crashed after some minutes. The same with Witcher 2 that i tried afterwards for 20-30 Minutes with no crash. To be sure i switched back to 1x 144hz 1x60hz and..... NO Crash in Cities Skylines, witch pretty safe crashed before. Maybe a cable/reseating problem? Recapturing what i done i was remembering putting the monitor cables 144hz in Slot 2, 60hz in Slot 1 instead of vice versa. Maybe this fixed something?
To go further i played Witcher 2 which was the game i really wanted to play and played for 30 Minutes and then it crashed. BUT without unmounting the drive??? The Samsung was still accessable. Why?
I keep logging proton and it says: Bytecode does not match shader cache; alongeside some other information. Its 30k rows code that i don't want to post all here. I remembered the first problems i had with witcher 2 and some kind with shader errors. It think it developed into unmounting over time and then i installed cities and it happend there to after some time. But i'm not sure. I will test it further.
At this point i believe its a problem in the grafic driver or a problem with temp files staggering up.
Are there proton log file analyst experts here?
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register

Or login with...
Sign in with Steam Sign in with Google
Social logins require cookies to stay logged in.
Register Forgot Login?
★ Support Us
Popular this week
Search or view by category
Contact
Latest Comments
Latest Forum Posts
Misc