PXE Deploy Fails - BCD Error 0xc98

Question

When I attempt to PXE boot any machine, physical or virtual, I get an error message, the pertinent details are:
"Recovery - Your PC needs to be repaired
File: \Tmp\x86x64{GUID}.bcd
Error code: 0xc0000098"
DHCP Options were set as follows:
066: CMDP (the name of the stand-alone DP)
067: SMSboot\x64\wdsnbp.com
One of the most bizarre facts is that I was able to run a PXE install one time and then the next day, the system displayed this error.
Here are some steps I have tried to resolve the issue:
Removed and Rebuilt the DP on the Primary Site (now removed completely).
Built a stand-alone DP on Server 2012 R2 in vmware vcenter 5 and configured it for PXE boot.
Restarted the server after confirming WDS was installed and it appears to be running correctly.
Verified all content was being distributed correctly and ensured boot images were set for PXE deploy.
Installed ADK 8.1 Update, built new Boot Images and distributed them to the DP.
Rebuilt the PXE Task Sequence using both x86 and x64 Boot Images.
Changed DHCP option from x86 to x64 and back and forth.
Ensured the SCCM Admin was explicitly added to the DP as a local admin.
Made sure all SMS folders on the DP are shared to everyone with read priv's and the SMSBoot folder location was shared to allow the DHCP options to connect to the correct network path.
Resintalled the ConfigMgr Console on the site server and my tech machine.
Updated SCCM to R2 CU3.
Read dozens of similar forum posts.
Cried a little.
The SMSPXE log on the Primary Site is no longer being updated since building the new DP. Don't know which logs to check or where they would be!
I am getting close to full reinstall of SCCM -- which I really don't want to do -- but I'm running out of forum posts to follow!! Can you help me stop bashing my head against a wall - it's starting to hurt.

Answer 1

Based on a similar thread, I traced the issue back to the MP.
Severity    Type    Site code    Date / Time    System    Component    Message ID    Description
Error    Milestone    GBT    11/4/2014 2:52:31 PM    XXXX.XXX.LOCAL    SMS_MP_CONTROL_MANAGER    5436    MP Control Manager detected management point is
not responding to HTTP requests.  The HTTP status code and text is 500, Internal Server Error.    Possible cause: Management point encountered an error when connecting to SQL Server.   Solution: Verify that the SQL Server is properly
configured to allow Management Point access. Verify that management point computer account or the Management Point Database Connection Account is a member of Management Point Role (msdbrole_MP) in the SQL Server database.    Possible cause: 
The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory  Solution:  Ensure SQL Server SPNs are correctly registered.  Review Q829868.    Possible cause: Internet Information Services (IIS)
isn't configured to listen on the ports over which the site is configured to communicate.   Solution: Verify that the designated Web Site is configured to use the same ports which the site is configured to use.    Possible cause: The
designated Web Site is disabled in IIS.   Solution: Verify that the designated Web Site is enabled, and functioning properly.    Possible cause: The MP ISAPI Application Identity does not have the requisite logon privileges.  
Solution: Verify that the account that the MP ISAPI is configured to run under has not been denied batch logon rights through group policy.    For more information, refer to Microsoft Knowledge Base article 838891.