Update to 10.6.7, system random shutdown at mbp mc721.

I check the graphic card setting in gfxCardstatus.
System will be random shutdown by using ATI6490, but force to use intel HD 3000 not so.

HI kong,
Welcome to the forums.
Have you recently upgraded/ replaced the computer ram? Have you tried running Apple Hardware Test?
Have you looked at the console log to see what's listed at the time of the shutdown?
Have you tried a SMC reset or a NVRAM reset?

Similar Messages

  • New system, random shutdowns w/ infinite reboot-cycle afterwards

    The problem:
    When using the machine normally, it will shutdown/go out. 2-3 seconds later, the machine turns on by itself, stays on for 1-2 seconds, Shutts off. Comes back after 2-3 seconds and shuts off again after 1-2 seconds of been on. It looks like it would continue this cycle infinitly, if I didn't physically turn off the power supply to the system. (I let it repeat 7-8 times, before I decided to cut off the power entirely from the system.)
    After cutting off the power entirely, I'm able to boot it up normally next time I plug it back in. The problem repeats itself, when it decides to shutdown randomly while in WindowsXP.
    This is my first MSI board. I chosed it because reviews showed it, that at stock speeds, it was the fastest in gaming benchmarks. I guess, I should've checked for stability issues first on the web :( The system:
    MSI 875P Neo Motherboard
    Intel P4 3.2G 800 Processor
    1GB Mushkin PC3200 Level 1 CAS2 DDR SDRAM, 2ea. DIMMs, w/heat spreaders
    Radeon 9800 Pro 256MB 4.1 catalyst driver
    Audigy 2
    Adaptec 29160N Ultra160 SCSI Host Adapter
    Plextor Ultraplex 40MAX SCSI CD-ROM
    Seagate ST336753LW 15k 68-pin U320 SCSI Hard Drive
    Mitsumi 1.44MB Floppy Driver
    Antec Performance One P160 Aluminum Chassis
    Antec SL350 350W Dual-Fan Power Supply
    Mad Hatter

    Quote
    Originally posted by Danny
    It's not my calculator. I like it, think it's fairly accurate and certainly useful. But I can take no credit for it. The author does browse this forum and hopefully will speak up if he wants the well deserved credit.
    I like it too.  All credit to the creator.  not meaning to slight anyone.   I also appreciate your link to it.
    Sure is useful, as I am sure most people, including myself, don't realize how much wattage they are consuming.
    These threads have surely convinced me of the value of a quality PSU.
    Was hanging out at CompUsa a month ago talking to a nice, bidget-minded feller who wanted all the cool light mods, and a cheap, but cool case, with no inkling of the power needs. Being the disciple I am now, I wish I could talk to him today and proselytize about power...

  • MacBook random shutdown w/10.6.7 update

    I installed the 10.6.7 combo update this morning, and now I have a problem with random shutdowns. The problem persists even after a PRAM reset. When I run Apple Hardware Test, the short test reports no problem. The extended test...shuts down before completion (before the PRAM reset, it ran for about 18 minutes; afterward, it ran for about 90 minutes).
    When I ran AHT, I did so with the system "stripped" (nothing but the MacBook), so it's not a peripheral problem.
    As long as I'm active (that is, using the mouse or keyboard), it won't shut down. I did have this problem with 10.6.6, but that was related to EyeTV recording and was not a system-wide issue.

    I spent a couple days off and on at the apple store. Had a brand new early 2011 macbook pro 8G I7 2.3... all the best.
    It was randomly shutting down, sometimes 2-3 times a day.
    After replacing everything, literally, including the entire machine, it was still doing the same thing.
    Finally, a genius at the gilbet, az, apparently the genius boss, started looking at it.
    The first thing he tried was turning off sharing.
    It worked instantly.
    So, here's one of the major causes of the random shutdown - Sharing
    If you share any directory that contains operating system information - the main disk, your user account, etc. OSX will die, usually with a Kernal panic (or several of them).
    It turns out that you should only share folders that have data, never anything that has OS or App information.
    I shared everything because it was easiest for me on my MS network to get to and from the machine. It was always problematic to decide what to share, or to create multiple shares on the mac and then get to them from the PC side of my network. Now that is what I must do.
    As soon as sharing was turned off on my main drive and on the user accounts, the random shutdowns ceased. I haven't had any since.
    Now all I have left is an issue with the mouse not responding after I close the lid and reopen it. Everything appears to work, but the mouse just won't move.

  • When I try to shutdown the MBP system (10.7.2) hang up on Software update screen...

    When I try to shutdown the MBP system (10.7.2) hang up on Software update screen... After this,restart only by powerbutton.
    HD cheked - OK, permossion -OK.
    Whats happens?

    I haven't seen that one reported before.
    In the course of your troubleshooting to date have you worked through the version of the following document that is appropriate to your Windows OS?
    iTunes for Windows Vista or Windows 7: Troubleshooting unexpected quits, freezes, or launch issues
    iTunes for Windows XP: Troubleshooting unexpected quits, freezes, or launch issues

  • Random shutdowns since battey update!

    Hi.
    I've had whine issues with my MBP 1st gen. which were fixed by a logic board replacement. I updated with the battery update recently and some bad bahaviour has happened since.
    Namely I've had two random shutdowns which never happened before.
    The first occasion I dismissed since I had it on high processor load and when the MBP shutdown I put it down to overheating.
    Today the story was different.
    The MBP was idling with some normal tasks. I unplugged the machine to cycle the battery as I do once a week or so. I calibrated formally last week after the battery update.
    Approximately a minute after unplugging, the MBP activated both its fans to high speed. The processor load on both cores was under 10% so it was not due to processor load or rogue non responding process. I waited and the fans started to wind down from their high speed in the gradual way they normally do.
    A minute or so later for no apparent reason the machine just shutdown all of a sudden.
    The battery appears to be draining alot quicker. For example in the last ten minutes since I've been slowly typing this the battery % has gone from 90% to 75% with CPU loads under 10%.
    I'm calibrating the battery again today but the sudden shutdowns really shake one's confidence in the machine in a deep way as you may all understand.

    Did you Reset the PMU (power management unit)
    between re-calibrations?
    When you re-calibrate make sure you leave it more
    than 5 hours draining without power, I generally aim
    for 7 hours before re-connecting power.
    It could be worth running the Hardware tests from
    Install DVD1 (hold down d at boot) and see if it
    reports any SNS (sensor) or MTR (motor) problems.
    I calibrated formally ie. 6 hours after normal power related shutdown and wake from deep sleep mode.
    I haven't reset the PMU but will try that later. I want to try and diagnose the problem as well as possible before trying lots of random things.
    I have noticed that my battery is down to 90% of full capacity ie ~4900 mAh (5500 mAh is the nominal when new). I only have 122 cycles in the 14 months I have owned this. It's mostly on AC power but nevertheless it never occured prior to the battery update (Ockham's razor).

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

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

  • 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

  • Vista - Sleep FINALLY fixed, still annoying Random Shutdowns

    Ok, they FINALLY fixed it so the Mac Pro wakes from sleep in Vista RC1 with the recent EFI update, now they need to fix the Random Shutdowns. These occur as if you were telling your system to shutdown, I do not suspect the power supply because it is not an abrupt power loss, it gracefully shuts down, but of-course is annoying as h3ll...
    Here's looking forward to the Leopard/Vista releases when all of this should be worked out!
    SH
    Does Vista RC2 run any better? Have better Bluetooth support?

    ... well... that was really a (slap in face) help ??
    I never tried sleep or hibernate, but I read the latest RTM had some fixes in there regarding better support now for laptops and sleep.
    Ignorance is bliss perhaps? or, it is a mixed world? or, there is still software that is not available...
    How about, curiosity? that's always been man's greatest strength, too.
    Being able to run Windows Vista on Mac Pro must be something even Apple engineers are keep to do and improve on.
    Every release for OS X takes a couple updates to be "ready" for use. Long-term that has meant 2-3 updates for the last three+ releases, and each release meant more work for everyone, developer and end user, while "rules" change and hardware and software has to be updated to accommodate those changes. Even good changes are still costly, and some have been costly.
    I've lived and survived FIVE releases, $600+ for one machine license, and over a year of that was "1.0" issues all over again. And the same story will get played out next year, too, bet on it.
    Some people like to explore linux and alternatives. I have, and while I've never felt linux offered the desktop experience I want, I thought SuSE 6.4 gave OS 8/9 a real run for the money at the time.
    Things to Love/Hate about Vista
    I can now help my Dad 1200 miles away with his PC Windows w/o needing a PC. I can run multiple VMs. One computer, multiple OSs. VMware, Parallels, CrossOver, as well as native installs.
    And maybe, just maybe, a more secure desktop PC will help everyone. However, a really good balanced review might actually be one from ComputerWorld - Vista may make Mac converts of IT folks!
    IT folks can support XP/Vista and be running Mac OS X
    ComputerWorld article

  • X220 - Random shutdown

    My X220 is running Windows 7 Enterprise Edition 32 bit. I have updated to the 1.21 version of the BIOS.
    I have a 128 GB SSD,
    I am still experiencing random shutdowns under these circumstances:
    1. Only when connected to AC power. I am using 65W standard AC/DC adapter.
    2, Has been connected to the LAN always when it happens
    I have re-configured my computer: Will come back with results.
    1. I did upggrade BIOS to 1.21
    2. I have now reduced the System Performance settiung in Power Manaher from a value of "Maximum Turbo" to "Turbo".
    Kommer tillbaka med findings.

    Grrrr.. while writing this entry - the computer made the random shutdown AGAIN (now using another machine).  Lenovo - can you PLEASE make at least ONE Thinkpad with IBM quality.... 
    Anyway .. here goes...
    Bought an X220 i7 a few months back.
    Data:
    Model:  4291-36G 
    OS:  Windows7 64bit (shipped with unit) + dual booting Ubuntu Linux 10.10 (64bit)
    On BOTH Windows AND Linux these random shutdowns started to happen during the last week - with no change in my usage pattern (software development, browsing, email, etc.  - under both linux and windows).
    The most strange part is that the behavior feels like someone is pushing/holding the power key at random times (anything from 5 to 20 minutes after boot) - because windows goes to "fast sleep" and linux pops up the shutdown/sleep selector when it happens.
    I just updated to the 1.21 bios (using a stand-alone CD from ISO).. luckily it didn't reboot while flashing... 
    This DID NOT FIX THE PROBLEM (I am not sure what bios was there before).
    This really smells like a HW issue.
    NOTE:  Temperature monitors say that the CPU is well under critical - so that doesn't seem to be the issue.
    My guess is:
    1. faulty motherboard (sending the power off event.. or other)
    2. could it be related to the fingerprint reader? - I know it's a long shot - but every time it has been initiated, I think my palms have rested, touching the reader as well as putting a light pressure everywhere else on the palm rest (just trying to help you to troubleshoot the design flaw - it's still a HW issue ;-))
    Lenovo - I have 3 years on-site support on it... how do I get a new unit ASAP (I live in Denmark)?  Can I just move the HDD to the new machine (I remember that Win7 may have some annoying copy protection linking machine, HDD and OS)?
    br
    Lars
    PS Lenovo - as I wrote in the beginning of this post... I have NEVER EVER EVER EVER (well, you get the picture) had ANY problems with this back when ThinkPads were done by IBM. Can you please start making some machines that are as stable as those?  So far, I have been the Proud owner of an X31, T41p, T21 and many more... and *not so proud owner of* T61p and now X220 - both seem pretty flawed - and I seem to remember an IBM internal stating they had to send 1/2 a shipment of T61's back because of serious problems with design, construction, etc...
    PPS I know I was a bit evil above... but still think that premium price should deliver premium product.

  • Satelite U505 S2002 - Random Shutdowns

    Hello
    I have been using my Satellite U505 S2002 for the last 3 years without any issues.  About 6 months back I had to replace the HDD as a result of few recovery and reinstall issues.   Things were working fine until about a month ago, when the system started to shut down during bootup.  The system would power off the moment the windows logo appeared on the screen while booting (win7).  It would get working after multiple attempts, but gets shuts down randomly in between. 
    I had opened the laptop and checked the airvents for any dust clogging, but didnt find any any blocks.  The laptop does not seem to overheat at all even when it worked. The fan also works fine.
    The laptop was left on on bios mode and it stayed on for more than 2 hours without any issues.  The moment, the OS is looaded, the system shuts off. 
    Tried running receovery and the same thing happens, it shuts down as soon as the windows files starts loading.
    Has anyone come across similar issues?  Please help on how to fix this problem
    Regards
    Unni

    HI,
    I had tried running memtest as well as the seatools and they did not report any error.  There are few other things that I did during the course of this week
    1. Tried to reset the laptop back to factory state using the DVDs that I purchased from Toshiba.  The laptops just switches off just after when the second progress bars (loading files) is completed. 
    2.  Installed win xp with a installation disk after formatting the HD.  Installation went without any problems (however, with may missing drivers, all utilities are not functional, eg sound, limited graphics etc).  The system now boots up in XP and works fine to some extend.
    3.  The same issue of random shutdown occurred even when working on XP,  after working on for 15-20 mins.
    4.  Installed speedfan and checked for temperatures.  CPU and HD temperatures were around 35-45 degrees and occasional 50+, however the ACPI temperature goes above 60 degree Celsius which I think might be the reason for the shutdowns.
    I believe it might be an occasional faulty CPU Fan which might be causing this issue.  The fan does run and I can feel the hot exhaust air,  but the stream is not very strong and is not as hot as it used to be earlier.   I am thinking of replacing the fan and update on what happened.
    Thanks for the help
    Unni

  • GT780DX - Random Shutdowns

    Hey. I've had a gt780dx for a good four/five months now, but last wednesday it randomly shut down. This has happened on various random points since then. Sometimes it's while starting up, sometimes it's just after it finished starting. Sometimes it's after two hours. Sometimes it doesn't happen for a day. When it does happen, it happens multiple times in a row.
    I system restored my laptop on friday to a point before a windows update was installed on wednesday. It worked perfectly fine for the rest of the weekend after that, but it's happening again. Just now I noticed windows tried to sneak by an update again, even without my consent. I system restored, but it happened a couple of times again already. After each of those times it did display the 'system restore succesfull' message, though. And it seems fine now, but for how long.
    It gives no error message or bsod before shutting down. Everytime I start it afterwards it tells me windows did not shut down properly and if I wanted to start in safe mode or not.
    I have tried safe mode. It still happens during that.
    I've just gone through the event log, and the one 'critical' error that pops up a lot is kernel power. Is this simply the name for a random shutdown or is this a clear sign that something in my laptop is broken?

    It happens when it's plugged in and it's happened when I'm on battery. I can't imagine it's overheating problems as my computer has never really felt warm whatsoever. The only time it does get warmer is when I'm playing some games and it hasn't crashed during one yet.

