# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000051f27e3710, pid=46476, tid=47096
#
# JRE version: OpenJDK Runtime Environment Temurin-21.0.3+9 (21.0.3+9) (build 21.0.3+9-LTS)
# Java VM: OpenJDK 64-Bit Server VM Temurin-21.0.3+9 (21.0.3+9-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C 0x0000000000000000
#
# 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:
# feather/java_error.log
[thread 12980 also had an error]
#
# If you would like to submit a bug report, please visit:
# https://github.com/adoptium/adoptium-support/issues
#
You're mentioning this occurring on world creation. Is that the only time this occurs? (Or can you not get further to test?)
And does this only occur, say, in a specific profile? Like with a certain version and with/without certain mods? Try just vanilla with the default vanilla bundled Java version and Java arguments, and try a few versions for good measure, and see if this is reproducible.
Unless something obvious jumps out to someone else (TileEntity might have an idea?), your Raptor Lake CPU may otherwise make this difficult to narrow down due to them known to be problematic with stability and degrading, and Minecraft can be CPU heavy. If, by chance, you have an Alder Lake CPU (12th generation), it might be worth testing it in place of it to rule it out. Otherwise, if you're also experiencing issues in, say, Unreal Engine games and/or during shader compilation scenarios, that would point towards the CPU.
What speed is your memory running at? 64 GB for DDR5 would likely mean either dual rank DIMMs or four single rank DIMMs (since single rank 32 GB DIMMs don't exist yet in the consumer space as far as I know), and getting those to play well at higher speeds has been much more difficult on DDR5 than on past RAM types. This is on top of the aforementioned issue, and I/O issues is one of the types that occur with those CPUs (if its at fault). Intel is typically able to achieve higher RAM speeds so if you're running them fairly fast (like at 7,200 MHz+), it might be worth trying something like 6,000 MHz, or if you're already running them at something like 6,000 MHz to 6,400 MHz, it might be worth trying down to as low as 4,800 MHz.
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000051f27e3710, pid=46476, tid=47096
#
# JRE version: OpenJDK Runtime Environment Temurin-21.0.3+9 (21.0.3+9) (build 21.0.3+9-LTS)
# Java VM: OpenJDK 64-Bit Server VM Temurin-21.0.3+9 (21.0.3+9-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C 0x0000000000000000
#
# 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:
# feather/java_error.log
[thread 12980 also had an error]
#
# If you would like to submit a bug report, please visit:
# https://github.com/adoptium/adoptium-support/issues
#
You're mentioning this occurring on world creation. Is that the only time this occurs? (Or can you not get further to test?)
And does this only occur, say, in a specific profile? Like with a certain version and with/without certain mods? Try just vanilla with the default vanilla bundled Java version and Java arguments, and try a few versions for good measure, and see if this is reproducible.
Unless something obvious jumps out to someone else (TileEntity might have an idea?), your Raptor Lake CPU may otherwise make this difficult to narrow down due to them known to be problematic with stability and degrading, and Minecraft can be CPU heavy. If, by chance, you have an Alder Lake CPU (12th generation), it might be worth testing it in place of it to rule it out. Otherwise, if you're also experiencing issues in, say, Unreal Engine games and/or during shader compilation scenarios, that would point towards the CPU.
What speed is your memory running at? 64 GB for DDR5 would likely mean either dual rank DIMMs or four single rank DIMMs (since single rank 32 GB DIMMs don't exist yet in the consumer space as far as I know), and getting those to play well at higher speeds has been much more difficult on DDR5 than on past RAM types. This is on top of the aforementioned issue, and I/O issues is one of the types that occur with those CPUs (if its at fault). Intel is typically able to achieve higher RAM speeds so if you're running them fairly fast (like at 7,200 MHz+), it might be worth trying something like 6,000 MHz, or if you're already running them at something like 6,000 MHz to 6,400 MHz, it might be worth trying down to as low as 4,800 MHz.
Usually this is a software error though.