Blue screen system halted message when OS starts to load

[Lee MacMillan]

Recently had to replace a failed mobo and do a repair install of Windows
2000. All went well and I've got all the service packs updated. The system
runs fine if it starts but about every 3rd start up attempt (I only use this
machine 2 or 3 times a week), as soon as Windows starts to load (after the
main screen), I'll get a blue screen with the message "system halted,
contact your hardware vendor."

I haven't changed any components other than the mobo (an Epox 8KHA+ that was
in my WinXP machine for several years). As noted, if Windows loads, the
sytem runs fine with no indication of a problem. At first I thought my
network card wasn't fully seated but I pulled it out and got the same error.
I have 3 SDRAM sticks (2x256 and 1x512), a Radeon 9250 video card, 1
Seagate 80gig drive, 1 floppy and an HP CDRW.

From my research I assume this is some kind of hardware problem but since
it's intermittant, I don't where to start. All suggestions are welcome.
Thanks.

 

[meerkat]

Recently had to replace a failed mobo and do a repair install of
Windows
2000. All went well and I've got all the service packs updated. The
system
runs fine if it starts but about every 3rd start up attempt (I only
use this
machine 2 or 3 times a week), as soon as Windows starts to load
(after the
main screen), I'll get a blue screen with the message "system halted,
contact your hardware vendor."

I haven't changed any components other than the mobo (an Epox 8KHA+
that was
in my WinXP machine for several years). As noted, if Windows loads,
the
sytem runs fine with no indication of a problem. At first I thought
my
network card wasn't fully seated but I pulled it out and got the same
error.
I have 3 SDRAM sticks (2x256 and 1x512), a Radeon 9250 video card, 1
Seagate 80gig drive, 1 floppy and an HP CDRW.

From my research I assume this is some kind of hardware problem but
since
it's intermittant, I don't where to start. All suggestions are
welcome.
Thanks.

Divide and conquer Lee.
D/load the Seagate drive tools, and test your H/drive.
D/load and run Memtest86, and test your RAM.
Disconnect your CDRW, to see if that makes any difference..
PSU could be getting tired, etc.

What you`re try to do is to isolate the problem H/ware.
HTH.

 

[Lee M.]

Divide and conquer Lee.
D/load the Seagate drive tools, and test your H/drive.
D/load and run Memtest86, and test your RAM.
Disconnect your CDRW, to see if that makes any difference..
PSU could be getting tired, etc.

What you`re try to do is to isolate the problem H/ware.
HTH.

I have downloaded Memtest86 already and will run that. The PSU is
relatively new so I don't think that's it. Can't help believe it's
something to do with the mobo since that's the only "new" component in the
system that was running fine until the previous mobo failed (bad caps).

Thanks for the suggestions. I guess I'll just have to "brut force" it until
I figure it out. A guy on the Windows 2000 forum suggested that my repair
install might not have accurately captured the new hardware and suggested a
fresh install. That will be my last resort.

Lee

 

[Larry Roberts]

Thanks for the suggestions. I guess I'll just have to "brut force" it until
I figure it out. A guy on the Windows 2000 forum suggested that my repair
install might not have accurately captured the new hardware and suggested a
fresh install. That will be my last resort.

Lee

That would be my suggestion as well. There are alot of
variables to consider when you change out the mainboard that doing a
fresh install seems to be the best route most of the time.