Can't boot - VFS can't open root device error after refresh installation

I did multiple tries of CachyOS installation on my PC. Installation was successful. However, after reboot, if I use the default (non-LTS) kernel, I always get a kernel panic with VFS eror (Can't open root device or unknown-block(0,0): error -6. The installation was on a NVME SSD (nvme0n1). I have another HDD in the PC for data and backup (sda). I understand that in newer kernel versions BTRFS was built into the kernel. That is the difference from the LTS kernel.

Tried multiple combinations:
- Manual partition with 2GB FAT32 partition for /boot, 200GB BTRFS partition for /, and the rest EXT4 partition for /home. Limine as bootloader.
- Manual partition with 300MB FAT32 partition for /boot/efi, 200GB BTRFS partition for /, and the rest EXT4 partition for /home. Grub as bootloder.
- Erase disk option allowing the installer to auto create partitions, with either Grub or Limine.

Photos of the error at: https://www.reddit.com/r/cachyos/comments/1pnob3b/cachyos_installation_boot_error/

Also for background info I installed CachyOS on the other 2 devices. One Asus Intel 6th gen laptop and one PC with MSI Z690 motherboard (using Limine). Both have no such issue.

I was using CachyOS on the Maximus PC without problems. This error (VFS error open root device) started to happen after one upgrade. The fix (workaround) I found was to remove autodetect hook from mkinitcpio.conf when building the kernels. I decided to reinstall the OS in hope of getting rid of the issue permanently, however reinstall does not help.
For more details of the issue refer to: https://discuss.cachyos.org/t/btrfs-module-support-in-linux-cachyos-6-17-7-latest-versions/18148

Start by comparing the default and LTS kernel boot behavior after the refresh installation, using the reported VFS error and the linked CachyOS discussion for context. Inspect the mkinitcpio.conf autodetect hook, then reproduce with the listed NVMe, BTRFS, bootloader, and partition combinations. Done means the default kernel boots the installed root filesystem without requiring the workaround.

Written by the indexing model from the issue text.