Shutdown on it's own...

I've been having a problem with my MacPro. On occasion, I leave the machine to render overnight, but when I come back the next morning it is off. It is not scheduled to shutdown by itself. This morning when I came in, I looked at the log and found the following:
8/25/09 6:43:22 PM com.apple.loginwindow[36] Shutdown NOW!
8/25/09 6:43:22 PM com.apple.loginwindow[36] System shutdown time has arrived
8/25/09 6:43:22 PM com.apple.SystemStarter[29] Stopping HighPoint In-Band Management Server
8/25/09 6:43:22 PM com.apple.SystemStarter[29] Shutting down Qmaster processes
8/25/09 6:43:28 PM com.apple.SystemStarter[29] Stopping HighPoint RAID Management Server
8/25/09 6:44:11 PM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
8/25/09 6:44:11 PM com.apple.launchd[1] (com.apple.ODSAgent) Unknown key: SHAuthorizationRight
8/25/09 6:44:11 PM com.apple.launchd[1] (org.apache.httpd) Unknown key: SHAuthorizationRight
8/25/09 6:44:11 PM com.apple.launchd[1] (org.cups.cups-lpd) Unknown key: SHAuthorizationRight
8/25/09 6:44:11 PM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
8/25/09 6:44:11 PM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
8/25/09 6:44:11 PM com.apple.launchd[1] (org.x.privileged_startx) Unknown key for boolean: EnableTransactions
8/25/09 6:44:11 PM com.apple.launchd[1] (com.apple.AEServer) Unknown key: SHAuthorizationRight
8/25/09 6:44:11 PM com.apple.launchd[1] (com.openssh.sshd) Unknown key: SHAuthorizationRight
8/25/09 6:44:17 PM org.apache.httpd[27] httpd: Could not reliably determine the server's fully qualified domain name, using ::1 for ServerName
It seems the machine thinks it is scheduled to shutdown, even though it's not.

As a first step, try a SMC reset.
DALE

Similar Messages

Anyone know why my computer would shutdown on it's own?

So far it this has happened three times now. My computer for no apparent (at least not apparent to me) has shutdown on it's own. After the second time it happened, I took the tower into the Apple store and the mac genius at the genius bar suggested that I have the power supply replaced. Well the power supply was replaced last Friday and then today the computer shutdown on it's own.
I went into the console log and this is what I found:
Mac OS X Version 10.4.10 (Build 8R218)
2007-08-29 09:13:53 -0700
2007-08-29 09:13:57.876 SystemUIServer[195] lang is:en
.TWAINBridge-ERROR: DS does not support the required CAP_SUPPORTEDCAPS
2007-08-29 09:14:04.158 SecurityFixer[227] No insecure startup items found!
Does this mean anything to anyone? And if so could it explain why the computer shuts off on its own?
Or is there some other underlying problem? Any help or suggestions on how to fix this problem would be greatly appreciated.
Thanks!

eyevwhy,
I don't know what the actual cause is, but here are a few thoughts...
The sudden shutdowns may or may not be related to the Console messages you referred to in your initial post, which appear to me to be logged at start up time. It's unclear to me whether or not you are even experiencing kernel panics.
I'd urge you to disconnect the hub and external drive for awhile, along with any other peripheral attachments you may have connected, ruling them out as potential culprits if the condition still recurs.
Is the Mac otherwise a stock FW800 without any added PCI cards or other internal modifications/add-ins? If not, I'd look there next for a potential conflict. If you're hooked to a UPS, you should try bypassing it for awhile, connecting your power cord directly to the wall socket and seeing if the issue resolves. If you're using a third-party keyboard, it might also be behind the issue.
Is your line voltage stable? Brownouts can drop the line voltage to a point where the PSU might shut down. Excessive line voltage (uncommon) or line voltage spikes can also shut it down.
Overheating inside the tower may also a potential cause of sudden shutdown. Do all three fans inside the tower operate okay and is the inside of the tower relatively clean, particularly in the vicinity of the CPU/CPU fan?
Other things worth considering... How frequently does the shutdown occur? Does it occur shortly after startup or after the Mac has been running for a considerable length of time? Have you changed or added RAM lately? Does the Mac exhibit any other issues? Is there anything noteworthy contained in your system log like repeating device error messages, etc?
Gary

3000 n100 laptop shutdown on it's own

