G
Guest
My lap top keeps shutting down in the middle of any program that I am using, especially when 2 or more programs are running, does anybody have any ideas why?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
W
w_tom
People might have some useful ideas after you first provided
basic information. Based upon what was posted, then
everything inside the computer is reason for failure. What
does the system (event) log say? What did the comprehensive
diagnostics from the manufacturer report? What is the
hardware? What is the OS? What are the programs?
basic information. Based upon what was posted, then
everything inside the computer is reason for failure. What
does the system (event) log say? What did the comprehensive
diagnostics from the manufacturer report? What is the
hardware? What is the OS? What are the programs?
R
Ronnie Vernon MVP
Willbert said:My lap top keeps shutting down in the middle of any program that I am
using, especially when 2 or more programs are running, does anybody
have any ideas why?
Think about what you have recently changed or installed, no matter how
innocent it seemed to be prior to the problem appearing.
The system is encountering a fatal error and you have the option set for it
to automatically restart when this occurs. Open Control
Panel/System/Advanced tab/Start Up and Recovery section/Settings button.
Remove the check mark from the Automatically Restart option. This will allow
the error to be displayed the next time it occurs.
You might also want to go to Start/Run and type: eventvwr.msc and press
OK. In the event Viewer, click on each of the items in the left side menu
and look for any Red X error messages that correspond to the last time this
behavior happened. Double click the entry to see the details of the error.
This may give you a clue as to program/hardware is causing the problem.
Another thing to look at is Start/Run, type: msinfo32 and press OK.
Expand the Components item and click on the Problem Devices. If there is an
entry for a hardware device there, it could be where the problem is coming
from.
You can start the troubleshooting by using the Configuration Utility which
controls the start up programs.
How to Troubleshoot By Using the Msconfig Utility in Windows XP:
http://support.microsoft.com/?kbid=310560
--
Ronnie Vernon
Microsoft MVP
Windows Shell/User
Please reply to the newsgroup so all may benefit.
G
Guest
Sorrry, I do not know all the technical data, that is why I am posting on this site.....your help would be appreciative. Thanks
R
Ronnie Vernon MVP
Willbert said:Sorrry, I do not know all the technical data, that is why I am
posting on this site.....your help would be appreciative. Thanks
Willbert
Just follow the instructions in my previous post and post the results back
here.
--
Ronnie Vernon
Microsoft MVP
Windows Shell/User
Please reply to the newsgroup so all may benefit.
http://www.dts-l.org
http://www.mvps.org
W
w_tom
In that last post was necessary technical data that you must
obtain and post. Getting that information is too simple. One
fact is even printed on outside of computer case.
Manufacturer's name and model number. If you don't know, then
use the Help in Windows to learn how to answer questions from
my last post. Another source is the msinfo32 program cited by
another poster. As for the comprehensive diagnostics: located
on you computer manufacturer's web site. This assuming your
computer was provided by a minimally responsible manufacturer.
Without that technical data, then no one can help you.
obtain and post. Getting that information is too simple. One
fact is even printed on outside of computer case.
Manufacturer's name and model number. If you don't know, then
use the Help in Windows to learn how to answer questions from
my last post. Another source is the msinfo32 program cited by
another poster. As for the comprehensive diagnostics: located
on you computer manufacturer's web site. This assuming your
computer was provided by a minimally responsible manufacturer.
Without that technical data, then no one can help you.
W
w_tom
No one need uncheck all those automatic restarts. Important
information is already stored and can be recovered in the
system (event) log - which is why Windows OSes come with
automatic restart enabled as default.
information is already stored and can be recovered in the
system (event) log - which is why Windows OSes come with
automatic restart enabled as default.
R
Ronnie Vernon MVP
w_tom said:No one need uncheck all those automatic restarts. Important
information is already stored and can be recovered in the
system (event) log - which is why Windows OSes come with
automatic restart enabled as default.
Not necessarily. Seeing the blue screen STOP: error message can often be a
quicker way to identify where a problem is occuring, especially if the error
is the result of a hardware problem. Also, the specific STOP: error messages
are cataloged and published. With the automatic restart enabled you will
miss this important information.
Error Messages: STOP MESSAGES:
http://www.aumha.org/win5/kbestop.htm
Troubleshooting Stop messages: general strategies:
http://www.microsoft.com/windows2000/en/datacenter/help/troubleshooting_general_stop_messages.htm
129845 - Blue Screen Preparation Before Contacting Microsoft:
http://support.microsoft.com/?kbid=129845
--
Ronnie Vernon
Microsoft MVP
Windows Shell/User
Please reply to the newsgroup so all may benefit.
http://www.dts-l.org
http://www.mvps.org
W
w_tom
The BSOD (blue screen of death) error message provides good
quick information IF the system user has the books or web
site to decode the stop error number and the associated four
following numbers. Most users do not. But that error
information is 'user readable' (not just code numbers) in the
system (event) log and is stored historically for experienced
repairmen who come later. The BSOD error message is lost
after it is read. Reasons why BSOD is not the default option
in XP and why most users are better off leaving the default
'restart on error' condition.
If the system is having a problem, the user need only review
the systems logs. For you (and for me) BSOD is a useful. For
most users, it is not. For them, letting the system restart -
the default option - is more useful.
quick information IF the system user has the books or web
site to decode the stop error number and the associated four
following numbers. Most users do not. But that error
information is 'user readable' (not just code numbers) in the
system (event) log and is stored historically for experienced
repairmen who come later. The BSOD error message is lost
after it is read. Reasons why BSOD is not the default option
in XP and why most users are better off leaving the default
'restart on error' condition.
If the system is having a problem, the user need only review
the systems logs. For you (and for me) BSOD is a useful. For
most users, it is not. For them, letting the system restart -
the default option - is more useful.
R
Ronnie Vernon MVP
w_tom said:The BSOD (blue screen of death) error message provides good
quick information IF the system user has the books or web
site to decode the stop error number and the associated four
following numbers. Most users do not. But that error
information is 'user readable' (not just code numbers) in the
system (event) log and is stored historically for experienced
repairmen who come later. The BSOD error message is lost
after it is read. Reasons why BSOD is not the default option
in XP and why most users are better off leaving the default
'restart on error' condition.
If the system is having a problem, the user need only review
the systems logs. For you (and for me) BSOD is a useful. For
most users, it is not. For them, letting the system restart -
the default option - is more useful.
Sorry, but I just cannot agree with this. The problem is that when the
system shuts down, in the eyes of the user, the only problem they have is
that the system just keeps shutting down. They may not be informed that
their system has suffered a fatal system error until some time later and by
then the problems may have been multiplied, sometimes beyond repair, and
then they lose everything.
--
Ronnie Vernon
Microsoft MVP
Windows Shell/User
Please reply to the newsgroup so all may benefit.
http://www.dts-l.org
http://www.mvps.org