Exception access violation java error

How To Fix Java Runtime Environment Error 0xC0000005

Explanation of EXCEPTION_ACCESS_VIOLATION

EXCEPTION_ACCESS_VIOLATION is typically an error (bug) found at runtime. Developers like Oracle Corporation usually go through several checkpoints before launching a software program like Java Runtime Environment. Although these preventive actions are taken, at times errors like error 0xC0000005 will be missed.

In the release of the latest version of Java Runtime Environment, an error could be encountered that reads, «EXCEPTION_ACCESS_VIOLATION. A fatal error has been detected by the Java Runtime Environment: EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x5278b517, pid=2480, tid=228.». If error 0xC0000005 occurs, developers will be told about that issue through error notifications that are built-in Java Runtime Environment. Oracle Corporation can then fix these errors in the source code and prepare an update for download. This situation happens due to Java Runtime Environment software upgrades being one of the solutions for error 0xC0000005 errors and other problems.

What’s the Reason for Error 0xC0000005?

You will have a failure during execution of Java Runtime Environment if you run into EXCEPTION_ACCESS_VIOLATION during runtime. We are going to review at the key causes of error 0xC0000005 errors:

Error 0xC0000005 Crash — The program encountered an error 0xC0000005 error because of a specified task, and terminated the program. When Java Runtime Environment cannot provide sufficient output to the given input, or doesn’t really know what to output, it will often confuse the system in this manner.

EXCEPTION_ACCESS_VIOLATION Memory Leak — The consequences of a Java Runtime Environment memory leak involve a malfunctioning operating system. Possible causes include failure of Oracle Corporation to de-allocate memory in the program, or when bad code is executing an «infinite loop».

Error 0xC0000005 Logic Error — You can experience a logic error when the program produces incorrect results even if the user specifies the right value. Oracle Corporation’s faulty source code can lead to these issues with input handling.

Most EXCEPTION_ACCESS_VIOLATION errors are the result of a missing or corrupt version of the file installed by Java Runtime Environment. Downloading and replacing your Oracle Corporation file can fix the problem in most cases. In some cases, the Windows registry is attempting to load a EXCEPTION_ACCESS_VIOLATION file that no longer exists, therefore we recommend running a registry scan to repair any invalid file path references.

Typical EXCEPTION_ACCESS_VIOLATION Errors

These EXCEPTION_ACCESS_VIOLATION-related Java Runtime Environment Troubles Include:

• «EXCEPTION_ACCESS_VIOLATION Application Error.»
• «EXCEPTION_ACCESS_VIOLATION not a Win32 program.»
• «EXCEPTION_ACCESS_VIOLATION has encountered a problem and needs to close. We are sorry for the inconvenience.»
• «Sorry, we can’t find EXCEPTION_ACCESS_VIOLATION.»
• «EXCEPTION_ACCESS_VIOLATION can’t be found.»
• «Error starting program: EXCEPTION_ACCESS_VIOLATION.»
• «EXCEPTION_ACCESS_VIOLATION not working.»
• «EXCEPTION_ACCESS_VIOLATION failed.»
• «Faulty Program Path: EXCEPTION_ACCESS_VIOLATION.»

Java Runtime Environment EXCEPTION_ACCESS_VIOLATION issues occur with installation, while EXCEPTION_ACCESS_VIOLATION-related software runs, during shutdown or startup, or less-likely during operating system updates. Notating when EXCEPTION_ACCESS_VIOLATION errors occur is paramount in finding the cause of the Java Runtime Environment problems and reporting them to Oracle Corporation for help.

Problem Sources of EXCEPTION_ACCESS_VIOLATION

EXCEPTION_ACCESS_VIOLATION problems can be attributed to corrupt or missing files, invalid registry entries associated with EXCEPTION_ACCESS_VIOLATION, or a virus / malware infection.

Chiefly, EXCEPTION_ACCESS_VIOLATION complications are due to:

• Corrupted or invalid EXCEPTION_ACCESS_VIOLATION registry entry.
• Malware infestation corrupted EXCEPTION_ACCESS_VIOLATION file.
• EXCEPTION_ACCESS_VIOLATION maliciously deleted (or mistakenly) by different rogue or valid program.
• A different application in conflict with EXCEPTION_ACCESS_VIOLATION, or other shared references.
• Corrupt download or incomplete installation of Java Runtime Environment software.

