Hi, I have Windows XP installed. The computer keeps restarting over and over
again. Sometimes it will go to the Select Startup Mode, but it will not start
in any mode, tried them all. I am able to start the Recovery Console and go
to the C:\Windows prompt, but I don't know what to do from here. I have
reinstalled the Kernel32.dll Actually got to see the Windows startup screen.
But that only happened once. Any help would be appreciated. Thank you

"Kathy" <Kathy@discussions.microsoft.com> wrote in message
news:98070B53-CE1B-40A7-AF3D-2F401219BBF3@microsoft.com...
> Hi, I have Windows XP installed. The computer keeps restarting over and
> over
> again. Sometimes it will go to the Select Startup Mode, but it will not
> start
> in any mode, tried them all. I am able to start the Recovery Console and
> go
> to the C:\Windows prompt, but I don't know what to do from here. I have
> reinstalled the Kernel32.dll Actually got to see the Windows startup
> screen.
> But that only happened once. Any help would be appreciated. Thank you

There are a lot of things that _could_ cause this. Bad mainboard, memory,
overheating of the CPU, corrupted operating system, and viruses. You may be
able to start narrowing the problem however. Go to Start > Settings >
Control Panel > double click "System" icon > click "Advanced" tab. Click the
"Settings" button under "Startup and recovery". Under "System Failure"
uncheck the "Automatically restart" checkbox and check the "Write an event
to the system log". You can now start to find the problem.

To read events (e.g., errors, warnings) go to Start > Settings > Control
Panel > double click "Administrative Tools" icon > double click "Events
Viewer". In the left hand pane select "System". In the right hand pane you
can select and view any event with a warning or error. If you find one or
more post the info here.

Mark

"Kathy" <Kathy@discussions.microsoft.com> wrote
> Hi, I have Windows XP installed. The computer keeps restarting over and
> over
> again. Sometimes it will go to the Select Startup Mode, but it will not
> start
> in any mode, tried them all. I am able to start the Recovery Console and
> go
> to the C:\Windows prompt, but I don't know what to do from here. I have
> reinstalled the Kernel32.dll Actually got to see the Windows startup
> screen.
> But that only happened once. Any help would be appreciated. Thank you

How far does it go before restarting? What is the history of this problem?
What changes were made to the system right before this problem surfaced?
What is the computer and it's configuration?

--
Rock [MS-MVP User/Shell]

Thanks Mark, but the computer won't start.

"Mark F." wrote:

>
> "Kathy" <Kathy@discussions.microsoft.com> wrote in message
> news:98070B53-CE1B-40A7-AF3D-2F401219BBF3@microsoft.com...
> > Hi, I have Windows XP installed. The computer keeps restarting over and
> > over
> > again. Sometimes it will go to the Select Startup Mode, but it will not
> > start
> > in any mode, tried them all. I am able to start the Recovery Console and
> > go
> > to the C:\Windows prompt, but I don't know what to do from here. I have
> > reinstalled the Kernel32.dll Actually got to see the Windows startup
> > screen.
> > But that only happened once. Any help would be appreciated. Thank you
>
> There are a lot of things that _could_ cause this. Bad mainboard, memory,
> overheating of the CPU, corrupted operating system, and viruses. You may be
> able to start narrowing the problem however. Go to Start > Settings >
> Control Panel > double click "System" icon > click "Advanced" tab. Click the
> "Settings" button under "Startup and recovery". Under "System Failure"
> uncheck the "Automatically restart" checkbox and check the "Write an event
> to the system log". You can now start to find the problem.
>
> To read events (e.g., errors, warnings) go to Start > Settings > Control
> Panel > double click "Administrative Tools" icon > double click "Events
> Viewer". In the left hand pane select "System". In the right hand pane you
> can select and view any event with a warning or error. If you find one or
> more post the info here.
>
> Mark
>
>
>

Hi Rock
It's an older computer with 20gig hard disk drive, only had 250meg memory
but I have added another stick today. Win XP Pro with SP2 included was
installed about 12 months ago. The machine had a virus in Jan this year but
that has been cleaned. I have just done a Norton boot/virus scan and I am
doing what used to be called a scandisk at the moment.
The machine will boot to the menu for Startup Choices i.e. Safe Mode, etc
etc. It doesn't matter which one I choose, it goes through the files until it
gets to mup. (sorry I have momentarily forgotten the extension) stops for
ages and then restarts. Sometimes it will go to the Windows Splash screen,
then the screen that checks your drive for errors will appear for about one
second and the computer restarts.
I think the last installation was Skype. But the computer was a bit dodgy
before, that is - restarting without warning, not often but occassionally.
Someone suggested the power supply might be on its way out, however the
machine has been in what is basically the Dos mode for about 4 hours now
without looking like restarting.
So I am thinking that a vital piece of the Windows Startup software may have
become corrupted. I just don't know how to fix it without reinstalling WinXP.
I have tried the Windows Rescue (or startup) disks, but same problem.
Thank you for any assistance, Kathy

