Several times now I have told the computer to turn off and discovered later that it was still on. I get that grey window that says fatal error not just error and it asks me to send a report so I have sent the report and waited and closed and still nothing from microsoft and it still does it. Is someone else using my computer and knows how to prevent me shutting down so they can continue to use it? Or is this problem solvable without having to worry about that? I have Malware bytes antimalware and also McAfee which seems useless. Both of them find nothing when scanning.
Page 1 of 1
Computer does not shut down, howcome? fatal error after telling computer to turn off
#2
Posted 24 April 2011 - 10:58 AM
Have you watched to see if the computer is restarting after the error message?
Can you post the exact error message?
If you find that the computer is restarting try either of the methods below to stop the automatic restart. Once it is disable you will get an error message rather than restarting. Please post that error message in this topic.
Can you post the exact error message?
If you find that the computer is restarting try either of the methods below to stop the automatic restart. Once it is disable you will get an error message rather than restarting. Please post that error message in this topic.
#3
Posted 24 April 2011 - 01:27 PM
1) Replace McAfee with ANY other anti virus app. McAfee is the worst.
2) Open msconfig and on the General tab choose "selective startup" (uncheck all three items) and reboot. Then shut down. Does the problem still occur? If not, start adding items back to msconfig one or two at a time, rebooting after each change, until the problem reappears and you'll have identified the offending process. This is clearly a time consuming process, but it is the best way to determine if some process loading with the system is the cause of your problem.
2) Open msconfig and on the General tab choose "selective startup" (uncheck all three items) and reboot. Then shut down. Does the problem still occur? If not, start adding items back to msconfig one or two at a time, rebooting after each change, until the problem reappears and you'll have identified the offending process. This is clearly a time consuming process, but it is the best way to determine if some process loading with the system is the cause of your problem.
Admin, Tweaks.com Forums
Share this topic:
Page 1 of 1

Help

Back to top