my 3000 n111 laptop keeps shutting down on it's own with no warning,,,have restored to facftory settings after getting battc.sys file corrupted message,,,bots fine but still shuts down on it's own sometimes.

As a first step, try a SMC reset.
DALE

Random, Sudden Shutdowns - A redux and other things to rule out first

Do a google search for "macbook random shutdown" and you'll find many people with similar problems reporting on various forums. At present, this issue has not been picked up by the mainstream PC news media. However, one should also note that only a fraction of those with problems are suffering this particular fault. A large number of other reasons must be ruled out before a MacBook owner should become convinced their machine is one which suffers this problem. Bad RAM, poorly seated RAM, improperly installed hard drive, corrupted OS, corrupted plists, bad batteries, bad chargers, corrupted PMU, and corrupted NVRAM all need to be ruled out first!
My own MacBook suffered the random sudden shutdown malady and eventually required complete replacement after a logic board replacement did not solve the issue. Some of the MacBooks appear to have a hardware problem which surfaces after a period of use. Many reported their problems starting after a month of ownership. Coincidentally, that also coincided with the release of 10.4.7, but most likely that is not at the root of the sudden, random, shutdown problem.
(However, 10.4.7 is strongly implicated in a separate MacBook problem - colored vertical lines during boot on some machines. That is probably a separate issue.)
Description of the Random, Sudden Shutdown Problem
MacBook suddenly shuts off to a completely powered down state seemingly at random. There are no kernel panic, mouse freezing, or other premonitory symptoms. The machine simply powers down suddenly. The screen goes black. The hard drive spins down and no sleep light illuminates. The machine simply turns itself off.
The shutdowns may occur on either battery or with AC adapter attached. Some owners report their MacBook is less prone to sudden shut down while on battery vs AC adapter. My own afflicted MacBook would suddenly shutdown on a fully charged battery or on either of two AC adapters.
The shutdowns occur with either 10.4.6 or 10.4.7 OS loaded. I went through several cycles of clean installs of the base 10.4.6 and the Intel Combo update to 10.4.7 before it became clear that it mattered not which OS was running. Another indicator that this is not an OS issue is that sudden shutdowns can occur in target mode and also when running just the Apple Hardware Test - which relies on minimal software to operate.
The shutdowns tend to grow more frequent once they begin. They may worsen to the point that a machine will not complete boot up before shutting down. It may take several power up presses to start the machine. Oddly enough, a machine that had difficulty starting up, may be easy to start up several minutes later. It may run for hours or minutes before another sudden shutdown. The frequency is low and random enough that is very difficult to demonstrate this fault to a service technician.
Some users are able to induce a sudden shutdown by running their CPU's at high load and thus heating up the machine. This is easily done by running the yes command in two Terminal windows. Some users report their MacBook is more prone to sudden shutdowns when their CPU is relatively cool. The bipolar reporting is confusing. There may be more than one type of sudden shutdown being reported. One due to CPU overheating and another due to another hardware problem which has yet to be elucidated.
Resetting of the PMU and PRAM MAY temporarily reduce the frequency of the sudden shutdowns, but the effect is temporary. Indeed, the effect may not even be real given the randomness of the shutdowns. None-the-less, one must perform PMU and PRAM resets to ensure that some corruption of those devices is not creating a reason for shutdowns. On my own MacBook, resetting PMU and PRAM (four chimes) did not prevent the random sudden shutdowns.
The sudden shutdowns occur with well seated stock RAM, replacement RAM, and reseated/replaced hard drives. Swapping out and testing both RAM and hard drive helps to eliminate those as the source of the problem. On my own machine, I exchanged the RAM and the hard drive to eliminate them as the cause. This made it considerably easier for the Apple genius to decide it was an internal problem.
In my case, a logic board replacement did indeed solve the fault, but several days later, sudden shutdowns began again. Presumably either the replacement board has the same weakness as the original or some other component of the machine was the actual reason for the sudden shutdowns. The former is quite likely because the machine was made stable for several days with a new logic board. At that point, I requested to be swapped to a new machine and the Apple Store manager wisely decided to help out his customer. For that I am most grateful. However, it is unlikely that the majority of people will have their machines swapped out, but instead repaired.
At this time, no official statement regarding cause for or acknowledgment of the MacBook's sudden random shutdown problem has been made. Because the underlying cause has not been revealed, it is impossible to know that a logic board replacement will permanently solve the problem or merely result in the same fault recurring later on the replacement board. Of course, we do not know if it actually is a logic board flaw.
My advice to MacBook owners whose machines develop the sudden random shutdown symptoms are to...
1. Get your data backed up immediately. The machine will likely suffer more and more frequent shutdown events.
2. Revert to stock RAM and hard drive if you have installed after-market replacements. You must do this and see if the shutdowns continue to occur. Otherwise, the first thing blamed will be your RAM and hard drive.
3a. Perform a PMU reset, by shutting down the MacBook. Removing the battery. Disconnect the AC Adapter. Then, press the power button for five seconds. The reinstall the battery and mains adapter. Restart the machine.
3b. Reset PRAM by holding option-command-P-R keys down during startup until you hear the chime at least three or four times.
Resetting the PMU and PRAM are standard procedures you'll otherwise be asked to perform to diagnose your machine.
4. Do a CLEAN install of the OSX if you wish to totally eliminate a bad OS install as the problem. This will destroy all your data. Alternatively, an archive and install will be helpful without totally destroying your data, but that will not let you exonerate your system files and settings. An alternative is to run Apple's hardware test utility which is found on your OS installation disc. However, an extended hardware test is needed because the shutdown flaw may take hours to surface.
Note: If your MacBook has become so "narcoleptic" that it cannot even complete a boot up sequence, try holding the power button down until you hear a loud beep. That may allow an otherwise balky machine to start.
Once you have done the above, and are still seeing random sudden shutdowns, you have largely done the preliminary footwork that you'll need to prove whether your MacBook has this particular problem and not something more common. Then, call AppleCare or visit your Apple Genius to have the machine repaired or replaced. Hopefully, the root cause of this problem will be discovered, disclosed, repaired and prevented. For now, it appears only a fraction of the MacBooks are suffering this fault, but the machine population is still young. Overall, the MacBook is perhaps the finest laptop I've bought from Apple. It will be nice to trust the machine to not lose my work.
BTW - resetting PMU may induce a separate 10.4.7 related bug which results in your MacBook exhibiting a white screen with progressively more numerous vertical color lines during startup. This appears to be fixable by resetting PRAM and then temporarily changing display resolution to something other than the current setting and then back.