"Rock" wrote:

> "Kathy" <Kathy@discussions.microsoft.com> wrote
> > Hi, I have Windows XP installed. The computer keeps restarting over and
> > over
> > again. Sometimes it will go to the Select Startup Mode, but it will not
> > start
> > in any mode, tried them all. I am able to start the Recovery Console and
> > go
> > to the C:\Windows prompt, but I don't know what to do from here. I have
> > reinstalled the Kernel32.dll Actually got to see the Windows startup
> > screen.
> > But that only happened once. Any help would be appreciated. Thank you
>
> How far does it go before restarting? What is the history of this problem?
> What changes were made to the system right before this problem surfaced?
> What is the computer and it's configuration?
>
> --
> Rock [MS-MVP User/Shell]
>
>

"Kathy" <Kathy@discussions.microsoft.com> wrote
> Hi Rock
> It's an older computer with 20gig hard disk drive, only had 250meg memory
> but I have added another stick today. Win XP Pro with SP2 included was
> installed about 12 months ago. The machine had a virus in Jan this year
> but
> that has been cleaned. I have just done a Norton boot/virus scan and I am
> doing what used to be called a scandisk at the moment.
> The machine will boot to the menu for Startup Choices i.e. Safe Mode, etc
> etc. It doesn't matter which one I choose, it goes through the files until
> it
> gets to mup. (sorry I have momentarily forgotten the extension) stops for
> ages and then restarts. Sometimes it will go to the Windows Splash screen,
> then the screen that checks your drive for errors will appear for about
> one
> second and the computer restarts.
> I think the last installation was Skype. But the computer was a bit dodgy
> before, that is - restarting without warning, not often but occassionally.
> Someone suggested the power supply might be on its way out, however the
> machine has been in what is basically the Dos mode for about 4 hours now
> without looking like restarting.
> So I am thinking that a vital piece of the Windows Startup software may
> have
> become corrupted. I just don't know how to fix it without reinstalling
> WinXP.
> I have tried the Windows Rescue (or startup) disks, but same problem.
> Thank you for any assistance, Kathy
>
> "Rock" wrote:
>
>> "Kathy" <Kathy@discussions.microsoft.com> wrote
>> > Hi, I have Windows XP installed. The computer keeps restarting over and
>> > over
>> > again. Sometimes it will go to the Select Startup Mode, but it will not
>> > start
>> > in any mode, tried them all. I am able to start the Recovery Console
>> > and
>> > go
>> > to the C:\Windows prompt, but I don't know what to do from here. I have
>> > reinstalled the Kernel32.dll Actually got to see the Windows startup
>> > screen.
>> > But that only happened once. Any help would be appreciated. Thank you
>>
>> How far does it go before restarting? What is the history of this
>> problem?
>> What changes were made to the system right before this problem surfaced?
>> What is the computer and it's configuration?
>>
>> --
>> Rock [MS-MVP User/Shell]
>>
>>


The fact that the failures are occurring at different places in the startup
process suggests to me this is a hardware problem. Could be the motherboard
failing, the power supply, or RAM.

Run at least two of these memory diagnostic utilities. They will create a
bootable floppy or CD. Boot from that and let them run for a long time, not
just a single pass.

Memtest86+
http://www.memtest.org/

Windows Memory Diagnostic
http://oca.microsoft.com/en/windiag.asp

DocMemory Memory Diagnostic
http://www.simmtester.com/page/produ...c/download.asp

http://www.elephantboycomputers.com/...ardware_Tshoot

--
Rock [MS-MVP User/Shell]

Have run three memory tests, with several passes for each,
have run the motherboard check. No Errors found. I did a
Norton Disk Doctor scandisk, no problems at all. The computer
has now been on for 9 1/2 hours straight without restarting.
The problem seems to be the startup of Windows.
Windows did start last night and I cleaned up the hard drive,
did a registry check, put a CD in the drive and bang, it shut
down and Windows hasn't started since, just the windows
logo screen and then it wants to run a check on the hard drive
because Windows was not shut down properly last time.
I might try re installing Windows XP, but this computer is
about to go out the window.
Kathy

"Rock" wrote:

