BSOD only after PXE

[jmeyer]

Hello,

FOG 1.6.0-alpha 1182
Kernel 6.1.22
Exit type : REFIND_EFI

After deploying an image that have been sysprep with the two last version of Windows 10 (21H2 and 22H2) and 11 22H2 on Lenovo M75q Gen2 and Lenovo M70q, I have BSOD “DRIVER VERIFIER DMA VIOLATION” if i go through EFI PXE.
If I disconnect network cable during boot, I don’t have this BSOD.

I don’t have the problem with Lenovo and HP computer from 2018.

What PXE could change during Windows boot that can create a BSOD ?

Thank you.

[Tom Elliott]

@jmeyer Some “drivers”, of which I’m guessing you’re using ipxe.efi as the boot file?, use a “firmware” injection methodology to load the device. This firmware approach can change - usually temporarily or until another driver forces the overwrite of that segment of the firmware ROM - cause a change.

I might suggest, changing the ipxe boot file to be card specific if possible. This should help prevent this flipflop sequence after booting.

Similarly, For this one device, does Exit Type: EXIT produce any better results?

[jmeyer]

The problem doesn’t appear with my other FOG server .
FOG version 1.5.9.37
Kernel 5.15.19
Exit type : REFIND_EFI

[george1421]

@jmeyer I would not consider fog 1.6.0-alpha for any type of productive use. While it has been kind of kept up in sync with the 1.5.x series it really hasn’t had much love in about 2 years.

IMO it really needs to get pulled until the developers can spend time with it working out its issues or they can get additional resources to spend time with the version.

[george1421]

@george1421 Thinking about this a bit more, lets have you run through this tutorial to rebuild iPXE to the latest version. https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe?_=1696626440791

I can’t say it will work (the act of rebuilding) with 1.6 since its been several years since I last installed it. But lets see about rebuilding iPXE and that might get you past that error message.

[jmeyer]

@george1421 As it’s happening only on my personnal FOG install, I don’t care to have to unplug lan cable.
I’ll try rebluild iPXE when I have time.
Thank you.

[Tom Elliott]

@jmeyer Some “drivers”, of which I’m guessing you’re using ipxe.efi as the boot file?, use a “firmware” injection methodology to load the device. This firmware approach can change - usually temporarily or until another driver forces the overwrite of that segment of the firmware ROM - cause a change.

I might suggest, changing the ipxe boot file to be card specific if possible. This should help prevent this flipflop sequence after booting.

Similarly, For this one device, does Exit Type: EXIT produce any better results?

[jmeyer]

@george1421 Rebuild to last version didn’t fix the problem.
@Tom-Elliott Exit type to EXIT give a “chainloading failed…”

using snponly.efi fixed the problem.

Thank you for your help.