I have to take that back.  After adding the drivers it built correctly once.  
Every time after that I get the same BSOD.
I must have changed something else along the way.  I'll have to go over my 
notes and see what I did and when to try and find out what I inadvertently 
added to the mix.

Mike


From: [email protected] [mailto:[email protected]] On 
Behalf Of Marable, Mike
Sent: Monday, August 10, 2015 2:51 PM
To: [email protected]
Subject: RE: [MDT-OSD] Windows 10 64bit + HP z620

Yep, that was it.  I added the drivers that HP had for Windows 10 on the z620 
and sure enough it worked.

Mike


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Keith Garner (Hotmail)
Sent: Monday, August 10, 2015 1:37 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [MDT-OSD] Windows 10 64bit + HP z620

98% of blue screen issues are caused by bad drivers. Your next step is the 
correct way forward.
Next, look to see if Windows wrote a dmp file to the machine and debug to find 
the culprit.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Marable, Mike
Sent: Monday, August 10, 2015 8:03 AM
To: '[email protected]' 
<[email protected]<mailto:[email protected]>>
Subject: [MDT-OSD] Windows 10 64bit + HP z620

I'm coming to my wits end with a problem deploying 64bit Windows 10 to our HP 
machines, specifically the z620 workstation and Elitebook 1040.  I'm using SCCM 
2012 R2 + MDT 2013 (with the DISM steps to make it work with Windows 10).

After the image comes down and it attempts to boot into the OS for the first 
time the machine will "blue screen", the ":( Something went wrong...." Screen 
stating a "CRITICAL_PROCESS_DIED".  Attempts to boot into Safe Mode, or 
disabling driver signing, or any of the F8 boot options also trip the failure.

Using the same task sequence to install the 32bit version of Windows 10 works 
successfully.
Using the same task sequence to install the 64bit version of Windows 10 on a 
Hyper-V virtual machine works successfully.

I've tried it both with and without an unattended XML and still get the failure.
I've tried it without any 3rd party drivers and get the failure.
I've tried multiple z620s and they all fail the same way.
I've reset the BIOs to the default factory settings and still get the failure.

I'm next going to try using the Windows 10 specific drivers that HP has for the 
z620.

Am I so deep that I'm missing something simple?

Mike Marable
Application Programmer/Analyst Lead
Enterprise Device Engineering and Management
MCSE, MCTS, MCITP, MCSA, MS  
[Profile<http://www.mycertprofile.com/Profile/5319166625>] 
[Blog<http://thesystemsmonkey.wordpress.com/>]
--------------------------------------------
"The difficult we do at once. The impossible takes a little longer."
-US Army Corps of Engineers

"It is better to have less thunder in the mouth and more lightning in the hand."
-Apache Proverb

I will rise when I have fallen.

"Unless you try to do something beyond what you have already mastered, you will 
never grow."
-Ralph Waldo Emerson





**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues

**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues
**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues 

Reply via email to