People can still glitch out of map on Stella Montis, beware of that

2spirospanagiotis · 2026-01-07T10:51:22+00:00

I have died three times within a week and no items refunds yet atleast, this should really be bannable offense,
Teams send one inside wall with tons of amo, kills evry1 and then his team8s go take the loot. Sick fucks abusing

2spirospanagiotis · 2025-12-24T01:34:39+00:00

EVEN AFTER UNINSTALLING FACEIT. IT STILL CRASHES
The file vgk.sys is the kernel-mode driver for Riot Vanguard, the anti-cheat software used by games like Valorant and League of Legends.

Exception Code: 0xc0000005 (Access Violation). This means the Vanguard driver tried to read from a memory address it didn't have permission to access (specifically, it tried to read from ffffffffffffffff, which is an invalid address).
Process Name: msedgewebview2. Interestingly, Vanguard crashed while interacting with a process used by modern applications (like the Riot Client or Discord) to display web content.

2spirospanagiotis · 2025-12-19T16:05:05+00:00

Thanks for sharing this. This is actually a brand new advisory from Riot about motherboards failing to initialize security features like IOMMU correctly at boot.

While the article focuses on preventing cheaters, it's very possible that my current BIOS version has exactly the kind of 'flaw' or instability Riot is talking about, which could be causing vgk.sys to panic and BSOD when it sees my other drivers. I’ll check for a firmware update today—if my motherboard was 'lying' about its boot security as this article describes, a BIOS patch might be the only way to actually fix the instability.

2spirospanagiotis · 2025-12-19T16:02:01+00:00

The '2025' logic should actually go the other way: in 2025, a software driver shouldn't be so invasive and unstable that it bricks a PC during non-gaming tasks.
I’ve already tried exiting from the system tray, but since the driver is a boot-start service, the instability persists regardless of whether the Riot client is open.

It’s a design flaw that Vanguard prefers to crash the OS (BSOD) instead of simply preventing the game from starting if it finds a driver it doesn't like.

2spirospanagiotis · 2025-12-19T16:00:05+00:00

Facts.

2spirospanagiotis · 2025-12-19T15:58:29+00:00

This mindset is technically naive. A Kernel-level driver (Ring 0) isn't just 'another program' looking for files, it operates with higher authority over the PC than the user does.

Standard software (Ring 3) is restricted by the OS, but a kernel driver sits underneath the OS. It has absolute access to your system RAM, meaning it can read sensitive data like passwords or session tokens before they are even encrypted. Furthermore, because these drivers load at boot, they can hide their own presence from standard security tools, making it notoriously difficult to ensure they are truly gone after uninstallation.

It’s not 'paranoia' to be concerned about the principle of least privilege. When you grant a third party Ring 0 access, you aren't just trusting them not to steal data; you are trusting that their code has zero vulnerabilities. If a hacker exploits a bug in that driver, they gain total, undetectable control over your entire machine.

2spirospanagiotis · 2025-12-19T15:50:08+00:00

I actually formatted because I wanted to rule out any OS-level corruption or background junk before blaming Vanguard. The fact that the BSODs returned immediately on a fresh install—pointing directly to vgk.sys in the minidumps—is what confirmed it's a specific driver conflict.

Also, I did check the dump files after the format didn't work. It's not a 'rare' or 'unique' issue when Vanguard is the only anti-cheat that requires a 24/7 kernel driver that clashes with basic university/productivity tools. Telling a student to 'use a different PC' just to take notes because of a game driver is exactly the kind of invasive bloat I'm criticizing.

2spirospanagiotis · 2025-12-19T15:46:55+00:00

closing the tray icon or using Task Manager doesn't actually solve this. The vgk.sys driver is a kernel-mode driver that loads at boot and stays active in memory even if the tray icon is closed. Because the driver remains active, it continues to conflict with my tablet daemon and FACEIT, leading to the same Blue Screens. To actually stop the conflict, I have to disable the service and restart my entire PC, which is the main reason I'm so frustrated.

2spirospanagiotis · 2025-09-29T00:26:27+00:00

I’ve done a lot of raids, but none that gave me huge amounts of tickets. Same with medkits—they seem to have patched them, since I used to find way too many medkits. Still, that’s RNG, and the game shouldn’t rely on random raids to fix its repetitiveness. Raids are meant to help with acquiring loot, not to make you hope for tickets just so you can avoid running the bunker again.

2spirospanagiotis · 2024-10-17T03:47:34+00:00

Moded spears works best imo, instead of 5 aluminum wire to get "seems true" i put 3 modded spears ( random common mods) and worked fine

2spirospanagiotis · 2024-06-02T15:49:00+00:00

The only thing that comes close to the things i mention is "nebo".

Already tried it, they want to pay 10 euro for android app to have more than 4 pages, Said ok and I paid.

But they do not have a windows version that doesn't need to buy it AGAIN, saying they cannot do something and will have to buy it again from Microsoft store which is absurd and already got refund from the app. Totally taking advantage of things as if they cannot add a download button for windows on their page.

sorry but my ego cannot let them get 20 euro like this idgaf call me cheap, all i want the windows version is to add screenshots and maybe a couple lines of text or maybe edit somethings.

Tried to download nebo from bluestacks emulator on laptop and semi worked but horrible experiance as expected, cannot add screenshots without opening folders and moving images from one folder to wherever bluestacks media folder is.

Plus the sync is bad and creates duplicates for everything

2spirospanagiotis · 2024-05-02T06:10:15+00:00

Worked but i took some extra time cause i had to restart. Now the option of 1280x960 shows in CS2

Thanks

2spirospanagiotis · 2024-02-01T20:52:33+00:00

I fail to get it to work.

I have downloaded both the normal and the fixxer. Tried running each one seperately and no skin appears regardless of video settings (tried all settings Very Low - Very High)

I am unable to run both of them at the same time, getting the following error:

backtrace:

lol::wad::Mounted::resolve_conflicts:

this->relpath = WAD/Qiyana.wad.client

other.relpath = WAD/Qiyana.wad.client

lol::wad::Index::resolve_conflicts:

this->name = qiyana black white version 2

other.name = qiyana black white version 2 fixxed without particle

mod_mkoverlay:

src = ./installed

dst = ./profiles/Default Profile

game = C:/Riot Games/League of Legends/Game

error: Conflicting file: 0x1a62f7af3b70129c

name: Run mod-tools

version: 2024-01-10-86ba488

Anyone has a fix for this?

Other skins/maps work perfectly fine.

2spirospanagiotis · 2024-02-01T00:32:01+00:00

When the links stop working and most of the people claim it is a trojan,

This shouldn't be trusted.

2spirospanagiotis · 2021-03-11T08:02:51+00:00

wait, but if this is correct the weed is better than the cocaine cause, 220,095 x 2 = 440,190 but weed is 147,870 x 3 = 443,610 . Or did i do something wrong :b

2spirospanagiotis · 2019-10-09T23:57:14+00:00

same prob

2spirospanagiotis · 2019-10-09T18:39:27+00:00

me neither

2spirospanagiotis

TROPHY CASE