EXCEPTION_ACCESS_VIOLATION Crash on Startup

Game is crashing on startup with the error of "An unexpected issue occurred and the game has crashed. We're sorry for the inconvenience. This crash may be caused by an invalid Java Runtime configuration. Check any custom configuration settings." 

The error log posts this: 

#

1. A fatal error has been detected by the Java Runtime Environment:
   #
2.  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000002108e27de98, pid=8148, tid=10000
   #
3. JRE version: Java(TM) SE Runtime Environment (17.0.3.1+2) (build 17.0.3.1+2-LTS-6)
4. Java VM: Java HotSpot(TM) 64-Bit Server VM (17.0.3.1+2-LTS-6, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
5. Problematic frame:
6. v  ~BufferBlob::vtable chunks
   #
7. No core dump will be written. Minidumps are not enabled by default on client versions of Windows
   #
8. If you would like to submit a bug report, please visit:
9.   https://bugreport.java.com/bugreport/crash.jsp
   #

---------------  S Y S T E M  ---------------

OS:
 Windows 11 , 64 bit Build 22000 (10.0.22000.675)
OS uptime: 0 days 0:55 hours

CPU: total 16 (initial active 16) (16 cores per cpu, 2 threads per core) family 23 model 8 stepping 2 microcode 0x0, cx8, cmov, fxsr, ht, mmx, 3dnowpref, sse, sse2, sse3, ssse3, sse4a, sse4.1, sse4.2, popcnt, lzcnt, tsc, tscinvbit, avx, avx2, aes, clmul, bmi1, bmi2, adx, sha, fma, vzeroupper, clflush, clflushopt

Memory: 4k page, system-wide physical 16332M (9230M free)
TotalPageFile size 19276M (AvailPageFile size 8126M)
current process WorkingSet (physical memory assigned to process): 2008M, peak: 2032M
current process commit charge ("private bytes"): 2197M, peak: 2222M

vm_info: Java HotSpot(TM) 64-Bit Server VM (17.0.3.1+2-LTS-6) for windows-amd64 JRE (17.0.3.1+2-LTS-6), built on Apr 25 2022 22:04:21 by "mach5one" with MS VC++ 16.8 / 16.9 (VS2019)

END.