Maybe you are looking for

  • Is there a way to help my desktop computer?

    Hi everyone, My issue is concerning my desktop computer at work. I'm not very technical, so please bare with me. It's an Apple, Mac desktop computer from anywhere between 2009 to 2011 (I'm not sure how to tell). It's running the Mac OS X version 10.6

  • External monitor not recognized (X200)

    Hi, I have an X200 with Vista When I connect an external monitor (or projector) it is not recognized.  Shift-F7 results in a message that no external monitor is detected.  However, if I leave the monitor connected, put the system in standby and then

  • 17inch Studio Display - What Cable to connect to Mac Pro?

    Hi Folks: I just got a Mac Pro with a 23" cinema display, and an ATI X-1900 card, but I also have a 17inch Studio Display that I was using with a G5. Which cable adapter do I need to connect the 17inch display to the Mac Pro as a second monitor?

  • Already bought iWork. How do I get the App Store to recognize App purchases that I've made over the past few years?

    I know I'm not the only person experiencing this issue, but I can't find who else has a solution. Essentially, I've been buying Mac Apps over the past few years and using them frequently. Now the App Store exists. Awesome. But how do I get the App St

  • IPhoto not synching albums with iPad

    I have uploaded 1500 pictures to my iPhoto on my iMac.  I already had about 10 existing albums in iPhoto.  I created two new ones which do show up correctly in iPhoto. I plugged in my iPad to my iMac and sync'd the iPad, then chose Photos to selectiv