Reinstall of XP Pro restarts at start of GUI

  • Thread starter Thread starter David Richardson
  • Start date Start date
D

David Richardson

I had a problem w/ my XP Pro SP1 install, so I reinstalled "in place" from
the SP1 CD (i.e. not a clean install).

When install's GUI phase starts, the mouse cursor appears and turns into a
"wait" cursor for a few seconds, then the machine reboots. I never see
the normal status screen of the GUI phase.

I've tried re-doing the "in place" install several times, to no avail.
I've searched through USENET and the Microsoft web site and tried several
suggestions, none of which helped.

I can boot the machine to another partition, but would really like to get
this install up and running.

I'm at a loss to try to figure this out. Any help is appreciated.

-David Richardson, davidwr.geo -at- yahoo.com
 
David said:
*I had a problem w/ my XP Pro SP1 install, so I reinstalled "i
place" from
the SP1 CD (i.e. not a clean install).

When install's GUI phase starts, the mouse cursor appears and turn
into a
"wait" cursor for a few seconds, then the machine reboots. I neve
see
the normal status screen of the GUI phase.

I've tried re-doing the "in place" install several times, to n
avail.
I've searched through USENET and the Microsoft web site and trie
several
suggestions, none of which helped.

I can boot the machine to another partition, but would really like t
get
this install up and running.

I'm at a loss to try to figure this out. Any help is appreciated.

-David Richardson, davidwr.geo -at- yahoo.com *


Are you getting a blue screen at all and then its reboots? You
scenario is exactly the same as mine, except that I'm getting a blu
screen for a split second after the splash screen and then it reboot
into the cycle.

Davi


-
dizz
 
Are you getting a blue screen at all and then its reboots? Your
scenario is exactly the same as mine, except that I'm getting a blue
screen for a split second after the splash screen and then it reboots
into the cycle.

Yes, the same minus the blue screen - my screen is still black when it
reboots.

I read your post Re: Setup <[email protected]> and yes, I too
get the "Setup encountered an error while trying to set system security.

An extended error has occurred."
error in setuperrlog.txt.

However, I've stopped getting these errors. I think the last time I got it
was after my first boot after the GUI yesterday, when it blue-screened
when making the device driver table. I don't remember the blue-screen
error message, but it was a STOP. I'd LOVE to see this message again.

Some other details:
1) I'm using a CD w/ XP Pro SP1 slipstreamed, OEM version.
2) It's the same CD I installed w/ originally.
3) I did make one change - I deleted \pagefile.sys and \hiberfil.sys
from the root of the drive after the problems started, that could have
exasperated things.

I do NOT have a Gateway.

Is your scenario still like mine?

-David Richardson, davidwr.geo -at- yahoo.com
 
David said:
*On Thu, 20 May 2004 17:47:00 -0500, dizz


Yes, the same minus the blue screen - my screen is still black whe
it
reboots.

I read your post Re: Setup <[email protected]> and yes,
too
get the "Setup encountered an error while trying to set syste
security.

An extended error has occurred."
error in setuperrlog.txt.

However, I've stopped getting these errors. I think the last time
got it
was after my first boot after the GUI yesterday, when i
blue-screened
when making the device driver table. I don't remember th
blue-screen
error message, but it was a STOP. I'd LOVE to see this messag
again.

Some other details:
1) I'm using a CD w/ XP Pro SP1 slipstreamed, OEM version.
2) It's the same CD I installed w/ originally.
3) I did make one change - I deleted \pagefile.sys and \hiberfil.sys
from the root of the drive after the problems started, that coul
have
exasperated things.

I do NOT have a Gateway.

Is your scenario still like mine?

-David Richardson, davidwr.geo -at- yahoo.com *


I too am using a XP Pro with SP1 with it on CD. I can't find an erro
log or anything stating what the blue screen error is.. I'm assumin
its a service or driver error.. but I can't be sure. Its driving m
nuts! I've tried reinstalling XP about 5 times now, and it doesn't fi
the problem. I'm almost to the point of just installing it on
different partition, then backup my data off C: and back everything of
and start over again.

Davi


-
dizz
 
I too am using a XP Pro with SP1 with it on CD. I can't find an error
log or anything stating what the blue screen error is.. I'm assuming
its a service or driver error.. but I can't be sure. Its driving me
nuts! I've tried reinstalling XP about 5 times now, and it doesn't fix
the problem. I'm almost to the point of just installing it on a
different partition, then backup my data off C: and back everything off
and start over again.

Did you make any alterations to the broken installation, like removing
\pagefile.sys and \hiberfil.sys? I'd like to rule out any changes I made
as the underlying cause.

By the way, I searched the net for "setup encountered an error while
trying to
set system security" and found several others with similar problems, both
on the web and in USENET.

I'm working with my computer manufacturer's tech support on this, I'll post
a followup. I'm seriously considering giving MS $35 to help me solve it,
but I'm concerned they'll call it a "hard issue" and charge $200+.

If you find a solution, please post it here, so others can see it.
I'll do the same.

-David Richardson, davidwr.geo -at- yahoo.com
 
Yes, the same minus the blue screen - my screen is still black when it
reboots.

