Stop: 0x0000007e blue screen Software Fault Handling example

When a non-Intel processor computer ghost is used, a blue screen crashes after the computer is restarted. the following error message is displayed after the blue screen:

A problem has been detected and Windows has been shut down to prevent damage to your computer...

Technical information:

* ** Stop: 0x0000007e (0xc0000005, 0xf87e6750, 0xf8a5430, 0xf8a8512c) system_thread_exception_not_handled
Note: • depending on the computer's system failure settings, the results of the STOP error message may be different.
• The four parameters in the brackets of the technical information in the Stop error message may be different, depending on the computer configuration. However, for this particular instance, the first parameter will always be c0000005.
• Not all "Stop 0x0000007e" error messages are caused by the problems described in this article.

For more information about how to solve the "Stop 0x0000007e" error, click the following article number to view the article in the Microsoft Knowledge Base:
"Stop 0x0000007e" error message appears after 330182 (http://support.microsoft.com/kb/330182/) is upgraded to Windows XP

Cause
Most computers contain images created by manufacturers by using the system preparation tool (sysprep. Sysprep enables computer manufacturers to generate images that can be used on different computers. If the original Windows XP Service Pack 1 (SP1) sysprep image is created on an Intel processor-based computer and then the sysprep image is deployed on a non-Intel processor-based computer, the problem described in the "Symptom" section may occur. In this configuration, after the computer is upgraded to Windows XP SP2, the intel processor Driver (intelppm. sys) may be loaded because the isolated registry key is still from the original sysprep image ).

This problem may also occur if the original Windows XP SP2 sysprep image was created on an Intel processor-based computer and then deployed on a non-Intel processor-based computer. Likewise, since the isolated registry entries are still from the original sysprep image, you may try to load the Intel processor Driver (intelppm. sys ).

For more information about the unsupported solution when deploying a sysprep image on a target computer with a vendor processor different from the original image-based Processor, click the following article number, to view the articles in the Microsoft Knowledge Base:
828287 (http://support.microsoft.com/kb/828287/) unsupported sysprep Scheme

Solution
Warning improper use of Registry Editor may cause serious problems and you may need to reinstall the operating system. Microsoft cannot guarantee that you can solve problems caused by improper use of the Registry Editor. You are at your own risk to use the Registry Editor.

To solve this problem, follow these steps:

1. restart the computer in safe mode.

For more information about the security mode in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
315222 (http://support.microsoft.com/kb/315222/) Description of safe mode startup options in Windows XP
2. Click Start, click Run, type regedit, and click OK ".
3. Locate and click the following registry key:
HKEY_LOCAL_MACHINE/system/controlset001/services/intelppm
4. In the right pane, right-click the start item and click Modify ".
5. In the value data box, type 4 and click OK ".
6. Exit the Registry Editor.
7. restart the computer.

The premise is that you can enter the safe mode. If you cannot, you can mount the hard disk to an Intel chip workstation, change the Registry, and then connect to the workstation.