> "Kathy" <Kathy@discussions.microsoft.com> wrote
> > Hi Rock
> > It's an older computer with 20gig hard disk drive, only had 250meg memory
> > but I have added another stick today. Win XP Pro with SP2 included was
> > installed about 12 months ago. The machine had a virus in Jan this year
> > but
> > that has been cleaned. I have just done a Norton boot/virus scan and I am
> > doing what used to be called a scandisk at the moment.
> > The machine will boot to the menu for Startup Choices i.e. Safe Mode, etc
> > etc. It doesn't matter which one I choose, it goes through the files until
> > it
> > gets to mup. (sorry I have momentarily forgotten the extension) stops for
> > ages and then restarts. Sometimes it will go to the Windows Splash screen,
> > then the screen that checks your drive for errors will appear for about
> > one
> > second and the computer restarts.
> > I think the last installation was Skype. But the computer was a bit dodgy
> > before, that is - restarting without warning, not often but occassionally.
> > Someone suggested the power supply might be on its way out, however the
> > machine has been in what is basically the Dos mode for about 4 hours now
> > without looking like restarting.
> > So I am thinking that a vital piece of the Windows Startup software may
> > have
> > become corrupted. I just don't know how to fix it without reinstalling
> > WinXP.
> > I have tried the Windows Rescue (or startup) disks, but same problem.
> > Thank you for any assistance, Kathy
> >
> > "Rock" wrote:
> >
> >> "Kathy" <Kathy@discussions.microsoft.com> wrote
> >> > Hi, I have Windows XP installed. The computer keeps restarting over and
> >> > over
> >> > again. Sometimes it will go to the Select Startup Mode, but it will not
> >> > start
> >> > in any mode, tried them all. I am able to start the Recovery Console
> >> > and
> >> > go
> >> > to the C:\Windows prompt, but I don't know what to do from here. I have
> >> > reinstalled the Kernel32.dll Actually got to see the Windows startup
> >> > screen.
> >> > But that only happened once. Any help would be appreciated. Thank you
> >>
> >> How far does it go before restarting? What is the history of this
> >> problem?
> >> What changes were made to the system right before this problem surfaced?
> >> What is the computer and it's configuration?
> >>
> >> --
> >> Rock [MS-MVP User/Shell]
> >>
> >>
>
>
> The fact that the failures are occurring at different places in the startup
> process suggests to me this is a hardware problem. Could be the motherboard
> failing, the power supply, or RAM.
>
> Run at least two of these memory diagnostic utilities. They will create a
> bootable floppy or CD. Boot from that and let them run for a long time, not
> just a single pass.
>
> Memtest86+
> http://www.memtest.org/
>
> Windows Memory Diagnostic
> http://oca.microsoft.com/en/windiag.asp
>
> DocMemory Memory Diagnostic
> http://www.simmtester.com/page/produ...c/download.asp
>
> http://www.elephantboycomputers.com/...ardware_Tshoot
>
> --
> Rock [MS-MVP User/Shell]
>
>

"Kathy" <Kathy@discussions.microsoft.com> wrote
> Have run three memory tests, with several passes for each,
> have run the motherboard check. No Errors found. I did a
> Norton Disk Doctor scandisk, no problems at all. The computer
> has now been on for 9 1/2 hours straight without restarting.
> The problem seems to be the startup of Windows.
> Windows did start last night and I cleaned up the hard drive,
> did a registry check, put a CD in the drive and bang, it shut
> down and Windows hasn't started since, just the windows
> logo screen and then it wants to run a check on the hard drive
> because Windows was not shut down properly last time.
> I might try re installing Windows XP, but this computer is
> about to go out the window.

