# EXCEPTION\_ACCESS\_VIOLATION (0xc0000005)

**URL:** <https://discuss.elastic.co/t/exception-access-violation-0xc0000005/373334>\
**Category:** Elasticsearch\
**Created:** [January 17, 2025, 2:19pm UTC](https://discuss.elastic.co/t/exception-access-violation-0xc0000005/373334 "2025-01-17T14:19:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![khaled-absalam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/khaled-absalam/32/140735_2.png) [@khaled-absalam](https://discuss.elastic.co/u/khaled-absalam)\
**Post date:** [January 17, 2025, 2:19pm UTC](https://discuss.elastic.co/t/exception-access-violation-0xc0000005/373334/1 "2025-01-17T14:19:49Z")

</div>

I'm encountering error running Elasticsearch 8.17.0 on Windows 11 Pro version 24H2 with embedded Java 23.0+37, this error started occurring since I upgraded Elasticsearch to 8.16.1, I've got a memory of 128GB and I'm using the auto configuration for JVM heap which translates to 31GB(around half of the free memory).  
**elasticsearch-service-x64-stdout**

```auto
2025-01-17 06:45:28 Apache Commons Daemon procrun stdout initialized.
CompileCommand: dontinline java/lang/invoke/MethodHandle.setAsTypeCache bool dontinline = true
CompileCommand: dontinline java/lang/invoke/MethodHandle.asTypeUncached bool dontinline = true
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000001ac610cbd45, pid=8880, tid=11664
#
# JRE version: OpenJDK Runtime Environment (23.0+37) (build 23+37-2369)
# Java VM: OpenJDK 64-Bit Server VM (23+37-2369, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# J 14900 c2 java.util.HashMap.putVal(ILjava/lang/Object;Ljava/lang/Object;ZZ)Ljava/lang/Object; java.base@23 (300 bytes) @ 0x000001ac610cbd45 [0x000001ac610cbb60+0x00000000000001e5]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# logs/hs_err_pid8880.log
[5378.521s][warning][os] Loading hsdis library failed
#
# If you would like to submit a bug report, please visit:
#  
#

2025-01-17 08:45:09 Apache Commons Daemon procrun stdout initialized.
CompileCommand: dontinline java/lang/invoke/MethodHandle.setAsTypeCache bool dontinline = true
CompileCommand: dontinline java/lang/invoke/MethodHandle.asTypeUncached bool dontinline = true

```

I followed the fix that was done in **[EXCEPTION\_ACCESS\_VIOLATION in Elasticsearch 8.16.1 Running on Java 17](http://discuss.elastic.co/t/exception-access-violation-in-elasticsearch-8-16-1-running-on-java-17/371277)** with no success of resolving the issue.

This also fails around the same time every day(give or take a few minutes) and sometimes randomly at anytime for other instances.

The problematic frame is also the same every time.

---

<div class="post-metadata">

**Author:** ![khaled-absalam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/khaled-absalam/32/140735_2.png) [@khaled-absalam](https://discuss.elastic.co/u/khaled-absalam)\
**Post date:** [April 25, 2025, 5:08pm UTC](https://discuss.elastic.co/t/exception-access-violation-0xc0000005/373334/2 "2025-04-25T17:08:13Z")

</div>

As of version 9.0.0 this error is still occurring, need advice please