On Wed, 17 Nov 2010 23:46:52 -0000, "Tim Meddick"
wrote:

This could be a symptom of whatever bootmanager you are using is not doing
it's job properly.

If you are using the Window's XP bootloader (i.e. the OS options list comes
up as laid out in your "boot.ini" file in the root of the XP partition)
then it may be another type of HD data corruption that's a possible cause.

Have you tried something as simple as booting from the XP setup disk and
selecting the "press R to repair using Recovery Console" option. Then
running CHKDSK C: /P from the RC prompt?

You could also try booting into one or other OS in "safe-mode" and
consulting the Event Log (NT, XP, Vista, Win7).

Just don't be so eager to jump to the conclusion that it's got to be a
hardware conflict....

==

Cheers, Tim Meddick, Peckham, London. :-)



Okay, I won't. The machine is still on and will stay on overnight.
It has not froze yet. The key change was removing the second (W7)
boot drive. At least it seems that way.

Thanks again

Duke


wrote in message
.. .
On Wed, 17 Nov 2010 04:07:23 -0000, "Tim Meddick"
wrote:

Could be.......

However, the most common cause of Window's PC "freezing up", by far and
away, is a software conflict....

Hardware conflicts usually result in the PC freezing very soon after
start
or being unable to start at all!!

Check any recently installed software.

Pay particular attention to exactly WHAT was going on / you were doing,
when the "freeze" occurred.

On reboot, take a look in the Event Log for any additional clues.

==

Cheers, Tim Meddick, Peckham, London. :-)


Thanks Tim

I thought that too. But I have dual bootable hard drives and it
happened with either drive booted. As a further test, I have
disconnected one of them and am running solely from the other.
So far no freeze. This AM though when I powered up I heard a slight,
unusual, sound coming from the CPU fan. I wonder if the fan is
binding up and CPU heat is the culprit. I need to watch that, and I
can since the tower is running with the cover off.

Duke