Try the fix described in this post - http://blogs.technet.com/b/dip/archive/2015/01/21/win2008r2-win7-stop-0xf4-during-task-sequence-os-deployment.aspx
This fixed my issues with being able to image a laptop model with 16GB of RAM using WinPE 5 x86. From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Wednesday, March 11, 2015 10:49 AM To: [email protected] Subject: [mssms] RE: Sporadic issues imaging PCs with more than 16 GB of RAM Yep, had tickets with Microsoft and everything. X64 is the only known fix, the issue is DISM. I have not tested the 8.1 update ADK to see if that resolves it. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael Gouldthorp Sent: Tuesday, March 10, 2015 11:40 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Sporadic issues imaging PCs with more than 16 GB of RAM I recently captured a new Windows 7 x64 image (using SCCM 2012 SP1 R2 CU2 on a Hyper-v VM) and now image fails to install on machines with 16 GB of RAM about 30% of the time. The systems will either Blue Screen (0x00000F4) or Black Screen. Systems with 8GB of RAM image without any problems whatsoever. >From the people I have talked to and the research I've done it sounds as >though I should use the x64 boot image (which appears to work in my >preliminary testing) . I'm just confused why this is an issue now and why the >issues itself is intermittent. Has anyone run into similar issues imaging systems with large amounts of RAM? Thanks, Mike Gouldthorp System Engineer II Sub-Zero Group, Inc. 608.271.2233 | subzero-wolf.com<http://www.subzero-wolf.com/> 2866 Buds Drive Fitchburg, WI 53719 [Description: Description: cid:[email protected]] The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
