rebooting randomly

[Patrick Tuite]

I have built a brand new Shuttle system - Pentium 4
Hyperthreading - very fast disk, 1GB RAM with Windows XP
Pro - the system reboots randomly a few times a day - I
have all patches/ updates up to date, virus checker
(McAfee) up to date, have checked system with Stinger for
the worm or any of the variants - no sign of any
infection. On reboot the windows error handling says it
was due to a driver problem, but as far as I can tell all
the system drivers are fully up to date - have been
through and downloaded them all in case and the problem
still continues.

Has anyone any suggestions?

 

[The Reverend XP]

Go>start\control panel\administrative tools\and double
click the event viewer. Now you are looking for red Xs in
any of the three logs shown on the left. Usually for this
sort of issue the application log will be the one to open
and look at. Double click the red X and a window will open
giving you more details as to what caused the issue. This
rarely leads to a solution by clicking Microsofts link but
try it anyway. At the very least make a note of what
program or module caused the conflict and that is likely
the driver you will need to get. You can also stop the
reboot by going>start\control panel\double click
system\advanced tab\startup and recovery-settings
button\then under system failure uncheck restart the
computer. While you are at it take note of the debug
section. If you track down this file there may be more
pointers as to what you need to do to resolve your
problem. Good luck

 

[Alex Nichol]

I have built a brand new Shuttle system - Pentium 4
Hyperthreading - very fast disk, 1GB RAM with Windows XP
Pro - the system reboots randomly a few times a day

You have something that is crashing - and the system's 'automatically
restart' is cutting in. It does this too readily. 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