> "Rock" wrote:
>
>> "Kathy" <Kathy@discussions.microsoft.com> wrote
>> > Hi Rock
>> > It's an older computer with 20gig hard disk drive, only had 250meg
>> > memory
>> > but I have added another stick today. Win XP Pro with SP2 included was
>> > installed about 12 months ago. The machine had a virus in Jan this year
>> > but
>> > that has been cleaned. I have just done a Norton boot/virus scan and I
>> > am
>> > doing what used to be called a scandisk at the moment.
>> > The machine will boot to the menu for Startup Choices i.e. Safe Mode,
>> > etc
>> > etc. It doesn't matter which one I choose, it goes through the files
>> > until
>> > it
>> > gets to mup. (sorry I have momentarily forgotten the extension) stops
>> > for
>> > ages and then restarts. Sometimes it will go to the Windows Splash
>> > screen,
>> > then the screen that checks your drive for errors will appear for about
>> > one
>> > second and the computer restarts.
>> > I think the last installation was Skype. But the computer was a bit
>> > dodgy
>> > before, that is - restarting without warning, not often but
>> > occassionally.
>> > Someone suggested the power supply might be on its way out, however the
>> > machine has been in what is basically the Dos mode for about 4 hours
>> > now
>> > without looking like restarting.
>> > So I am thinking that a vital piece of the Windows Startup software may
>> > have
>> > become corrupted. I just don't know how to fix it without reinstalling
>> > WinXP.
>> > I have tried the Windows Rescue (or startup) disks, but same problem.
>> > Thank you for any assistance, Kathy
>> >
>> > "Rock" wrote:
>> >
>> >> "Kathy" <Kathy@discussions.microsoft.com> wrote
>> >> > Hi, I have Windows XP installed. The computer keeps restarting over
>> >> > and
>> >> > over
>> >> > again. Sometimes it will go to the Select Startup Mode, but it will
>> >> > not
>> >> > start
>> >> > in any mode, tried them all. I am able to start the Recovery Console
>> >> > and
>> >> > go
>> >> > to the C:\Windows prompt, but I don't know what to do from here. I
>> >> > have
>> >> > reinstalled the Kernel32.dll Actually got to see the Windows startup
>> >> > screen.
>> >> > But that only happened once. Any help would be appreciated. Thank
>> >> > you
>> >>
>> >> How far does it go before restarting? What is the history of this
>> >> problem?
>> >> What changes were made to the system right before this problem
>> >> surfaced?
>> >> What is the computer and it's configuration?
>> >>
>> >> --
>> >> Rock [MS-MVP User/Shell]
>> >>
>> >>
>>
>>
>> The fact that the failures are occurring at different places in the
>> startup
>> process suggests to me this is a hardware problem. Could be the
>> motherboard
>> failing, the power supply, or RAM.
>>
>> Run at least two of these memory diagnostic utilities. They will create
>> a
>> bootable floppy or CD. Boot from that and let them run for a long time,
>> not
>> just a single pass.
>>
>> Memtest86+
>> http://www.memtest.org/
>>
>> Windows Memory Diagnostic
>> http://oca.microsoft.com/en/windiag.asp
>>
>> DocMemory Memory Diagnostic
>> http://www.simmtester.com/page/produ...c/download.asp
>>
>> http://www.elephantboycomputers.com/...ardware_Tshoot


It still sounds like a hardware issue. Good luck.

--
Rock [MS-MVP User/Shell]

On Apr 26, 3:50 am, Kathy <K...@discussions.microsoft.com> wrote:
> Have run three memory tests, with several passes for each,
> have run the motherboard check. No Errors found. I did a
> Norton Disk Doctor scandisk, no problems at all. The computer
> has now been on for 9 1/2 hours straight without restarting.
> The problem seems to be the startup of Windows.
> Windows did start last night and I cleaned up the hard drive,
> did a registry check, put a CD in the drive and bang, it shut
> down and Windows hasn't started since, just the windows
> logo screen and then it wants to run a check on the hard drive
> because Windows was not shut down properly last time.

You are randomizing suspecting things. Time to start over in an
organized procedure. Idea is simple. Once something is verified,
then you need not suspect it; move on. That was what you had hoped to
accomplish with the memory diagnostic. But you were fixing doors
rather than first verifying the integrity of that household
foundation. Therefore the doors (memory) are still not exonerated
(not yet known OK).

Foundation is the power supply system. Not just a power supply.
Two minutes will accuse or exonerate that system if you have a $20
multimeter and use procedure in "When your computer dies without
warning....." starting 6 Feb 2007 in the newsgroup alt.windows-xp
at:
http://tinyurl.com/yvf9vh

Meter is so ubiquitous as to be sold in K-mart, Lowes, Radio Shack,
Wal-mart, Home Depot, ... IOW it sells like a screwdriver. Meter
and numbers in that procedure is necessary AND provides data that
better trained responders can reply to.

Once the power supply system is exonerated and numbers are posted
here (for further information), then move on a to next suspect. If
computer is from a responsible manufacturer, then diagnostics are
provided free on disk drive and on their web site. Otherwise you must
do what you did with memory - download each from the corresponding
component manufacturer. For example, did you download the disk drive
diagnostic from that disk drive manufacturer?

Meanwhile, one startup option should record or display each file as
it loads. IOW if Windows does not load, then what is that file it got
stuck loading? MUP.??? is often code associated with file names on
the disk drive. A number of reasons could create that including a
change of the disk drive setup parameters in BIOS. If that is
correct, then system is having problem finding valid file names on
disk drive. However we discuss this only to prepare for that future
analysis. First we must get facts long before fixing anything.

Once power supply system is exonerated, and once you are executing
diagnostics, well, that memory diagnostic will not report accurately
until you put hardware in another normal temperature that makes
problems obvious. Memory must be tested also with heat. Hairdryer on
highest setting will not heat memory hot enough, but enough to at
least make the memory test more useful. Heat is a diagnostic tool for
all hardware. All computer hardware must pass diagnostic at room
temperature AND at temperature as hot as hair dryer can make it.