I read your post Re: Setup <[email protected]> and yes, I too
get the "Setup encountered an error while trying to set system security.

An extended error has occurred."
error in setuperrlog.txt.

However, I've stopped getting these errors. I think the last time I got
it
was after my first boot after the GUI yesterday, when it blue-screened
when making the device driver table. I don't remember the blue-screen
error message, but it was a STOP. I'd LOVE to see this message again.

Some other details:
1) I'm using a CD w/ XP Pro SP1 slipstreamed, OEM version.
2) It's the same CD I installed w/ originally.
3) I did make one change - I deleted \pagefile.sys and \hiberfil.sys
from the root of the drive after the problems started, that could have
exasperated things.

I do NOT have a Gateway.

Is your scenario still like mine?

Below is a slightly-edited version of what I sent to my PC
maker's tech support people:

=====cut here=====

Additional information:
\windows\system32\config\system.evt had a message that said the
manifest file
\windows\winsxs\manifests\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a.Manifest
was corrupt. Sure enough, it was a 2K file of all binary-0's.
After backing it up, I deleted it.

I am now back to where I was the first time I tried the "recovery
install" a couple days ago, namely: a BAD_POOL_ERROR.

Here's what happened after I deleted the corrupt commmon-controls
manifest file:

I inserted the Windows XP SP1 CD and rebooted. I did NOT "hit any key
to boot to the CD." The hard disk booted and I booted the Windows XP
Pro partition. It entered phase 2 of the install, as I expected it to.
It did NOT reboot (hooray!).
It said there were 39 or so minutes remaining in the installation.
The progress bar progressed, and it said it was doing something with
drivers or something like that.
When the progress bar was at or near completion, I got the dreaded
blue screen of death, same as a few days ago.

Here's the relevant info from the blue screen of death:
BAD_POOL_CALLER
STOP: 0X000000C2 (0X00000007 0X00000CD4 0X020C0008 0X851F4ABD)

After rebooting to the XP Home partition, I did some post-analysis.
Unfortunately, I do not have a memory dump (I tried adding one to
the XP Pro's "system" registry hive, but there is no
"currentcontrolset" entry in that hive, and the ControlSet001
entry is already configured for a memory dump).

The common-controls manifest that was previously deleted was
recreated and appears to be OK. It is an XML file.

HOWEVER, \windows\system32\config\system.evt now has a
different error message in it. Here is the file cut-and-pasted
from Notepad. Please forgive the spaces, ?'s, and other garbage
characters, I think the original file was in Unicode. My
Newsreader will corrupt some of the system.evt file, but
the text part is the only important part. If you need
the full file, email me.

-------cut here, begin \windows\system32\config\system.evt -----
0 LfLe  0 0    ?: 0 $
LfLe ?v?@?v?@ ?  ` `  S i d e B y
S i d e D A V I D W R 3 M i c r o s o f t . W i n d o w s .
C o m m o n - C o n t r o l s T h e r e f e r e n c e d
a s s e m b l y i s n o t i n s t a l l e d o n
y o u r s y s t e m .

$ ? LfLe ?v?@?v?@y ?  \ \
? E v e n t L o g D A V I D W R 3 5 . 0 1 . 2 6 0 0
S e r v i c e P a c k 1 U n i p r o c e s s o r
F r e e ? d LfLe ?v?@?v?@u ? \
\ \ E v e n t L o g D A V I D W R 3 d T
LfLe ?v?@?v?@; ?  ` ` N
S i d e B y S i d e D A V I D W R 3 R e s o l v e
P a r t i a l A s s e m b l y M i c r o s o f t .
W i n d o w s . C o m m o n - C o n t r o l s T h e
r e f e r e n c e d a s s e m b l y i s n o t
i n s t a l l e d o n y o u r s y s t e m .