thanks for the comprehensive info. i experienced this for the first time today. i bought my macbook the day they were released. the shutdown happenned for me after leaving my computer on overnight with no programs running. about two minutes into web browsing it shutdown. it then shutdown in the middle of restarts. i disattached power cord, external hard drive, dvd burner & ethernet & it powered up and has been working for about 20 minutes since.
this computer has really been a lemon. first my superdrive scratches the **** (just previewed this, i can't believe they sensor the h_ word?) out of discs, then the trackpad button becomes very hard to push. i've been working around those issues using an external dvd burner and mouse, but not sure how to work around sudden shutdowns. i haven't been able to send it in for repairs yet since i bought it cause i needed it's dvd authoring capabilities for a class i was taking, plus i wanted to make sure nothing else went wrong (self fulfilling prophecy?). i was planning on taking it on vacation with me, but guess i better pack my old ibook too (which other than a cd burner which sucked from the start, has been very reliable). i'll send in my macbook when i get back.
anyway, thanks for the info & advice! i'll back up my crucial data now.
white macbook, 2GHz, 1GB ram (factory installed) Mac OS X (10.4.7)
macbook Mac OS X (10.4.6)
macbook Mac OS X (10.4.6)

Random Shutdowns (Driving me crazy)

After owning my MacBook for about a month, just 2 days ago, my MacBook randomly shutdown right after I booted it up. Then when I went to power up again, it immediately shutdown after the ding start-up noise.
The shutdowns have gotten more frequent and sometimes I have to try about 3 power ups in order for it to stay on.
Just a note (but I don't think it's related) I installed Windows XP through Bootcamp yesterday, however the shutdowns had already been occuring a day or two BEFORE I installed it.
I am using upgraded RAM (2x512mb), however it's the RAM that Apple provided me with, and therefore I don't have the stock 512mb original RAM. It was already upgraded the day I got it.
Other than those two significant changes to my MacBook, nothing else is different.
Again, note that these shutdowns have occured after owning my MacBook for about a month. (I bought it at the end of July).

contact apple care. this is a relatively common problem. Either go to an apple store or send in your macbook and they'll fix it. It took them about two days to fix mine and I've had it back about a month now with no problems.

Solaris 10 shutdown sequence

Hi everyone,
I'd like to take control of Solaris 10 shutdown sequence, to run own process just after svc.startd ends (remounts rootfs read-only) and before system is halted. My process sends some data to serial port to shutdown UPS system. Unfortunately /sbin/rc0 script is executed too early and causes unclean shutdown.
Is this a method to take control of shutdown sequence?
Best regards.
Tom.

TomCP wrote:
The idea with patching OBP is very good but is it possible to work?I had tried a test of patching OBP 3.10.24 on a Netra t1-105. All it does is to write the string "Shutdown the UPS" to Serial Port A but it shows it is possible to patch OBP.
The built in power-off command was:
ok see power-off
: power-off
   0 (f005ead4) (f005e7b8) 64 ms 1 (f005ead4) (f005e7b8) 3e8 ms
;To test the changes first create a new word to output a string and then contain the first word of power-off, which in this case was *0*
ok : shutdown-ups
] cr ." Shutdown the UPS " cr 0
] ;Then patch the new word into the start of power-off:
ok patch shutdown-ups 0 power-offAnd test what happens when the modifed power-off is executed:
ok power-off
Shutdown the UPS
lom>To make the patch to power-off permanent, append to the end of nvramrc (the cd ttyb to device end lines were existing modifications)
ok printenv nvramrc
nvramrc =             cd ttyb
                      0 0 " ignore-cd" property
                      device-end
                      cd ttya
                      0 0 " ignore-cd" property
                      device-end
                      : shutdown-ups
                      cr ." Shutdown the UPS " cr 0
                      patch shutdown-ups 0 power-offAs a final test, executed a shutdown from Solaris and checked the test "Shutdown the UPS" string appeared:
# shutdown -i5 -y -g0
Shutdown started.    Tue Mar 11 01:02:55 GMT 2008
Changing to init state 5 - please wait
Broadcast Message from root (console) on netra-t1 Tue Mar 11 01:02:55...
THE SYSTEM netra-t1 IS BEING SHUT DOWN NOW ! ! !
Log off now or risk your files being damaged
# svc.startd: The system is coming down. Please wait.
svc.startd: 70 system services are now being stopped.
Mar 11 01:03:13 netra-t1 rpcbind: rpcbind terminating on signal.
SUNW,pci-gem0: Could not Establish Link -- Check if the cable is plugged in.
svc.startd: The system is down.
syncing file systems... done
Shutdown the UPS
lom>

Frequent Shutdown of Lenovo n100 3000 laptop

Hi,
I have had a lenovo 3000 N100 for the last 3 years. For the first year it worked pretty well, but since the last year it seems to shutdown frequently on its own. Just before it shuts down I can hear the fan whirring furiously. It seems its a heating problem but I could be wrong. I was wondering if others also faced something similar and if there is a solution to this?
Thanks for your help.
Regards

Turn your laptop over.
Remove the battery.
Remove the cover over the CPU heatsink/fan. (upper right)
Blow out any dust/debris with compressed air.
Dust builds up in the fins of the heatsink, and may cause overheating.

Ipod nano video firmware

I think the current v1.0.2 firmware is in need of an update, as this has caused me no end of problems with my ipod nano video, causing it to shutdown on it's own and then require switch to disk mode, to restore. Trouble is, each time I get it back to v1.0.1 firmware, as soon as it's connected to iTunes, it recognises v1.0.2 is available and prompts me to install (whether I have auto update checked or not).
With v1.0.2 I also have a problem after I've added songs as the ipod just switches to a black screen with the apple logo and it can't be used. Not much use for a player bought as a present for someone.
So c'mon Apple, do the decent thing and provide a firmware update to fix this problem, as it seems I'm far from being the only one having problems going by the forums here.

Send your feedback to Apple via the appropriate link.
iPod Feedback.
Also, when discussing the nano 3rd gen, it's always best to use the correct forum.

IMAC G5 shutsdown while in sleep

