The customer created two different vdisks from two different master target devices on Nutanix.
Both master target devices appeared to have identical hardware configuration in Nutanix management console.

One vdisk failed to boot against PVS targets created via CVAD Setup Wizard, while the other booted fine against the same target devices.
The vdisk which failed to booted showed a message Attempting to set IP address on boot NIC... followed by a BSOD 60 seconds later.

Checking further the source of the  PVS BSOD was identified.
The working and non working vdisks had different network adaptor configurations.
Using MSInfo32 -> Components -> Network -> Adapter , it can be checked that each vdisk had a different entry for PNP Device ID for their network adaptors.

Nutanix based VMs, if booted before without secure boot enabled, will need network adaptors recreated after enabling secure boot to ensure network hardware configuration is identical to a VM which was only ever booted with secure boot enabled.
Steps:

1. Power Off the Master target VM
2. Ensure Secure Boot/vtpm is enabled (enable it not already enabled)
3. Remove the network adaptors from the VM
4. Recreate the network adaptors 
5. Boot the VM, and complete usual steps to create a new PVS vdisk

Problem Cause

Nutanix based VMs network hardware configuration may differ inside windows depending on the configuration of secure boot when the VM first booted. This different configuration may not be visible in Nutanix management console.

Below VMs will have different network hardware configuration:

• VM has secure boot currently, and booted first without secure boot
• VM has secure boot currently, and has only booted with secure boot enabled (never started without secure boot)
  
  

The non working vdisk was created from a VM which was initially created and booted without secure boot enabled.