Windows XP, used to reboot on BSOD, no longer does

[Confused]

I have a dual Celeron "server" running Windows XP Pro, and when it BSOD'd, say from overclocking too far it would reboot, however now it doesn't do that. I liked the way that it used to reboot automatically and used to be OK to use for it's purpose (web server and Seti Queue for Seti @ home) for a while longer til i noticed it rebooting and could troubleshoot it.

Now however, it's not rebooting automatically, even tho the "Reboot on errors" is selected in the Startup and Recovery options under the Advanced tab on System Properties screen.

It is set up in the BIOS for ACPI, and also "Power Control by APM" is selected, do i need to turn this option to off?

Thanks

ConfusedBW

 

[SoulAssassin]

<< I have a dual Celeron "server" running Windows XP Pro, and when it BSOD'd, say from overclocking too far it would reboot, however now it doesn't do that. I liked the way that it used to reboot automatically and used to be OK to use for it's purpose (web server and Seti Queue for <a class=ftalternatingbarlinklarge href="http://www.teamanandtech.d2g.com/seti" target=blank>Seti @ home</A>) for a while longer til i noticed it rebooting and could troubleshoot it.

Now however, it's not rebooting automatically, even tho the "Reboot on errors" is selected in the Startup and Recovery options under the Advanced tab on System Properties screen. >>



What's the stop error? I vaguely remember hearing whether it reboots is dependent upon the error.



<<
It is set up in the BIOS for ACPI, and also "Power Control by APM" is selected, do i need to turn this option to off?
>>



Doubt it but you never know.

 

[Confused]

The error i'm getting now is something like

* Hardware malfunction

The system has halted and needs to be restarted

* Please contact your hardware vendor


CBW

 

[MoFunk]

I am not certain on this, but on my WinXP box, when it crashes (rarely) I either get that halt error or it reboots. I think because it is being shown as a hardware error it wont do an automatic reboot, I think that it reboots mainly for software issues.

 

[Confused]

Darn it.

It was doing this when clocked at 72FSB (433 CPU) or even 92FSB (552 CPU)

I can't see how it *could* be a heat problem if it is that, there's 2 Athlon coolers on the CPUs and a fan blowing air directly onto the north bridge! Unless it's the 32 or 64MB stick ram (can't remember what size) alongside the 128MB Crucial PC133 that isn't liking the higher FSB...

With only the 128 with 2 seti clients and WinXP it's running on about 15MB free RAM...but if it will run stable o/ced then it might be time to invest in some more RAM!

ConfusedBW

 

[Junior0579]

That's weird. It must have something to do with being a hardware issue.