The computer shutdown overnight on its own. The back was warm and I could not restart the machine - no chime or screen response. The only thing I saw was an LED on a usb device turned on briefly. I unplugged the power cord waited a while and then got a chime, and the usb led but nothing more. After about 30 minutes it was quite a bit cooler and the machine booted and ran OK. Sometime later in the day it went to sleep and the fans started whining and it shutdown. I checked the console as recommended elsewhere and got a reason for the shutdown as -110. (I assume that indicates a power supply, which was replaced two years ago) The next day I disabled the shutdown mode and it remained on all night. Is there a way to be sure it's a power supply before buying one and finding out it's the logic board? The machine is 5 years old and has been trouble prone. Thanks.
tom

110 is the code for thermal problems, and it's either the power supply or defective caps. You can open the machine up and inspect the caps and you can also run DiskWarrior or TechToolPro if you have access to either.
You can also check the [LEDs|http://support.apple.com/kb/HT2831] to see what they indicate.

HT3964 Security Update 2014-002 version 1.0 Issues

My MacBook Air was working fine until the Security Update 2014-002 version 1.0 was installed on Apr 24, 2014. Ever since then, it goes into deep hibernation or shutdown/restart on its own. How would I resolve this without a TimeMachine backup? Thank-you.

Hey there MAK-SJ,
It sounds like your computer is going to sleep and/or restarting by itself after a recent update. I would start by checking to see if there are any Hot Corners that may have gotten enabled somehow with this:
OS X: When your Mac doesn't sleep or wake
http://support.apple.com/kb/TS5357
Your computer sleeps at unexpected times
Make sure you have not set a Hot Corner that tells the display to sleep, or the computer to sleep.
See the following related articles for this symptom.
OS X: If your computer screen goes black
Magnets in devices may cause computer to sleep unexpectedly
If this is not the case, I would use the troubleshooting from the Additional Troubleshooting section of the article down toward the bottom.
Thank you for using Apple Support Communities.
All the best,
Sterling

On start up my screen is black and the computer beeps 3 times

Last time I used my MacBook air the screen went black and the computer shutdown on it's own. On start up the screen remains black and the computer beeps three times intermittently. Does anyone know how I can fix the problem? Thanks in advance.

Send it to an AASP or Apple Store for repair.
(59858)

Setting Resource Manager to start at boot automatically

I am putting together a script to automatically install multiple vendor software packages for a test system. As part of that script, it would be nice to set the Resource Manager configuration to start at boot.
Is there a registry setting or equivalent that I can set (instead of providing manual instructions such as listed at Configuring the VXI Resource Manager to Run at Startup )?

Not sure how much detail you are looking for. I did this by setting up a start/stop script in /etc/init.d (chkconfig 345 91 10).
Since I still run the backend (database) as the ORA_OWNR and only run the webservice as root, I start this in a two step process.
the shutdown is a 3 step process because the node_manager gets left running until the stopall command is issued.
Code excerpt:
case "$1" in
start)
# Oracle listener and instance startup
echo -n "Starting Oracle: "
# Changed ses to run as root so that the webservice can bind to port 80 instead of port 7777
# Backend (aka ses database) still needs to run as ora_ownr, so start becomes a
# two step process
su - $ORA_OWNR -c "$ORA_HOME/bin/searchctl start_backend < /home/$ORA_OWNR/.tmp_passwd.txt"
$ORA_HOME/bin/searchctl start < /home/$ORA_OWNR/.tmp_passwd.txt
touch /var/lock/subsys/oracleses
echo "OK"
stop)
# Oracle listener and instance shutdown
echo -n "Shutdown Oracle: "
# mid-tier owned and stopped by root. backend owned and stopped by ora_owner
# node manager is left running by stop command (root), so a stopall needs to be re-issued
# after the database has come down.
$ORA_HOME/bin/searchctl stop < /home/$ORA_OWNR/.tmp_passwd.txt
su - $ORA_OWNR -c "$ORA_HOME/bin/searchctl stop_backend < /home/$ORA_OWNR/.tmp_passwd.txt"
$ORA_HOME/bin/searchctl stopall < /home/$ORA_OWNR/.tmp_passwd.txt
rm -f /var/lock/subsys/oracleses
echo "OK"
reload|restart)
$0 stop
$0 start
echo "Usage: $0 start|stop|restart|reload"
exit 1
esac

My song/ album-mixed up, missing contacts, wants verify my email passwords...all since last update...help

