Sudden shutdowns at a specific time

I have a Dual-Core 2x2.66 Mac Pro that has a strange sudden shutdown issue. I don't have any mixed RAM or anything like that. Nor do I have an PCI cards for expansion. The Mac just has a couple of Apple SATA drives internally and a few FireWire drives on it's ports.
I did a search but didn't find anything that duplicates my problem.
Basically the Mac does a sudden shutdown and reboot every so often with varying frequency (sometimes several times a week, sometimes once a week).
The odd things is that other than a rare exception, it always occurs at a specific time of day (8:41 am to be exact).
My first thought was that perhaps I have some software that is running an automatic, prescheduled function at that time and that is causing the problem. But a review of the software I have installed that I know does this type of thing reveals no prescheduled activities at this time. I have even tried to watch my Activity Monitor at that time and of course the times that I do so, the shutdown doesn't occur.
It seems to me it maybe software/system related, but I hesitate to go all out and wipe my system and reinstall everything because of the sheer number of Apps I have loaded (I do graphics and video work so I am running full suites of Apple and Adobe stuff as well as a bunch of other stuff).
I would certainly do so if I were sure that were the problem, but I don't want to do that if it isn't going to resolve anything?
I had a similar issue with an iMac, but that was not time of day dependent and occurred far more frequently - AppleCare replaced the power supply.
Any thoughts on the cause?
Thanks

As a test try deleting the /Library/Preferences/SystemConfiguration/com.apple.PowerManagement.plist file. You might also try booting into safe mode to see if that makes a difference. Also creating a new user account and logging into that account (log out of your normal account) may also be useful in troubleshooting this.

