Unsolved
This post is more than 5 years old
1 Message
0
111702
February 11th, 2014 09:00
Latitude e6430 BSOD - MDT
We have a mixed Dell environment and use MDT 2012 u1 to image our systems.
All models image fine, except the e6430. The issue occurs while setup is installing devices, and results in a BSOD.
I updated the drivers to the newest CAB from Dell, as well as updating the BIOS to the newest release... no change.
During the MDT phase, this particular model seems to take a bit longer for DISM to write the unattend.
Some other things I have tried:
-Different TS
-Used UEFI instead of legacy
-DBAN'd the drive
-Hardware diagnostics (OK)
-Different units of e6430
-Reseated/swapped RAM
-Switched out HDDs
I attempted to look at logs, but MDT logs show nothing of importance (that I found). Again, this only affects the e6430.
Other models work fine: e6420, e6430s, e6520, e6530, e6440, Optiplex 380, 390, 3010, etc, etc.
Any ideas?
dcat78
1 Message
0
February 17th, 2014 09:00
Try removing the Free Fall driver from your install. I'm using SCCM 2012 R2 with a little MDT mixed and have yet to be able to install that one very specific driver. STMicroelectronics 3-Axis Digital Accelerometer is the name of the driver as it comes up in SCCM.
Joe_S_La
1 Message
0
April 23rd, 2014 07:00
Gaspumper,
I ran into this same problem with the 6430 deployment using MDT2013 and WDS on Server 2012 R2. I struggled with it for a few weeks before I tried recreating my Windows install .wim file from scratch. This resolved it for me.
I decided to try recreating the .wim after I did a few test images on the 6430 without injecting drivers. I was able to get through deployment on those machines, but when trying to install one of the USB hub drivers (iusb3hub in my case), it would bluescreen.
I then installed Windows on a 6430 from disc and tried to install the same drivers... encountered no problems.
So, the .wim itself seemed isolated as the problem. Sure enough, it was. I have no idea why, but a fix is a fix.