CPU-caused Windows failure

The author of the management of the room has a computer failure, the screen appears as follows:

An internal stack overflow has caused the session to is halted change STACKS setting in your CONFIG. SYS file and then try again see this phenomenon, the author thought of the hard disk protection card. In the past, some machines have similar faults, so long as the hard disk protection card is unloaded, the system can start normally. But this time, even if the protection card is unplugged, the fault still remains. According to the ScreenTip, the system should be corrupted and windows will need to be reinstalled. For a variety of reasons, the system sometimes can not detect the hard disk protection card, then there will be protection failure, system damage is also possible.

Immediately with the protection card with the network copy program to update the system, after the update is complete, the restart failure is still.

Try booting to Safe mode, and the following prompts appear during startup:

ERROR:HIMEM.SYS has detected unreliable XMS memory at Adderss 00242b9a

XMS Driver not installed

To continue starting your computer, press ENTER

After the carriage return, the screen prompts "HIMEM." SYS is missing ", system deadlock. See Himem.sys does not load correctly, suspected memory problems, recall the boot process saw a short screen, because it is a shared system memory integrated graphics card, more convinced that there is memory problems. However, after the memory has been replaced, the problem has not been resolved, and the replaced memory is completely normal on the other machine.

Restore the previously backed up image files with ghost, then minimize the hardware, and the CMOS discharge, call the most conservative security defaults, all kinds of measures have failed, the author into confusion. Finally decided to format the C disk, and reinstall the system, in the installation process unexpectedly encountered failure.

Hard drive failure? But the system does not suggest that the hard drive has bad way, will not have the CPU problem? Try. Replace the same model of the CPU, boot to DOS mode, and restore the backup with Ghost, reboot, all normal! Instead of the original CPU of another computer, but there are the same fault phenomenon.

The truth is that the CPU is the cause of Windows failure. Suspicion is a cache failure, the author has shut down the CPU secondary cache, the fault is still, it seems that the CPU is dead.