The PVS Target VMs cannot boot due to the following error message:
Stop Code: SYSTEM THREAD EXCEPTION NOT HANDLED
What Failed: CVhdMp.sys

We can modify the wait time using the following registry keys: This is the number of times the BNIStack will try to initialize the network (default 5) and wait in between attempts (default 200 ms) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BNIStack\Parameters Name:SocketOpenRetryIntervalMS Type: REG_DWORD Data: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BNIStack\Parameters Name:SocketOpenRetryLimit Type: REG_DWORD Data:

---

Problem Cause

The exception message in the blue screen indicates that there are some network adapter issues due to BNIstack could not load sucessfully throwing, "Error: 'BNIStack failed,network stack could not be initialized'"

This issue is generally caused due to incorrect streaming NIC identifier, Ghost\hidden network adapters or sometimes it takes longer than expected for the network to initialize and become available for the bnistack driver.  

The error in the screen indicates that PVS BNIstack driver tried to load , waited for sometime , but could not find the network.

In case it does not help then please refer to the solution for similar issues in the following articles:

CTX224827
How to troubleshoot PVS TD bootup error 'BNIStack failed,network stack could not be initialized'
CTX203060
Error: "BNIStack failed, network stack could not be initialized" on one streaming NIC network in Provisioning Services
CTX203471
Failed to convert vdisk with error message "BNIStack failed, network stack could not be initialized"
CTX216891
Error code 0x00007E, BSOD, When Creating vdisk - BNIStack Failed, Network Stack Could Not Be Initialized
CTX202087
BSOD with Error: "STOP 0x0000007E and CVhdMp.sys Error: BNIStack failed, network stack could not be initialized"