Qosmio F40 - Random Shutdowns while gaming.

My Qosmio F40 has been crashing when I game. I'm playing either World of Warcraft or Warcraft3, and within 20-30 minutes the laptop just quickly turns off.
It won't let me power back up for about 5-10 minutes, and when it does it brings me to the black and white screen saying that it wasn't shutdown properly.
I've had no other problems with the Qosmio F40, I've been very happy with it.
This started happening about 2 weeks ago and has been consistent over those two weeks. I ran a 'Video Card Stability Test' and it also caused my laptop to crash. I've checked for new drivers and there are none available currently. My Video card came stock with the laptop and is a Nvidia GeForce 8600M GT.
I'm running Windows Vista (32-bit). I don't think it is getting over-heated because a few months ago I could seriously game on it for about 8-10 hours straight with no problems.
Any suggestions, any help/advice would be greatly appreciated.
Thanks,
Daniel

I completely agree with Maurice.
Fact is that a non-Toshiba graphic driver doesnt support the overheating protection and usages of any 3rd graphic drivers can leads to the overheating issues
In your case the notebook could overheats due to the dust and debris inside the notebook.
This could prevent the fans from rotating with full speed.
So try to clean the ventilators using the compressed air spray which is a professional tool for such jobs ;)

Similar Messages

Random Shutdown While Running On Battery

I've been experiencing random shutdowns when running on the battery of my iBook G4 12" (2004). The iBook has been working fine when the power adapter plugged in and I don't know the route of the problem! If anyone could enlighten me it would be much apppreciated! I have run the Hardware Test and everything has come back thumbs up. I'm thinking this maybe a Logic Board problem, im hoping that it isn't because that is costly!
Any help is greatly appreciated, Cheers.

Hi,
Welcome to the Discussions.
I would suspect a bad battery. It's ~2 years old (the average life of a lithium ion battery) and it doesn't happen when plugged into the mains. Older batteries often report false information about the percent of charge in them. It can read 60% when in fact it's 1%.
Go to Apple Menu>About this Mac>More Info and see what the capacity of the battery is and the number of charge cycles.
John

Qosmio X305-Q705 BSOD while gaming

I bought this laptop in December from Best Buy, I live in Canada but it was bought in Delaware (my girlfriend lives in PA so she picked it up for me) and I picked it up when I visited her just after Christmas. Everything seemed to work ok, I went about 2 weeks with no problems and then after updating the bios to 1.70 (it's not at 1.80 with same problems that will be explained) as well as updated the Nvidia drivers with the beta drivers off the Nvidia site.
I refuse to format, as I know that will not fix this issue but this is my only computer, I do a lot of gaming and work on my computer away from home so I stopped investing in desktops and got a laptop to replace my desktop. I used a Toshiba a few years back, then I went to a MacBook Pro last May and now this, I never had a problem running games on my other 2 laptops when I had them but this one just keeps blue screening on me when gaming, at random. It will be less than 30 minutes playing a game, sometimes hours. It doesn't happen daily either so I do not know what is causing this but it is getting very very frustrating, I paid a lot of money for this laptop and it doesn't work. The system, for those who may ask is running Vista Home Premium 64-bit.
Here are the dates and times of the BSOD's I get:
1) Jan.14 at 00:29 hours, with BSOD error "PFN_LIST_CORRUPT" (while playing World of Warcraft);
2) Jan.15 at 02:32 hours, with BSOD error "PAGE_FAULT_IN_NONPAGED_AREA" also showing "dxgkrnl.sys" file below (while playing Warhammer Online);
3) Jan.16 at 01:45 hours, with BSOD error "DRIVER_IRQ_NOT_LESS_OR_EQUAL (while playing Warhammer Online)"
4) Jan.17 at 23:21 hours, with BSOD error "IRQ_NOT_LESS_OR_EQUAL" (while playing World of Warcraft);
5) Feb.01 at 14:13 hours, with BSOD error "IRQ_NOT_LESS_OR_EQUAL" (while playing World of Warcraft).
Toshiba, what is going on? Please fix this, or send me back a full refund and I will take my business elsewhere! This is ridiculous that a brand new computer is having these issue, and it seems others have the same problem so it's not isolated to 1 or 2 machines it seems. you guys screwed up or put really really cheap parts in these systems. Oh, and it doesn't seem to overheat either, I keep it in a well ventilated and cool area as well as I have a laptop cooling pad underneath it, my MBP I had before this got hotter and never had problems so it's not a heat issue.
Message Edited by NightHawk on 02-08-2009 02:07 AM