T ? LfLe nv?@?v?@ @  y A X
( Z T c p i p 6 D A V I D W R 3  V 
@ S e c u r i t ? ? LfLe
nv?@?v?@? ?  y A V ( X N e t B T
D A V I D W R 3  X ? ?  ?
S e c u r i t ? ? ? LfLe nv?@?v?@? ?  y A
V ( X N e t B T D A V I D W R 3 
X ? ?  ? S e c u r i t ? ? ?
LfLe w?@w?@? ?  y A V ( X N e t B
T D A V I D W R 3  X ? ? 
? S e c u r i t ? ? ? LfLe w
?@w?@? ?  y A V ( X N e t B T
D A V I D W R 3  X ? ?  ?
S e c u r i t ? ? ? LfLe
-w?@-w?@? ?  y A V ( X N e t B T
D A V I D W R 3  X ? ? 
? S e c u r i t ? ? ? LfLe
-w?@-w?@? ?  y A V ( X N e t B T
D A V I D W R 3  X ? ? 
? S e c u r i t ? ? ( """"3333DDDD0 ? 
(




-------cut here, end \windows\system32\config\system.evt -----

=====cut here=====

Does anyone know how I can force a memory dump, and does anyone
know what SideBySide is? I'll be researching both after
posting this note.
 
Summary:
I had to do a "recovery" install of MS Windows XP SP1 (OEM).
I was getting a blue-screen-of-death (BSOD) with the following:
BAD_POOL_CALLER
STOP: 0X000000C2 (0X00000007 0X00000CD4 0X020C0008 0X851F4ABD)
near the end of the configuring-devices section of phase 2 (the GUI
phase) of the install.

Solution:
The following products were installed on the system before it crashed.
Removing the *.sys files from \windows\system32\drivers and related
files from \windows\system32 for ALL of these products allowed the
install to complete. I restored the files and rebooted and my system is
happy.
McAfee Internet Security Suite 2004 (only the Personal Firewall Plus
5.0.15 component was installed).
Computer Associates Easy AntiVirus (the free-for-1-year-version that is
mentioned on the Microsoft Windows Update web page)
MediaFour MacDrive 5.0.13.

Details follow the quoted bits from earlier in the thread.

David said:
Below is a slightly-edited version of what I sent to my PC
maker's tech support people:

=====cut here=====

Additional information:
\windows\system32\config\system.evt had a message that said the
manifest file
\windows\winsxs\manifests\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a.Manifest

was corrupt. Sure enough, it was a 2K file of all binary-0's.
After backing it up, I deleted it.

I am now back to where I was the first time I tried the "recovery
install" a couple days ago, namely: a BAD_POOL_ERROR.

Here's what happened after I deleted the corrupt commmon-controls
manifest file:

I inserted the Windows XP SP1 CD and rebooted. I did NOT "hit any key
to boot to the CD." The hard disk booted and I booted the Windows XP
Pro partition. It entered phase 2 of the install, as I expected it to.
It did NOT reboot (hooray!).
It said there were 39 or so minutes remaining in the installation.
The progress bar progressed, and it said it was doing something with
drivers or something like that.
When the progress bar was at or near completion, I got the dreaded
blue screen of death, same as a few days ago.

Here's the relevant info from the blue screen of death:
BAD_POOL_CALLER
STOP: 0X000000C2 (0X00000007 0X00000CD4 0X020C0008 0X851F4ABD)

Details:

Digging around with a debugger (it's nice to have 2 machines) I got a
list of loaded device drivers (One of Microsoft's web pages has
instructions on diagnosing BAD_POOL_CALLER stops, and it shows how to
get the list of loaded modules, among other useful things. Search for it.).

I compared this list to the list of drivers on a parallel installation
of windows (it's nice to have lots of disk space) on another partition
of the same machine.

I then checked the "Company" for each of these modules, and made a note
of those NOT made my Microsoft.

The companies represented included
McAfee Security
Network Associates Technology, Inc. (which is related to McAfee)
Computer Associates
MediaFour Corproation
and PowerQuest

Using "details view" of windows explorer and by using the "view->choose
details" pull-down menu I sorted \windows\system and
\windows\system32\drivers by company. I then moved all files made by
these 5 companies to a temporary location.
I then removed \windows\inf\infcache.1 and rebooted.
The install completed successfully.

Hoping to narrow down the culprit, I took one company's files and
restored them and rebooted, and repeated with each company. The system
always rebooted successfully, so I do not know which files were the problem.

I then ran windows update and rebooted. My system is now stable and, as
far as I can tell, back to the way it was.

Here is a list of files that I had to move out of the way, along with
the directory, the company, and the file version. Note that the real
culprit is probably a *.SYS file, I moved the rest away just to avoid
confusion.

Computer Associates (RealTime Anti-Virus Protection Driver):
\windows\system32\VetMsgNT.1 (no version)
\windows\system32\VetMsgNT.exe 1.1.0.1
\windows\system32\drivers\Vet-Filt.sys 10.54.0.12
\windows\system32\drivers\Vet-Rec.sys 10.54.0.12
\windows\system32\drivers\VetFDDNT.sys 10.59.2.0
\windows\system32\drivers\VetMonNT.sys 10.54.0.12

McAfee Security (McAfee Personal Firewall Plus 5.0)
\windows\system32\MpfApi.dll 5.0.5.1
\windows\system32\drivers\MpFirewall.sys 5.0.1.7

Network Associates Technology, Inc. (grouped with McAfee):
\windows\system32\mcinsctl.dll 4.0.0.74

MediaFour Corporation (HFS/HFS+ FSD for Windows NT/2000/XP):
\windows\system32\MACDRAPI.DLL 5.0.7.3
\windows\system32\MDPROPS2.CPL (no version)
\windows\system32\drivers\MDFSYSNT.SYS 5.0.13.0
\windows\system32\drivers\MDPMGRNT.SYS 5.0.13.0

PowerQuest (XMNT2002)
\windows\system32\XMNT2002.exe 8.0.0.0
PowerQuest (PQIMount.sys - PQI Image Mounting Device Driver)
\windows\system32\drivers\PQIMount.sys 2.1.0.309
PowerQuest (PowerQuest Boot Mode Driver.)
\windows\system32\drivers\PQNTDRV.sys 8.0.0.0

I'm posting my experience in the hopes that if anyone else has a similar
problem, they can save a lot of time.

David Richardson
davidwr.geo -at- yahoo.com
 
Back
Top