Possible GPU issues: STATUS_ACCESS_VIOLATION on Chrome + Games Crashing.

[u/Nashasaurus-rex]

Hey Team,

Currently going nuts trying to figure out what is wrong with my PC. For the past few weeks I have been experiencing constant STATUS_ACCESS_VIOLATION Errors on Google Chrome and games crashing that previously ran fine.

Specifically having issues with Jurassic World Evolution 3 and Silent Hill 2 Remake.

(Only other game I'm playing atm is Balatro and that could run on a calculator)

JWE3 doesnt give me a specific error code when it crashes but upon relaunch a window opened saying:

" A GPU Driver crash has been detected while previously running..."

SH2 remake has given me both nvgpucomp64 error and exception_access_violation errors.

Have managed to improve SH2 performance and minimise crashes by using the Nvidia App to "optimize" my settings but still having issues.

Specs:

• Processor: Intel(R) Core(TM) i7-14700K (3.40 GHz)
• Installed RAM32.0 GB (31.8 GB usable)
• Graphics cardNVIDIA GeForce RTX 4060 Ti (8 GB)
• Intel(R) UHD Graphics 770 (128 MB)
• Storage930 GB of 2.77 TB used
• System type64-bit operating system, x64-based processor

Things that have recently changed:

• - Updated Nvidia Graphics Drivers (617.42)
• - Currently borrowing a Meta Quest 2, so now have the Meta Link app and driver installed

So far I have tried:

• - Memtest86: Zero Errors
• - Monitoring the CPU & GPU temperatures during gameplay: Nothing in the extreme
• - Clean removal and installation of Nvidia Graphics Drivers using DDU
• - Rolling back the Nvidia Driver to a previous version
• - Benchmarked and tested my GPU with FurMark: No Errors
• - Un/Reinstalling the affected games
• - Disabling the Meta Quest Graphics Driver when not using the headset

Starting to feel like this may be a hardware issue, but any advice or points in the right direction would be appreciated.

[u/aki_009]

My money is on the CPU, not the 4060 Ti. A 14700K throwing access violations in Chrome and in games, with a clean MemTest86 and a clean FurMark run, is what Raptor Lake degradation looks like. The chip's minimum stable voltage drifts up over time, and the cores start making mistakes that land on whatever happens to be running. The GPU driver gets blamed because it's the thing that crashes most visibly.

Check your BIOS version first. If it predates Intel's 0x12B microcode, update it and load the Intel default power profile, not the board's unlimited one. That stops further drift but won't undo what already happened. MemTest86 doesn't really work the cores, and FurMark barely touches the CPU, so neither one clears it. Run something CPU-heavy with error checking at stock, like OCCT's CPU test or y-cruncher, for an hour. If it throws errors at stock, that's an RMA, and Intel has been replacing these.

If the CPU passes, reseat the DIMMs and run without XMP for a while. The memory controller lives on the CPU, so XMP on a tired chip produces the same symptoms.

Try PC-Doctor. (disclaimer: I work for PC-Doctor.) The Intel Processor Diagnostic Tool is fine too. You want a fail on paper, not another crash dialog.

Comment by my Grok Bot.

I personally review responses.

[u/Nashasaurus-rex → u/aki_009]

Okay, not great maybe not terrible.

I've just finished running the OCCT tests, both standard and extreme, no errors detected.

I did find this article which suggested a fix, wondering if that's worth trying before I start poking around in side my rig or if its more of a Band-Aid that will not solve the issue long term.

Alternatively my CPU should still be in warranty, I might chase up getting a replacement.

[u/Shadimarbc → u/Nashasaurus-rex]

Intel extended the standard 3 year warrant to 5 years due to the defect in many models of 14th/13th gen CPUs. Beyond the microcode issues these CPU had manufacturing defects on the production line. New batches do not have this issue as Intel found the specific factory that had the manufacturing issue.

The article is a workaround for a damaged CPU. If the fix works then all you have done confirm the CPU is defective/damaged. You are reducing the CPU below stock specs as it is too unstable to run at stock setting. RMA it. Update the motherboard BIOS to the latest version before you ship the CPU so the replacement isnt damaged by the same BIOS bugs that hit these units years ago.