Random Shutdown and Previous shutdown cause: -x2

Hi,
I had twice "random shutdown" for now. My MacBook is about 4 month old and It happend with about 3 weeks between them.
I tried stress testing it with 'yes >/dev/null' heating it up and cooling it down several times but I could not reproduce the Problem. However, looking at older system.log files, I found the "Previous shutdown cause: -82" lines in there. My question: Some MBs seem to report -72, others -82 as the shutdown cause known as random shutdown but what actually is the difference? Is it possible to guess the time it will take to get it repaired depending on the shutdown cause (which obviously describe two different conditions)?
Thanks a lot in advance and sorry for my somewhat clumsy english;-)
Peter

I don't know where you are in Austria, but I took my RSD macbook to mcshark in Vienna, and they repaired it, replaced the case, and returned it to me in one day. That was last Friday and it's been working great since. They knew all about the heat sink problem, didn't even ask for my user name or password, left my hard drive completely intact - they were absolutely super.
If you are anywhere near Vienna, call McShark and make an appointment - they'll repair it quickly for sure.

Similar Messages

  • "Ignore Sessions During Shutdown" and "Graceful Shutdown Sequence"

    Hi
    I have J2EE application consisting of WEB and EJB layers deployed on WL 8.1
    I start the Graceful Shutdown Sequence with Ignore Sessions During Shutdown option set. sessionDestroyed() method of registered HttpSessionListener is fired but at this moment JNDI tree is already empty, EJB module undeployed and the listener is not able to get to application's EJBs.
    In the documentation (http://e-docs.bea.com/wls/docs81/adminguide/overview_lifecycle.html#1045901) Ignore Sessions During Shutdown option is explained as follows:
    "If you enable this option WebLogic Server will drop all HTTP sessions immediately, rather than waiting for them to complete or timeout."
    What does "drop" mean here? Is this some exception to Graceful Shutdown Sequence and the following excerpt from the documentation? : "During a graceful shutdown, subsystems complete in-flight work and suspend themselves in a specific sequence and in a synchronized fashion, so that back-end subsystems like JDBC connection pools are available when front-end subsystems are suspending themselves."
    Regards

    Hi,
    You can use tcodes
    SMQR --> To register a queue
    SMQS --> To register a destination in Queue Schedular
    SMQ1 --> OutBound Queue Details
    SMQ2 --> Inbound Queue Details
    SXMB_ADMIN --> Manage Queue to register,deregister and activate the queue.
    Check the link for more details : http://help.sap.com/saphelp_nw04/helpdata/en/59/d9fa40ee14f26fe10000000a1550b0/frameset.htm
    For step details for server start/stop you can search on google for more details. And for an idea check the section Managing the SAP Start-Up Service via the SAP MMC Snap-In in the link https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3e3fad90-0201-0010-2f91-c8907db40bfe
    Thanks!
    Edited by: sudhir tiwari on Nov 12, 2008 12:00 PM

  • Aug 10 18:34:08 localhost kernel[0]: Previous Shutdown Cause: -72??

    I am having the random shut down problem, and I am wondering what this:
    Aug 10 18:34:08 localhost kernel[0]: Previous Shutdown Cause: -72
    means.
    Specifically the "-72" part
    (It appears in the console after I restart after the random shut downs...)

    I was having the same problem and all of my codes were -72. However, I noticed that when I shut it down myself, the codes were also -72. In other words, there was no distinction between random shutdowns and intentional shutdowns.
    Since I got mine back from repair on Wednesday, my codes are now 3 or 0 when I shut it down myself. (I haven't tested this out, but I think they are 3 when I use the power button to shut down, and 0 when I do it via software.) Haven't had a random shutdown since getting it back (knock on wood). Also haven't had a code -72 since.
    It would be interesting to know if anyone who ISN'T having random shutdown problems is getting a code -72.

  • Please Help with Shutdown and Next Steps

    Hello,
    In the process of trying to back the Lacie External Hard drive which has 50 + gigs of valuable information, the computer locked up and it had to be shutdown. The power was turned off and turned back on. I purchased Disk Warrior and was able to regain access to all of my files. I then went to backup the disk. Itunes was open with nothing playing and mydesktop went blank. Everything on the computer was acting funny. I could not close itunes (it kept coming back) nor would things open. I also can not shut down the computer and the external drive is still connected so Im afraid it may do irreparable damage if I shut it down hard. Mac even identified that it needed to shutdown and said (Shutdown in 60 seconds, counted down and nothing happened). Can someone please advise me on my best course of action to try and cleanly shutdown the computer and reboot (Hopefully, it will remount the desktop). I am fairly new to Mac's so I would appreciate any help I can get. thanks.
    Scott

    Hi Scott, not a warm fuzzy feeling I'm sure. So you were backing up your mac and POOFF!!! Everything from there was all screwed up....Did I get that right? The first thing I would do is insert the install disc and restart the computer..If you have to shut it down by holding the power button...do it. Restart and hold the "C" key down after you hear the tone and release it when you see the Apple logo. Choose your language and when the install screen comes up choose "Utilities>disk utilities"....Repair Disc and then repair permissions. Close and quit installer.
    The data on your computer should have been untouched by the back-up operation. It is just copying your Macintosh HD to the Lacie. What program were you using??? In the future you can open the activity monitor located Applications>Utilities>Activity Monitor and select Active processes ---if it opens in your dock but not on your desktop, click the dock icon---this will show you what is working at the time and if its not responding. ---Just because its not responding doesn't mean its locked up. But from here you could have chosen the iTunes that would not quit and forced it to quit...same with any program running--BE CAREFUL WHAT YOU SHUT DOWN--if you don't know what it is leave it alone or get on the web and find out.
    There are many more things that could be the problem but try these first and get back I'll try to get ya going...
    Good luck, glynn

  • Previous Shutdown Cause: 0

    I'm investigating on my Mac Pro2,1 randomly shutdown, and I discovered the concerning log in Console: "Previous Shutdown Cause: 0"
    Does anybody know what this "Cause: 0" means??

    The most frequent cause of uncontrolled power-off (not controlled shutdown) is overheating.

  • Kernel: Previous Shutdown Cause: -128

    i have macbook pro OS X10.7 2011 15´
    it goes off unexpectedly after a period of time ( usually 30m) i look at the console and look ''the word shut'' up
    and i found this . which i have no idea what it means.
    6/20/14 1:15:31.000 a.m. kernel: Previous Shutdown Cause: 5
    6/20/14 1:44:46.000 a.m. kernel: Previous Shutdown Cause: -128
    6/20/14 2:14:51.000 a.m. kernel: Previous Shutdown Cause: -128
    6/20/14 2:19:04.498 a.m. shutdown: halt by TemochePeralta:
    does any one know what this means ? please help !

    Did you get a resolution ? My 1 month old iMac started to have the same issue. Shuts down randomly and I can't figure out why. I've noticed so far that it has done so when I'm not using it. For example I turned it on, work on it for few minutes and it works fine, I walk away for few minutes come back and it's off. And no it's not in standby mode it is completely off. Same thing happened to me few times already. I could be using it for few hours leave it and then when I come back minutes or hours after it's off. I'm getting the Previous Shutdown Cause: -128 code as well... I'm going to speak to apple support tonight and see what can they tell me about it.

  • Kernel: previous shutdown cause: -60

    My MacBook Pro stopped and started starting up randomly. I went and looked at the console and it said kernel: Previous Shutdown Cause: -60. Please help me I want to make sure this isn't serious.

    So I called Apple. Turns out this can sometimes happen (Kernel errors). So they walked me through resetting my kernel and from there they said to just watch it and if it happens again then they will walk me through running some more tests on it.

  • Consulte message: "previous shutdown cause: 5"

    My system has been shutting down randomly for the past several days. I'm trying to determine whether it's due to the Mac or to the peripherals. I brought it to an Apple store to have diagnostics run. They ran OK but one of the store "geniuses" checked the console messages and found this repeated message sequence, but couldn't interpret it:
    DirectoryService[35] Improper shutdown detected
    kernal systemShutdown false
    kernal Previous Shutdown cause: 5
    What does "shutdown cause 5" refer to?

    A shutdown cause of 5 is usually an OS-initiated shutdown.
    It results either from pressing the power button and then clicking 'Shutdown', or selecting Shutdown from the Apple menu.
    Shut your computer down normally, then power back up and look in Console.
    0 and 2 can indicate power loss, usually anything that's negative, like -128 or -60 is abnormal.
    If it's heat or battery related, you'll have a different code. The fact that it's showing up as 5 makes me wonder if the computer is experiencing a sudden loss of power...is it a laptop?
    A disclaimer: the codes differ slightly between models, I'm speaking from my experience, but Apple doesn't publish the meaning of the codes, so there's not a good way to be certain.

  • Random Shutdowns and Logs

    Like some others, I have started having random shutdowns and some high fan activity. So I can probably guess that it is the power supply.
    However, in previous posts on this topic, some have suggested checking a couple of different acitivity logs that exist somewhere on everyone's Mac.
    My question is...what logs might they be, and how does one find them?
    Thanks for any assistance....
    CHUCK
    iMac G5   Mac OS X (10.4.8)  

    Hi Chuck--
    But is there a log that would show me why the
    computer randomly shutdown?
    Shutdowns and going to sleep are two different things. If your power supply is starting to fail, your computer will periodically just shutdown completely. Sometimes, the fans will run faster, but often, they won't. If this happens, you can find it out by looking at the system log right after you reboot, or by typing a command in the Terminal application. Terminal is found in your Utilities folder. You would just open it and type the following command, followed by the "enter" key:
    <pre class="command">sudo dmesg | grep shutdown</pre>Unfortunately, those codes are not published anywhere. However, my iMac G5 has shut off a couple of times due to the UPS inexplicably draining its battery. The last time was Sunday night, and here's the code I get from that command (you'll have to type in your password when it asks):
    <pre class="command">AppleSMU -- shutdown cause = -110</pre>I've also seen -118 and -122 as the error codes. I think the latter came when I had the same random shutdown problem. You can also find the same information in your system log, using the Console application. However, it's mixed in with a whole bunch of other stuff, so it's harder to find. You can use the little search window at the top right of the Console app to help you narrow it down. If your system has been on overnight since it last shut down, you may need to look at an older log, so look at the one marked system.log.0.gz for yesterday, and so on, where the larger the number in the name, the older it is.
    The second problem is that the computer overheats and puts itself to sleep. This is, fortunately, easier to find in the logs. Once it cools down a bit and you can get it running again, use the Console application and see if you see lines much like this:
    <pre class="command">May 28 10:49:08 localhost kernel: Thermal Manager: max temperature exceeded for 30 seconds, forcing system sleep
    May 28 10:49:08 localhost kernel: SMUNeo2PlatformPlugin core dump:
    May 28 10:49:09 localhost kernel: IOHWControls:
    May 28 10:49:09 localhost kernel: [0] "System" Type:"fan-rpm" Id:0 TGT:1343 CUR:1343
    May 28 10:49:09 localhost kernel: [1] "Hard Drive" Type:"fan-rpm" Id:2 TGT:1929 CUR:1919
    May 28 10:49:09 localhost kernel: [2] "CPU" Type:"fan-rpm" Id:1 TGT:4400 CUR:4401
    May 28 10:49:09 localhost kernel: [3] "sysclk slew" Type:"slew" Id:256 TGT:1 CUR:1
    May 28 10:49:09 localhost kernel: IOHWSensors:
    May 28 10:49:09 localhost kernel: [0] "CPU Power" Type:"power" Id:5 CUR:12.2119 W
    May 28 10:49:09 localhost kernel: [1] "CPU T-Diode" Type:"temp" Id:0 CUR:85.38558 C
    May 28 10:49:09 localhost kernel: [2] "CPU Current" Type:"current" Id:1 CUR:1.15552 A
    May 28 10:49:09 localhost kernel: [3] "CPU Voltage" Type:"voltage" Id:2 CUR:11.64384 V
    May 28 10:49:09 localhost kernel: [4] "Hard drive" Type:"temperature" Id:4 CUR:54.0 C
    May 28 10:49:09 localhost kernel: IOHWCtrlLoops:
    May 28 10:49:09 localhost kernel: [0] "Clock Slew" Id:0 MetaState:1 "Force Reduced Speed"
    May 28 10:49:09 localhost kernel: [1] "PowerMac8,1 B System Fans" Id:1 MetaState:0 "Normal"
    May 28 10:49:09 localhost kernel: [2] "CPU Fan" Id:2 MetaState:0
    May 28 10:49:09 localhost kernel: ---------------------------------</pre>Your output could be somewhat different, since this is the log from an iMac running 10.3.9, not Tiger.
    If you see this error, the fans can't get enough cool air flowing through the interior of the computer. Some people have reported that they've had success in fixing it by carefully cleaning out the vent holes at the bottom of the iMac, so air flows freely again. They've reported that pet hair or dust can get in there and clog it up.
    On the other hand, this log is from a replacement logic board on that iMac. When I showed the techs that log, they didn't even bother with any tests, other than look to see if the interior of the computer was dirty (it wasn't) before they decided to replace the logic board as a defective.
    charlie

  • "Previous Shutdown Cause" codes?

    Hi -- My MacBook has been experiencing some problems.. intermittently shutting itself down, and getting worse & worse until I couldn't even start the laptop up. I believe the problem was a faulty memory module (3rd party, installed myself) -- after replacing the original Apple memory I haven't experienced any problems.
    In the system.log, I see this message after a system failure & crash:
    Jul 8 18:46:51 localhost kernel[0]: Previous Shutdown Cause: -82
    Does anyone know what this code means?
    thanks,
    Jon
    MacBook   Mac OS X (10.4.7)   (previously 2G ram)

    Sorry to hear that. Hopefully they will just give you a new machine.
    Be sure to do the following:
    1.) Try to exhibit the problem. Mine shut down three times in the store. The last time it shut off at home, I left it alone, boxed it up and took it in to the genius bar. We booted and viola! It shut down within a couple minutes. Then it shut off during boot. Then we powered it back on and it booted but shutoff within a few minutes.
    2.) Open console.app and go to /var/logs/system.log[number]
    Click on each one of these logs, hit control-R to load the whole log, and filter on "Previous" for Previous Shutdown Cause. This will show the genius exactly when the problem started and how often.
    3.) Be FIRM (not argumentative) and insist on having a new macine. Tell them you are very disappointed in having a brand new machine fail. Talk to a manager if necessary. I didn't have to ask twice. Apple knows this is a problem (unofficially), though the knowledge may vary from Apple Store to Apple Store and genius to genius, BUT it is known and you can reference the vast number complaining on this very board.
    Good Luck!!!
    BTW, my replacement week 24 machine have been running fine since I received it July 6. No problems yet.

  • Previous Shutdown Cause: 3

    Does anyone have any clue what this means? I don't understand computer-speak. My MacBook shuts down unexpectedly if it is left inactive for more than a couple minutes--sometimes the fan is running, most of the time it's not. Sometimes there are active applications, sometimes there aren't. Sometimes it's plugged into the adapter, sometimes it's on battery. Nothing is consistent except the fact that I can't walk away for 2 minutes to answer the phone or get a snack without returning to a shutdown computer.
    Help!
    Thanks.
    Here's what the system console says when I search for the term shutdown:
    Sep 5 14:30:56 localhost kernel[0]: Previous Shutdown Cause: 3
    Sep 5 15:13:18 localhost kernel[0]: Previous Shutdown Cause: 3
    Sep 6 09:16:26 localhost kernel[0]: Previous Shutdown Cause: 3
    Sep 6 09:17:58 localhost kernel[0]: Previous Shutdown Cause: 3
    Sep 6 12:42:08 localhost kernel[0]: Previous Shutdown Cause: 3
    Here are my specs:
    Model Name: Mac
    Model Identifier: MacBook2,1
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2.16 GHz
    Number Of Processors: 1
    Total Number Of Cores: 2
    L2 Cache (per processor): 4 MB
    Memory: 1 GB
    Bus Speed: 667 MHz
    Boot ROM Version: MB21.00A5.B06
    SMC Version: 1.17f0
    My Macbook was purchased in mid August 2007, and it runs 10.4.10, so the earlier firmware problems shouldn't be the problem. I would call Apple Support, but I'm in the Middle East, so wherever I call will be long distance. I'm trying to resolve this problem independently. It will be a tremendous inconvenience if I have to travel to Rosh Haayyin (near Tel Aviv) to take it to an authorized repair location...or worse ship it back to the U.S.

    If you can get it to run long enough, try running your hardware tester. It sounds like it may be going into 'thermal shutdown.' You may have a thermal sensor acting up.
    -Bmer
    Mac Owners Support Group
    Join Us @ MacOSG.com
    YouTube.MacOSG.com
    iTunes: MacOSG Podcast
     An Apple User Group 

  • What does this mean? Aug 26 12:30:02 Tegans-MacBook-Pro kernel[0] Debug : Previous Shutdown Cause: -60

    My MacBook has been running really slowly lately so I followed username Link's advice to open the terminal and see what message comes up after I input the code that he gave. The message that came up was : Aug 26 12:30:02 Tegans-MacBook-Pro kernel[0] <Debug>: Previous Shutdown Cause: -60
    What does this mean?
    I've deleted all large files and apps that were taking up room. My computer is down to the bare minimum now.
    Any help would be appreciated.

    Have you already verified/repaired the hard disk with Disk Utility? If not, do so.

  • Previous shutdown cause

    Ever since i tried an old ubuntu live cd with boot camp today, my previous shutdown cause on startup has been listed as 3, it has always been 0 before this.
    One thing to note as the ubuntu live cd locked up on restart, so I had to power off, but after several reboots/power offs it still sais:
    Jul 5 12:44:16 localhost kernel[0]: Previous Shutdown Cause: 3
    when booting up?
    Does anyone have a table of what the different shutdown causes are? (I'm not noticing any difference in how the system is behaving)

    I don't have an answer to your question, but do have another instance of it; and I'm still in shock as my MacBook just crashed!
    I have just experienced the "black veil of death"--an opaque black screen descended over my computer and said I had to re-start. When I checked the system log I too had the message:
    localhost kernel[0]: Previous Shutdown Cause: 3
    Can anyone shed any light on the possible cause of this previously unknown event (an OS-X system crash)?! James

  • Previous shutdown cause: -128 MacBook Pro 2008

    What does this mean?
    How do I stop this from happening?
    So far today this has happened over 15 times in the past 2 hours.

    Hi Baltwo!
    Previous shutdown -128 happening on a 2.1GHz MacBook running 10.5.8, too.
    Machine actually puts up the same "Are you sure you want to shutdown..." dialog box you get from pressing power button, with barely enough time to hit Cancel - if you're paying attention. Turn your back for an instant, and you'll miss it. Do nothing = off.
    Completely random. Battery in good condition and at 100%, AC adapter plugged in and OK, replaced OS (A&I), Reset PRAM, SMU..... sure would like to know what -128 means! Only happens when left unattended for awhile (all sleep, screen saver and related functions set to never or off). "userCanceledErr," huh. What's THAT mean?!
    Only other clue (maybe) was "Throttling respawn: Will start in 4 seconds. Arguments = (null)" and the only reason that caught my attention is because you _might_ have 4 seconds to cancel shutdown. Throttling respawn?

  • Previous shutdown cause: -128

    MacBook Pro Model Identifier: MacBookPro5,2 Processor Name: Intel Core 2 Duo Processor Speed: 2.66 GHz Number of Processors: 1 Total Number of Cores: 2 L2 Cache: 6 MB Memory: 8 GB Bus Speed: 1.07 GHz Boot ROM Version: MBP52.008E.B05 SMC Version (system): 1.42f4 Serial Number (system): W892217G2QT Hardware UUID: C4FF9457-58A6-53CF-9F1D-C459531E5EB2 Sudden Motion Sensor: State: Enabled
    My mac does not power on immediatly i need to press power on button few times. I notice also it is crushing while uploading files via dropbox or other Apps.
    I recently change battery because i had a problem with it.
    Thanks in advance for every advise.
    Best

    Hi Baltwo!
    Previous shutdown -128 happening on a 2.1GHz MacBook running 10.5.8, too.
    Machine actually puts up the same "Are you sure you want to shutdown..." dialog box you get from pressing power button, with barely enough time to hit Cancel - if you're paying attention. Turn your back for an instant, and you'll miss it. Do nothing = off.
    Completely random. Battery in good condition and at 100%, AC adapter plugged in and OK, replaced OS (A&I), Reset PRAM, SMU..... sure would like to know what -128 means! Only happens when left unattended for awhile (all sleep, screen saver and related functions set to never or off). "userCanceledErr," huh. What's THAT mean?!
    Only other clue (maybe) was "Throttling respawn: Will start in 4 seconds. Arguments = (null)" and the only reason that caught my attention is because you _might_ have 4 seconds to cancel shutdown. Throttling respawn?

Maybe you are looking for

  • NF-e 3.10 - p_Devol percentual da mercadoria devolvida

    Pessoal boa tarde, Para as devoluções de compra com IPI, é necessário enviar o campo p_Devol(Percentual da mercadoria devolvida). Esse campo é visível na tela de itens - aba "Taxes" da J1B3N. No meu processo de devolução de compras, esse campo sempre

  • Max Degree of Parallelism, Timeouts and Deadlocks

    We have been trying to track down some timeout issues with our SQL Server. Our SQL Server runs a AccPac Account System, an Internal Intranet site and some SharePoint Content DBs.   We know that some of the queries are complex and take some time, thou

  • My iPhone5 and iPad Air won't sync by USB with iTunes 11.1.4(62)

    Since updating to iTunes 11.1.4(62) both my iPhone 5 and iPad Air do not sync. I am using an Apple USB cable plugged directly into my 27" late 2012 iMac. WIth the phone I get an -50 error message. With theiPad Air it gets up to syncing Apps, and then

  • Safari 3 Quits and Quits and Quits

    Installed 10.4.11 and got Safari 3 which quits at the slightest notion. For example when more than one window is open and I go to close one it quits altogether. Also if I voluntarily quit the app I always get an error message informing me that the ap

  • Incorrect PO price vs. tax requirement in Poland

    Please advice how to handle situations in SAP, where the Purchase Order price is incorrect at the time of Goods Receipt. 1.     Legal tax requirement: invoice quantity and value must match There are situations when the Buyer enters an incorrect price