Potential PHN18-71 CPU problem(?) When using code editors with Turbo or Productivity mode, it crashes!

nameofmy

Working on this machine around 10 months. Games run smothly, cant complain. But for 5 months(or more, cant recall) now when I work in code editor program(Visual Studio 2022) from time to times I get crucial services of that program shut down, which makes the program unusable untill restart. The problem was pretty small, so I was able to ignore it. But recently I started using new program(JetBrains Rider) and same issue happens, but for this exact problem its even worse. I started digging this time a bit this time, and found that this has to do with MEMORY_ACCESS_VIOLATION.
I checked some forums and found that there was a list of CPUs from Raptor Lake line that usually have this kind of problem. As I checked my CPU(i9-14900HX) is not in that list, but I still get this stuff. Now I think I recall that from sometime tabs on my browser gets crashed with some similar code(or thats my paranoia).

I tried to run tests for CPU with Intel Diag program, but all tests passed correctly. Have anyone encountered something like this?
Also, when Im using code editors with Turbo or Productivity mode, crashed are MUCH more frequent.

[Edited the thread to add issue detail]

Puraw

Thanks for raising this, but let's be careful not to jump to conclusions based on anecdotal behavior or vague forum lists.

• The i9-14900HX isn’t part of any confirmed batch exhibiting MEMORY_ACCESS_VIOLATION issues. Intel’s diagnostic tools passing cleanly already rule out hardware faults in most cases.
• Crashes tied to code editors—especially under Turbo/Productivity modes—are more likely linked to software-level memory handling, plugin conflicts, or aggressive power management settings.
• JetBrains Rider and Visual Studio both rely heavily on background services and indexing. If those are interrupted by third-party overlays, unstable drivers, or RAM timing mismatches, the symptoms can mimic CPU instability.
• Browser tab crashes with similar codes may point to RAM or GPU instability, not CPU flaws. Worth checking RAM modules for compatibility and running MemTest86 for deeper validation.

Unless Intel issues a microcode advisory or OEMs confirm a pattern, it’s premature to label the 14900HX as problematic. Let’s keep the thread focused on reproducible diagnostics and avoid fueling speculation that could mislead others.