NightHawk wrote:
Wow, not a single response from anyone at Toshiba?
I just had another blue screen of death while playing WoW about 20 minutes before I posted this reply. This didn't show any specific error, it just said "A process or thread crucial to system operation has unexpectedly exited or been terminated". I also had a video crash, I don't the file name with me but some error where my computer locked up for a few seconds, then the screen went black and then recovered and gave me a message saying a video file stopped working but has recovered. I think the video card and ram in this machine were bad right out of the box.
Seriously, this computer cost me a lot of money, and within the first few weeks of using it(about a week of using it under my normal usage conditions) I started getting BSOD's. My first laptop never had issues and was a Toshiba Satellite A100 (forget the rest of the model) and then I had a MacBook Pro which was great even with Vista x64 running through Bootcamp, but this Qosmio a completely different story, these BSOD's are starting to piss me off.
As I mentioned, my girlfriend bought it from a Best Buy in Delaware but by the time I got it home (I live in Toronto, ON) and started seeing the issues I had no way to return it otherwise I would have. Is anyone from Toshiba going to comment on this problem? I tried updating to the new 1.90 bios as well. Should I revert to the 1.40 bios or what because I didn't see the first BSOD until I updated to the 1.70 bios but of course I didn't have much time using the laptop prior to updating to 1.70 so I don't know if that was the problem or not, but 1.80 and 1.90 didn't fix anything regarding these BSOD's so I'm guessing it's faulty hardware you guys put in these systems.
Message Edited by NightHawk on 02-08-2009 02:06 AM
If you read the terms of service, there is no official Toshiba presence here. I'd suggest that you call Toshiba Tech Support and see what, if anything, they suggest. Be prepared to use the recovery process to wipe the drive and put it back to 'out-of-the-box', as that is likely the first thing they will want you to do to eliminate a software issue.
I don't own a Qosmio, so I have nothing specific to suggest. Sorry.

Random hardlocks while gaming

It's happening again, one reason I moved from *buntu was the random hardlocks, well I'm getting them again, 3 times last night while playing, and only happens when I'm playing, mainly WoW
So any clue as to what is causing this? The locks are so bad all I can do is force power off and restart, what logs should I be checking etc,?

z0phi3l wrote:
Nope, cleaning out my system did no good
I'm going to try turning off Compiz and seeing if that helps any like I've heard
hmm, well what was the last thing u changed before u started having lock-ups. Did u do a system upgrade? check the logs around the time it started and u will have a good lead to follow.

Problems with random shutdown after replacing a swollen battery

Hello all,
Perhaps one of you can help with this issue.
I'm using a Macbook Pro 17" mid-2007 model. A few months ago, the power disconnected from the machine when the battery had already run down and the machine did a hard shutdown. When I booted it back up there were serious problems with the display. Eventually it stopped working altogether. I took it for service and it was determined to by the NVIDIA graphics processor problem, so Apple replaced my motherboard.
When I got the machine back from servicing, there was a rattle in the right fan that gradually got worse. After a while the touchpad button stopped depressing in the center. I also experienced several random shutdowns while operating on battery power. I learned about the swelling battery issue with macbooks and ordered a replacement. By the time the replacement battery arrived my original battery was quite swollen. I'm concerned that the swelling battery may have warped the case a bit, leading to the fan noise.
I have now replaced the battery, but I'm still experiencing random shutdowns after 20+ minutes of use on battery power. I have done the RSS tests that were recommended in other forums and there doesn't seem to be any random shutdown problems when I'm plugged in -- only under battery power. My understanding is that a swelling battery can sometimes cause the battery to disengage from the electrical contacts on the MB, causing a sudden shutdown. I'm wondering why the problem is persisting now with a new battery? After one random shutdown, I tried to power up again using the battery, while pushing the battery into place at various angles, but I couldn't find any angle that would give power to the machine. The fan noise is also still present.
Can anyone offer an explanation or advise on any methods to overcome these random shutdowns? I have checked the console and the machine isn't registering any error when it shuts down, although when it restarts it says "DirectoryService[35] Improper shutdown detected"

