8 Replies Latest reply on Oct 21, 2016 6:58 AM by phoffmann

    0x7E BSOD after applying wim image and install drivers with dism (W7 x64)

    Rookie

      Good morning,

       

      We are trying to solve this problem for months, but we have tried all the solutions from the web and the problems remains, also in models that  where correctly working.

       

      Our company is deploying W7 64 bit, on a lot of different models, using Landesk, using many vbs scripts made by us. The gold image is made on a virtual machine, then syspreped and captured. This syspreped wim is deployed to the client by a WinPE 5.0 x86 (W8.1 32 bit), using imagex command, the same problems happens using dism commands. First of all, we partition the disk in MBR, with one partition of 300 mb for booting, and another one for the system. Then the syspreped wim is applied, to both partitions (we have also tried to create de boot partition instead of appliying it). At last, we install the drivers to the offline image using dism. So, although we use Landesk, the problem happens doing all the process manually with WinPE, and I think it would happen with any deployment app.

      It happens on new and older machines, at the beginning we think that it could be because of the SSD disks, but it also occurs on non SSD Disks…We use use BIOS mode, instead of UEFI, but we have tried with this one, and is the same.

       

      Finished this process, the machine is restarted, but when Windows logo is charging it freezes, and gives a BSOD with 0x7E error. We have seen that this only happens with a fully updated image, not if we use a clean W7 installation captured, but when we update this virtual machine, and capture it, always happens. The only way we can avoid this, is not installing the drivers, or remove some drivers after a lot of test-error. It always freezes when loading disk.sys (seen at safe mode) but, sometimes is due to the audio driver, another one the usb 3, another one the hotkeys… it has no sense, and we have not found any easy way to know it, because no log or dump is created.

       

      We have installed the NVMe patches from Microsoft on the image, installed the intel and Samsung NVMe disk on the offline image, tried not installing some of the Microsoft updates on the image, making the image from the beginning again, but nothing has been successful. And to make it more strange, sometimes it happens on the same machine at the first deployment, but if you try it second, it works…

       

      Can anybody see the sense of this behavior? Any idea of how to solve this?

       

      Thanks in advance.

        • 1. Re: 0x7E BSOD after applying wim image and install drivers with dism (W7 x64)
          Kenyon Expert

          What machine vendor are you working with? Do the machines you are working with have MVMe drives? Is the BIOS drive setting set to RAID or another mode?

          • 2. Re: 0x7E BSOD after applying wim image and install drivers with dism (W7 x64)
            Rookie

            Most of them are HP laptops, but it happens also on some Dell. I´m not sure if the drives are NVMe... one of the disks, for example, is a Sandisk SD7SN6S 256GB. We have tested with bios and uefi modes, and is the same. Usually we configure them in AHCI mode, but this model (HP Elitebook 840 G3) gives no option to configure it.

            • 3. Re: 0x7E BSOD after applying wim image and install drivers with dism (W7 x64)
              Kenyon Expert

              I believe the Sandisk drive to not be an NVMe interface. Are you removing all partitions as part of your Pre-OS installation? I am guessing that when the gold image is sysprepped you are utilizing the generalize option?

              1 of 1 people found this helpful
              • 4. Re: 0x7E BSOD after applying wim image and install drivers with dism (W7 x64)
                Rookie

                I think you are right, i´ve not seen that this drive is NVMe, although I´ve tested with NVMe drivers, and without them.

                Yes, we sysprep de machine with generalize option. And before applying the image we clean all the disk and make the new MBR partitions usig diskpart

                • 5. Re: 0x7E BSOD after applying wim image and install drivers with dism (W7 x64)
                  jParnell Specialist

                  Is there a reason you are applying the the system partition after laying down the wim rather than using bcdboot to generate boot information? That is not a likely part of your issue, but I have never seen this method done before, and cannot fathom the logical reason behind it.

                   

                  Everything is pointing to it being a driver issue, from what I've seen. Looking up the Sandisk model number you provided, I'm seeing several different versions; If this is your version, it is an NVMe drive. From my experience, you must set the SATA mode to RAID (even in a single disk), on UEFI, and use the Intel RST drivers, injected in your boot wim (for OSP) and deployed to your image using DISM (see my post here Re: Windows 7 Image on a NVMe Solid State Drive ).

                   

                  Here is the way our scripts work, so that you may compare for reference.

                   

                  Diskpart:

                  select disk=0
                  clean
                  convert mbr
                  create part pri size=300
                  format fs=ntfs quick label=System
                  active
                  assign letter=S
                  create part pri
                  format fs=ntfs quick label=Windows
                  assign letter=C

                   

                  bcdboot:

                  bcdboot C:\Windows /s S:

                   

                  ImageX:

                  imagex /apply Z:\images\Win7x64_standard.wim 1 C:\

                   

                  DISM:

                  dism /image:C:\ /add-driver /driver:C:\drivers /Recurse /ForceUnsigned

                   

                  We use a method of detecting the model (based on the WMI query "wmic csproduct get name", if memory serves) to copy our models' drivers to C:\drivers (after the image is laid down), where it is staged for DISM to inject.

                   

                  When we capture a reference computer (again, using ImageX), we only capture the partition for Windows; we leave the System partition out of the mix.

                  1 of 1 people found this helpful
                  • 6. Re: 0x7E BSOD after applying wim image and install drivers with dism (W7 x64)
                    Rookie

                    Thanks for anwering jParnell, and sorry for not answering before, I was making more tests in order to cancrete a bit more the problem.

                     

                    We aren´t using bcdboot only for the reason that we used to do as this when working with XP, it´s only because we mantained this deployement way. I agree with you that the correct way is using bcdboot, we are thinking about changing it, but we would have to change all the OSD scripts, so we delaying it... In our case we would use the bcdboot.exe from the Windows installation, because we yet are with BIOS mode an using 32 bit WinPE.

                    The script we use is the same as yours, only changes the part of the boot partition.

                     

                    As Said, we aren´t working in UEFI, neither provisioning, and we are not capable to change this already, we will do it as we start deploying W10. But I think the problem is not related to this, because if we deploy with less drivers, all the proccess goes well.

                     

                    This days I´ve been making several test with differebt Windows Updates, as in a clean install it works, and after updating it crashes, I thought that maybe an update would cause it. I have checkes that KB3033929 was making trouble, after installing it the blue screen appears. I have read something about it, but after instllaing some newer updates, this one disapeared. I think that another one should be installed before this not to have problems. I´m not sure, but I supose that newer one has replaced it, or maybe it has been correctly installed after it.

                    The fact is that, now, I have a working updated W7, the only update that remains is the October RollUp, I´m now testing if it works OK or not, in previous test blue screen has appeared after installnig it, I will tell you when I´m sure.

                     

                    I have not installed any specific NVMe driver, and its working. A curious behaviour is that when charging Windows logo in the first reboot after deploying, it make a little snap, like a tiny stop, I think it happens when charging disk drivers.

                     

                    I´ll make some more test and tell you about the results.

                    • 7. Re: 0x7E BSOD after applying wim image and install drivers with dism (W7 x64)
                      Rookie

                      After the last tests, I´ve seen that the last October update (KB3185330) is creating problems on our deployment system. After installing it, our deployment on a HP Elitebook 840 G3 gives the 0x07E BSOD. As Microsoft has decided to mix all the updates in a big one... I don´t know how to solve it... maybe not installing the update on the golden image, and wait to November Update... and pray it doesn´t break something else...

                      • 8. Re: 0x7E BSOD after applying wim image and install drivers with dism (W7 x64)
                        phoffmann SupportEmployee

                        Miguel wrote:

                         

                        After the last tests, I´ve seen that the last October update (KB3185330) is creating problems on our deployment system. After installing it, our deployment on a HP Elitebook 840 G3 gives the 0x07E BSOD. As Microsoft has decided to mix all the updates in a big one... I don´t know how to solve it... maybe not installing the update on the golden image, and wait to November Update... and pray it doesn´t break something else...

                         

                        ... yeah - that's pretty much my vote. Since you can't select things out, "just" try to patch the system as part of the post-OS install.

                         

                        There have always been a "few" difficult / annoying patches that'd break stuff, but with the new bundles, we can't just remove those & deal with them later. You have to ignore the entire month, and maybe several at that .

                         

                        First priority (in the end) is to get "a functional OS on", then a functioning agent ... patching AFTER that may be annoying, but at least it's not something that should brick your systems for you. Not ideal, but it looks like that "necessary, clunky workaround" is still going to be with us for quite some time thanks to the new update model .