latest.log

Attached is the log, as Minecraft is freezing and not generating a crash report. The primary information is that literally thousands and thousands of lines are being generated in the log like this:

[26Jan2021 01:13:44.306] [Render thread/WARN] [net.minecraft.client.renderer.model.BlockModel/]: Unable to resolve texture due to reference chain thatch->thatch in abnormals_core:block/thatch/thatch_stairs_inner

starting at line 1094, and going down another ten thousand lines. I have no idea what's causing this.

Try reinstalling the mod

Deleting and redownloading the mod, unfortunately, provided the same result.

Abnormals Core isn't the only mod giving weird render warnings in the logs.
[26Jan2021 01:14:02.626] [Render thread/WARN] [net.minecraft.client.renderer.model.BlockModel/]: Unable to resolve texture due to reference chain trim->trim in storagedrawers:block/half_drawers_orientable
[26Jan2021 01:13:56.641] [Render thread/WARN] [net.minecraft.client.renderer.model.BlockModel/]: Unable to resolve texture due to reference chain trim->trim in storagedrawers:block/full_drawers_orientable
I'm not sure what would cause this, but I suspect it's caused by some sort of incompatibility or tampering.
Try removing storage drawers and see if it no longer freezes.

latest.log
Disabled Storage Drawers, still doing it.

Okay, so, I've tracked down which mod it's interacting with and causing it to freak out. Specifically, somehow it's an interaction with the Connected Textures Mod that's doing it. Why, I don't know, but it definitely shouldn't be doing that.

Specifically it happens if you have Abnormals-Core, Neapolitan and Connected Textures Mod all in the same pack. Neapolitan references the thatch base model from abnormals-core and my guess is that that causes Connected Textures Mod to scan the (by itself invalid) base model even though it is never used for a block on its own

That'd be an issue on CTM's side. Open an issue over there.

Farmers Delight suffers of the same issue.
vectorwing/FarmersDelight#169

Yeah that's why it's likely a CTM issue

Has been marked as a CTM bug, follow it there: Chisel-Team/ConnectedTexturesMod#149