Provided is much work. Many steps cannot be started until others
have completed. Idea is to find a problem long before trying to fix
or replace anything. Any attempt to fix something too early may only
exponentially complicate your problem. And no test is valid until the
computer's foundation - power supply 'system' - is exonerated with a
multimeter.

Thank you everyone for your help and suggestions.
So far I have done the memory test, motherboard test, hard drive check,
virus check, will do the multimeter test in the morning when I can buy one.
Switched the memory from another computer and back again. Installed a cooling
fan. Re installed Windows XP Pro. Took the hard drive out (Quantum Fireball)
and put it into another machine and it did exactly the same thing, restarted
over and over again.
Managed to start the computer today in safe mode, (hadn't been switched on
for about 12 hours) ran for about forty minutes in Windows before it crashed.
Kathy

"w_tom" wrote:

> On Apr 26, 3:50 am, Kathy <K...@discussions.microsoft.com> wrote:
> > Have run three memory tests, with several passes for each,
> > have run the motherboard check. No Errors found. I did a
> > Norton Disk Doctor scandisk, no problems at all. The computer
> > has now been on for 9 1/2 hours straight without restarting.
> > The problem seems to be the startup of Windows.
> > Windows did start last night and I cleaned up the hard drive,
> > did a registry check, put a CD in the drive and bang, it shut
> > down and Windows hasn't started since, just the windows
> > logo screen and then it wants to run a check on the hard drive
> > because Windows was not shut down properly last time.
>
> You are randomizing suspecting things. Time to start over in an
> organized procedure. Idea is simple. Once something is verified,
> then you need not suspect it; move on. That was what you had hoped to
> accomplish with the memory diagnostic. But you were fixing doors
> rather than first verifying the integrity of that household
> foundation. Therefore the doors (memory) are still not exonerated
> (not yet known OK).
>
> Foundation is the power supply system. Not just a power supply.
> Two minutes will accuse or exonerate that system if you have a $20
> multimeter and use procedure in "When your computer dies without
> warning....." starting 6 Feb 2007 in the newsgroup alt.windows-xp
> at:
> http://tinyurl.com/yvf9vh
>
> Meter is so ubiquitous as to be sold in K-mart, Lowes, Radio Shack,
> Wal-mart, Home Depot, ... IOW it sells like a screwdriver. Meter
> and numbers in that procedure is necessary AND provides data that
> better trained responders can reply to.
>
> Once the power supply system is exonerated and numbers are posted
> here (for further information), then move on a to next suspect. If
> computer is from a responsible manufacturer, then diagnostics are
> provided free on disk drive and on their web site. Otherwise you must
> do what you did with memory - download each from the corresponding
> component manufacturer. For example, did you download the disk drive
> diagnostic from that disk drive manufacturer?
>
> Meanwhile, one startup option should record or display each file as
> it loads. IOW if Windows does not load, then what is that file it got
> stuck loading? MUP.??? is often code associated with file names on
> the disk drive. A number of reasons could create that including a
> change of the disk drive setup parameters in BIOS. If that is
> correct, then system is having problem finding valid file names on
> disk drive. However we discuss this only to prepare for that future
> analysis. First we must get facts long before fixing anything.
>
> Once power supply system is exonerated, and once you are executing
> diagnostics, well, that memory diagnostic will not report accurately
> until you put hardware in another normal temperature that makes
> problems obvious. Memory must be tested also with heat. Hairdryer on
> highest setting will not heat memory hot enough, but enough to at
> least make the memory test more useful. Heat is a diagnostic tool for
> all hardware. All computer hardware must pass diagnostic at room
> temperature AND at temperature as hot as hair dryer can make it.
>
> Provided is much work. Many steps cannot be started until others
> have completed. Idea is to find a problem long before trying to fix
> or replace anything. Any attempt to fix something too early may only
> exponentially complicate your problem. And no test is valid until the
> computer's foundation - power supply 'system' - is exonerated with a
> multimeter.
>
>

Tested power supply, all showed 0 except the green wire which showed 0.2.
Installed new power supply, no good, exactly as before.
"Kathy" wrote:

>
> Thank you everyone for your help and suggestions.
> So far I have done the memory test, motherboard test, hard drive check,
> virus check, will do the multimeter test in the morning when I can buy one.
> Switched the memory from another computer and back again. Installed a cooling
> fan. Re installed Windows XP Pro. Took the hard drive out (Quantum Fireball)
> and put it into another machine and it did exactly the same thing, restarted
> over and over again.
> Managed to start the computer today in safe mode, (hadn't been switched on
> for about 12 hours) ran for about forty minutes in Windows before it crashed.
> Kathy
>
> "w_tom" wrote:
>
> > On Apr 26, 3:50 am, Kathy <K...@discussions.microsoft.com> wrote:
> > > Have run three memory tests, with several passes for each,
> > > have run the motherboard check. No Errors found. I did a
> > > Norton Disk Doctor scandisk, no problems at all. The computer
> > > has now been on for 9 1/2 hours straight without restarting.
> > > The problem seems to be the startup of Windows.
> > > Windows did start last night and I cleaned up the hard drive,
> > > did a registry check, put a CD in the drive and bang, it shut
> > > down and Windows hasn't started since, just the windows
> > > logo screen and then it wants to run a check on the hard drive
> > > because Windows was not shut down properly last time.
> >
> > You are randomizing suspecting things. Time to start over in an
> > organized procedure. Idea is simple. Once something is verified,
> > then you need not suspect it; move on. That was what you had hoped to
> > accomplish with the memory diagnostic. But you were fixing doors
> > rather than first verifying the integrity of that household
> > foundation. Therefore the doors (memory) are still not exonerated
> > (not yet known OK).
> >
> > Foundation is the power supply system. Not just a power supply.
> > Two minutes will accuse or exonerate that system if you have a $20
> > multimeter and use procedure in "When your computer dies without
> > warning....." starting 6 Feb 2007 in the newsgroup alt.windows-xp
> > at:
> > http://tinyurl.com/yvf9vh
> >
> > Meter is so ubiquitous as to be sold in K-mart, Lowes, Radio Shack,
> > Wal-mart, Home Depot, ... IOW it sells like a screwdriver. Meter
> > and numbers in that procedure is necessary AND provides data that
> > better trained responders can reply to.
> >
> > Once the power supply system is exonerated and numbers are posted
> > here (for further information), then move on a to next suspect. If
> > computer is from a responsible manufacturer, then diagnostics are
> > provided free on disk drive and on their web site. Otherwise you must
> > do what you did with memory - download each from the corresponding
> > component manufacturer. For example, did you download the disk drive
> > diagnostic from that disk drive manufacturer?
> >
> > Meanwhile, one startup option should record or display each file as
> > it loads. IOW if Windows does not load, then what is that file it got
> > stuck loading? MUP.??? is often code associated with file names on
> > the disk drive. A number of reasons could create that including a
> > change of the disk drive setup parameters in BIOS. If that is
> > correct, then system is having problem finding valid file names on
> > disk drive. However we discuss this only to prepare for that future
> > analysis. First we must get facts long before fixing anything.
> >
> > Once power supply system is exonerated, and once you are executing
> > diagnostics, well, that memory diagnostic will not report accurately
> > until you put hardware in another normal temperature that makes
> > problems obvious. Memory must be tested also with heat. Hairdryer on
> > highest setting will not heat memory hot enough, but enough to at
> > least make the memory test more useful. Heat is a diagnostic tool for
> > all hardware. All computer hardware must pass diagnostic at room
> > temperature AND at temperature as hot as hair dryer can make it.
> >
> > Provided is much work. Many steps cannot be started until others
> > have completed. Idea is to find a problem long before trying to fix
> > or replace anything. Any attempt to fix something too early may only
> > exponentially complicate your problem. And no test is valid until the
> > computer's foundation - power supply 'system' - is exonerated with a
> > multimeter.
> >
> >

Kathy wrote:
> Tested power supply, all showed 0 except the green wire which showed
> 0.2. Installed new power supply, no good, exactly as before.
> "Kathy" wrote:

Today's PSUs are switching power supplies and some are designed so that if
there is no load (computer) connected to them, they turn themselves off
internally. So, the PSU has to be connected when you test it, to be
certain.

Do you mean that, with the PSu connected to the computer, the power switch
ON and using a meter set to read VOLTS, DC, in say the 25 or 15 0r 10V
range, you are seeing 0 VOLTS on the other wires? You should be seeing
12, -12, 5, maybe 3.5, 3.3, or lower DC voltages coming out of the PSU, off
the top of my head.
It is very unlikely that an internal short in the computer would
completely shut the PSU down permanently. You should only have to apply
power to, say, the mother board and a disk drive to do the testing.

If you aren't seeing ANY voltages coming from the PSU, then it's not
getting power since you changed it out for another one. Check the fuse/s!
They are usually in a small black cap that you unscrew and pull out. It
might be located on the PSU or sometimes they stick out the back of the
computer itself.
REmove the AC power, unplug it from the wall, and pull out the fuse.
Set your meter to read ohms, and a low scale (say, 1 or 10 ohms), and
measure across the fuse. If it doesn't read 0 ohms, replace the fuse; it's
blown.
If you are getting 0V DC output from the PSU, this is an extremely likely
source of the problem and many people forget it, though it's the very first
thing that should be checked, in addition to the integrity of the power cord
itself, and even the outlet. If the cord and fuse are OK, plug something
else into the outlet and be sure the outlet has power.

