Why is SP2 crashing systems with XP already installed and working?

[Guest]

We have 2 Gateway systems:

System A:
Model: 300S LTD - Shipped w/XP Home edition installed
Ship Date: 11/27/2001

System B:
Model: PERFORMANCE 800 - Shipped w/ME installed and upgraded to XP Pro
Ship Date: 9/27/2000

Both sytems operate fully without errors or device conflicts.

They both cannot boot without a "blue screen" flash and loop until shut off
in reboot. The "blue screen" occurs after the spash screen for XP appears and
drivers are loading. The screen flashes so rapidly that the error code can
not be read.

We have tried a clean install on both systems with brand new hard drives and
slipstreaming the SP2 into the install CD.

System B can be statred in Safe Mode but can not run IE6 without errors.

What are we missing here?

 

[Guest]

That blue screen message will probably refer to some driver that is failing.
Start in Safe Mode and turn off the restart on error setting, or open the
Event Viewer to find the error. (run eventvwr.msc).

Press WinKey-Break,(or start/run 'sysdm.cpl'), click Advanced Tab, Start
Up... area, Settings button, Remove check from "Automatically Restart" On the
next reboot, you will be able to read the error that caused the restart.
Windows XP Restarts When You Try to Shut Down Your Computer (Q311806)
http://support.microsoft.com/support/kb/articles/q311/8/06.ASP

 

[Ron Martell]

We have 2 Gateway systems:

System A:
Model: 300S LTD - Shipped w/XP Home edition installed
Ship Date: 11/27/2001

System B:
Model: PERFORMANCE 800 - Shipped w/ME installed and upgraded to XP Pro
Ship Date: 9/27/2000

Both sytems operate fully without errors or device conflicts.

They both cannot boot without a "blue screen" flash and loop until shut off
in reboot. The "blue screen" occurs after the spash screen for XP appears and
drivers are loading. The screen flashes so rapidly that the error code can
not be read.

We have tried a clean install on both systems with brand new hard drives and
slipstreaming the SP2 into the install CD.

System B can be statred in Safe Mode but can not run IE6 without errors.

What are we missing here?

Open Control Panel - System - Advanced and click on the Settings
button in the Startup and Recovery (bottom) section. In the Startup
and Recovery window click on the checkbox for "automatically restart"
to clear it.

That should put an end to the reboots but you will likely still
received the Blue Screen Of Death error. However you can now read the
error message. Post the information, including the STOP code, all 4
parameters, and any file or module names mentioned back here.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[Guest]

Thanks Mark,

I was able to turn off the restart and this is the error that came up:

Stop: C0000221 Unknown Hard Error
\Systemroot\System32\ntdll.dll

 

[Guest]

"STOP: C0000221 unknown hard error" or "STOP: C0000221
STATUS_IMAGE_CHECKSUM_MISMATCH" error message occurs :
http://support.microsoft.com/kb/314474/en-us

There are several ways to repair a system with corrupt files. A Repair
setup, running SFC /SCANNOW, or maybe just using MSCONFIG.exe to 'expand
file' on the ntdll.dll.

 

[Enkidu]

"STOP: C0000221 unknown hard error" or "STOP: C0000221
STATUS_IMAGE_CHECKSUM_MISMATCH" error message occurs :
http://support.microsoft.com/kb/314474/en-us

There are several ways to repair a system with corrupt files. A Repair
setup, running SFC /SCANNOW, or maybe just using MSCONFIG.exe to 'expand
file' on the ntdll.dll.

They tried a clean install from an XP disk slipstreamed with SP2 (as I
read it). The PC came with ME, so could it be that they don't have the
correct XP video or motherboard drivers?

Cheers,

Cliff

 

[Guest]

First of all I was able to get System "B", that came from the factory with ME
installed,switched over to a new larger hard drive and more memory by using
Acronis and after several hours of reading as to why it came up with multiple
errors after cloning. I found that cloning needs to have preperation done to
work on new hardware installs. I found a great article explaining how to use
Sysprep to help Windows know what to do with the new hardware the cloned OS
sees.

Now on to System "A" that came installed with XP Home. Home installs perfect
with the restore disk on the new larger hard drive and more memory. The
problem as I stated before comes when SP2 is installed over the system
install (this is also true for a clean install n this system).

This time per the suggestions on this post I turned on the restart on error
so the error screen could be seen after installing SP2. I agree with Cliff
(Enkid0) that the problem is most likely a video or some hardware conflict
(made very obvious by the "STOP: C0000221 unknown HARD ERROR MISMATCH"
wording. The problem with Mark's suggestion of reading the log file or any
other option is that the SP2 install makes the entire system unable to get
into since it cannot be booted into the operating system via safe mode or any
other mode.

If you have any further suggestions on where I can discover clues to this
STOP: error I will be happy to explore further to help me and many others out
there trying to keep hardware from the dumps.

 

[Guest]

First of all I was able to get System "B", that came from the factory with ME
installed,switched over to a new larger hard drive and more memory by using
Acronis and after several hours of reading as to why it came up with multiple
errors after cloning. I found that cloning needs to have preperation done to
work on new hardware installs. I found a great article explaining how to use
Sysprep to help Windows know what to do with the new hardware the cloned OS
sees.

Now on to System "A" that came installed with XP Home. Home installs perfect
with the restore disk on the new larger hard drive and more memory. The
problem as I stated before comes when SP2 is installed over the system
install (this is also true for a clean install n this system).

This time per the suggestions on this post I turned on the restart on error
so the error screen could be seen after installing SP2. I agree with Cliff
(Enkid0) that the problem is most likely a video or some hardware conflict
(made very obvious by the "STOP: C0000221 unknown HARD ERROR MISMATCH"
wording. The problem with Mark's suggestion of reading the log file or any
other option is that the SP2 install makes the entire system unable to get
into since it cannot be booted into the operating system via safe mode or any
other mode.

If you have any further suggestions on where I can discover clues to this
STOP: error I will be happy to explore further to help me and many others out
there trying to keep hardware from the dumps.

 

[Guest]

First of all I was able to get System "B", that came from the factory with ME
installed,switched over to a new larger hard drive and more memory by using
Acronis and after several hours of reading as to why it came up with multiple
errors after cloning. I found that cloning needs to have preperation done to
work on new hardware installs. I found a great article explaining how to use
Sysprep to help Windows know what to do with the new hardware the cloned OS
sees.

Now on to System "A" that came installed with XP Home. Home installs perfect
with the restore disk on the new larger hard drive and more memory. The
problem as I stated before comes when SP2 is installed over the system
install (this is also true for a clean install n this system).

This time per the suggestions on this post I turned on the restart on error
so the error screen could be seen after installing SP2. I agree with Cliff
(Enkid0) that the problem is most likely a video or some hardware conflict
(made very obvious by the "STOP: C0000221 unknown HARD ERROR MISMATCH"
wording. The problem with Mark's suggestion of reading the log file or any
other option is that the SP2 install makes the entire system unable to get
into since it cannot be booted into the operating system via safe mode or any
other mode.

If you have any further suggestions on where I can discover clues to this
STOP: error I will be happy to explore further to help me and many others out
there trying to keep hardware from the dumps.