Compatible with Windows 11, 10, 8, 7, Vista, XP and 2000

Источник

Ошибка EXCEPTION ACCESS VIOLATION — как исправить

При запуске игры или программы, а иногда и во время работы с ними вы можете столкнуться с ошибкой Exception Access Violation, в заголовке окна может быть информация об Unhandled Exception, Unexpected Error или Fatal Error, в тексте — коды наподобие 0xc0000005 или указание на DLL. Ошибка типична для Windows 10, предыдущих версий системы и, с большой вероятностью, останется и в Windows 11.

В этой инструкции о возможных способах исправить ошибку Exception Access Violation, которая, по сути, обычно сводится к невозможности какого-либо модуля программы или игры получить доступ к нужной области оперативной памяти.

Exception Access Violation как результат работы антивирусного ПО

Среди наиболее часто встречающихся причин ошибки у русскоязычного пользователя, особенно при использовании нелицензионных игр или программ — антивирус: встроенный Windows Defender или какой-либо сторонний.

Возможные действия исправить Exception Access Violation для этого случая:

1. Проверьте, сохраняется ли ошибка, если временно отключить ваш антивирус.
2. Добавьте папку с программой или игрой в исключения антивируса. В случае использования Защитника Windows сделать это можно, открыв «Безопасность Windows» — «Защита от вирусов и угроз» — «Управление настройками» и добавив нужную папку в разделе «Исключения».

Функция предотвращения выполнения данных в памяти также может привести к рассматриваемой ошибке для некоторых программ, попробуйте её отключить. Для этого:

1. Нажмите клавиши Win+R на клавиатуре, введите sysdm.cpl и нажмите Enter.
2. На вкладке «Дополнительно» в разделе «Быстродействие» нажмите кнопку «Параметры».
3. Откройте вкладку «Предотвращение выполнения данных», выберите пункт «Включить DEP для всех программ и служб, кроме выбранных ниже» и добавьте в список исполняемый файл программы или игры, которая вызывает ошибку Exception Access Violation. Примените настройки.

Дополнительные способы исправить ошибку

Два указанных выше метода чаще всего возвращают работоспособность и являются решением проблемы, но не всегда. Дополнительно вы можете попробовать следующие способы:

1. Для относительно старого ПО — попробовать запустить программу или игру в режиме совместимости с предыдущей версией ОС, подробнее: Режим совместимости Windows 10.
2. Если ошибка стала появляться в программе, которая до этого работала исправно на этом же компьютере, попробуйте использовать точки восстановления системы на дату, когда проблема ещё не наблюдалась.
3. В случае, если вы столкнулись с проблемой после переустановки Windows на компьютере или ноутбуке, вручную установите все оригинальные драйверы устройств, включая драйверы чипсета. Вручную — это не с помощью «Обновить драйвер» в диспетчере устройств, а загрузив драйверы с официального сайта производителя материнской платы или ноутбука.
4. Попробуйте запустить программу или игру от имени администратора.
5. Проверьте оперативную память на ошибки, этот фактор также может оказаться причиной ошибке Exception Access Violation.
6. Иногда ошибка возникает после ручного добавления библиотек DLL в систему в папки C:WindowsSysWOW64 и C:WindowsSystem32. Иногда это оказываются не рабочие DLL, иногда — разрядность библиотеки не соответствует расположению.
7. Для программистов на JAVA: сообщают, что ошибка может возникнуть, когда x64 системах в PATH указание на SysWOW64 идёт перед System32.

Также, если речь идёт о загруженной из Интернета (с неофициального сайта) программе, можно попробовать удалить её, а затем скачать из другого источника.

Видео

Буду благодарен, если в комментариях вы сможете поделиться, какой из способов сработал в вашем случае.

Источник

How to fix “Exception Access Violation” error on Windows 10?

Issue: How to fix “Exception Access Violation” error on Windows 10?

Hello. How can I fix exception_access_violation error? Usually, it shows up when I play a game, but yesterday I received the same message on Facebook. I’m using Windows 10. Please help!

EXCEPTION_ACCESS_VIOLATION is a Windows-specific error [1] message, which may strike all OS versions (7, 8, 8.1, etc.). Usually, it is marked by a numeric error code 0xc0000005 and may be dubbed as Unhandled Exception Access Violation. This is the Windows error that users tend to experience from time to time.

