BSOD after kbe load

We are having an issue with a new model laptop that we just received it is the Latitude 3379. The model has no NIC so we purchased the Dell USB-C to ethernet adapter.
I created the new boot environment with the required drivers just after the kbe loads and it shows the windows 10 icon it BSOD.
Quest has told us to contact Dell and Dell has told us to contact Quest so here I am.

We are at a loss as we have never really run into something like this where we are at a loss on what to do next.


5 Comments   [ + ] Show comments
  • Hello khoelle, Have you used the dell driver tool on one of the machines that was up and running with your network setup? If so, have you recached the drivers and created a new KBE? - jboling 4 years ago
    • Yea. Just created another KBE as well just to be sure. Same issue, we have also tried a USB boot. I updated the M.2 SSD firmware as well. The errors we get on the BSOD aren't really consistent either. We have have about 5 different error types. - khoelle 4 years ago
  • Well I am closer than I was this morning. I downloaded the .cab file and updated the network/storage drivers in the kbe driver feed. I also read that some systems require chipset drivers as well.
    I now get everything copied over and image applied but the first reboot causes BSOD
    I did apply new drivers to the driver feed too so I will follow up with my findings when I hopefully check the log file soon. - khoelle 4 years ago
  • I just got this computer on my desk today and was asked to get it imaged....... same issues (different errors) as first reported and just finished up with a new KBE so will give it a try.... gave it a run and it shows the system error 1231 has occurred. I did the new .cab and recached all drivers then built new KBE.
    So I hope someone else can give some insight. - TimHR 4 years ago
    • We have another one coming in later this week or early next week. My plan is to use the driver extractor program to pull the drivers off the dell image. The laptop ran great with the dell image so there must be some kind of difference in the drivers used on their image and what is in the .cab - khoelle 4 years ago
  • Sorry forgot to mention that I used DoubleDriver to pull the drivers off just in case we were missing the correct one(s) and then rebuilt everything. - TimHR 4 years ago
  • I should note that right now our windows 10 image is not UEFI. I was able to build a USB dell recovery and that installed fine through uefi. I talked to a del tech and he suggested trying a regular ssd and not the m.2 but we don't have that type of motherboard connector available to try that.
    I am kind of at a roadblock only thing I haven't tried is installing with no drivers in the post install feed - khoelle 4 years ago

Answers (2)

Posted by: Nico_K 4 years ago
Red Belt
which blue screen do you get?
I really suggest to follow this article (it is valid for other systems too, recently ran into the issue with an older E6530)

  • I have been getting memory management/page file bsods I will give this a try as well thanks - khoelle 4 years ago
Posted by: khoelle 4 years ago
Yellow Belt
OK I finally got through to Quest.
The issue is we used a physical system for image capture and the problem is that sysprep can sometimes leave behind old drivers and this is what is causing the BSOD after image/driver install.
To test this we were asked to do a scripted install and it installed without a hitch.

Next week our goal is to set up a VM windows 10 UEFI Image 

Hopefully this points others in the right direct as well.

  • OK you are getting it to image then you had been getting the BSOD........ I have not been able to get it to the white page to choose a image or a script it starts to load up then I get BSOD page fault error or a memory management error.
    We always so far have imaged all the computers with legacy set.
    I tried setting to UEFI and it tries to load up the same but I still get the same BSOD with a error.

    How are you getting it to the white page to start the image????? - TimHR 4 years ago
    • I copied the network\storage\chipset drivers from the feed into the KBE driver feed thats when I got past the first BSOD - khoelle 4 years ago
      • Copied the storage\chipset drivers from feed into KBE now all ready had copied
        the network drivers, it now loads to the white page and I can choose deploy image or script with out errors.

        Deployed Win 7 image with Legecy and it imaged without errors. Deployed a win 7 imaged lots of drivers missing.
        Deployed Win 7 image with UEFI and it did not image.
        Deployed Win 10 image with Legecy and it imaged without errors. It did reboot a few times 1 driver with a warning symbol
        called Trusted Platform Module 2.0, says the best driver is all ready installed.

        I am also using the Dell dock WD15 with 130W adapter. You do not need the dock but it seems you need
        a USB Type-C Cable (thunderbolt) to get the nic part. So a USB Type-CTM Cable to ethernet would might work great.

        Tried a USB to Ethernet cable did not work. The cable does see the network when in the desktop just will not PXE image. - TimHR 4 years ago
    • Yea I installed the .cab after doing a base w10 image and there were several missing drivers same Trusted Platform Module being the only one I couldn't fix.
      I will reach out to dell about an updated .cab - khoelle 4 years ago
  • We build our images in a VM - TimHR 4 years ago
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