This is going to be a bit long but I suspect the X13SAE(-F) has some sort of stability issue, and I think it is related to the BIOS.
Installed Server 2019, and everything worked great - even Hyper-V which is not meant to work with the E-cores enabled. Installed all drivers and moved our VM's over and it has been working fine for around 7 days.
1st problem, on a reboot to add features to the host OS, some of the VM's would not start - the VM configuration files some how got corrupted. We re-created the VM's and attached the original VHDX. We did many disk checks / scans nothing wrong with the NVME drives that store the VM's (they are not new moved from the previous server).
2nd problem, the OS install got corrupted, and Server 2019 started to moan that sources could not be found to install a role - tried all the fixes, even adding the sources manually, etc, etc, So to save time - I installed a new boot SSD, and installed a fresh copy of Server 2019, exactly as before - enabled Hyper-V and rebooted, now getting a BSOD - weird, so I disabled the E-cores to see if that would work, and yes it did - so Hyper-V does need the E-cores disabled to work, so why did it work before with the E-cores enabled? (This is why I am thinking some sort of BIOS issue).
3rd problem, the fresh install of 2019 went well, everything installed, imported the VM's checked they work ok - then started the windows updates to bring it up-to-date, Then got a BSOD on reboot, with stopcode 0000021a, - tried everything to fix. So called it a day and re-installed the original BOOT SSD, and got back to where I had started the day.
Like I said the system works great when running, reboots scare me now, - just cannot trust if it will boot up with no errors.
Action plan for next week - install another Boot SSD, update firmwares BMC and BIOS, reset the board (BMC/BIOS to default), re-apply all the BIOS settings, and re-install Server 2019 - and see if we can get it to install and reboot with no BSOD's or file corruption.
Just adding my experience.
Installed Server 2019, and everything worked great - even Hyper-V which is not meant to work with the E-cores enabled. Installed all drivers and moved our VM's over and it has been working fine for around 7 days.
1st problem, on a reboot to add features to the host OS, some of the VM's would not start - the VM configuration files some how got corrupted. We re-created the VM's and attached the original VHDX. We did many disk checks / scans nothing wrong with the NVME drives that store the VM's (they are not new moved from the previous server).
2nd problem, the OS install got corrupted, and Server 2019 started to moan that sources could not be found to install a role - tried all the fixes, even adding the sources manually, etc, etc, So to save time - I installed a new boot SSD, and installed a fresh copy of Server 2019, exactly as before - enabled Hyper-V and rebooted, now getting a BSOD - weird, so I disabled the E-cores to see if that would work, and yes it did - so Hyper-V does need the E-cores disabled to work, so why did it work before with the E-cores enabled? (This is why I am thinking some sort of BIOS issue).
3rd problem, the fresh install of 2019 went well, everything installed, imported the VM's checked they work ok - then started the windows updates to bring it up-to-date, Then got a BSOD on reboot, with stopcode 0000021a, - tried everything to fix. So called it a day and re-installed the original BOOT SSD, and got back to where I had started the day.
Like I said the system works great when running, reboots scare me now, - just cannot trust if it will boot up with no errors.
Action plan for next week - install another Boot SSD, update firmwares BMC and BIOS, reset the board (BMC/BIOS to default), re-apply all the BIOS settings, and re-install Server 2019 - and see if we can get it to install and reboot with no BSOD's or file corruption.
Just adding my experience.