My song and album covers are mixed up, I am also missing tons of my contacts, my phone shutdown on it's own yesterday and it's been repeatedly asked me to verify my email passwords...all since last update...help

I have the same problems with emails and it has possibly cost me business. I deleted a load that I thought were from Facebook before noticing that the subjects were not always matching the content. I have since found out that emails were sent to me regarding some freelance work and as I did not reply they have gone elsewhere that I must have deleted because the subject said they were from Facebook.
it is still happening with emails received today.

MBP 2008 On Last Leg

I bought my MBP back in 2008 at my university because I was tired of PCs. I had a Gateway then two HPs, and finally my Mac and it's been the best ever. However, I'm currently starting to run into troubles and I think it might just be do to age. I've googled, youtubed, and searched for about every troubleshooting tip I can find and not really getting any answers except, "It's probably your hardware." So this makes things difficult because I am also currently deployed and I use my Mac to stay in contact with family and friends as well as take care of finances and occasionally take care of some work and schooling when I have the free time. If my Mac finally just stops working, I'm going to lose the capability of all that. Yes we have MWR, but its super small and almost always busy. Time limit on it is only a half hour. Now apparently I'm suppsed to call Support to try and have them help me figure it out, but they want to charge me $19 because everything on it has expired. It's almost 5 years old, of course its going to expire. Don't really know what I'm supposed to do besides order a brand new Mac, but don't really want or can afford to drop the cash. What else can I do? Some of the issues I'm having are:
Mac will restart or shutdown on it's own. Sometimes when it reboots I also get a gray failure screen. Time that it stays on varies to a couple hours to sometimes only twenty minutes.
Screen flickers now and then and then produces a very crappy image which I have to restart to fix.
The Mac is getting super hot in the top left corner near the ESC key. I've noticed it get warm before, but this is actually slightly painful to the touch. I rest it on a laptop cooler and have those fans on, but it's really not helping. Some troubleshooting tips have suggested this may be one of the reasons that I'm having difficulties.
My trackpad is non operational. It went out about 2 weeks ago and I was forced to switch to using a mouse. Took forever to disable the trackpad when a mouse was plugged in through Universal Access because I could not even click with the track pad by simple touch or by pushing.
And finally, it's just become downright slow. I don't have a lot of programs or anything on it, but when I first had it, started up and everything went smoothly. Now just even opening Safari, the icon will bounce for quite awhile before it finally loads.
Am I going to just have to pony up the dough or is there something Apple can do to help me out? Thanks.

Your MBP seems to be on its last legs, and it's hard to figure out exactly what the problem is.
Certain MBP models are eligible for extended coverage, and it's possible that your unit qualifies:
http://support.apple.com/kb/TS2377?viewlocale=en_US&locale=en_US
In any case, I'd visit your nearest Apple Store when you can. There are a few other potential issues you might want to investigate.

Satellite A135 laptop reboots on it's own following normal shutdown

My Satellite A-135 has begin rebooting on it's own after a normal shutdown. Running Vista with 1 GB ram, use Firefox 3.6 browser and all programs, Windows updates, anti virus, anti malware, etc. are kept up to date. I routinely run anti malware and Avira anti virus scans and keep my registry and temp files, etc. clean with CC Cleaner. Use File Hippo and CNET Techtracker to keep aware of new software updates. Also use Win Patrol to monitor what programs and processes are running so I don't think I have a malware or virus problem. haven't added any hardware or software recently. Laptop sits on a cooling fan pad so overheating is not a problem. I can turn it off by removing the battery or by pushing the 'off' button (off button results in a safe mode screen the next time I turn the computer on). Other than this new, aggravating problem the computer runs perfectly. I bought this laptop new a few years ago and am the only user. It has not been dropped or otherwise abused so I'm at at loss as how this happened...unless it's some kind of hardware failure. I haven't done a system restore to see if that helps and will await some expert opinions before doing anything. Any good solution from someone who's solved the same problem will be greatly appreciated.

You might want to try a power reset and setting the defaults in the BIOS.
Turn off computer. Unplug AC adapter and remove the battery. Press and hold
down the power button for 30 seconds.
Put battery back in, Plug Charger back in.
Power on the computer and hold down F2 to enter the BIOS. Load BIOS defaults by
pressing F9 then F10 to save changes.

Shutdown on it's own...

Similar Messages

Maybe you are looking for