Latitude E7450 Crashing in PE Environment
My company just recently ordered a number of Latitude E7450 laptops and tasked me with pushing a company image to them.
We already have MDT 2012 running on a 2012 server, that we use to successfully deploy images to all of our other dell computers (including the E7440). However, after loading the drivers for the system into Drivers section of the deployment workbench and updating the deployment share, I am getting a Windows 8 BSOD type error. The PXE boot picks up successfully, and it loads the PE .WIM, but just before it brings up the task selection screen it blue screens (I actually see the PE desktop background for just a second before crash).
As usual it says, "The PC ran into a problem and needs to restart. We're just collecting some error info, and then you can restart. (0% complete)". Below it says 'If you'd like to know more, you can search online later for this error: SYSTEM_EXCEPTION_NOT_HANDL
The problem is that the BSOD dump never gets to 1%, much less completes the data collection, so I have no way to look at any log files to try and figure out what is causing the problem. Does anyone have any ideas as to how I might be able to force it to complete the log dump? Or failing that, an alternate method of making it dump to a secondary remote location so that I can see if it is actually dumping and not moving the progress bar?
Thanks,
Damon M.
We already have MDT 2012 running on a 2012 server, that we use to successfully deploy images to all of our other dell computers (including the E7440). However, after loading the drivers for the system into Drivers section of the deployment workbench and updating the deployment share, I am getting a Windows 8 BSOD type error. The PXE boot picks up successfully, and it loads the PE .WIM, but just before it brings up the task selection screen it blue screens (I actually see the PE desktop background for just a second before crash).
As usual it says, "The PC ran into a problem and needs to restart. We're just collecting some error info, and then you can restart. (0% complete)". Below it says 'If you'd like to know more, you can search online later for this error: SYSTEM_EXCEPTION_NOT_HANDL
The problem is that the BSOD dump never gets to 1%, much less completes the data collection, so I have no way to look at any log files to try and figure out what is causing the problem. Does anyone have any ideas as to how I might be able to force it to complete the log dump? Or failing that, an alternate method of making it dump to a secondary remote location so that I can see if it is actually dumping and not moving the progress bar?
Thanks,
Damon M.
ndis.sys has to do with networking, so it could be an issue of the LAN driver.
ASKER
I can try and see if there are other network drivers available, but I already have the Windows 7 Deployment driver pack.
I'll let you know if I find anything.
I'll let you know if I find anything.
ASKER
No good. Downloaded the PE driver pack, imported into the PE boot image in Deployment Services, but it is still failing at the same point.
Anyone have any ideas for getting a log off of this thing? I seem to remember there was a way to copy any logs to a non-local path, but I can't seem to find the command now.
Anyone have any ideas for getting a log off of this thing? I seem to remember there was a way to copy any logs to a non-local path, but I can't seem to find the command now.
You only want to add driver support to WinPE that is absolutely necessary. Adding a "driver pack" to WinPE is generally not a good idea, because by the sounds of it WinPE is picking up a driver with the same PnPID, but it's the wrong one.
What I would do is install MDT 2012 on a fresh box, the copy out the WinPE from that install and overwrite your WinPE. Under the WinPE build section where to add drivers, make a selection profile and build out the folder structure. Only add NIC drivers if they are needed to this selection profile.
I used to run MDT 2010: now I run MDT 2013 with the "Total Control" method: http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management. This will require some work on your part, but I can tell you it's very worth it and a lot more predictable then just throwing all the drivers in one pile and hoping for the best.
What I would do is install MDT 2012 on a fresh box, the copy out the WinPE from that install and overwrite your WinPE. Under the WinPE build section where to add drivers, make a selection profile and build out the folder structure. Only add NIC drivers if they are needed to this selection profile.
I used to run MDT 2010: now I run MDT 2013 with the "Total Control" method: http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management. This will require some work on your part, but I can tell you it's very worth it and a lot more predictable then just throwing all the drivers in one pile and hoping for the best.
ASKER
I understand that drivers should be controlled and I am not just dumping them into a pile and letting the system sort it out.
But my question is about getting a log off of a crashing system so that I can see exactly what the issue is rather than rebuilding my entire driver setup to worm out one bad driver.
Anyone have any ideas on this?
But my question is about getting a log off of a crashing system so that I can see exactly what the issue is rather than rebuilding my entire driver setup to worm out one bad driver.
Anyone have any ideas on this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER