Not so random shutdowns...

Hi,
My Macbook is just over a year old now still under applecare, I had random shutdowns before and did the firmware update which fixed it. Yesterday, I had the +please hold down the power button...+ message and so did thinking little of it, after all it is not uncommon to have to do it once in a while. Since then though it has been intermittently restarting all on its own and occasionally throwing up the +please hold power...+ message. Interesting to note is the optical drive noise when it restarts itself. I know how it should sound, the kind of mechanical movement sound that happens when you restart normally (or launch parallels and windows grabs hold of your drive). However, occasionally on these restarts it pauses during this sound several times making the same noise but stuttering through it... Strange!
It seems that I can often make it restart or throw up the power button message by just lifting up the front of the computer, as you would if you were turning it around or something. This leads me to believe it's a hardware fault... Looking under the battery compartment the two outside screws that are on the battery connection side were loose and nearly falling out so I tightened those back up, still the problem persists.
After the last restart message I copied this error report, I have no idea what to look for, just wondering if anyone can see anything helpful?
panic(cpu 1 caller 0x001A4A55): Unresolved kernel trap (CPU 1, Type 13=general protection), registers:
CR0: 0x8001003b, CR2: 0x00270000, CR3: 0x00e08000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x00025fde, ECX: 0x02fa4d90, EDX: 0x24188000
CR2: 0x02f67af8, EBP: 0x13f7bfc8, ESI: 0xfc52147b, EDI: 0x0000009c
EFL: 0x00010046, EIP: 0x00101a00, CS: 0x00000004, DS: 0xb018000c
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2f67968 : 0x128d08 (0x3cc0a4 0x2f6798c 0x131de5 0x0)
0x2f679a8 : 0x1a4a55 (0x3d24b8 0x1 0xd 0x3d1cc8)
0x2f67ab8 : 0x19aeb4 (0x2f67ac4 0xe 0xffe10048 0xc)
0x13f7bfc8 : 0x19b28e (0x2f67b0c 0x1 0x19ad3b 0x2f97d90) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffffb58
Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386
Model: MacBook1,1, BootROM MB11.0061.B03, 2 processors, Intel Core Duo, 1.83 GHz, 1 GB
Graphics: Intel GMA 950, GMA 950, Built-In, spdisplaysintegratedvram
Memory Module: BANK 0/DIMM0, 512 MB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 512 MB, DDR2 SDRAM, 667 MHz
AirPort: spairportwireless_card_type_airportextreme (0x168C, 0x86), 1.1.9.3
Bluetooth: Version 1.9.0f8, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Network Service: Parallels Host-Guest, Ethernet, en2
Network Service: Parallels NAT, Ethernet, en3
Serial ATA Device: WDC WD1200BEVS-60LAT0, 111.79 GB
Parallel ATA Device: MATSHITACD-RW CW-8221
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
I have tried a PMU reset, PRAM reset and whatever it is that happens when you hold the power button when you turn it on to make it beeeeeeep... The issue happens with or without the power cable attached.
Unless anyone can suggest anything here I'll be taking it to the repair centre...
Thanks for reading!

Ok, this is not an answer but it may help you a little: have you checked your logs? It may be an indication of what has happened there. If you don't know the drill: go to console under applications/utilities, select logs, and go there to /library/logs/panic.log. Some information may appear there, for instance if there is some consistent cause like one of your processors, some specific fault.
Not much, I know, but at least you may glean something out of it.

