none
Rebooting Issues with Deploying to a Optiplex 7040-Setup never completes.

    Question

  • We are trying to use both MDT and SCCM to reimage this unit (Optiplex 7040). The imaging process completes normally. When the unit restarts, it goes into a constant Repair boot loop. I have rebooted it in safemode and then notice that on AMDKMPFD.sys, the unit will restart. Both deployments have been configured to use ONLY drivers for the 7040. Anyone had this issue?

    I have created a MDT task sequence isolating the drivers for the 7040 and it still has the issue.

    Monday, January 25, 2016 7:28 PM

Answers

  • You can't install this from USB or DVD. Windows 7 is missing essential system parts required to perform the install.

    You can however create an image, where you inject certain hotfixes and put it on the computer.
    I can confirm this works with SCCM

    The steps I followed:

    1. Install Windows Assessment and Deployment Kit (Windows ADK)
    https://www.microsoft.com/en-us/download/details.aspx?id=39982

    2.Create the folders C:\share\Win7 , C:\share\temp , C:\share\NVMEw7fix , C:\share\NVMEw7fix2

    3. Download hotfix 2990941 for NVMe and extract to C:\share\NVMEw7fix

    https://support.microsoft.com/en-us/kb/2990941

    4. Download hotfix for stop error after you install hotfix 2990941 and extract to C:\share\NVMEw7fix2

    https://support.microsoft.com/en-us/kb/3087873

    5. Launch Deployment and Imaging Tools Environment (CMD in Windows Kits)

    6. Run these commands to inject the hotfixes:

    DISM /mount-wim /wimfile:"c:\share\Win7\Win7Ent_18062015.wim" /index:2 /mountdir:c:\share\temp

    DISM /image:c:\share\temp /add-package /packagepath:c:\share\NVMEw7fix

    DISM /image:c:\share\temp /add-package /packagepath:c:\share\NVMEw7fix2

    DISM /unmount-wim /mountdir:c:\share\temp /commit

    7. Upload the image to SCCM and deploy


    Stijn

    • Proposed as answer by BT White Wednesday, March 30, 2016 2:15 PM
    • Marked as answer by Ty GlanderModerator Wednesday, April 06, 2016 10:39 PM
    Tuesday, March 22, 2016 8:32 AM

