we have a password for PXE.   We F12 a machine, PXE works.  We are prompted with the PXE password, enter the password and the task sequence fails right away.    This error is shown.  

Now, what is very odd is we have not made any changes to our CM2012 environment for a long time.   And, I can build OSD machines from different sites.

we have 1 primary site server in building 1

we have 8 different DPs in eight different buildings.

In building 1 we have our data center and in our data center we have vSphere.   Within vSphere I can build new machines using OSD and vSphere pulls its images from our Primary site server in building 1

I can built OSD images from different buildings.

yet physical machines in building 1 will not build.

what on earth can cause that?  

Have you already examined smsts.log?

No, but we did need to examine the brain of the fool doing the build !!   I had added a new task sequence for USMT (Torsten, you replied to that post of mine as well).  Well the USMT (Testing) task sequence appeared BEFORE our Windows 7 Build task sequence and this this moron was inaccurate with his assessment and it turns out he was just pressing ENTER at the task sequence window never noticing there was a new item.  So the USMT still does not work and yes, it comes and goes really fast.  We are in separate buildings so it makes it hard to troubleshoot.  Sorry for the false alarm.  

You really need to look at smsts.log and if you can post it here. Hit f8 and from here you should be able to launch cmtrace and view the log file. it should be in X:\WINDOWS\Temp\SMSTSLog. That error code is fairly generic in your screenshot and we need to try and narrow down where the issue is in the process to see if we can identify what is causing the error code. The log will help with this.