Similar Messages

  • Tiger Restarts by himslef. Not the Random Shutdown!

    If I keep it running for a long time (+2 hours) and I'm not using it (it is iddle, like downloading something) Tiger restarts!
    It restarts, it is not a shutdown. If I let Firefox open with more than one tab when Tiger tries to restart firefox ask for confirmation on closing the tabs and it does not restart, so it is something software based (I think)
    anyone can help me?

    Hi Fokss,
    The battery needs to be removed as well in order to reset the SMC. The SMC can be set to start up, shut down or sleep at specific times or intervals.
    The other thing I would check is to see what the settings are in the system preferences>Energy Saver>Options. Is restart after a power failure checked? If so the SMC could be getting weird when the battery/power-cord switch functions
    An API is an application programming interface. The way OS X.4+ handles everything it does happens through this I/O API part of the OS. I don't believe a re-install of the OS would help and adding an ext HDD may compound the confusion. On a side note of ext. FW HDD's I have found that images/audio and or video files that are not contained within folders are causing other issues with this same I/O API as the OS wants to treat the HDD as some other type of device especially bus powered HDD's
    I would just back up the important files. Get your email stuff from Home (User)>Library>Mail drag folder to external. Your safer bet is to just copy this Library folder to a CD as other info you would most likely want is in here. The logs are located here in this library as well. There are also logs located in the OS HDD>Library>Logs. Both are different.
    Console shouldn't purge the logs upon restart. If you click on logs in the top left of the window the list should appear. Click on the CrashReporter's arrow to expand the list.
    You hadn't listed aperture before. What other of these types of apps are you using and how is their performance? How are your camera connections?
    Thanks
    W1

  • Random shutdowns - IT'S THE BATTERY, NOT THE LOGIC BOARD!!!!

    Hey,
    Just got my battery replacement, and the shutdown problem is GONE. Here's how you verify - run your Macbook with the battery removed, on AC power - the problem disappears.
    The tech told me that it is a short in the battery, which tells the PMU that there is no power (whether there is or not!)...anyway, I hope this is helpful to all of you!
    P.S. If you're also getting the vertical lines at startup, that's a video driver issue - just zap the PRAM so you can boot, and once booted, change the resolution to something else and back to normal - it will fix the problem entirely.
    THERE IS HOPE!!!!

    <<<dear ASPs! this is -NOT- true!!!! it is NOT the battery!>>>
    probably thanks to you my ASP (DataQuest, Zurich Switzerland) only replaced my battery and handed back my MacBook unrepaired.
    After the "repair" the problem at first was rare but after just three days I'm back at normal frequency of random shutdowns. I have to spend another two weeks waiting for my macbook. this time I'm sending it to Netherlands
    I guess that it's really that badly calibrated thermal module causing these shutdowns. obviously the thermal module is irritated especially if you use your macbook often - so after 1-2 weeks of repair time the problem is barely apparent. (which causes unsuccessful repair - "testing after battery replacement worked fine" says ASP)
    MacBook 1.8Ghz   Mac OS X (10.4.7)   & iBook 2 600

  • Macbook problems, hard drive crash, random shutdown, freezes

    I bought my macbook used a few months ago, and it worked flawlessly until about 3 weeks ago. The system started freezing and not booting (getting folder icon instead of apple at startup). I ran drive setup and tried to repair the drive, but this did not fix the problem. DiskWarrior also could not fix it. I pulled the drive and installed a new hard drive, as I wanted a larger capacity anyways. All my problems appeared fixed for about two weeks, then similar problems began occurring. I backed up all the files I needed to an external firewire drive and attempted to reformat the new internal drive. Drive Setup says it can not reformat the drive - can't mount it and if it does, the drive disappears while in the process of formatting. I pulled the new drive and am having it replaced under warranty. I am using the firewire drive to run my computer, and this seemed to work fine for a day or two until the computer just started shutting down with no warning. Everything goes black, including the little light on the front of the computer. I have to hold down the power button for 10 seconds before it lets me start the computer back up. I had read this may be a memory issue, so I ran memtest and it says the memory is fine (I need to do it in single user mode still, however). I also tried pulling both sticks of ram. They are both 1GB crucial memory. I put each stick in by itself and tried it in both slots and was able to reproduce the shutdown issue with any ram configuration of either stick.
    After all this, I realized the firewire drive was only running 10.5, so I updated all the software through software update, and it is now running 10.5.2. It seems to be working better as I have not experienced a random shutdown yet, but I'm anticipating it may start back up soon. Today, however I experienced a different problem - the screen froze on me and the only way to get anything to happen was to force a shutdown with them power button. It's restarted and seems to be working fine again for now.
    I've run some logs and here's some things I've found:
    When the latest freeze happened, I got this repeated over 100 times:
    Apr 29 11:04:31 jon-turners-macbook quicklookd[536]: CGContextClosePath: no current point.
    I've also seen this:
    Apr 29 11:18:19 jon-turners-macbook kernel[0]: Previous Shutdown Cause: 3
    Apr 29 11:18:19 jon-turners-macbook kernel[0]: GFX0: family specific matching fails
    Apr 25 19:19:50 localhost kernel[0]: hi mem tramps at 0xffe00000
    Should there be anything else I can check? I would run Apple Hardware Utilities, but I don't have the original disks, just the Leopard installer. I have Disk Warrior, but it seems strange this would happen with multiple systems and drives. I'd like to get Techtool Pro, but haven't had the money/time to order it yet.

    Thanks for the replies!
    Yeah, I think it's the HDD. I was just worried that the RAM was bad and corrupted the HDD or something, but given the symptoms I think you guys are right. Ordered a 7200RPM 320GB HDD off Amazon Prime...will be here tomorrow
    I'll post how it goes after I finish installing it. I'm backing up as I type.
    I wonder if I can fix the ir port and the sleep indicator light when I install the hard-drive. The sleep indicator light never turns off. It stays on as long as my computer is on, only turns off when I shut it down.

  • K9N Platinum: CPU upgrade = Random shutdowns..

    I just installed a new AMD Athlon 64 X2 3800+ EE in my MSI K9N Platinum motherboard (MS-7250 v1.0, the 070 model according to the box). I had updated the BIOS to version 1.7 before installing the CPU. Anyhow, I got the CPU installed and it seemed to be running fine. Until I started playing my games. Upon playing fifteen (!!!) minutes of Day of Defeat, the system completely turned off. COMPLETELY. No error messages. I check core temp's log to make sure the CPU wasnt overheating; it wasnt. The max temp was 38C on one of the cores. Just to make sure the CPU wasnt the problem, I ran two instances of prime95 for 5 hours and there were no calculation errors whatsoever. I also ran 3-4 loops of SuperPi, using the 32M test. No errors.
    I have come to the conclusion that it must be the motherboard, and possibly it does not like the CPU. Or else it is having the same random shutdown problems as many other K9N Platinum/Ultra boards are experiencing. From what i have read, this issue only relates to boards that are 040, 050, or 060 models. I have a 070 model, and I AM GETTING THIS PROBLEM!!
    Help!!!
    Full specs:
    MSI K9N Platinum MS7250 V1.0, BIOS 1.7, model 070
    AMD Athlon 64 X2 3800+ EE (old CPU: AMD Athlon 64 3500+; had no issues with the 3500+) vcore: 1.225
    1 GB OCZ Platinum DDR2-800, 5-5-5-15, 2.1v
    eVGA GeForce 7800GT videocard with Zalman VF900, 490/1220
    Hitachi Deskstar 7K80 SATA HDD
    LITE-ON DVD-ROM drive
    Floppy drive
    3x 80mm fans, 1 cold cathode
    Antec Truepower 430 watt PSU, dual +12v @ 17A a piece.
    Any ideas? 

    well, i know that ACPI has to do with power saving features.
    http://en.wikipedia.org/wiki/ACPI
    and HPET also has something to do with CPUs
    http://en.wikipedia.org/wiki/HPET
    and MCP55 is the nortbridge.
    so i suppose i can conclude that it protects from overvoltage or promotes more power-saving?  i dunno i really dont care as long as my PC works now, 

  • White Macbook 2006 random shutdown solved removed cpu heatsink and more

    I picked up a cheap macbook from a secondhand retailer for $300 and it regularly shutdown, froze, restarted as well as the grey kernel panic screen completely random no real pattern. I set about trying to solve the problem swapping ram and hard drive with my identical 2006 macbook (which I had similar problems with last year, fixed that one with a new battery connector cable). The ram and hard drive made no difference so I downloaded istat menus to see if any combination of cpu voltage, current and temperature were causing the random shutdowns. It seemed when the temperature reached certain values the computer would shutdown or freeze(around 30 to 50 degrees). I'd read on other forums about faulty cpu temperature diodes so I reapplied heatsink compound to the cpu heatsink and checked all the wiring for shorts but nothing seemed to solve the problem. I was ready to retire the computer and use it for spares for my other macbook when needed but I pulled the keyboard off one more time and tried something completely radical. This fix requires some forward planning and software installation but it has completely solved my Random shutdowns completely.
    for instructions see my next post *Fix for random shutdowns white macbook*

    Ok this is not for the non technical person but it is quite a simple process with the right instructions.
    This first step is very important install the software coolbook($10) and fan control (Free)( not smc fan control). Set up coolbook to operate the cpu at the lowest speed and voltage for both power adapter and battery(1002MHz and .95Volts). Remove the keyboard to access the computer logic board (instructions can be found at iFixit). Remove the four screws and two connectors holding the heatsink to the logicboard and gently lift the heatsink out (very important that you leave the fan screwed in and connected). Close the computer back up if you wish to test just gently connect the keyboard and loosly sit the keyboard back in. Restart and reset the pram immediately. Let the computer boot up and then open system preferences and configure Fan Control to your liking. So far no random shutdowns for over a week (was getting many a day previously.

  • Macbook won't detect external display anymore - Random shutdown injury??

    Hi,
    my Macbook has the dreaded random shutdown thing happening, often it can't even get through the startup sequence. If I reset the PMU and PRAM and check the disk every week I can keep it running. Applecare are making not particularly helpful suggestions like "run it in safe mode" - hello people, random means it can take days to happen again... I use this computer for work so I need it at full capacity every day!!!
    Anyway, enough angry ranting. The casualty of today's RS and subsequent PRAM PMU resetting is my external display (Viewsonic LCD). The macbook is no longer sending signals to it (display says "no signal"). When I ask the macbook to "detect displays" nothing happens. I have restarted the macbook several times and unplugged and replugged the display connection it doesn't help. Yes, I have the AC power cable plugged in on the Macbook (I know it doesn't like talking to the screen if I don't).
    The display and macbook have always worked fine together in the past...
    Does anyone have any suggestions on how to test for causes or fix this display related problem?
    MacBook   Mac OS X (10.4.8)  
    Powerbook G4   Mac OS X (10.4.2)  

    You don't mention ever having brought the problem to Apple's attention, or what resulted from your request for Apple's help with it. This isn't a universal or widespread problem. It may be a hardware fault in your own equipment that needs to be resolved with a repair, or it may be a software problem (corrupt file, incompatible software conflict, update needed, etc., etc.). You seem to think Apple should have fixed it for you without your lifting a finger, and you're eager to complain about Apple's lack of support. But you've offered nothing to indicate that Apple even knows you need support. You do have to ask for it. Have you done so?
    We have no idea what steps you've taken to try to narrow down the possibilities, e.g., making sure the monitor is turned on; trying a different video cable as iVmichael has suggested; testing the monitor with the same cable on a different computer; testing a different monitor with the same cable and then with a diferent cable on your computer; substituting a different cable adapter, if you are using one; applying all applicable system software updates and then Repairing Permissions and Repairing Disk; starting in Safe Mode and seeing whether the monitor is recognized and activated then; seeing whether the monitor is detected in System Profiler; and so on. You may have done some of these things, but you haven't told us about them or about the results.

  • To Everyone with Random Shutdowns! (Solved! REALLY!)

    Hey all,
    I had posted about a week back about my Macbook (Core duo white, late 2006), it was having the same symptoms as some of the others with the known random shutdown syndrome (RSS). Like many others I had thought it was the end of my macbook and the logicboard needed replacing because that is what the 'genius' people do, but I was still wondering what would cause it. It would randomly shut off! (or so I thought) I'd be typing in Safari, watching a youtube video, and even playing games, it would just shut off and I could hear the hard drive spin down. I'd restart and it would do it again sometimes right away, sometimes hours later.
    This got me to thinking (like others have said) that it must be an issue with over heating. To test my theory I backed up my HD, and tried to reinstall Snow Leopard after zeroing the HD (as a fresh install). During the install process the Macbook's fan started to get loud and then it happened, it died again! So, this proved to me that it is NOT a software/OS issue at all, which means the said efforts in other posts of changing screen saver and energy saver settings had nothing to do with the cause! Aha moment!
    I thought to myself... something is making it shutdown, obviously, and has to do with too much heat as the fan was going crazy even while reinstalling the OS. After reading many posts on different support forums I came accross the possibility that it could be the heatsink and/or sensor that is attached to it. I also found out that this "RSS" only applies to the non-unibody, core duo, and core 2 duo macbooks... you know what that means?
    These models are the only ones with the shared memory and GPU on the same heatsink! GAH! A possible solution presents itself? To make a long post even longer... I removed the keyboard, carefully unscrewed the heatsink and fan and what did I see? Cracked and dried out thermal paste on the CPU AND GPU, they are both under the same heatsink after all, this was bad, really bad.
    Luckily I had some Arctic Silver thermal paste in a tube from years ago when I upgraded my PowerMac CPU. Using some rubbing alcohol and a soft cloth I removed the crud on the heatsink, processor, and GPU (I might add that there was way too much paste on there in the first place). I waited an extra few minutes to make sure the alcohol evaporated, and then I applied a small (dime sized) amount of thermal past directly onto the two chips, I aligned the heatsink carefully and gave it a very small gentle push down onto the chips, reattached the sensor wire to the mainboard, and screwed the heatsink back in.
    After putting the keyboard back on and making sure all screws were in... I immediately turned on the laptop and reinstalled the OS. The OS install took approximately 10 mintues! (crazy!) The last time I did that it took over 30 mins to install! I was stunned!
    After the OS installed I let the computer idle and shut down, I let it sit for about an hour to allow the paste to contract as it cooled. After starting up again I immediately downloaded Temperature Monitor and installed it (I did have it running when my mac had RSS by the way), here are the results to prove my theory:
    My Macbook with RSS:
    CPU1 and CPU2 Idle temp - 114 degrees (F)
    Heatsink temp - 128 degrees (F)
    Approximate over heating temp - 184 degrees (F) (causing the heatsink sensor to shutdown the laptop)
    My Macbook with new high quality thermal paste:
    Idle temp of CPU1, CPU2, and GPU - 77 degrees (F)
    Heatsink temp - 84 degrees (F)
    Running temp with adobe CS4, youtube, and typing this message - 103 degrees (F)
    Pretty amazing if you ask me!
    Before I applied the thermal paste my Macbook took at least a minute to start up with a fresh OS install, now it only takes about 15 seconds! I have not heard the fan spin up and go crazy since! And I can't even explain to you how much fast it is now!
    This does prove that Random shutdown syndrome (RSS) is caused ONLY by your GPU over heating due to old thermal paste between the chips and heatsink! A design flaw by Apple? probably not because thermal paste will crack and dry over time.
    This also proves that energy conversion to data in the chips can decrease because of over heating, causing the computer performance to dramatically drop!
    So before you take your out-of-warranty macbook to Apple or a repair shop, see what your internal temp readings are and try to replicate the problem with over heating your CPU/GPU! This was a 10 minute fix! I am still amazed at how much faster everything is, and haven't had a random shutdown since! I hope this helps alot of people that think they are out of luck and have to pay to get it fixed!
    - Cory -

    I too have this problem as well and it has been getting worse lately, I don't know what to do anymore. Here is a little info about my macbookPro. I have the late 2008 unibody model, i bought it in late 2009 Refurbished from Apple. Recently my mac has been turning off out of nowhere. I may be doing something and all of a sudden it just shuts off, it usually happens faster when i start to open up more programs like Photoshop or Final Cut Pro. My mac is out of warranty now and i dont know how much apple is going to charge me to fix it. i mean they want 50 bucks just to talk to them on the phone (ridiculous if you ask me)!.
        I have a temperature sensor installed and here is my data
    CPU A Proximity: 126F
    CPU A Temperature Diode: 133F
    Graphics Processor Chip 1: 122F
    Graphics Processor Heatsink 1: 113F
    Graphics Processor Heatsink 2: 126F
    Graphics Processor Temperature Diode: 131F
    Left Palm Rest: 91F
    Main Heatsink 3: 122F
    Main Logic Board: 118F
    Northbridge Chip: 127F
    Northbridge Position: 124F
    Here is more data from the Power
    Battery Information:
      Model Information:
      Manufacturer:          GSA-1281
      Device Name:          ASMB016
      Pack Lot Code:          0
      PCB Lot Code:          0
      Firmware Version:          0
      Hardware Revision:          0
      Cell Revision:          0
      Charge Information:
      Charge Remaining (mAh):          3739
      Fully Charged:          No
      Charging:          No
      Full Charge Capacity (mAh):          4610
      Health Information:
      Cycle Count:          68
      Condition:          Normal
      Battery Installed:          Yes
      Amperage (mA):          -1766
      Voltage (mV):          11793
    System Power Settings:
      AC Power:
      System Sleep Timer (Minutes):          0
      Disk Sleep Timer (Minutes):          0
      Display Sleep Timer (Minutes):          90
      Automatic Restart on Power Loss:          No
      Wake on AC Change:          No
      Wake on Clamshell Open:          Yes
      Wake on LAN:          No
      Display Sleep Uses Dim:          Yes
      GPUSwitch:          2
      PrioritizeNetworkReachabilityOverSleep:          0
      RestartAfterKernelPanic:          157680000
      Battery Power:
      System Sleep Timer (Minutes):          60
      Disk Sleep Timer (Minutes):          0
      Display Sleep Timer (Minutes):          2
      Wake on AC Change:          No
      Wake on Clamshell Open:          Yes
      Current Power Source:          Yes
      Display Sleep Uses Dim:          Yes
      GPUSwitch:          2
      Reduce Brightness:          Yes
      RestartAfterKernelPanic:          157680000
    Hardware Configuration:
      UPS Installed:          No
    AC Charger Information:
      Connected:          No
      Charging:          No
      PLEASE HELP ME, I CAN NO LONGER TRUST MY MAC FOR WORK. any replies will be appreciated. thanks

  • Random Shutdown Because of Heat Sensors?

    I bought my white MacBook in mid-May (week 19 production) and it worked fine with the exception of a whine when I did not have the iSight Cam on, the occasional mooing after using the computer heavily then using the CPU lightly for a while, and the discoloration. If you ask me it wasn't that much of a set back because this computer was fast and reliable... or so I had thought!
    All of a sudden about a week ago, after I had the discoloration fixed, thanks to AppleCare (which only took 5 days), my computer shut down randomly in the middle of light usage...
    At first I had thought that my external hard drive was the problem and I was very upset that this had happened. I tried to reboot my computer, but all that would happen was the usual DVD drive start up sound and then it would turn off again. I tried about 5 times to restart it with no luck, so I walked away. About 20 minutes later I was able to start it back up...
    After not using my external hard drive for a day, it happened again, in the middle of normal internet browsing and listening to music it randomly shutdown. I thought that maybe it was an OS 10.4.7 issue, because I had not had any problems with x.6, so I erased and restarted from scratch, and once again, another MacDeath. Once again, I thought it to be my fault in my installation of 2Gb of RAM. I re-installed the custom 2x256 RAM that came with the computer ( and will remain in my hands forever, because you can't even pay someone to take away a stick of 256Mb RAM these days) well after the old RAM was forcefully shoved back in, it died again! This is when I started to get mad...
    I put up with the whinning, I put up with the heat, I put up with the discoloration (for a while), but now this? WHY!
    Over the next week it happened almost daily and sometimes when I would turn on my computer after it being off for at least 5 hours, it would load my home screen and after about a minute I would hear the fan come on for a few seconds, and then it would die again. I noticed that most times that my MacBook would shutdown unexpectedly, the fan had just turned on for a few seconds or I was playing a game and the fan was already on...
    So today I called AppleCare and I had to wait about 30 minutes before I talked to someone... (When I called last time about discoloration, the wait was about 5 minutes) So either there are more and more angry customers calling, or Apple is firing employees to increase their stock value...?
    When I finally got through the man told me that it was most likely not the Logic Board, but instead FAULTY HEAT SENSORS and/or FAULTY HEAT SINK APPLICATION. I won't lie I have seen Core Duo Temp show readings as high as 91 C (about 196 degrees F). I knew that this things got hot, but not so hot as to start a fire if left on too long....
    So I am getting a box from DHL tomorrow (woohoo) MacB. and I get to part ways again, but this time, from reading many threads, I assume our time apart will be much longer approaching around 2 WEEKS!!!
    All I hope is that AppleCare will fix the heat sensors that are supposed to shutdown the computer when it gets overheated.... I have to go to school in about a month and I will not have time to deal with these kinds of issues! I really like the MacBook and all of it's features, but I did not sign up to get a MacDieOnMeBook!
    APPLE USE SOME OF THE 24% SALE INCREASE THIS QUARTER TO HELP YOUR LOYAL CUSTOMERS WHO HAVE BEEN WITH YOU THROUGH THE GOOD AND THE BAD!
    MB 2GHz White 2GB RAM - 250 GB External HD   Mac OS X (10.4.6)  

    As of yet i'm not exactly sure about the heatsink problem, although a few in here have reported machines that work well after having this part replaced, while others who only had the MLB replaced reported a recurrence of the problem.
    as for the volume indicator, i noticed that mine did that too, but it was in fact muted whether or not the tool bar indicated it. i dismissed this as a small quirk, similar to when my volume indicator didnt change as i pressed the volume buttons on my old laptop. but so long as there was an acknowledging "squirt" noise on the computer indicating change of volume, that shouldnt be a problem.
    good luck withyour MB

  • Random shutdown then fixed?

    well like alot of other users i got the random shutdown on my macbook the other night. i've been a long time windows user and finally got around to getting myself one of these nice new macbooks just last friday. (my pervious mac being a powerbook 190cs about 9yrs ago now) anyways all was going well till it randomly shut down on me. so i unplugged it and turned it on again this time it took alot less time to just shut itself down without my input. after this it wouldn't even make mac OS so i held the power button for 15 secs and it booted and didn't shut down for the rest of the night (except for when i reset it).
    i had had boot camp installed and while i was in the city today i went into next byte and talked to the guy in there who said that some people had solved it with a software fix. i had a look through these forums and saw that bootcamp didn't seem to play a part in most cases of this happening.
    i ended up deleting bootcamp off the hard drive as i was no longer using it after finding replacements for all bar VS 2005 and Access and was using them in parallels. after deleting bootcamp i haven't had a problem however in trying to work out what it was i noticed that instead of displaying the apple logo first up when i booted the machine it held the folder with ? on it for a minute. after getting rid of bootcamp this no longer happened.
    i dunno how or why but it no longer seems to be randomly resetting and not turning on. i'm hoping that its fixed becuase i really don't wanna have to send it in to apple for some of the fixes other people have had to do.
    anyways i just thought i'd post it incase it helps someone.

    Anybody have any ideas?
    I shut it down for a couple days. Just tried starting it up last night and it only made it to the login screen before it shut down again. This time it didn't try to turn back on.

  • Random Shutdown in 2010 for a 2006 Macbook

    Hello-
    I have a 2006 Macbook 1.83 GHz processor and I never had the whole random shutdown problem previously... it burned through batteries like nothing and I was about to install my third hard drive, but no random shutdown problems. Well, now I have it...
    Anyway, it is out of warranty, obviously.
    1) Will Apple still replace the heatsink, since it was defective even though I am out of warranty?
    2) If not, does anyone know if by replacing the heatsink that should fix the problem?
    Thanks

    Sure Apple will replace the heat sync. At a price. I may be something else though. It might be full if dust after all these years. You could try putting a vacuum cleaner over the in vent and give it a good sucking. Worked for a friend of mine...

  • Random shutdowns/screen off on Mavericks

    I've been getting random shutdowns on my MBA 2013. It almost always happens when I've closed the lid to put it to sleep. After that when I open it the screen always stays black and nothing happens. I have to press down on the power button for a while to get it to reboot.
    I've noticed it happening since I upgraded to Mavericks. I thought it might be a problem because I just updated so I did a clean install last week but it's continued to happen.
    Any ideas what this could be due to?
    I have a log from a shutdown I had last night. If anyone could help me out that would be nice.
    [QUOTE]
    30/1/14 23:57:10.038     CalendarAgent[200]     [com.apple.calendar.store.log.caldav.qu eue] [Adding [<CalDAVAccountRefreshQueueableOperation: 0x7ff7394d2460; Sequence: 0>] to failed operations.]
    30/1/14 23:57:10.000     kernel[0]     ARPT: 117352.987238: MacAuthEvent en0 Auth result for: 6a:12:f8:a9:b9:50 MAC AUTH succeeded
    30/1/14 23:57:10.000     kernel[0]     wlEvent: en0 en0 Link UP virtIf = 0
    30/1/14 23:57:10.000     kernel[0]     AirPort: Link Up on en0
    30/1/14 23:57:10.000     kernel[0]     en0: BSSID changed to 6a:12:f8:a9:b9:50
    30/1/14 23:57:12.299     configd[18]     network changed: DNS* Proxy
    30/1/14 23:57:12.300     UserEventAgent[11]     Captive: [CNInfoNetworkActive:1655] en0: SSID 'freebox_chouquette' making interface primary (cache indicates network not captive)
    30/1/14 23:57:12.301     UserEventAgent[11]     Captive: CNPluginHandler en0: Evaluating
    30/1/14 23:57:12.303     UserEventAgent[11]     Captive: en0: Not probing 'freebox_chouquette' (cache indicates not captive)
    30/1/14 23:57:12.303     UserEventAgent[11]     Captive: CNPluginHandler en0: Authenticated
    30/1/14 23:57:12.307     configd[18]     network changed: v4(en0!:192.168.0.10) DNS+ Proxy+ SMB
    30/1/14 23:57:13.498     apsd[183]     Unrecognized leaf certificate
    30/1/14 23:57:14.000     kernel[0]     AppleCamIn::handleWakeEvent_gated
    30/1/14 23:57:14.000     kernel[0]     AirPort: RSN handshake complete on en0
    30/1/14 23:57:14.000     kernel[0]     flow_divert_kctl_disconnect (0): disconnecting group 1
    30/1/14 23:57:14.000     kernel[0]     AppleCamIn::handleWakeEvent_gated
    30/1/14 23:57:14.672     ntpd[43]     SYNC state ignoring +0.636547 s
    30/1/14 23:57:14.987     airportd[86]     _doAutoJoin: Already associated to “freebox_chouquette”. Bailing on auto-join.
    30/1/14 23:57:15.761     configd[18]     network changed: v4(en0:192.168.0.10) v6(en0+:2a01:e35:1392:2910:60f3:d832:197c:abfa) DNS! Proxy SMB
    30/1/14 23:57:17.197     configd[18]     network changed: v4(en0:192.168.0.10) v6(en0!:2a01:e35:1392:2910:bae8:56ff:fe1b:efdc) DNS Proxy SMB
    30/1/14 23:57:19.193     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.197     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.199     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.201     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.204     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.205     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.205     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.207     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.207     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:20.125     loginwindow[67]     CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
    30/1/14 23:57:20.424     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:20.608     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:20.763     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:20.792     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:21.261     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:21.262     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:21.263     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:59:15.087     WindowServer[95]     _CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
    30/1/14 23:59:15.088     loginwindow[67]     find_shared_window: WID -1
    30/1/14 23:59:15.088     loginwindow[67]     CGSGetWindowTags: Invalid window 0xffffffff
    30/1/14 23:59:15.088     loginwindow[67]     find_shared_window: WID -1
    30/1/14 23:59:15.088     loginwindow[67]     CGSSetWindowTags: Invalid window 0xffffffff
    30/1/14 23:59:15.000     kernel[0]     Network delay is not specified! Defaulting to 0x384
    30/1/14 23:59:15.000     kernel[0]     Network delay is not specified! Defaulting to 0x384
    30/1/14 23:59:15.185     WindowServer[95]     device_generate_desktop_screenshot: authw 0x7fa2d87567e0(2000), shield 0x7fa2d8512440(2001)
    30/1/14 23:59:15.218     WindowServer[95]     device_generate_lock_screen_screenshot: authw 0x7fa2d87567e0(2000), shield 0x7fa2d8512440(2001)
    30/1/14 23:59:16.919     WindowServer[95]     CGXDisplayDidWakeNotification [117478993110615]: posting kCGSDisplayDidWake
    30/1/14 23:59:16.920     WindowServer[95]     handle_will_sleep_auth_and_shield_windows : Deferring.
    30/1/14 23:59:23.010     loginwindow[67]     CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
    30/1/14 23:59:33.000     kernel[0]     IOPMrootDomain: idle revert, state 21
    31/1/14 00:00:07.000     bootlog[0]     BOOT_TIME 1391122807 0
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.appstore" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.authd" sharing output destination "/var/log/system.log" with ASL Module "com.apple.asl".
    Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.authd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.bookstore" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.eventmonitor" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.install" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.iokit.power" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.mail" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.MessageTracer" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.performance" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     kernel[0]     Longterm timer threshold: 1000 ms
    31/1/14 00:00:11.000     kernel[0]     PMAP: PCID enabled
    31/1/14 00:00:11.000     kernel[0]     PMAP: Supervisor Mode Execute Protection enabled
    31/1/14 00:00:11.000     kernel[0]     Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
    31/1/14 00:00:11.000     kernel[0]     vm_page_bootstrap: 1997719 free pages and 83049 wired pages
    31/1/14 00:00:11.000     kernel[0]     kext submap [0xffffff7f807a5000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff80007a5000]
    31/1/14 00:00:11.000     kernel[0]     zone leak detection enabled
    31/1/14 00:00:11.000     kernel[0]     "vm_compressor_mode" is 4
    31/1/14 00:00:11.000     kernel[0]     standard timeslicing quantum is 10000 us
    31/1/14 00:00:11.000     kernel[0]     standard background quantum is 2500 us
    31/1/14 00:00:11.000     kernel[0]     mig_table_max_displ = 74
    31/1/14 00:00:11.000     kernel[0]     TSC Deadline Timer supported and enabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=1 LocalApicId=0 Enabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=2 LocalApicId=2 Enabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=3 LocalApicId=1 Enabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=4 LocalApicId=3 Enabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=5 LocalApicId=255 Disabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=6 LocalApicId=255 Disabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=7 LocalApicId=255 Disabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=8 LocalApicId=255 Disabled
    31/1/14 00:00:11.000     kernel[0]     calling mpo_policy_init for TMSafetyNet
    [/QUOTE]

    I've been getting random shutdowns on my MBA 2013. It almost always happens when I've closed the lid to put it to sleep. After that when I open it the screen always stays black and nothing happens. I have to press down on the power button for a while to get it to reboot.
    I've noticed it happening since I upgraded to Mavericks. I thought it might be a problem because I just updated so I did a clean install last week but it's continued to happen.
    Any ideas what this could be due to?
    I have a log from a shutdown I had last night. If anyone could help me out that would be nice.
    [QUOTE]
    30/1/14 23:57:10.038     CalendarAgent[200]     [com.apple.calendar.store.log.caldav.qu eue] [Adding [<CalDAVAccountRefreshQueueableOperation: 0x7ff7394d2460; Sequence: 0>] to failed operations.]
    30/1/14 23:57:10.000     kernel[0]     ARPT: 117352.987238: MacAuthEvent en0 Auth result for: 6a:12:f8:a9:b9:50 MAC AUTH succeeded
    30/1/14 23:57:10.000     kernel[0]     wlEvent: en0 en0 Link UP virtIf = 0
    30/1/14 23:57:10.000     kernel[0]     AirPort: Link Up on en0
    30/1/14 23:57:10.000     kernel[0]     en0: BSSID changed to 6a:12:f8:a9:b9:50
    30/1/14 23:57:12.299     configd[18]     network changed: DNS* Proxy
    30/1/14 23:57:12.300     UserEventAgent[11]     Captive: [CNInfoNetworkActive:1655] en0: SSID 'freebox_chouquette' making interface primary (cache indicates network not captive)
    30/1/14 23:57:12.301     UserEventAgent[11]     Captive: CNPluginHandler en0: Evaluating
    30/1/14 23:57:12.303     UserEventAgent[11]     Captive: en0: Not probing 'freebox_chouquette' (cache indicates not captive)
    30/1/14 23:57:12.303     UserEventAgent[11]     Captive: CNPluginHandler en0: Authenticated
    30/1/14 23:57:12.307     configd[18]     network changed: v4(en0!:192.168.0.10) DNS+ Proxy+ SMB
    30/1/14 23:57:13.498     apsd[183]     Unrecognized leaf certificate
    30/1/14 23:57:14.000     kernel[0]     AppleCamIn::handleWakeEvent_gated
    30/1/14 23:57:14.000     kernel[0]     AirPort: RSN handshake complete on en0
    30/1/14 23:57:14.000     kernel[0]     flow_divert_kctl_disconnect (0): disconnecting group 1
    30/1/14 23:57:14.000     kernel[0]     AppleCamIn::handleWakeEvent_gated
    30/1/14 23:57:14.672     ntpd[43]     SYNC state ignoring +0.636547 s
    30/1/14 23:57:14.987     airportd[86]     _doAutoJoin: Already associated to “freebox_chouquette”. Bailing on auto-join.
    30/1/14 23:57:15.761     configd[18]     network changed: v4(en0:192.168.0.10) v6(en0+:2a01:e35:1392:2910:60f3:d832:197c:abfa) DNS! Proxy SMB
    30/1/14 23:57:17.197     configd[18]     network changed: v4(en0:192.168.0.10) v6(en0!:2a01:e35:1392:2910:bae8:56ff:fe1b:efdc) DNS Proxy SMB
    30/1/14 23:57:19.193     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.197     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.199     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.201     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.204     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.205     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.205     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.207     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:19.207     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:20.125     loginwindow[67]     CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
    30/1/14 23:57:20.424     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:20.608     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:20.763     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:20.792     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:21.261     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:21.262     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:57:21.263     com.apple.mtmd[62]     Failed to get the path for fd 5 (Invalid argument)
    30/1/14 23:59:15.087     WindowServer[95]     _CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
    30/1/14 23:59:15.088     loginwindow[67]     find_shared_window: WID -1
    30/1/14 23:59:15.088     loginwindow[67]     CGSGetWindowTags: Invalid window 0xffffffff
    30/1/14 23:59:15.088     loginwindow[67]     find_shared_window: WID -1
    30/1/14 23:59:15.088     loginwindow[67]     CGSSetWindowTags: Invalid window 0xffffffff
    30/1/14 23:59:15.000     kernel[0]     Network delay is not specified! Defaulting to 0x384
    30/1/14 23:59:15.000     kernel[0]     Network delay is not specified! Defaulting to 0x384
    30/1/14 23:59:15.185     WindowServer[95]     device_generate_desktop_screenshot: authw 0x7fa2d87567e0(2000), shield 0x7fa2d8512440(2001)
    30/1/14 23:59:15.218     WindowServer[95]     device_generate_lock_screen_screenshot: authw 0x7fa2d87567e0(2000), shield 0x7fa2d8512440(2001)
    30/1/14 23:59:16.919     WindowServer[95]     CGXDisplayDidWakeNotification [117478993110615]: posting kCGSDisplayDidWake
    30/1/14 23:59:16.920     WindowServer[95]     handle_will_sleep_auth_and_shield_windows : Deferring.
    30/1/14 23:59:23.010     loginwindow[67]     CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
    30/1/14 23:59:33.000     kernel[0]     IOPMrootDomain: idle revert, state 21
    31/1/14 00:00:07.000     bootlog[0]     BOOT_TIME 1391122807 0
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.appstore" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.authd" sharing output destination "/var/log/system.log" with ASL Module "com.apple.asl".
    Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.authd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.bookstore" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.eventmonitor" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.install" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.iokit.power" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.mail" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.MessageTracer" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.performance" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     syslogd[18]     Configuration Notice:
    ASL Module "com.apple.securityd" claims selected messages.
    Those messages may not appear in standard system log files or in the ASL database.
    31/1/14 00:00:11.000     kernel[0]     Longterm timer threshold: 1000 ms
    31/1/14 00:00:11.000     kernel[0]     PMAP: PCID enabled
    31/1/14 00:00:11.000     kernel[0]     PMAP: Supervisor Mode Execute Protection enabled
    31/1/14 00:00:11.000     kernel[0]     Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
    31/1/14 00:00:11.000     kernel[0]     vm_page_bootstrap: 1997719 free pages and 83049 wired pages
    31/1/14 00:00:11.000     kernel[0]     kext submap [0xffffff7f807a5000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff80007a5000]
    31/1/14 00:00:11.000     kernel[0]     zone leak detection enabled
    31/1/14 00:00:11.000     kernel[0]     "vm_compressor_mode" is 4
    31/1/14 00:00:11.000     kernel[0]     standard timeslicing quantum is 10000 us
    31/1/14 00:00:11.000     kernel[0]     standard background quantum is 2500 us
    31/1/14 00:00:11.000     kernel[0]     mig_table_max_displ = 74
    31/1/14 00:00:11.000     kernel[0]     TSC Deadline Timer supported and enabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=1 LocalApicId=0 Enabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=2 LocalApicId=2 Enabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=3 LocalApicId=1 Enabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=4 LocalApicId=3 Enabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=5 LocalApicId=255 Disabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=6 LocalApicId=255 Disabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=7 LocalApicId=255 Disabled
    31/1/14 00:00:11.000     kernel[0]     AppleACPICPU: ProcessorId=8 LocalApicId=255 Disabled
    31/1/14 00:00:11.000     kernel[0]     calling mpo_policy_init for TMSafetyNet
    [/QUOTE]

  • Macbook in repair for kernal panics and random shutdowns.....

    It's been exactly one week since I sent in my macbook for random shutdowns. I called today to check on the status and they told me it was on hold because they needed more info from me as they can not replicate the problem. This thing was shutting down on me 3-4 times a day without warning. I gave them all kinds of suggestions, ie: check logic board, power management system, panic logs, etc. Don't these techs know how to troubleshoot? My biggest fear is that they won't find the problem and they'll send my defective Macbook back to me. What are my options then? It was bought for me by a friend in Denver who brought it down to Albuquerque for me (500 miles away) so returning it to a store is not an option. I know other people are having this problem so I know I'm not crazy and delusional. I don't want to be stuck with a defective computer but my 2 week grace period is over. What can I do?
    MacBook   Mac OS X (10.4.5)  

    Here's an update on my repair. It's been 2 weeks and they finally found the problem to be a bad logic board. They said it was on hold for repair to replace the board and didn't specify a return time. I expressed a concern with having a month old computer that has already been in for a major repair. After some polite but concerned dialouge between myself and a product specialist, she offered me a new one. I accepted the offer gladly. She even asked black or white? My original was white. So chalk one up for Apple customer support. They seems like they're out to make things right with their customers. You just have to remain calm and patient.

  • Random shutdown problem on G5 dual 2.3 GHz w/OS 10.4.7

    Hello,
    I’m using a dual 2.3 GHz G5, and it’s been working flawlessly since I bought it about a year ago. Until yesterday, I was running OS 10.4.5. Yesterday I upgraded to 10.4.7, and as soon as I booted up after the install, I started having a maddening problem with my computer randomly shutting down. (Not sleeping, but a complete power down.)
    At first, the shutdown would happen immediately after powering up; my computer wouldn’t even make it to the blue progress bar. I zapped the PRAM and tried something I found online about unplugging the computer for 15 seconds, then plugging it back in. It now boots up, and I can log in, but the computer still shuts down randomly.
    There seems to be no pattern to the shutdowns. I tried taxing the processor by opening and resampling huge Photoshop files while lots of other apps were open, and things were fine. Then it would conk out while I was composing an email.
    I’ve heard of this random shutdown problem affecting Macbooks, but I have yet to find anything about G5 towers and OS 10.4.7. Does anyone have any info/advice?
    Many thanks.
    G5 dual 2.3 GHz Mac OS X (10.4.7) 2.5 GB RAM, 250 GB HD
    G5 dual 2.3 GHz Mac OS X (10.4.7) 2.5 GB RAM, 250 GB HD

    Thanks for the advice. I did check the system.log in Console and found the following altert:
    PMU FORCED SHUTDOWN, CAUSE = -122
    Now, since my computer is just over a year old, and since this problem happened immediately after applying the 10.4.7 OS update, I found it hard to believe that my hardware could be responsible. After 2 days of troubleshooting, I was stumped; after a 2-hour service call, so was Apple tech support. I ended up doing an archive and install back down to 10.4.5, and all is well.
    I tested this issue on other machines running 10.4.7 and had no problems. It seems that the following specific combination of elements triggered the problem:
    • PowerMac G5 dual 2.3 GHz (dual 1.8 machines did not exhibit the same problem)
    • OS 10.4.7
    • Logging in with Open Directory/Active Directory mobile profiles
    • iTunes 7
    Bottom line: if you’re using a dual 2.3 GHz PowerMac with mobile OD/AD profiles, do not update to 10.4.7, and steer clear of iTunes 7, at least until there is a patch update available.
    (And Apple wants to be taken seriously in the enterprise market?)
    G5 dual 2.3 GHz Mac OS X (10.4.7) 2.5 GB RAM, 250 GB HD

  • My iPhone 5 randomly shutdown and rebooting doesn't seem to work for me, what should I do?

    It also happens when I'm charging my phone, and also the battery percentage doesn't show that correct battery level not unless I turn off and on.. I tried rebooting the phone but it doesn't seem to work for me, random shutdown still happens..

    Will not turn on, will not turn on unless connected to power, or unexpected power off
    Verify that the Sleep/Wake button functions. If it does not function, inspect it for signs of damage. If the button is damaged or is not functioning when pressed, seek service.
    Check if a Liquid Contact Indicator (LCI) is activated or there are signs of corrosion. Learn about LCIsand corrosion.
    Connect the iPhone to the iPhone's USB power adapter and let it charge for at least ten minutes.
    After at least 30 minutes, if:
    The home screen appears: The iPhone should be working. Update to the latest version of iOS if necessary. Continue charging it until it is completely charged and you see this battery icon in the upper-right corner of the screen . Then unplug the phone from power. If it immediately turns off, seek service.
    The low-battery image appears, even after the phone has charged for at least 20 minutes: See "iPhone displays the low-battery image and is unresponsive" symptom in this article.
    Something other than the Home screen or Low Battery image appears, continue with this article for further troubleshooting steps.
    If the iPhone did not turn on, reset it while connected to the iPhone USB power adapter.
    If the display turns on, go to step 4.
    If the display remains black, go to next step.
    Connect the iPhone to a computer and open iTunes. If iTunes recognizes the iPhone and indicates that it is in recovery mode, attempt to restore the iPhone. If the iPhone doesn't appear in iTunes or if you have difficulties in restoring the iPhone, see this article for further assistance.
    If restoring the iPhone resolved the issue, go to step 4. If restoring the iPhone did not solve the issue, seek service.

Maybe you are looking for