PC Hangs On Boot Up

[nick]

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

My PC is hanging during the boot process. I can get past Windiws XP Logo,
then the screen goes blank and nothing else happens (usually go to the log on
screen).
I know it is a driver / hardware issue as the Automatic Error Reporting
tells me this, BUT, it doesn't tell me which driver or the hardware is
causing the problem.
I know it isn't the memory as I've checked this with the MS memory testing
tool.

Anyone got any suggestions?

Many thanks

 

[Guest]

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

what you might want to try is to unhook all PCI cards and boot backup and
see what happens. Then if it boots up put each device back in one at a time.

Its worth a shot.
good luck

"Nick" <Nick@discussions.microsoft.com> wrote in message
news:F092F712-29B4-4977-8311-300A31453961@microsoft.com...
> My PC is hanging during the boot process. I can get past Windiws XP Logo,
> then the screen goes blank and nothing else happens (usually go to the log
> on
> screen).
> I know it is a driver / hardware issue as the Automatic Error Reporting
> tells me this, BUT, it doesn't tell me which driver or the hardware is
> causing the problem.
> I know it isn't the memory as I've checked this with the MS memory testing
> tool.
>
> Anyone got any suggestions?
>
> Many thanks

 

[nick]

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

I am going to try that, however, the problem doesn't happen every time!

"hustedj" wrote:

> what you might want to try is to unhook all PCI cards and boot backup and
> see what happens. Then if it boots up put each device back in one at a time.
>
> Its worth a shot.
> good luck
>
> "Nick" <Nick@discussions.microsoft.com> wrote in message
> news:F092F712-29B4-4977-8311-300A31453961@microsoft.com...
> > My PC is hanging during the boot process. I can get past Windiws XP Logo,
> > then the screen goes blank and nothing else happens (usually go to the log
> > on
> > screen).
> > I know it is a driver / hardware issue as the Automatic Error Reporting
> > tells me this, BUT, it doesn't tell me which driver or the hardware is
> > causing the problem.
> > I know it isn't the memory as I've checked this with the MS memory testing
> > tool.
> >
> > Anyone got any suggestions?
> >
> > Many thanks
>
>
>