Precision 3560 BSOD After Imaging with MDT 8456

We just received our first Precision 3560 systems and we cannot deploy due to a BSOD during the deploy process.  We have never received new Dell equipment this early in their lifecycle.  I have never imported A00 CAB files for any model so there is no wiggle room to easily try a prior release of any driver.  Since the BSOD is an  Inaccessible Boot Driver my first thought is the Intel storage driver.  I am not sure if the issue is specific to Precision 3560 since it is the only new one I have due to someone buying Latitude 7410s that don't have silly RJ45 jacks.

• MDT 8456 with ADK 2004 and the fix for issues with non-EUFI devices
• Dell WinPE A22 used due to Storage Drivers not working in A18 with this laptop model -- did not try older version last night due to A22 shipping after the 3560 shipped.
• Verified the model is Precision 3560 using the WMIC command -- Dell once named a tablet with an odd name that had nothing to do with the marketing model number.
• Downloaded CAB file a second time to ensure a mistake was not made.  Using the 3560 CAB file as we always use the model specific drivers.
• "Total Control" methodology for driver control in MDT -- burnt by bad Win7 drivers years ago.  Use the option to always import the driver when importing.
• BIOS updated before image attempt to the version available on 2/11/2021

Steps to reproduce:

1. PEXE boot into MDT
2. Complete the MDT wizard steps (tried our 2004 image as well as our older 1809 one -- no 1903/1909 image)
3. MDT partitions disk
4. MDT inject drivers
5. MDT "installs" operating system, applies unattend.xml with DISM
6. MDT reboots the PC
7. BSOD with inaccessible boot device - I believe this is still WinPE in control at this point.

Nothing useful in the MDT logs on the device -- they are pretty sparse at this point in the MDT cycle.  I failed to look for a memory dump last night, but for some reason I want to say one is not available during the process.  Johan Arwidmark has an article on debugging BSOD on WinPE that I will be using as a guide to see if I can get a memory.dmp file when I visit the office tonight. (Staying out during regular business hours due to COVID unless there is a true emergency.)