Problem

At a random moment, the IDE (IntelliJ IDEA, Rider and others) process crashes without error messages. Analyzing java_error_log.* files shows that crashes happen at different locations in the source code.

Most crash logs will have the following error code EXCEPTION_ACCESS_VIOLATION (0xc0000005). Example:

# A fatal error has been detected by the Java Runtime Environment:
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffc9d29cb6a, pid=6648, tid=9300
...
Host: Intel(R) Core(TM) i9-14900KF, 32 cores, 31G,  Windows 11 , 64 bit Build 22621 (10.0.22621.3235)

While this code is rather generic, it indicates a problem with the CPU and/or RAM, memory controller, motherboard, overclock, overheat and other system stability problems.

For Rider IDE, the backend log usually contains the below error:

Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Solutions

1) There is a known bug with the i9-14900K and i9-13900K CPU (and possibly other Intel Core 13th and 14th Gen models) that can cause permanent degradation of the CPU and crashes.

Update to the 0x129 microcode if this BIOS has already been released for your motherboard, disable any overclocks (switch to Intel default recommended profile), and ensure the CPU is not already permanently damaged.

If the CPU is already damaged, in some cases it may help to slightly increase the voltage and use more aggressive loadline calibration settings.

2) Use Intel® Extreme Tuning Utility (Intel® XTU) to reduce a default Core Ratio as a workaround. Try to set 55 or 51 instead of default 57:

3) Check the details how to increase the voltage and adjust loadline calibration settings in BIOS.

4) Check the detailed instructions on what BIOS settings to use if the microcode update is not yet available for your motherboard.

5) See the instructions on how to find if your CPU is damaged.

6) In some cases, e.g. with CPUs like i9-13900H, when advanced overclocking options are not available, disable Intel® Turbo Boost technology in your BIOS settings

7) If the issue remains, monitor the CPU temperature. It might be crash happens when CPU temperature is close to critical. If the temperature really comes close to critical (90+ =>100) , you might want to consider changing (or change thermal compound) the cooling, ensuring it is sufficient enough for the CPU used;

8) For Asus motherboards, set SVID Behavior to Typical Scenario in Bios;