Battledield now throwing an error because Valorant is already sitting in kernel memory. Time to buy your EA Battlefield PC but don’t forget your Valorant PC
Battledield now throwing an error because Valorant is already sitting in kernel memory. Time to buy your EA Battlefield PC but don’t forget your Valorant PC
Soooo, you’re telling me, that if I want to use a NVIDIA graphics card in Linux, I am not allowed to load its official driver’s kernel modules unless I either deactivate secure boot or generate my own signing key and load it into the UEFI, as otherwise this would make the kernel untrusted. But on windows every $random_game_publisher is allowed to run at kernel level without it being considered untrusted?
deleted by creator
Who could have foreseen that letting game companies into the kernel would cause problems?
Micro transactions on intentionally caused blue screens when?
Microsoft, ironically. The one time they were right.
Granted, it wasn’t in anyone’s best interests but their own for not wanting anyone else to have kernel level access.
I’d like to report an issue with your code.
Well, see, there’s your problem. You handcrafted this code carefully, but didn’t think about today’s coding standards. That’s outdated code you use. Why use a simple print with variable substitutions, if you can instead just vibe print it by sending a rough description what your program tries to output to an LLM to account for such possible errors! /s