Microsoft KB Archive/888372

= You receive a “Stop 0x0000007E” error message after you upgrade to Windows XP Service Pack 2 on a non-Intel-processor-based computer =

Article ID: 888372

Article Last Modified on 5/16/2006

-

APPLIES TO


 * Microsoft Windows XP Service Pack 2
 * Microsoft Windows XP Service Pack 2

-





SYMPTOMS
After you upgrade a computer that uses a processor other than an Intel processor to Microsoft Windows XP Service Pack 2 (SP2), you may receive the following error message after you restart the computer:

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

Technical information:


 * STOP: 0x0000007E (0xC0000005, 0xFC5CCAF3, 0xFC90F8C0, 0xFC90F5C0) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Notes  The results of a Stop error message may vary according to the computer's system failure settings. The four parameters that are inside the parentheses of the technical information for the Stop error message can vary depending on the computer's configuration. However, for this particular instance, the first parameter will always be C0000005. Not all Stop 0x0000007E error messages are caused by the problem that is described in this article.

For additional information about how to troubleshoot Stop 0x0000007E errors, click the following article number to view the article in the Microsoft Knowledge Base:

330182 &quot;STOP 0x0000007E&quot; error message after you upgrade to Windows XP





CAUSE
Most computers include an image that the manufacturer created by using the System Preparation (Sysprep) tool. Sysprep lets the computer manufacturer generate an image that can be used on different computers. The problem that is described in the &quot;Symptoms&quot; section may occur if the original 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, the Intel processor driver (Intelppm.sys) may try to load because an orphaned registry key remains from the original Sysprep image.

This issue may also occur if the original Windows XP SP2 Sysprep image is created on an Intel-processor-based computer and if it is then deployed onto a non-Intel-processor-based computer. Again, the Intel processor driver (Intelppm.sys) may try to load because an orphaned registry key remains from the original Sysprep image.

For additional information about unsupported scenarios when you deploy a Sysprep image on a destination computer that has a different vendor's processor than what the original image is based on, click the following article number to view the article in the Microsoft Knowledge Base:

828287 Unsupported Sysprep scenarios

Note We do not support using Sysprep to install an operating system from an image if the image was created by using a computer that has a different processor. For example, you cannot create a Sysprep image on a computer that has an Intel processor and deploy the image to a computer that has an AMD processor.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Additional query words: windowsxp winxp blue screen bugcheck 0x7e 0x0000007E amd via transmetta

Keywords: kberrmsg kbtshoot kbsetup KB888372

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.