BrowSer frequently encounters "STATUS_ACCESS_VIOLATION" errors and artifacts.
BrowSer frequently encounters "STATUS_ACCESS_VIOLATION" errors and artifacts.
I initially think the problem might be related to insufficient VRAM, as graphical performance is affected. However, it could also be due to a newer GPU—try MSI Afterburner and lower VRAM clocks if the NVIDIA panel restricts it. My next thought is RAM-related, so run memtest86 on a USB drive and check for errors. After that, clear the CMOS to eliminate any XMP overclock settings and see if RAM issues remain if the first test indicated problems. In short, I’d clear CMOS in both cases just to confirm.
Adjusted VRAM clocks on MSI after the burner, no improvement. Ran MEM86 and Windows Memory Diagnostic—no errors detected for my RAM. Reset CMOS by jumping pins on MOBO, but nothing changed. Swapped RTX 3080TI for GTX 1080 still causes the same problems (artifacts and Chrome crashes with status_access_violation). Still can’t open Firefox without a sudden crash alert. Found a Reddit thread matching my symptoms.
I changed the MOBO and placed an order for an ASUS TUF Gaming Z590-Plus to replace my GIGABYTE Z590 AORUS ELITE AX. The issue continues, and I'm getting anxious. I don’t want to buy a CPU just to test hardware problems. It looks like the CPU is probably not the cause. There might be something specific to the Chromium-based system affecting only a small group of users. I’m planning to try swapping MOBO again and have the new board ready for shipment back to Amazon. EDIT: I’ll follow this user’s instructions to check if it’s a CPU-related problem; see the thread: https://forums.
Hey, I know this might seem a bit intense, but thanks for getting through it. I was struggling for hours with my setup—trying different RAM, GPU, virus scans, and network cards. Then I found this thread that helped me solve it quickly. It turns out the CPU that failed was a Ryzen 5600G, which suggests this problem isn’t just limited to Intel systems. Appreciate the help!
I reviewed the discussion yesterday. I also own an AMD chip, 5900x. I was pleased to see your message again today. I’ve faced problems with my processor since installation—random BSODs, game crashes, and the status_access_violation error in Chrome. What steps did you take to investigate your AMD thread issue?
I'm also sorry for bringing this up again, but I just wanted to mention that I was facing very similar problems as you, aside from my Discord freezing too. I wanted to let you know that after swapping out my CPU, all these issues disappeared right away. It was unexpected for the new 13900k, but your update helped me figure it out. Thanks a lot!
Hey! If anyone reads this, just note I faced the same issues mentioned and tried everything without success. I checked my old i5 7600 before purchasing, but it had burnt pins, so I went ahead and bought an i7 7700. Since then everything is working fine—chrome runs smoothly and video players are stable. If you're experiencing similar problems, I recommend replacing your CPU. Thanks a lot for the post; it really helped me!
It seems the fix wasn<|pad|>, so I removed the GPU and used the integrated graphics. That didn’t help either—downgrading to the built-in GPU didn’t resolve the problem. While testing on the integrated graphics, I installed HWiNFO, configured Chrome to run on a single core, and ran stress tests. No specific core failed consistently; in fact, the system stayed stable throughout. Interestingly, the issue appeared to reappear about 20 hours after a reboot. I didn’t test with a single RAM stick or swap memory, but ran Memtest and found no memory errors. Further research suggests Asus’s default settings might be too lenient for high-end CPUs like the 14900k. Some users reported success by limiting TDP, clock speeds, or P-core multipliers. I discovered that lowering the P-core turbo frequency to 5.4GHz (after adjusting from the default) improved stability, though 5.7 and 5.6GHz also showed issues. I also found articles and guides that recommended tweaking these parameters. The Short and Long Duration TDP settings were both set to 253W by default, which seemed odd given the flexibility offered. Other reports indicated Chrome and Firefox would crash under certain conditions, possibly due to compatibility quirks with these CPUs. Finally, my Chrome and Edge tabs would freeze with “Aw Snap!” messages, and Firefox would crash intermittently. I also noticed strange graphical glitches in Chrome, including artifacts during gameplay. After replacing the CPU and adjusting settings, the graphical issues vanished, and Chrome became more stable. This advice from a chatbot proved useful in locating relevant solutions.