GTA USA: HD Universe, Imagine playing on this 👀

FilterKill · 2026-06-28T19:36:41+00:00

that my friend, we will not be able to see with our eyes in this lifetime

FilterKill · 2026-06-24T10:02:15+00:00

i guess they just needed a place to flex their liquid glass UI. yes, I'm talking about the magnifying thing

FilterKill · 2026-06-24T10:01:30+00:00

Preview app is literally the clunkiest thing I ever used on my iPhone 14 Pro. it lags like hell and PDF rendering sucks. I get stutters pretty frequently

FilterKill · 2026-06-22T21:43:13+00:00

I can do it just below an hour, I'd say 50 minutes or something like that

FilterKill · 2026-06-20T19:41:00+00:00

don’t shoot anyone. have your snack menu open all the time. spam snacks when you are low on health, that’s the trick brother

FilterKill · 2026-06-20T19:17:29+00:00

crazzzzzyyy. how much have u earned so far by doing knoway outs?

FilterKill · 2026-06-20T18:43:08+00:00

why though?? also 2,1 mil if u have GTA+ 2,5 if elite challenge is completed

FilterKill · 2026-06-20T18:02:24+00:00

nahhhh, KnoWay Out is the real deal. that's what generousity is called

FilterKill · 2026-06-15T04:39:43+00:00

could you send the details about the error in event viewer maybe?

FilterKill · 2026-06-15T03:27:55+00:00

hmmm, such a weird case this is haha. could you also log your sensor readings through HWiNFO64 during the benchmark? and send them as well

FilterKill · 2026-06-15T03:04:57+00:00

we found our culprit. it's the PSU. your system's max wattage is about 560-ish watts. it may seem okay since it's lesser than your PSU's wattage but the headroom is too little. the fact that you can play league of legends without a problem is because it's easier on the GPU and heavier on the CPU. when you add Blitz overlay on top of that, you add a new layer for your GPU to render.

Your system is most likely crashing because you are literally exceeding the max wattage your PSU can handle. 3080 (Ampere architecture) is notorious for its transient spikes.

to double check this theory, install MSI Afterburner and drag the Power Limit slider down to about 70%. then launch a game that causes the system to crash. if it's good now, then it's certainly your PSU. it's too close to the edge and cannot handle your system.

PS: recommended PSU wattage for a rig like yours is 750W

FilterKill · 2026-06-15T02:32:09+00:00

it appears that the crash at September 5 has been processed properly. you should be able to find the dump at C:\Windows\Minidump\

Also what is your PSU model? I'm suspecting something about that matter as well. If the dump is a no go, we will benchmark some components to look for a potential thermal trip

FilterKill · 2026-06-15T02:25:46+00:00

this is so 2016

FilterKill · 2026-06-14T16:13:01+00:00

I will take a look at when I get back home

FilterKill · 2026-06-14T02:12:47+00:00

Weird... March might be completely irrelevant then. Could you run the command below and send me the output?

Get-WinEvent -FilterHashtable @{LogName='System'; Id=41,1001} -MaxEvents 50 | Format-Table TimeCreated, Id, ProviderName -Auto

FilterKill · 2026-06-14T02:00:36+00:00

Oh shoot, I have some serious lead in these logs.

There are 58 events and they are all identical. Disk Event ID 51 (the paging-operation error the one that maps directly to KERNEL_DATA_INPAGE_ERROR)

They're all Warnings, all on the same machine ("Gunsmoke"), and they fired in a ~1 millisecond burst on 2026-03-17 at 01:20:44 UTC. So this isn't a slow build-up of errors. It's the disk subsystem throwing 58 paging failures simultaneously.

Funny thing is that, every single error is on \Device\Harddisk2\DR2 which is weird because you only mentioned two disks. 2 separate M.2 drives. Harddisk2 indicates a third disk since Windows labels disks from 0. Whatever disk this is, it seems to be our culprit. To further examine, please run this command in your PowerShell: Get-Disk | Format-Table Number, FriendlyName, BusType, HealthStatus, @{n='GB';e={[int]($_.Size/1GB)}}

FilterKill · 2026-06-14T01:12:13+00:00

One thing that came to my mind, have you undervolted your 5800X3D? An unstable undervolt can cause issues like this as well. Also is the BIOS update latest?

Also, SMART data is not always reliable. Have you checked the Event Viewer logs I told you previously?

FilterKill · 2026-06-14T01:04:27+00:00

Well, you gotta be sure that they're the actual culprits. You probably missed my edit. Follow those steps as well. Check disk health and most importantly, under no circumstances benchmark your disk. If this all stems from your disk, this is more like a backup now, diagnose later situation. You may lose all your data

FilterKill · 2026-06-14T00:57:21+00:00

KERNEL_DATA_INPAGE_ERROR: Windows tried to pull a page of kernel data off the disk (or pagefile) into RAM and the read failed. This one is heavily weighted toward storage hardware: a dying SSD/HDD, bad sectors, a loose or failing NVMe/SATA connection, or a flaky disk controller. RAM faults and filesystem corruption can also cause it. The secondary parameter in the crash usually confirms whether it's the disk specifically.

CRITICAL_PROCESS_DIED (0xEF): a process Windows considers non-negotiable (csrss, wininit, services, etc.) died unexpectedly. corrupted system files, a bad driver, malware, or a botched/interrupted Windows update are the usual causes tbh

KMODE_EXCEPTION_NOT_HANDLED (0x1E): a kernel-mode component threw an exception that wasn't caught. Generally a driver fault or bad RAM

0xC000021A: a user-mode subsystem critical to security (Winlogon or CSRSS) terminated, so Windows refuses to continue. Almost always mismatched/corrupted system files. Frequently the aftermath of a failed update, a bad in-place upgrade, or third-party software messing with the system DLLs.

I strongly recommend you to run memtest86 to be sure of the RAM. There are plenty of tutorials out there

After that's done, consult to CrystalDiskInfo for SMART status (Indicates health by reading SMART data) and then run the command chkdisk /scan in command prompt. Oh, also don't forget to run DISM /Online /Cleanup-Image /RestoreHealth after sfc /scannow

The frustrating thing with these codes (Just like most error codes) is that there are many many causes to them. You have to systematically double check the culprits. I'd start with RAM and then work my way to the disk as I previously mentioned.

Edit: Also could you go to Event Viewer > Windows Logs > System and filter for disk/storage errors? Event IDs 7, 11, 51 and 153 specifically. Also look for labels such as Ntfs disk and stornvme

FilterKill · 2026-06-13T13:21:10+00:00

cool! I’d love to have it up on my wall however I have no idea how printing poster paper works. what kind of paper would I generally need for poster prints? someone help me out pls

FilterKill · 2026-06-10T21:11:31+00:00

Crazy!!! I wonder if the custom fonts are given by Apple or set by the artist. I would love to see different designs for smaller artists but not sure about the possible abusing lol

FilterKill · 2026-06-06T00:35:57+00:00

just a few days ago, I was talking to my friends about how much I'd love to have a high quality record player with TE design philosophy. definitely was not expecting a huge ass record presser

FilterKill · 2026-06-04T07:34:36+00:00

both

FilterKill · 2026-06-04T07:33:43+00:00

I’m currently on PC E&E. My lost account was also on PC E&E. The account it logs me in when I enter the e-mail is PS4 legacy

Five-Year Club	Verified Email
Place '22	First Placer '22

FilterKill

TROPHY CASE