HTH
Pop`


>
>>
>> Thank you everyone for your help and suggestions.
>> So far I have done the memory test, motherboard test, hard drive
>> check, virus check, will do the multimeter test in the morning when
>> I can buy one. Switched the memory from another computer and back
>> again. Installed a cooling fan. Re installed Windows XP Pro. Took
>> the hard drive out (Quantum Fireball) and put it into another
>> machine and it did exactly the same thing, restarted over and over
>> again.
>> Managed to start the computer today in safe mode, (hadn't been
>> switched on for about 12 hours) ran for about forty minutes in
>> Windows before it crashed. Kathy
>>
>> "w_tom" wrote:
>>
>>> On Apr 26, 3:50 am, Kathy <K...@discussions.microsoft.com> wrote:
>>>> Have run three memory tests, with several passes for each,
>>>> have run the motherboard check. No Errors found. I did a
>>>> Norton Disk Doctor scandisk, no problems at all. The computer
>>>> has now been on for 9 1/2 hours straight without restarting.
>>>> The problem seems to be the startup of Windows.
>>>> Windows did start last night and I cleaned up the hard drive,
>>>> did a registry check, put a CD in the drive and bang, it shut
>>>> down and Windows hasn't started since, just the windows
>>>> logo screen and then it wants to run a check on the hard drive
>>>> because Windows was not shut down properly last time.
>>>
>>> You are randomizing suspecting things. Time to start over in an
>>> organized procedure. Idea is simple. Once something is verified,
>>> then you need not suspect it; move on. That was what you had hoped
>>> to accomplish with the memory diagnostic. But you were fixing doors
>>> rather than first verifying the integrity of that household
>>> foundation. Therefore the doors (memory) are still not exonerated
>>> (not yet known OK).
>>>
>>> Foundation is the power supply system. Not just a power supply.
>>> Two minutes will accuse or exonerate that system if you have a $20
>>> multimeter and use procedure in "When your computer dies without
>>> warning....." starting 6 Feb 2007 in the newsgroup alt.windows-xp
>>> at:
>>> http://tinyurl.com/yvf9vh
>>>
>>> Meter is so ubiquitous as to be sold in K-mart, Lowes, Radio
>>> Shack, Wal-mart, Home Depot, ... IOW it sells like a
>>> screwdriver. Meter and numbers in that procedure is necessary AND
>>> provides data that better trained responders can reply to.
>>>
>>> Once the power supply system is exonerated and numbers are posted
>>> here (for further information), then move on a to next suspect. If
>>> computer is from a responsible manufacturer, then diagnostics are
>>> provided free on disk drive and on their web site. Otherwise you
>>> must do what you did with memory - download each from the
>>> corresponding component manufacturer. For example, did you
>>> download the disk drive diagnostic from that disk drive
>>> manufacturer?
>>>
>>> Meanwhile, one startup option should record or display each file
>>> as it loads. IOW if Windows does not load, then what is that file
>>> it got stuck loading? MUP.??? is often code associated with file
>>> names on the disk drive. A number of reasons could create that
>>> including a change of the disk drive setup parameters in BIOS. If
>>> that is correct, then system is having problem finding valid file
>>> names on disk drive. However we discuss this only to prepare for
>>> that future analysis. First we must get facts long before fixing
>>> anything.
>>>
>>> Once power supply system is exonerated, and once you are executing
>>> diagnostics, well, that memory diagnostic will not report accurately
>>> until you put hardware in another normal temperature that makes
>>> problems obvious. Memory must be tested also with heat. Hairdryer
>>> on highest setting will not heat memory hot enough, but enough to at
>>> least make the memory test more useful. Heat is a diagnostic tool
>>> for all hardware. All computer hardware must pass diagnostic at
>>> room temperature AND at temperature as hot as hair dryer can make
>>> it.
>>>
>>> Provided is much work. Many steps cannot be started until others
>>> have completed. Idea is to find a problem long before trying to fix
>>> or replace anything. Any attempt to fix something too early may
>>> only exponentially complicate your problem. And no test is valid
>>> until the computer's foundation - power supply 'system' - is
>>> exonerated with a multimeter.

On Apr 28, 8:02 am, Kathy <K...@discussions.microsoft.com> wrote:
> Testedpower supply, all showed 0 except the green wire which showed 0.2.
> Installed newpower supply, no good, exactly as before.

In the original post, you were testing memory, etc. Therefore
purple wire HAD voltage even when computer was off. For purple wire
can have no voltage: power supply not connected to AC electric?

Demonstrated is why collecting information - taking voltage numbers
- must be performed without yet trying to fix anything. Without
voltages, then original problem exists AND now a second problem is
created.

Meter must be set to 20 volt DC range. Red lead contacts purple
wire. Black lead touches black wires or computer chassis. If purple
wire does not have voltage, then nothing works. No lights. No fan
spins. No memory test. Nothing.

However if purple wire does have voltage and if number is not
sufficient, then system will do strange things such as only start
sometimes.

Apparently something new has been made defective. Fact collection
starts with voltage on that purple wire. It was working before. What
did you do to create a new problem - no voltage on that purple wire?
Demonstrated is why nothing must be replaced until first facts have
been collected. With two problems, the failure has now been made
exponentially more complex.

Purple wire always has voltage when computer is off but connected to
AC mains. If any change is made without disconnecting power cord from
wall, that purple wire voltage can create hardware damage. Swapping
hardware without first identifying a problem is performed by the
untrained. Don't make that mistake. Don't fix anything without
first learning what is wrong. Your only question is why purple wire
voltage is gone. Is AC power cord connected properly?

If yes, then remove AC power cord. Disconnect only connector to
motherboard. Restore AC power cord. Measure voltage between purple
and black wires. Report resulting numbers.

As I said, I installed a brand new power supply and the same thing happened.
So it is not the power supply.
I have installed the hard drive into another computer and it seems happy
enough.
I'll leave it there.
I do not have the facilities to test the motherboard (except software checks)
I have given up and the tower will now be thrown out. :)
Thank you all for your help. It has been appreciated.
Regards, Kathy

"w_tom" wrote:

> On Apr 28, 8:02 am, Kathy <K...@discussions.microsoft.com> wrote:
> > Testedpower supply, all showed 0 except the green wire which showed 0.2.
> > Installed newpower supply, no good, exactly as before.
>
> In the original post, you were testing memory, etc. Therefore
> purple wire HAD voltage even when computer was off. For purple wire
> can have no voltage: power supply not connected to AC electric?
>
> Demonstrated is why collecting information - taking voltage numbers
> - must be performed without yet trying to fix anything. Without
> voltages, then original problem exists AND now a second problem is
> created.
>
> Meter must be set to 20 volt DC range. Red lead contacts purple
> wire. Black lead touches black wires or computer chassis. If purple
> wire does not have voltage, then nothing works. No lights. No fan
> spins. No memory test. Nothing.
>
> However if purple wire does have voltage and if number is not
> sufficient, then system will do strange things such as only start
> sometimes.
>
> Apparently something new has been made defective. Fact collection
> starts with voltage on that purple wire. It was working before. What
> did you do to create a new problem - no voltage on that purple wire?
> Demonstrated is why nothing must be replaced until first facts have
> been collected. With two problems, the failure has now been made
> exponentially more complex.
>
> Purple wire always has voltage when computer is off but connected to
> AC mains. If any change is made without disconnecting power cord from
> wall, that purple wire voltage can create hardware damage. Swapping
> hardware without first identifying a problem is performed by the
> untrained. Don't make that mistake. Don't fix anything without
> first learning what is wrong. Your only question is why purple wire
> voltage is gone. Is AC power cord connected properly?
>
> If yes, then remove AC power cord. Disconnect only connector to
> motherboard. Restore AC power cord. Measure voltage between purple
> and black wires. Report resulting numbers.
>
>
>

On Apr 29, 12:06 am, Kathy <K...@discussions.microsoft.com> wrote:
> As I said, I installed a brand new power supply and the same thing happened.
> So it is not the power supply.

Assumption (it is not a power supply) is only probable. Power
supply system includes other components - with an 's'. Furthermore, a
defective power supply can work in one system and fail in another.
All are examples of why, with shotgunning, we still do not
definitively know what is good and which is bad.

Obviously there is no interest in fixing that unique system.
However the point is that replacing a power supply - shotgunning -
does not exonerate anything. A power supply 'system' is more than a
power supply. Those meter measurements imply that shotgunning also
created another problem - exponentially complicated a failure. An
auto mechanic that did shotgunning would be unemployed quickly.
Shotgunning (according to meter numbers) created another failure.
Multiple reasons why shotgunning - replacing a power supply -
accomplished nothing useful.

Should a future problem occur, use the lesson from this experience:
shotgunning only created another failure. Never replace anything
until something is definitively known defective. With a meter, see a
defect first and faster. Even see a defect before it creates
failures. Then, with a meter, see if that defect was eliminated by
new parts. Especially powerful when a system has more than one
defect; a failure made exponentially more complex.

Two minutes with numbers on a meter - no shotgunning - would have
defined what is good and suspect - faster, definitively, and without
creating more damage.