Yep, it is video (or: or audio for video) so unless you're sure you need it (because you work or will work with the DVC Pro HD video/audio codec), you can remove the plug from its' folder and put it in your documents folder (don't trash it, I have no idea if it is necessary for non-DVC Pro HD users to have it installed too).
The WWW is littered with posts from people encountering bugs and crashreports with DVCPROHDAudio.plugin as the main suspect. Most of those posts seem to be from video people rather than audio folks.
http://www.google.nl/search?q=DVCPROHDAudio.plugin&ie=utf-8&oe=utf-8&aq=t&rls=or g.mozilla:en-US:official&client=firefox-a
But, if you get crashes and you see this one mentioned in the report, disable it, restart, and see if the problem's gone.

G505s Random Shutdown

When I am using my laptop on a regular basis, It tends to release Burning to the touch air from the side of the laptop. I ahve had random shutdowns while I am working on something. It will not load up a system restore, when I press the power button it automatically boots up windows 8 into normal startup. I am still under warrenty and I am wondering if it is a malfunction with this specific laptop or happening to others of this model. Would the warrenty fix this problem I am having. I have had this happen 5-6 times now.
Solved!
Go to Solution.

Actually no I haven't had the problem anytime recently. Thank you for checking!

Qosmio X870 overheats while gaming

Hello,
i have qosmio that is running about 95-100 celzius GPU and 85-90 CPU temperatures while gaming from day 1.
Then i got shut downs due to overheating about 9 months later.
I go to service, and they clean it and repaste it , it didnt shut down anymore but high temperatures stayed.
20 days later GPU died, they replaced it, then 10 months later GPU died again, i heard burning inside the laptop.
They put new one again, but after that when i game for 2 hours, screen shuts down at least once, somethimes twice in that time.
I took laptop to service for fourth time, few days later they are saying that they didn't still diagnosed the malfunction.
But my biggest concern is that temperatures are high all that time, i read on A.s.u.s forum that guy with that kind of temperatures got replace immediatly, and the new notebook got 20 degrees lower temp.
Laptop is about 20 months old, and my question is:
do i ever have right for replacement or they will just patch it up every few months until warranty expires :( because they are planing to repair it again.
I need it for video editing also, thats why i bought it, and now for the 4th time my bussines is on hold for a week or two.
Sorry for long post, im hoping for some answer or mail where i can request replacement, thank you.

> do i ever have right for replacement or they will just patch it up every few months until warranty expires because they are planning to repair it again.
As far as I know Toshiba authorized service partner can just repair the notebook and you should ensure that the notebook will be fixed to your fullest satisfaction.
>I took laptop to service for fourth time, few days later they are saying that they didn't still diagnosed the malfunction. But my biggest concern is that temperatures are high all that time,
From my experience if the notebook does not shut down automatically, the temperature level isnt too high. Usually in case of overheating, the notebook should power off automatically to protect the internal parts from damage.

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.

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.

Iphone 6 randomly shutdown in standby mode

My Iphone 6 16gb randomly shutdown in standby mode, i only can turn it on by hold POWER + HOME. here is the log :
{"name":"Reset count","bug_type":"115","os_version":"iPhone OS 8.1 (12B411)"}
Incident Identifier: F0B79DBE-0BE1-431A-813E-70E7E2C17942
CrashReporter Key: 7305c452a84bf7ce3738c4bedf794c8e76fc4c58
Date: 2014-11-24 09:17:58 +0700
Reset count: 1
Boot failure count: 2
Boot faults: wdog btn_rst
Boot stage: 32
Boot app: 2681261667
Is this a hardware issue or software issue? thanks

Hi hnguyen1982,
If you are having an issue with your iPhone shutting down unexpectedly, I would suggest that you troubleshoot using the steps in this article -
If your iOS device restarts, displays the Apple logo, or powers off while you're using it - Apple Support
Thanks for using Apple Support Communities.
Best,
Brett L

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.

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]

Random Shutdowns on a MBP Core Duo, Suggestions/Help would be great

I've had two random shutdowns of my mac since purchasing it back in August. The first happened on January 11th, when it said it was at 11-12% power. The second happened about two weeks later, at 23% power. I've been looking around these forums and other pages, and haven't really found anything that has helped so far.
Details of the first crash:
Open apps- Firefox (5 windows, two had about 20+ tabs open, the rest were single page, and yes, I know it crashes often with that many), Camino (1 window with 5 tabs), and Word 2004, as well as Quicktime open to the iPhone stream.
I had an USB key plugged in, to which I was saving my Word document.
So I was working in Word while in front of the TV and during an interesting bit, didn't do anything for a minute. So, like the many times earlier, it slept the display to conserve power (in "Better Energy Savings" mode). I moved my finger on the trackpad to wake it back up, and it turned back on the backlighting, and then stopped. I thought it had just went back to sleep, but after a few key presses and a check of the light that usually pulsates when it's sleeping (plus the USB key , I found out that the computer had turned off. I let it sit for a while, and when I plugged it back into AC power and turned it on, with my USB key still plugged in, and although it booted to my desktop, the Finder never started (so no desktop icons for anything), unplugging the USB key fixed this and everything returned to normal. I then installed the only update I was missing, one for iChat, restarted, and continued working.
In the second incident, I only had my browsers open, nothing external plugged in, and my displayed was dimmed to the third darkest level. When it was at about 23% power, it once again randomly shut down. This time, I attempted to turn it back on, and nothing happened. After plugging it into AC power, it turned on and once logged in showed a very low (2-6%) power, so I guess it was reporting the power incorrectly?
Anyways, went back to look at the battery exchange on Apple's website. I had checked before when they started it, and was pretty sure mine wasn't covered, and a second check confirmed that. My Mac's serial is W8618091VWX, which isn't covered by the recall.
So, I have a few questions:
1. Is there a toll-free number I can phone Apple (Canada) at? The only number I've found seems to be only free for those who bought their computer in the last 90 days, which I'm no longer covered by, and haven't been for a while. Talking to someone at Apple would be good.
2. Otherwise, if I took my computer to an Authorized Service Provider, would they be able to take a look at it and answer some questions? I bought my MBP at a London Drugs and they aren't service providers, so how much would it cost to do this?
3. Is there a definite cause for these random shutdowns? It seems to vary among other people, so it would be helpful if I could try something to eliminate one of the causes.
4. Does Tiger report battery levels pretty accurately? In the past when I reached 6% I got a warning and was able to plug it into AC power and had no problems.
Thanks for any help you can provide.
Macbook Pro 2.16 GHZ Core Duo, 15.4", 1GB RAM Mac OS X (10.4.8)

I had this problem of RSD fixed for a while after having had the battery replaced by Apple, till yesterday, when the MBP suddenly experienced a shutdown during a meeting presentation, while it was connected to the AC power. At the first restart, as coming back from a stop-mode, for a while appeared a warning of low-battery level, with battery level indicator flashing red and showing the empty icon but with a 86% of charge level and a new shut-down definitely put the MBP out of service, no way to have it functioning again. Obviously, AC power was OK, no problem with the microphone or the projector ( I was at the podium of an international meeting) and a lucky precaution ( double save of the same presentation on a friend's twin MBP, that worked correctly) saved the job.
Then, a couple of hour later, my MBP started up normally and everything works fine, with or without MAGsafe connected to AC power, almost up to now.
I've read the post with a link to the procedure for resetting the power controller chip on the mainboard, I'll do it in a minute, hoping that this will help.
Any further suggestion?
ambabu, Italy

Qosmio F40 - Random Shutdowns while gaming.

Similar Messages

Maybe you are looking for