The error is shown in a form of a pop-up window and prevents PC users from using particular apps normally. Many people reported this problem occurring during gameplay or when launching specific apps (Java, Visual Studio, World of Warships, Overwatch, Minecraft, etc.). Sometimes, the error shows up randomly, but in this case, the pop-up indicates a problematic file, [2] for example, ntdll.dll, odbc32.dll, and similar.

According to experts the Exception Access Violation pop-up may be triggered by corrupted software, which ends up with memory corruption. [3] In other words, the EXCEPTION_ACCESS_VIOLATION error means that some parts of the software the user is trying to launch may be trying to access protected memory address and the access is denied due to protection.

There are particular EXCEPTION_ACCESS_VIOLATION error variations and based on the reasons and solutions differ:

• EXCEPTION_ACCESS_VIOLATION java error that people experience when using Java, so programs related to it need fixing, in particular.
• Unhandled Exception Access Violation Visual Studio error – reinstalling the affected app might solve the issue the quickest.
• EXCEPTION_ACCESS_VIOLATION error related to ntdll.dll, odbc32.dll files shows a particular file that is causing the error.
• Exception Access Violation WoW, Minecraft, Overwatch error is related to certain games, so solutions involve changing settings, altering files or reinstalling the applications entirely.

In some rare cases, the Exception Access Violation error may be triggered by an antivirus program. Many people reported Kaspersky as a culprit, but there’s no official prove provided that this particular antivirus program causes the error exceptionally, so you should try to disable or remove any third-party antivirus program to check if it’s not causing the problem.

How to fix the EXCEPTION_ACCESS_VIOLATION error

If the antivirus is not the culprit, then we would recommend scanning the system with Reimage Mac Washing Machine X9 optimization utility. It can deal with problematic system files, such as ntdll.dll and odbc32.dll. You can repair other system pieces and solve unrelated problems, so fixing this error becomes easier. Also, some tools like this can alter Windows Registry entries, repairs any damaged data on the computer.

You need to try and check if the machine is working smoothly. Sometimes quick optimization can solve the error temporarily or permanently. If the issue is related to the application or a game, you can try to fix EXCEPTION_ACCESS_VIOLATION error manually with the methods listed below.

#1 Add a program to the Data Execution Prevention exceptions list

If a specific program is giving the EXCEPTION_ACCESS_VIOLATION error, you should try adding that specific application to Data Execution Prevention exceptions list. To do so, please follow these steps:

• Open Control Panel and select System and Security.
• Select System and click Advanced System Settings on the left pane.
• Open Advanced tab.
• Click Settings under Performance and open Data Execution Prevention tab.

#2 Run a Windows hardware troubleshooter

• Go to the Windows search bar and type in Settings.
• Click on the Update & Security option.
• Look for Troubleshoot and select it.
• Click Hardware and Devices.
• Hit Run the troubleshooter.

#3 Disable User Account Control

This method is applicable in case you encounter the error when launching Java apps. Once you disable the User Account Control, try to install/reinstall Java and run its apps.

• Open Control Panel and select Accounts.
• Click User Accounts and select Change User Account Control settings.
• Move the slider until you set it to Never Notify and click OK.

#4 Create options.ini file to fix EXCEPTION_ACCESS_VIOLATION error

If the only app affected by EXCEPTION_ACCESS_VIOLATION error is Lord of The Rings: Battle for Middle Earth, try the following methods:

• Press Windows key + R, type %appdata%, and click Enter.
• Open My Battle for Middle Earth Files folder. If the folder is empty, create an options.ini file in it.

Right-click on empty space while in the folder, and select New ->Text Document.

This tutorial demonstrates how to solve the EXCEPTION_ACCESS_VIOLATION error in Java.

Solve the Java VM EXCEPTION_ACCESS_VIOLATION

While working with JVM on windows, sometimes it throws the EXCEPTION_ACCESS_VIOLATION error, which crashes the Java Virtual Machine. This error is basically a NullPointerException.

The EXCEPTION_ACCESS_VIOLATION looks like this:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffa50da9b2a, pid=8984, tid=11524
#
# JRE version: OpenJDK Runtime Environment (14.0.1+7) (build 14.0.1+7)
# Java VM: OpenJDK 64-Bit Server VM (14.0.1+7, mixed mode, sharing, tiered, compressed oops, g1 gc, windows-amd64)
# Problematic frame:
# V  [jvm.dll+0x349b2a]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows.

