I don't want to spend any more on my PC. It was the largest amount of money I had ever seen when I first bought it. Even if I have way more resources now, I don't believe… (funda kabanzi)
I don't want to spend any more on my PC. It was the largest amount of money I had ever seen when I first bought it. Even if I have way more resources now, I don't believe that a few faulty locations in my memory should be causing so many problems for myself and for developers who have no clue why their users keep crashing.
It is either my RAM or VRAM. Disabling XMP on my RAM dampened these issues but couldn't fully solve them.
It's exactly as I said. Normal programs just crash. Kernel-level programs or anti-cheats can entirely blue screen my PC. It all has to do with where these programs are writing to in my hardware. It's only a few locations that I have faulty. Most programs work fine. Most games work fine. Most crashes are very transient.
Firefox is a transient and common crasher for me. It's so painful to be scrolling a page and have the page crash, just for the previous page to load instead of the newer one that I was on, and on top of that I could also be losing work or effort.
I know this isn't exactly a dev support page, but this problem is so recurring that I don't know what to think anymore. There has to be a way to check which memory locations are fried without causing a bluescreen or crashing the program. Maybe it's a Windows issue and devs could easily fix it, if it weren't for Windows bottlenecks like labelling the faulty locations as "protected". I've seen at least 1 crash where the output said something like "Error: tried writing to protected location" blah blah blah then it spit out some hexcode or exact location and blahblahblah. And that was the entire error message.
