• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

BSOD only after PXE

Scheduled Pinned Locked Moved Solved
Windows Problems
3
7
892
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    jmeyer
    last edited by jmeyer Oct 6, 2023, 2:38 AM Oct 6, 2023, 8:28 AM

    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.

    J G 2 Replies Last reply Oct 6, 2023, 12:35 PM Reply Quote 0
    • T
      Tom Elliott @jmeyer
      last edited by Oct 10, 2023, 9:58 AM

      @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?

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      1 Reply Last reply Reply Quote 0
      • J
        jmeyer @jmeyer
        last edited by Oct 6, 2023, 12:35 PM

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

        1 Reply Last reply Reply Quote 0
        • G
          george1421 Moderator @jmeyer
          last edited by Oct 6, 2023, 6:47 PM

          @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.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

          G J 2 Replies Last reply Oct 6, 2023, 9:09 PM Reply Quote 0
          • G
            george1421 Moderator @george1421
            last edited by Oct 6, 2023, 9:09 PM

            @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.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            J 1 Reply Last reply Oct 10, 2023, 8:02 AM Reply Quote 0
            • J
              jmeyer @george1421
              last edited by Oct 10, 2023, 8:02 AM

              @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.

              T 1 Reply Last reply Oct 10, 2023, 9:58 AM Reply Quote 0
              • T
                Tom Elliott @jmeyer
                last edited by Oct 10, 2023, 9:58 AM

                @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?

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                1 Reply Last reply Reply Quote 0
                • J
                  jmeyer @george1421
                  last edited by jmeyer Oct 11, 2023, 3:59 AM Oct 11, 2023, 9:52 AM

                  @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.

                  1 Reply Last reply Reply Quote 0
                  • [[undefined-on, J jmeyer, Oct 11, 2023, 10:01 AM]]
                  • 1 / 1
                  1 / 1
                  • First post
                    7/7
                    Last post

                  256

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project