Constant Rebooting

[Msbx]

I've recently switched from 98 to XP and I really want to like it but
I've got a major headache and so far I'm
not impressed. My computer is constantly rebooting itself regardless of
what I'm doing, even if it's idle.
I've ruled out any hardware and some software and now I'm starting to go
nuts. I've used the Recover Console
to replace kernel32.dll as was suggested on a help site. Didn't work.
However there is a Failure Audit that
may be tied to it. The following are the error messages. I don't know
how to run the IP monitor snap-in, so
any help and/or suggestions will be greatly appreciated. Thanks in advance!

Msbx


Event Type: Failure Audit
Event Source: Security
Event Category: Policy Change
Event ID: 615
Date: 1/9/2004
Time: 7:24:59 PM
User: NT AUTHORITY\NETWORK SERVICE
Computer: COMPUTER
Description:
IPSec Services: IPSec Services failed to get the complete list of
network interfaces on the machine. This can be a potential

security hazard to the machine since some of the network interfaces may
not get the protection as desired by the applied

IPSec filters. Please run IPSec monitor snap-in to further diagnose the
problem.

--------------------------------------------------------------------

Event Type: Failure Audit
Event Source: Security
Event Category: Policy Change
Event ID: 615
Date: 1/9/2004
Time: 7:24:59 PM
User: NT AUTHORITY\NETWORK SERVICE
Computer: COMPUTER
Description:
IPSec Services: IPSec Services failed to initialize RPC server with
error code: The authentication service is unknown.
.. IPSec Services could not be started.

 

[Alex Nichol]

I've recently switched from 98 to XP and I really want to like it but
I've got a major headache and so far I'm
not impressed. My computer is constantly rebooting itself regardless of
what I'm doing, even if it's idle.

You have something that is crashing - and the system's 'automatically
restart' is cutting in. It does this only too easily. Turn this off: in
Control Panel - System - Advanced, click Settings in the Startup and
Recovery section. There uncheck 'automatically restart'. You can also
usefully change the 'write debugging information' to (none) unless you
are actively needing a dump for debugging something, or to 'minidump' if
you are getting errors that you wish to report on to Microsoft. You
may now get a Blue screen failure instead, but at least will get some
guidance as to what is happening

The likelihood is that it is a troubled driver - if so a blue screen
will have a reference at the bottom to 'something.sys'. Look for that -
probably in windows\system32\drivers, right click and take Properties.
The version page should indicate what it relates to