JVM actively uses OS signals (or exceptions in Windows terminology) for its own purposes:
- for implicit null pointer checks and stack overflow checks;
- for safepoint polling;
- for remote memory barriers;
- etc.
SEGV (or exception 0xC0000005) is also generated intentionally on JVM startup to verify certain CPU/OS features. Some OSes or hypervisors had a bug that AVX registers are not restored after signal processing. Therefore, JVM needs to check whether this is the case (the source). So it generates an exception by writing to zero address and then handles it.
This is what happens in your case. And yes, it is normal.