Microsoft already has resources in place designed to help end users troubleshoot a Stop 0x0000007E error in Windows XP, and there are additional causes to implementing Service Pack 3 that may conduct to this scenario.Still, this does not mean that XP SP3 is off the hook.The problem Windows XP Service Pack 1 (SP1) Sysprep image is created on an Intel-processor-based computer and if the Sysprep image is then deployed on a non-Intel-processor-based computer.Under this configuration, after the computer is upgraded to Windows XP SP2 or SP3, the Intel processor driver (Intelppm.sys) may try to load because an orphaned registry key remains from the original Sysprep image," Microsoft said.
In response, Microsoft published Knowledge Base article 888372 detailing the issue.
Users looking to Service Pack 3 for Windows XP, as Service Pack 2's second coming and the perfect reason to avoid Windows Vista SP1, might need to reconsider their plans.
The reason is rather simple, despite the fact that it has spent over two months more time in development compared to Vista SP1, while containing only a minor, standard evolution in comparison to SP2, XP SP3 has come to the table with a flood of issues, a wide variety of them impacting the deployment process.
But at the same time this is also valid for original XP SP2 and XP SP3 Sysprep images that have been built on an Intel-processor-based machine, only to be subsequently deployed onto computer powered by a processor which is not from Intel. Apparently all it takes is a registry tweak in order to resolve the problem.
The end users first have to reboot their machine into Safe Mode and then make their way in the registry to HKEY_LOCAL_MACHINE - SYSTEM - Control Set001 - Services - Intelppm and then modify the Value data by entering 4 in the box.