Most of the time, the EXCEPTION_ACCESS_VIOLATION is an error in the Java Virtual Machine. Sometimes it can also occur by the native code.

Here are some important points which can help us to know the real reason behind this error so we can solve it:

1. When this error occurs, it generates a log file containing all the information about the error. For example, there can be an error in the Path statement.
2. The VM will most likely crash with low memory. This low memory can be increased from the eclipse.ini file.
3. The VM bugs are also caused by garbage collection; we can look into the heap if the garbage was running at the time of the VM crash.

You will most likely find the solution for this error in these three points.

Related Article — Java Error

Java.Lang.OutOfMemoryError: Unable to Create New Native Thread

Error: Ошибка 0xC0000005 — EXCEPTION_ACCESS_VIOLATION. Среда выполнения Java обнаружила фатальную ошибку: EXCEPTION_ACCESS_VIOLATION (0xc0000005) на pc = 0x5278b517, pid = 2480, tid = 228.

	Error Number:	Error 0xC0000005
Error Name:	EXCEPTION_ACCESS_VIOLATION
Error Description:	EXCEPTION_ACCESS_VIOLATION. A fatal error has been detected by the Java Runtime Environment: EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x5278b517, pid=2480, tid=228.
Developer:	Oracle Corporation
Software:	Java Runtime Environment
Applies to:	Windows XP, Vista, 7, 8, 10, 11

Explanation of EXCEPTION_ACCESS_VIOLATION

EXCEPTION_ACCESS_VIOLATION is typically an error (bug) found at runtime. Developers like Oracle Corporation usually go through several checkpoints before launching a software program like Java Runtime Environment. Although these preventive actions are taken, at times errors like error 0xC0000005 will be missed.

In the release of the latest version of Java Runtime Environment, an error could be encountered that reads, «EXCEPTION_ACCESS_VIOLATION. A fatal error has been detected by the Java Runtime Environment: EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x5278b517, pid=2480, tid=228.». If error 0xC0000005 occurs, developers will be told about that issue through error notifications that are built-in Java Runtime Environment. Oracle Corporation can then fix these errors in the source code and prepare an update for download. This situation happens due to Java Runtime Environment software upgrades being one of the solutions for error 0xC0000005 errors and other problems.

What’s the Reason for Error 0xC0000005?

You will have a failure during execution of Java Runtime Environment if you run into EXCEPTION_ACCESS_VIOLATION during runtime. We are going to review at the key causes of error 0xC0000005 errors:

Error 0xC0000005 Crash — The program encountered an error 0xC0000005 error because of a specified task, and terminated the program. When Java Runtime Environment cannot provide sufficient output to the given input, or doesn’t really know what to output, it will often confuse the system in this manner.

EXCEPTION_ACCESS_VIOLATION Memory Leak — The consequences of a Java Runtime Environment memory leak involve a malfunctioning operating system. Possible causes include failure of Oracle Corporation to de-allocate memory in the program, or when bad code is executing an «infinite loop».

Error 0xC0000005 Logic Error — You can experience a logic error when the program produces incorrect results even if the user specifies the right value. Oracle Corporation’s faulty source code can lead to these issues with input handling.

Most EXCEPTION_ACCESS_VIOLATION errors are the result of a missing or corrupt version of the file installed by Java Runtime Environment. Downloading and replacing your Oracle Corporation file can fix the problem in most cases. In some cases, the Windows registry is attempting to load a EXCEPTION_ACCESS_VIOLATION file that no longer exists, therefore we recommend running a registry scan to repair any invalid file path references.

Typical EXCEPTION_ACCESS_VIOLATION Errors

These EXCEPTION_ACCESS_VIOLATION-related Java Runtime Environment Troubles Include:

• «EXCEPTION_ACCESS_VIOLATION Application Error.»
• «EXCEPTION_ACCESS_VIOLATION not a Win32 program.»
• «EXCEPTION_ACCESS_VIOLATION has encountered a problem and needs to close. We are sorry for the inconvenience.»
• «Sorry, we can’t find EXCEPTION_ACCESS_VIOLATION.»
• «EXCEPTION_ACCESS_VIOLATION can’t be found.»
• «Error starting program: EXCEPTION_ACCESS_VIOLATION.»
• «EXCEPTION_ACCESS_VIOLATION not working.»
• «EXCEPTION_ACCESS_VIOLATION failed.»
• «Faulty Program Path: EXCEPTION_ACCESS_VIOLATION.»

