Surface Pro 9 won't boot after a seemingly successful installation

[kubaspek]

I'm building a flake which integrates devices to it's config, but I've encountered issues with this Microsoft Surface Pro 9. I've partitioned the ssd for dualboot between Win11 and NixOS, compiled a NixOS compatible kernel, ran nixos-install from an installation thumbdrive and everything seemed to work, but when rebooting into NixOS, a series of scary error messages popped up.

Here is a photo of the faulty boot:

My config:
https://github.com/kubaspek/nixos/

In hosts/desktops/surface/ you can find the host specific config for the Surface and nixos-hardware imports are in flake.nix on lines 18 and 123

I suspect the problem is either somewhere here or perhaps in nixos-hardware itself, but I really don't know:

# The system config for Surface

## Sources

{ config, lib, pkgs, inputs, ... }: {

### BOOT
    
    boot.supportedFilesystems = ["ntfs"];
    boot.loader.efi.canTouchEfiVariables = true;
    boot.loader.efi.efiSysMountPoint = "/boot";
    #boot.blacklistedKernelModules = ["ov13858"];

boot.loader.grub = {
      enable = true;
      efiSupport = true;
      #zfsSupport = true;
      efiInstallAsRemovable = false;
      memtest86.enable = true;
      device = "nodev";
      useOSProber = true;
      /*mirroredBoots = [
        {
          devices = ["nodev"];
          path = "/boot";
        }
      ];*/
  };

# Disk and FS config
{config, pkgs, ...}: {
### ZFS CONFIG
    #boot.zfs.requestEncryptionCredentials = ["nvme"];

  #boot.kernelPackages = config.boot.zfs.package.latestCompatibleLinuxPackages;
    #boot.zfs.package = pkgs.zfs_unstable;
/*
services.zfs = {
      trim.enable = true;
      autoScrub.enable = true;
    };
*/


### MOUNTS
  fileSystems."/" = {
    device = "/dev/disk/by-uuid/b69e469e-3d00-4338-a415-c5abd8a939e7";
    fsType = "ext4";
  };

  fileSystems."/boot" = {
    device = "/dev/disk/by-uuid/DA67-00D0";
    fsType = "vfat";
    #options = ["noexec" "nodev"];
  };

I've tried blacklisting the "vo13858" kernel module, because the boot sequence had a problem with it, but I got another error after doing that so the problem is probably somewhere else anyways

Feel free to ask for any additional info
Thanks