So what @stephane suggested was to switch to the Testing branch and use the latest kernel supported by Manjaro, which is 5.16. And see if it’s working.
You can revert back to Stable and LTS kernel afterward.
# mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
-> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> Starting build: 5.10.96-1-MANJARO
==> Building image from preset: /etc/mkinitcpio.d/linux515-rt.preset: 'default'
-> -k /boot/vmlinuz-5.15-rt-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-rt-x86_64.img
==> Starting build: 5.15.18-2-rt28-MANJARO
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-rt-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515-rt.preset: 'fallback'
-> -k /boot/vmlinuz-5.15-rt-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-rt-x86_64-fallback.img -S autodetect
==> Starting build: 5.15.18-2-rt28-MANJARO
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-rt-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
-> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
-> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect
==> Starting build: 5.4.176-1-MANJAROyeah no idea why it’s trying to install the 5.15-rt module for a kernel I don’t have, I think that is a bug with how it;s managing kernel modules for the driver.
[manjaro corey]# pacman -Q | grep linux
archlinux-appstream-data 20220107-1
archlinux-keyring 20220125-1
lib32-util-linux 2.37.3-1
linux-api-headers 5.12.3-1
linux-firmware 20220119.0c6a7b3-3
linux-firmware-whence 20220119.0c6a7b3-3
linux510 5.10.96-1
linux510-headers 5.10.96-1
linux510-nvidia 510.47.03-1
linux510-virtualbox-host-modules 6.1.32-5
linux515-rt 5.15.18_rt28-2
linux54 5.4.176-1
linux54-headers 5.4.176-1
linux54-nvidia 510.47.03-1
linux54-virtualbox-host-modules 6.1.32-5
mips-linux-gnu-binutils 2.37-1
util-linux 2.37.3-2
util-linux-libs 2.37.3-2
Now it is there and has caused this issue lol
can you try to remove
mhwd-kernel -r linux515-rtor suppress
ls /etc/mkinitcpio.d/*.preset
rm /etc/mkinitcpio.d/linux515-rt.preset
cat /etc/mkinitcpio.d/linux515.presetis there any -rt in last result ( cat ) ?
I removed it 
[manjaro corey]# mhwd-kernel -r linux515-rt
checking dependencies...
Packages (1) linux515-rt-5.15.18_rt28-2
Total Removed Size: 99.18 MiB
:: Do you want to remove these packages? [Y/n] y
:: Running pre-transaction hooks...
(1/2) Removing linux initcpios...
(2/2) Remove DKMS modules
:: Processing package changes...
(1/1) removing linux515-rt [##############################################################################################] 100%
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Updating Kernel initcpios for Nvidia-DRM...
(4/4) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
grub-probe: error: cannot find a GRUB drive for /dev/sdd1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdd1. Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
[manjaro corey]# pacman -Q | grep linux
archlinux-appstream-data 20220107-1
archlinux-keyring 20220125-1
lib32-util-linux 2.37.3-1
linux-api-headers 5.12.3-1
linux-firmware 20220119.0c6a7b3-3
linux-firmware-whence 20220119.0c6a7b3-3
linux510 5.10.96-1
linux510-headers 5.10.96-1
linux510-nvidia 510.47.03-1
linux510-virtualbox-host-modules 6.1.32-5
linux54 5.4.176-1
linux54-headers 5.4.176-1
linux54-nvidia 510.47.03-1
linux54-virtualbox-host-modules 6.1.32-5
mips-linux-gnu-binutils 2.37-1
util-linux 2.37.3-2
util-linux-libs 2.37.3-2
Do you still want me to check using the command for 5.16 or do it with 5.10?
then
mkinitcpio -Pyou can add linux516
mhwd-kernel -i linux516Alright done, should I restart now?
Yes, try to restart and see if the problem still persists.
last check just before reboot
ls /usr/lib/modulesYep that fixed it guys! thanks for at least getting me back up and running, needed to also do sudo update-grub in case as the grub menu didn’t show up and went right into my main Manjaro OS.
Wonder why it all wonked out and broke it 
you should not have 5.15-rt-MANJARO or extra-5.15-rt-MANJARO
yeah no idea why that was even installed as I never use that kernel and just stick with the default LTS kernel
Might need to have the code checked and see if it’s doing that or if others are having a similar issue.
you have added with MSM ( Gui ) or with mhwd-kernel command ?
As far as I know kernel don’t install by themselves. What is output of mhwd-kernel -li
Are you talking about the Manjaro kernel tool or driver installer tool for Nvidia and other drivers?
Yeah it doesn’t, maybe it mistakenly installed on a update?
may be something wrong in mhwd script for 515-rt ( and 515 LTS … ) or version modules nvidia wrong in 5.15-rt nvidia
@philm , @oberon
mhwd-kernel -li ✔
Currently running: 5.10.96-1-MANJARO (linux510)
The following kernels are installed in your system:
* linux510
* linux54
Yeah could be, when I install I select the closed source driver on the live cd so it’s already installed and leave the kernel on the LTS
You could add the 5.15 kernel too, and remove or keep the 5.4 (from Manjaro Settings Manager).
You have multiple kernels now so if you fail to boot on update, you can switch kernel on boot (flood the escape and/or shift key during boot to force Grub menu to show if it doesn’t automatically show) in case you have an issue after update (didn’t re-read all thread to check if you tried but that was a possibility).