Java Runtime Environment EXCEPTION_ACCESS_VIOLATION issues occur with installation, while EXCEPTION_ACCESS_VIOLATION-related software runs, during shutdown or startup, or less-likely during operating system updates. Notating when EXCEPTION_ACCESS_VIOLATION errors occur is paramount in finding the cause of the Java Runtime Environment problems and reporting them to Oracle Corporation for help.

Problem Sources of EXCEPTION_ACCESS_VIOLATION

EXCEPTION_ACCESS_VIOLATION problems can be attributed to corrupt or missing files, invalid registry entries associated with EXCEPTION_ACCESS_VIOLATION, or a virus / malware infection.

Chiefly, EXCEPTION_ACCESS_VIOLATION complications are due to:

• Corrupted or invalid EXCEPTION_ACCESS_VIOLATION registry entry.
• Malware infestation corrupted EXCEPTION_ACCESS_VIOLATION file.
• EXCEPTION_ACCESS_VIOLATION maliciously deleted (or mistakenly) by different rogue or valid program.
• A different application in conflict with EXCEPTION_ACCESS_VIOLATION, or other shared references.
• Corrupt download or incomplete installation of Java Runtime Environment software.

Product by Solvusoft

Download Now
WinThruster 2022 — Scan your PC for computer errors.

Compatible with Windows 11, 10, 8, 7, Vista, XP and 2000

Optional Offer for WinThruster by Solvusoft | EULA | Privacy Policy | Terms | Uninstall

OutOfMemoryError

The most common cause of an OutOfMemoryError is that your program
is running out of heap space: that is, the memory space set aside for
the objects that your program creates. There are usually two possibilities:

• you know that your program is fairly «memory intensive»:
  it creates and deliberately holds on to a fair number of
  objects, or a large amount of data etc, at any one time;
  in this case, the starting point is usually to just increase the heap size;
• or, the OutOfMemoryError may be an indicator of a
  memory leak: your program is holding on two objects when you’re
  not expecting it to.

To increase the heap size, you can add a heap size setting to the Java
startup command used to launch your program. For example:

java -Xms128m -Xmx512m MyClass

will tell Java to initially allocate a minimum heap space of 128 MB,
and allow this to grow up to 512 MB. (In reality, there is not usually
a «single heap» in modern JVMs, but rather the space you allocate is
portioned into different areas for newly created objects, longer-lasting
objects etc. But many programs won’t need to worry about this.)
Because of the overhead of growing the heap when it gets full, you should
set a «decent» minimum size if you know that your application is likely to
be memory-hungry.

Note too that successive JVMs have got more sensible about allocating
a sensible heap size by default. Early JVMs tended to allocate what is now
a fairly piddly amount by default, e.g. 32 MB. But from Java 5 onwards,
the default allocation has been significantly improved, and makes it easier
in cases where you’re bypassing the command line altogether (e.g. on systems
where you can double-click on an executable Jar to run it). So if you’re
running an earlier JVM, one solution may simply be to upgrade your JVM.

If you’re running in an IDE such as Eclipse, you generally need to find the place
in the Project Settings where you can specify «VM arguments».

Heap size limits

On 32-bit machines, the maximum heap size is typically just under 2 GB (Windows
with default settings), or just under 3 GB on UNIX-like systems. Technically, the maximum
heap size is determined by the maximum amount of contiguous memory space that the
Java process can allocate. Under windows, this usually ends up being about 1650-1700 MB out
of the theoretical 2GB memory space.

This limit does not generally apply to 64-bit machines provided that you are genuinely running
a 64-bit JVM.

NullPointerException

This is one of the most common exceptions to occur in Java programs. It happens when you
try to call a method on a null object reference (or when you try to access fields on one).
So let’s say we have some code such as the following:

int noFiles = dir.listFiles().length;

If we get a NullPointerException on this line, it means that either
dir is null, or that the result of listFiles() (which is supposed to
be an array of File objects) is null. In principle, without knowing more about
the surrounding code, either of these who objects could be the one that is null. We need to
use a process of logic and elimination to try and work out which one is null. If the line was
as follows:

int noFiles = fileList.length;

then we would have to follow our program back to where fileList was created
(or where the variable was last set) and work out why it could be being set to null.

