# Elasticsearch

**URL:** <https://discuss.elastic.co/t/elasticsearch/371275>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring, elastic-stack-security, runtime-fields\
**Created:** [December 1, 2024, 11:11am UTC](https://discuss.elastic.co/t/elasticsearch/371275 "2024-12-01T11:11:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [December 1, 2024, 2:30pm UTC](https://discuss.elastic.co/t/elasticsearch/371275/2 "2024-12-01T14:30:02Z")

</div>

Closed duplicate of

> [@EXCEPTION\_ACCESS\_VIOLATION in Elasticsearch 8.16.1 Running on Java 17](https://discuss.elastic.co/t/exception-access-violation-in-elasticsearch-8-16-1-running-on-java-17/371277):
>
> Error Summary: I'm encountering a fatal error when running Elasticsearch 8.16.1 on Windows Server 2016. The process crashes with an access violation. Below are the details: System Configuration: -OS: Windows Server 2016 (64-bit), Build 14393. -JVM: Java(TM) SE Runtime Environment (17.0.12+8). -Memory: 32GB physical memory, 16GB heap size (-Xms16383m, -Xmx16383m). Elasticsearch Version\*\*: 8.16.1. Error Details: EXCEPTION\_ACCESS\_VIOLATION (0xc0000005) at pc=0x000002c55fc5aaa1 Problematic f…

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch/371275)._