Similar Messages

  • Mid 2010 Macbook Pro 13" sudden shutdown with no errors

    I have a mid 2010 Macbook Pro 13" 2.66 GHz with 2x4GB of Crucial RAM, the original 320GB HDD and running OS X 10.10.1; however, this problem has already been bugging me back when I had Mavericks. For about a year and a half now my laptop would suddenly shutdown with a click sound. It first only did it about once every couple of weeks but now it'll sometimes do it within five minutes of turning it on. Sometimes it'll last a couple hours, and other times it'll last 5 seconds. It's not temperature related, because it'll do it whether it has just been turned on or been on for over an hour. I reset the PRAM and SMC, but that didn't fix it. I ran tests with Disk Utility and it said there were some issues with the disk. Disk Utility wasn't able to do it, so I repaired it with fsck in Single User Mode. I thought this was finally going to work, but within 15 minutes it shut down again. Finally I ran the Apple Hardware Test and put it through the extensive test. After it was done running, it said that everything was ok. So according to that there should be nothing wrong with the internal hardware. I would check in the console logs, and it would give me -2 and -60 for "Previous shutdown cause: ". At this point I have no idea what could be causing the problems.

    I took it in to the Genius Bar over the weekend, and they ran their tests on it. It passed with flying colors; including the battery, which is doing quite well for its age. So with that being said, they said that the problem is probably with the logic board since everything else came back ok. At this point, I am better off investing in a new computer since a new logic board goes for $400 without labor, and that is if the problem really is only with the logic board since that was their best guess, not definitive.

  • 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)  

  • Sudden Shutdown of iMacs with 16GB of RAM

    An ongoing discussion of iMac shutdowns over at Apple Discussion has prompted me to try to get some answers to this issue that we too are seeing in one of our i5 iMacs with 16GB of 3rd Party RAM.
    http://discussions.apple.com/messageview.jspa?messageID=13311466&stqc=true
    Recently we found that the issue could be repeated when transforming a layer in Photoshop CS5. Dragging the image around, resizing it a few times will consistently cause a sudden shutdown of the machine. Not a standard shutdown or kernel panic, but an instant off to black screen. The machine will boot right back up with no problem.
    Further, we also found that this would occur when the Photoshop tile cache size was set to 128k. Setting it up to 1024k seemed to get rid of the issue and we were never able to recreate the issue when set to 1024k tile cache.
    Now I would think to blame Photoshop, but it happened in CS4 and CS5. It also has happened in other apps as well. It just so happens that Photoshop
    is doing something that exacerbates the issue and triggers it.
    Now, my question is this. And it is rather technical in nature, so if any Adobe techs are reading this, I would love your take on it.
    I'd like to know what is going on in terms of data exchange between, RAM, video card or swap space when an image is being transformed.
    Does the change in the tile cache size change how large the chunks of data are that are cached to the video card as well?
    I'm wondering what the change in tile cache size could possibly be changing that could alleviate this issue.
    There are also a number of reports that say removing 4 or 8 GB to leave 12GB or 8GB configs alleviates this issue as well. Do machines with smaller RAM configs exchange data in different size blocks?
    I hope this all makes sense. Any info would be appreciated.
    Scott

    Not a standard shutdown or kernel panic, but an instant off to black screen.
    That means that you have a hardware problem, probably in the RAM, but possibly in the motherboard.  (having inadequate power supply to the RAM is a common problem that causes this - could be a bad capacitor, or a bad design)
    An Apple technician should be able to put a scope on the power and signal pins of the RAM and see the problem happen (looking for a capacitive discharge pattern in the signals, dropping below signal threshold).
    Changing the tile and cache size just changes the RAM access pattern slightly, but doesn't affect GPU usage much.
    Yes, Photoshop moves a lot of data in and out of RAM with highly optimized code - which tends to expose problems with the hardware sooner than other applications.

  • Not able to jump to a specific time on a music track (time slider has disappeared!)

    I don't know how it happened (update of iOS version?) but the time indicator saying how far into the music track as well as the time slider allowing me to 'scratch' to a specific time have both disappeared.
    Only the volume slider remains! How can I reinstate the time feature?

    thanks... i suddenly feel rather silly. although i swear i tried everything previously and it didn't work. oh well.

  • The scheduled time "Do Not Disturb" suddenly stays on all the time

    I set up my Do Not Disturb for specific time frame. It worked fine for months, coming on at 10pm going off at 8am. Suddenly last week I noticed it stayed on all day!
    No matter what I do it does not automatically go on and off now. I've tried turning my phone on and off, but that is no help.

    See here:
    http://support.apple.com/kb/TS4510

  • Suddenly shutdown for very hot

    My laptop suddenly shutdown for heatsink very hot. Right now what can I do. Pls help me.

    JahangirIT wrote:
    My laptop suddenly shutdown for heatsink very hot. Right now what can I do. Pls help me.
    Hi,
    What were you doing at that time ? Can you restart the machine now ? What is your machine and its OS ?
    Regards.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • Delayed shutDown of server, set time?

    Hello,
    I have a macmini server and when I shut down the server it times out because I run VMware Fusin with 3 Linux VMs
    and it takes about 1,5minutes to suspend.
    Is there a way to specify the system to wait at least 120sec before shutting down?
    Sincerely,
    DB

    I'm not sure if the -t switch works in OS X, but it would be like this from the command line:
    sudo shutdown -s -t 120
    Or at a specific time:
    sudo shutdown -s -h 21:15:00
    The -f switch forces running applications to shutdown, but again I'm not sure if that switch works in OS X:
    sudo shutdown -s -f -t 120

  • Sudden Shutdown - X200

    I am running Windows 7 on my X200.  Just recently I have experienced a new issue with it - it suddenlty shuts down for no reason.  I don't mean gracefully, but as if you pulled the battery and disconnected the power.  It has done it while running on battery and while plugged into AC.  Frequency so far is just a couple of times over the last week or so, and twice in the last couple of days.  Anyone have any ideas at what I could look at to check this?  Thanks.

    I ordered the X200 with Windows 7, online from Lenovo on Dec 9, 2009. Received it on Dec 24, 2009 evening. I understand exactly what you mean, sudden shutdown with no reason.  The cursor/ mouse was frozen and shut down suddenly. I have to reboot this new machine all the time. I  called the tech support the day I received. I was told to send it back to fix. I have to wait for the box, so I can ship it for repair. I tried to call local warrantee service providers. They said it takes time to just look into it and takes time to get parts. I waited until Dec 28, 2000 to called the tech support again (it was holiday weekend). The support tried to help, telling me to run the recovery. After the recovery was run, same result. It keeps shutting down. I was told that if I send it back it will take 2 weeks to return to me. So, it will be 4 weeks before I get a working laptop, if when it comes back and works. So, I decided to return. I was told that they will charge me the restocking fee for this non working laptop. I spoke to the supervisor. He investigated the case that I called. He agreed to give me full refund to return it. I have to see whether I actually received the full refund.  I will update whether I get full refund.
    It took at least 30 min wait time for each call.

  • Sudden shutdown when working on battery mode, clock reset

    Hi
    i am running windows 7 32 bit on an HP dv6970ej (dv6000) and my problem is sudden power failures when working on battery.
    my first battery was worn out a few months ago and so I replaced it (with an HP original). it worked fine for a while but lately when I am working on battery mode the system shuts down with no warning.
    the thing is that when I plug it back to the AC the battery is almost full - 85%-90% charged.
    also - the last few times the power went down the clock was reset. i replaced the BIOS little battery but that didn't seem to make much difference. 
    i also tried to update the BIOS, didn't change anything.
    the main issue of course is the system shutting down unexpectedly, while the battery is obviously still holding charge.
    any suggestions?

    the clock reset is just a side effect of the main issue - system power failure. as long as there are no sudden shutdowns the clock is saved. plus i guess i am not gonna replace the whole motherboard so that's why i am less concerned about that.
    what really bugs me is not having the ability to disconnect the computer from the AC for more that a few minutes. sometimes it shuts down after two minutes, sometimes after 10-15 min.
    i am thinking- maybe it has anything to do with voltage drops or something like that or incorrect reading of the battery, because as i said - when i plug it back in - in indicates 80%-90% charge level.
    I also ran a diagnostic on the battery's wear level. the old battery was definitely worn out, but the current one seems to be OK on that aspect.

  • Satellite L855-10P - Sudden shutdown playing 3D games

    Hello,
    When trying to play 3D games, after more or less time playing, often less than 10 minutes, my Satellite will suddenly shutdown. Afterwards, it can't be booted up again before some time.
    This sort of symptom is generally due to overheat, a common problem with Satellite laptop (and by the way, this is probably the last Toshiba I buy since they can't seem to get that fixed).
    The usual solution is to remove dust from inside the laptop, for example with a gentle vacuum cleaner.
    It is impossible to do correctly without opening (and voiding the warranty) since they didn't put an access to the fan and heatsink, put can help once in a while.
    On this model however, the exhaust is block by a grid (part of the heat sink I suppose, which makes sense) and on the intake, the fan is blocked so that it can't turn in the opposite direction, meaning it is almost impossible to s*ck the dust. Result: almost impossible to remove dust. Well played.
    So normally I would send my laptop back for "repair" (which is just opening the thing to remove the dust and maybe redo the thermal paste, but you can't do that yourself of course), but in this case I noticed it shutdown really quick.
    I can leave it on a 2D game or old low quality 3D games (say Supreme Commander in low quality mode) for hours without problem, even in hot weather, but as soon as I try a newer game (for example Resident Evil 6, even in low quality) it shutdown pretty fast and without feeling so hot.
    So I am wondering if maybe this time it would be a problem with the graphic card/driver. Let's say something like a command than crash the graphic card.
    I have a AMD Radeon HD 7670M with the driver version 8.932.5.3000 (the only one available for this computer and Windows 7 64 bits on the Toshiba website).
    Is there a know issue that could cause the graphic card to crash or overheat more than expected with this model?
    (If you wonder why I didn't wrote s*ck in full letter, it is because the profanity filter on this forum don't think it is a word that can be used in normal conversation.)

    >When trying to play 3D games, after more or less time playing, often less than 10 minutes, my Satellite will suddenly shutdown. Afterwards, it can't be booted up again before some time.
    To me it sounds like a GPU has operated at full capacity and produced lot of warmness leading to high internal temperature.
    In my eyes the unit shut down due to the high temperature.
    The notebook supports a kind of hardware protection. The unit will shut down automatically to prevent the hardware from damage.
    Dust and debris might be one of the reasons why the parts cannot be cooled down properly.
    >This sort of symptom is generally due to overheat, a common problem with Satellite laptop
    This sort of symptom happens to all notebooks worldwide because of air circulation.
    >I can leave it on a 2D game or old low quality 3D games (say Supreme Commander in low quality mode) for hours without problem, even in hot weather, but as soon as I try a newer game (for example Resident Evil 6, even in low quality) it shutdown pretty fast and without feeling so hot
    Running games on low quality does not stress the GPU a lot and this lead to low heat dissipation and low temperature.
    >Is there a know issue that could cause the graphic card to crash or overheat more than expected with this model?
    I dont think so mostly such issues can be resolved by changing the settings within the windows power options (decreasing the CPU/GPU performance, change of cooling method) and of course within the game settings (low details, etc)

  • How can I automatically have the XRAID turn on and off at a specific time?

    Hi Everyone,
    I was wondering if anyone can help me figure out how to turn on and off the XRAID at a specific time. My electrical bills are crazy. Is there a way to get this done?
    Thanks,
    Jorge

    Hi Everyone,
    I was wondering if anyone can help me figure out how
    to turn on and off the XRAID at a specific time. My
    electrical bills are crazy. Is there a way to get
    this done?
    Thanks,
    Jorge
    I think turning the RAID on and off periodically is a bad idea. But if you really really really want to do this ....
    Connect the xserve raid to a 'metered power strip such as those provide by APC. you can telnet to the power strip via the network to power off individual port)
    write a script (run on the xserve or powermac that the RAID is connected to (direct or via switch)
    0) quit application (issue a quit command or if the application have a stop command (example databse can be stopped)
    1) unmount volume (must)
    2) issue a telnet command via expect script to control the power strip to power off the array.
    If you have java cli access to the array (see alienraid.org).(I have not tried this before.)
    http://alienraid.org/article.php?story=xserveraidtools12&query=command
    You can issue a command to execute the RAID admin shutdown command.
    Put the master script into a unix cron job.
    macbook pro   Mac OS X (10.4.7)   typing this on a white box pc

  • I was charge my MacBook pro , and suddenly shutdown him self , and I cannot switch it on again ???

    I was using my MacBook Pro , and same time I was plug it to charge , and suddenly shutdown himself , and at this time the battery was 80% , and I try many times to switch on again , but I cannot , I has this problem for almost two days now ,  I'm really worry about it , and I need to open it fast because all my work in there .
    Please I need your answer fast .
    Thanks

    Seems you might have a hardware problem. Like the Logic board has failed. your best option is to take the system to an Apple store to have it properly diagnosed as to the problem.

  • Sudden shutdown of MBP while on battery power

    I have started experiencing sudden shutdowns after being on battery power for 15 minutes. So far this has occurred while using Safari and Photoshop CS3. When I have checked the system log file, it has indicated "Previous shutdown cause: -103"
    I have searched the web for this code and not found it yet - does anyone have an idea as to what this could refer to or what the issue might me? this is a 2008 MBP (purchased in August, 2008)

    Those figures actually look fine, ze red baron.
    At a maximum capacity of 5315mAh it is still at around 95% of original maximum capacity. Very different from what I expected when I wrote my earlier post!
    It is possible that the figures are somewhat misleading if you haven't calibrated it in recent times, though. See http://support.apple.com/kb/HT1490 for the process.
    You should also reset the SMC - see http://support.apple.com/kb/HT3964.
    Remove and replace the battery, too.
    I am wondering, though, if the battery is as good as the figures currently indicate, whether something else may be involved here. Has it ONLY shut down when using the programs you refer to, or is happening generally, regardless of what is running?
    Cheers
    Rod

  • How to address a specific time in VOD for iOS

    Using Flash and RTMP it's easy to go to a specific time in a VOD stream served from AMS using the seek method.
    Is there similar ability to seek to a specific time in VOD delivered to Safari on iOS?  The native video player provides a currentTime method, but I've not seen documentation anywhere to suggest currentTime or another method to provide rapid and accurate time based access from AMS.
    FWIW, Wowza documentation provides an answer:
    http://www.wowza.com/forums/content.php?326-How-to-specify-a-play-start-time-and-duration- for-HTTP-streaming
    TIA,
    RT

    Nitin, the link you provided is a bit better than nothing, but it refers to the AVPlayer object in applications, rather than iOS delivered data.  In our experience currentTime is a settable property for the native video player in mobile Safari, using a normal progressive uploaded stream, as the documentation shows:
    http://developer.apple.com/library/safari/#documentation/AudioVideo/Reference/HTMLMediaEle mentClassReference/HTMLMediaElement/HTMLMediaElement.html
    The question is "Are there browser based methods that seek AMS delivered streams more quickly or with better accuracy?" 
    Everyone is aware that mobile is exploding.  On some of our videocentric apps the share for iOS is approaching 20%.  PM Kevin Towes, what are you doing to accomodate this need???

Maybe you are looking for