Because cases like this can be ambiguous or because it can be difficult to trace
back to the origin of a null object, it is good practice to check for
nulls as early on as they can be eliminated. For example, at the beginning
of a method that we write, we can put in an explicit null check:

private int getFileListLength(File[] files) {
  if (files == null)
    throw new NullPointerException("File list cannot be null");
}

Now, if the file list is null, we’ll get a null pointer exception «as soon as the
problem can be detected», rather than later on in the code when it may be more difficult
to work out the source of the null.

Runnable task = new Runnable() {
  public void run() {
    myMethod();
  }
};
Thread thr = new Thread(null, task
  "ExtraStackThread", 1024 * 1024 * 2);
thr.start();
thr.join();

EXCEPTION_ACCESS_VIOLATION

In rare circumstances, a Java program could stop with a message similar to the following:

# An unexpected error has been detected by HotSpot Virtual Machine:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x7c042340, pid=1743, tid=122
#
# Java VM: Java HotSpot(TM) Client VM (1.5.4_02)
# Problematic frame:
# C [ntdll.dll+0x2430]

Essentially, Java will stop with a message such as the above if a «serious» error
occurs that means the JVM can’t continue to function. Usually, the most discriminating
line is the first mention of a DLL, such as the line in bold above.
The source of the error could
be any of the following:

• a bug in the JVM itself; search Google and/or the Java web site
  for a mention of ntdll.dll+0x2430;
• a bug in some non-Java code that was being run at the time:
  e.g. Java might have been calling into a printer driver, graphics driver etc.

If you’re not sure what to do but are not using the latest version of the JVM for
your system, then a good first course of action is usually to upgrade your JVM.
If the bug is in some other DLL, e.g. a printer driver, database driver,
graphics driver etc, then it is best to see if you can upgrade the component in question.

If the error is occurring in some native code that you have written, then
you need to find out which line of code corresponds to the offset mentioned (in this
case, 0x2430, although the DLL isn’t one of ours in this example). Usually you can tell
your compiler to generate a «map file» that gives a list of code offsets per line number.
Because of compiler optimisations, line numbers may be approximate.

I was using jssc 2.8.0 and java 8. Need to switch to Java 11 for project requirement.
After everything is ported the jssc library seems to cause jvm to crash on window 10.
(Log is attached)

---------------  S U M M A R Y ------------

Command Line: -Dvisualvm.id=622907326716200 --module-path=C:Program FilesJavajavafx-sdk-11.0.2lib --add-modules=javafx.controls,javafx.fxml --illegal-access=warn --add-modules=javafx.base,javafx.graphics --add-reads=javafx.base=ALL-UNNAMED --add-reads=javafx.graphics=ALL-UNNAMED -javaagent:C:Program FilesJetBrainsIntelliJ IDEA Community Edition 2019.1.3libidea_rt.jar=50486:C:Program FilesJetBrainsIntelliJ IDEA Community Edition 2019.1.3bin -Dfile.encoding=UTF-8 App

Host: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz, 8 cores, 7G,  Windows 10 , 64 bit Build 17763 (10.0.17763.1158)
Time: Thu May 21 00:17:24 2020 Atlantic Daylight Time elapsed time: 18 seconds (0d 0h 0m 18s)

---------------  T H R E A D  ---------------

Current thread (0x0000026644350000):  JavaThread "Timer-0" [_thread_in_native, id=19756, stack(0x000000b036000000,0x000000b036100000)]

Stack: [0x000000b036000000,0x000000b036100000],  sp=0x000000b0360feb00,  free space=1018k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  0x000000007110b5db

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  jssc.SerialNativeInterface.openPort(Ljava/lang/String;Z)J+0
j  jssc.SerialPort.openPort()Z+65
j  Serial.attemptDongleConnect()V+72
j  Serial$3.run()V+45
j  java.util.TimerThread.mainLoop()V+221 java.base@11
j  java.util.TimerThread.run()V+1 java.base@11
v  ~StubRoutines::call_stub

siginfo: EXCEPTION_ACCESS_VIOLATION (0xc0000005), reading address 0x000000004c095fe6

There is similar bug reported earlier — https://bugs.openjdk.java.net/browse/JDK-8203772
However, this was closed as jssc issue.
I am using openjdk 11. Wondering this is fixed. Since 2.9.0 mentions following in the fixes section.
Fixed hard crash on Windows using JDK11

hs_err_pid18016 (1).log