All replies

  • Looking at the Optiplex 7040 and it appears to have a base intel intigrated graphics card.....

    Why are you pushing a AMD graphics driver at it??

    Monday, January 25, 2016 7:37 PM
  • I am not pushing an AMD card at it.  the Task sequence is specifically targeting the drivers from the Cab file.  Unless Dell messed up somewhere in publishing the driver cabs.

    Monday, January 25, 2016 7:38 PM
  • Can you pull a version from the AMDKMPFD.sys file. You might have to updated the driver cab pack.

    AMD Radeon R5 340X and R7 350X Driver
    This package provides AMD Radeon R5 340X and R7 350X Driver and is supported on OptiPlex 7040 and 5040 running the following Operating Syste...
     View details
    Video_Driver_N65PP_WN32_14.502.1041_A00.EXE | Update Package for Microsoft® Windows® (360 MB)
    Video|Release date 28 Oct 2015|Last Updated 28 Oct 2015|Recommended
    Version 14.502.1041,A00
    This file will automatically self-install after downloading.Restart required Download File
     Add to download list

    Intel HD, 5300, 5500, 6000, 515, 520, 530, P530, Iris 540 Graphics Driver View details
    Video_Driver_0XR5N_WN32_10.18.15.4279_A01.EXE | Update Package for Microsoft® Windows® (183 MB)
    Video|Release date 28 Oct 2015|Last Updated 24 Nov 2015|Recommended
    Version 10.18.15.4279,A01
    This file will automatically self-install after downloading.Restart required Download File
     Add to download list

    nVIDIA GeForce GTX 745 Graphics Driver View details
    7040_Video_Driver_Y3Y37_WN32_10.18.13.5324_A00.EXE | Update Package for Microsoft® Windows® (300 MB)
    Video|Release date 16 Oct 2015|Last Updated 22 Oct 2015|Recommended
    Version 10.18.13.5324,A00
    This file will automatically self-install after downloading.Restart required Download File

    • Edited by The Grim Monday, January 25, 2016 7:50 PM html formating
    Monday, January 25, 2016 7:49 PM
  • Will post an update, testing now.

    Monday, January 25, 2016 7:52 PM
  • Looking at the Dell cabs for 7-10 release was 12/22/2015.
    Monday, January 25, 2016 7:55 PM
  • ok,  went back to my MDt as a test, Deleted the AMD driver, I then received a reboot of death on Disk.sys.  Took it another step and removed ALL of the drivers for the 7040, Still got the reboot of death for disk.sys.

    Monday, January 25, 2016 8:30 PM
  • even with a base image it is BSOD, might want to take off the kid gloves and try a base install on it to insure stability. 

    Hopefully you still have an install disk that isn't being used for a coaster.

    Monday, January 25, 2016 9:18 PM
  • Are you enabling bitlocker? If so - update the BIOS. There is a bug in some of the Optilex 7040 BIOS'es that causes reboot into repair.

    Niklas Ramstedt IT-support / Sys admin

    Thursday, February 25, 2016 6:36 AM
  • Did you have a look at this document?

    http://www.dell.com/support/article/us/en/19/SLN300564

    Apparently these devices only have USB3 which Windows 7 does not natively support.

    Converting the article to SCCM and I think you can insert those drivers mentioned in the install.wim of your sccm image.

    I have not yet tested this but will do so in the coming week.


    Stijn


    Friday, March 18, 2016 9:50 AM
  • We are having the same issues with our 7040's and SCCM OSD.  I tried safe mode and it rebooted on the AMDKMPFD.sys driver, so I removed our driver package and created a new one with only the drivers needed for our config (based off service tag).   Now it's rebooting at disk.sys just like OP.  I have the latest BIOS version and we are not deploying BitLocker to our desktops so TPM is off.
    Monday, March 21, 2016 4:53 PM
  • Have you tried injecting the drivers from the Dell article into your boot image?

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Monday, March 21, 2016 7:19 PM
    Moderator
  • Not into the Boot image, but I just added them to my 7040 driver package.  Just waiting on my DP to update and then I'll redeploy and test.  Correct me if I am wrong, but it's I think we are past the point where the boot image is an issue, right?  If it were an issue with the boot image then it wouldn't even get to the point of installing the OS and drivers, etc.?
    Monday, March 21, 2016 7:39 PM
  • It will likely end up drivers for the make model and WinPE. Are you using the Total Control method of driver management ?

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Monday, March 21, 2016 9:13 PM
    Moderator
  • You can't install this from USB or DVD. Windows 7 is missing essential system parts required to perform the install.

    You can however create an image, where you inject certain hotfixes and put it on the computer.
    I can confirm this works with SCCM

    The steps I followed:

    1. Install Windows Assessment and Deployment Kit (Windows ADK)
    https://www.microsoft.com/en-us/download/details.aspx?id=39982

    2.Create the folders C:\share\Win7 , C:\share\temp , C:\share\NVMEw7fix , C:\share\NVMEw7fix2

    3. Download hotfix 2990941 for NVMe and extract to C:\share\NVMEw7fix

    https://support.microsoft.com/en-us/kb/2990941

    4. Download hotfix for stop error after you install hotfix 2990941 and extract to C:\share\NVMEw7fix2

    https://support.microsoft.com/en-us/kb/3087873

    5. Launch Deployment and Imaging Tools Environment (CMD in Windows Kits)

    6. Run these commands to inject the hotfixes:

    DISM /mount-wim /wimfile:"c:\share\Win7\Win7Ent_18062015.wim" /index:2 /mountdir:c:\share\temp

    DISM /image:c:\share\temp /add-package /packagepath:c:\share\NVMEw7fix

    DISM /image:c:\share\temp /add-package /packagepath:c:\share\NVMEw7fix2

    DISM /unmount-wim /mountdir:c:\share\temp /commit

    7. Upload the image to SCCM and deploy


    Stijn

    • Proposed as answer by BT White Wednesday, March 30, 2016 2:15 PM
    • Marked as answer by Ty GlanderModerator Wednesday, April 06, 2016 10:39 PM
    Tuesday, March 22, 2016 8:32 AM
  • Stijn SES's steps worked for us.  We successfully imaged a 7040 via SCCM OSD with a win7 image.
    • Edited by BT White Wednesday, March 30, 2016 3:37 PM spelling
    Wednesday, March 30, 2016 2:16 PM
  • Nice writeup Stijn, fixed our issues as well.
    These NVME drives got us by surprise. Nice evolution nontheless: very fast and compact.

    Using W7ent on MDT2013

    I simply copied install.wim out of our existing sources folder in the MDT share and copied it back afterwards.

    I had to change the index to 1 (/index:1)

    Dell has a lot of documentation as well
    http://www.dell.com/support/article/us/en/19/SLN301149/
    Tuesday, May 03, 2016 2:29 PM
  • I'm having the exact same issue. Have you found a solution yet?

    Thanks

    Wednesday, May 04, 2016 6:02 PM
  • Have you tried the suggestions in the post?

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it.

    Wednesday, May 04, 2016 6:12 PM
    Moderator
  • I'm trying Stijn SES's suggestion now, I just wanted to confirm that fixes OP's issue since they never confirmed it did.
    Wednesday, May 04, 2016 7:07 PM
  • I added both packages to my image using DISM as mentioned before but I'm still getting a boot loop when I image a 7040 Micro. It blue screens during the boot and references DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Wednesday, May 18, 2016 11:32 AM
  • I am receiving this issue on new Workstations with a Xeon v4 CPU. (Precision T7910)
    The reason is probably that the Chipset Drivers in the CAB are out of Date, there is also no straight-forward way to extract them and update them on your own. (Extracted them from the DriverStore from my target system)

    Removing the drivers from ATI helped as a workaround.
    Deployment finished but chipset drivers are missing afterwards.

    Wednesday, May 18, 2016 12:41 PM
  • I decided to inject Optiplex 9020M drivers when imaging a 7040 micro and it did not blue screen/reboot loop after applying the image. Now I'm going back and swapping some drivers to see what works and what doesn't.
    Thursday, May 19, 2016 12:26 PM
  • Hi

    I got this to work in MDT by adding the two hotfixes in as a new Packages group. Then adding them to a new Selection Profile and then having it run an Offline Update task sequence which the selection profile just created just after the driver injection.

    This succesfully installed and configured windows when we were experiencing similar issues.

    Also we had already imported a Samsung NVME already which may be required but not 100% sure on that
    Thursday, June 23, 2016 11:18 AM
  • Can you please give us a step by step tutorial please....
    Tuesday, July 19, 2016 10:29 PM
  • I owe the author of this reply a beer or two. It worked for me. Thanks!

    Jason

    Thursday, August 25, 2016 7:43 PM
  • these hotfixes worked a treat using MDT 2013. Instead of using DISM i just added the packages and used a task sequence to inject them into the image at the pre-install section. NVMe SSD's now boot and complete the install. Thanks for the post.

    Ollie

    Thursday, September 08, 2016 4:08 PM
  • Hello guyz,


    I had the same problem of loop rebooting after winpe deployment . Computer reboot when loading AMDKMPFD.sys. I deleted this driver. After, the computer reboot when loading disk.sys

    My 7040 computers have samsung PM961 NVMe 256gb ssd.

    My MDT deployment failed because the DELL driver package, I imported in MDT,  doesn't have the NVME drivers.

    I just add the PM961 NVMe driver to MDT "out-of-box drivers".

    Now, all is OK.

    No more fail. You can keep AMDKMPFD.sys.


    See ya.




    • Edited by Mike-eul Tuesday, January 17, 2017 3:14 PM
    Tuesday, January 17, 2017 3:11 PM