Random Shutdown Without Command

Hello.
My name is Weston Erbentraut, and I have a mid-2010 I7 Macbook Pro. More recently, (over the past four months or so), I been experiencing (random shut down without command) from my computer. I have done a bit of online research regarding possibly issues that may be wrong with it, but still no clear solutio
It is not currently under warranty, and yes I have up-graded everything to a fault.
Is it possible that there might be something wrong with my hard-drive? I have a 500 GB SATA Disk.
Would someone please help me?
- Thanks,
Cityfish.

# System started at 2014-03-10 02:21:21.7771
# system: Weston’s MacBook Pro
02:21:21.7833 Argument[0]: '/Users/Shared/Battle.net/Agent/Agent.2380/Agent.app/Contents/MacOS/Agent'
02:21:21.7833 Argument[1]: '--locale=enUS'
02:21:21.7834 Argument[2]: '--session=4577714830806487036'
02:21:21.7834 Agent is running as Administrator.
02:21:21.7840 Unable to parse agent.db file, generating default database.
02:21:21.7841 Database Insert: /
02:21:21.7841 Database Insert: /agent
02:21:21.7841 Database Insert: /agent/download
02:21:21.7842 Database Insert: /backfill
02:21:21.7842 Database Insert: /game
02:21:21.7842 Database Insert: /gamesession
02:21:21.7842 Database Insert: /install
02:21:21.7842 Database Insert: /option
02:21:21.7843 Database Insert: /repair
02:21:21.7843 Database Insert: /update
02:21:21.7843 Database Insert: /register
02:21:21.7843 Database Insert: /version
02:21:21.7843 Database Insert: /spawned
02:21:21.7843 Database Insert: /createshortcut
02:21:21.7843 Database Insert: /uninstall
02:21:21.7843 Session Hash found: '4577714830806487036'
02:21:21.8852 Initialize HttpProtocol Server Called.
02:21:21.8862 Agent started on port #1120
02:21:21.8862 Registered Periodic Event: "auth validation event" with a resolution of 10000 and a start delay of 10000
02:21:21.8863 Registered Event: "shutdown event"
02:21:21.8863 Registered Event: "database flush event"
02:21:21.8863 Registered Periodic Event: "network connection event" with a resolution of 60000 and a start delay of 0
02:21:21.8863 Handle Event: "network connection event"
02:21:22.2295 Incremental patch:
02:21:22.2295 -source url: http://dist.blizzard.com.edgesuite.net/bna/a2717/a-2380-2717-mac.mpq.torrent.39C 103980BC887D6B3679C5F0B1823A6
02:21:22.2295 -dest: /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/Cleanup At Startup/Blizzard/AgentUpdate_A72FE453/a-2380-2717-mac.mpq
02:21:22.2725 Firing Event: "database flush event"
02:21:22.2725 Handle Event: "database flush event"
02:21:22.2726 Request Issued: GET /agent
02:21:22.2730 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : false,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:22.2748 Request Issued: GET /game
02:21:22.2748 Response: 200
02:21:22.2863 Request Issued: POST /agent
"opt_in_feedback" : true
02:21:22.2863 Response: 200
02:21:22.2872 Request Issued: GET /agent
02:21:22.2873 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:22.7887 Request Issued: GET /agent
02:21:22.7888 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:23.2906 Request Issued: GET /agent
02:21:23.2906 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:23.7920 Request Issued: GET /agent
02:21:23.7920 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:24.2935 Request Issued: GET /agent
02:21:24.2936 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:24.7948 Request Issued: GET /agent
02:21:24.7948 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:25.2962 Request Issued: GET /agent
02:21:25.2963 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:25.7975 Request Issued: GET /agent
02:21:25.7976 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:26.2989 Request Issued: GET /agent
02:21:26.2989 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"progress" : 0.177164,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:26.8009 Request Issued: GET /agent
02:21:26.8010 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"progress" : 0.177164,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:27.3027 Request Issued: GET /agent
02:21:27.3027 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"progress" : 0.620074,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:27.8042 Request Issued: GET /agent
02:21:27.8043 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"progress" : 0.620074,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:28.3055 Request Issued: GET /agent
02:21:28.3056 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"progress" : 1.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:28.8069 Request Issued: GET /agent
02:21:28.8070 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1001.000000,
"progress" : 1.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:29.3084 Request Issued: GET /agent
02:21:29.3085 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1003.000000,
"progress" : 1.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:29.8099 Request Issued: GET /agent
02:21:29.8100 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1003.000000,
"progress" : 1.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:30.3117 Request Issued: GET /agent
02:21:30.3118 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1003.000000,
"progress" : 1.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:30.8278 Request Issued: GET /agent
02:21:30.8279 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1003.000000,
"progress" : 1.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:31.3306 Request Issued: GET /agent
02:21:31.3307 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1003.000000,
"progress" : 1.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:31.8360 Request Issued: GET /agent
02:21:31.8363 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1003.000000,
"progress" : 1.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:31.9532 Handle Event: "auth validation event"
02:21:32.3385 Request Issued: GET /agent
02:21:32.3386 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1003.000000,
"progress" : 1.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:32.8399 Request Issued: GET /agent
02:21:32.8400 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1003.000000,
"progress" : 1.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:33.3424 Request Issued: GET /agent
02:21:33.3425 Response: 200
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 12346.000000,
"state" : 1003.000000,
"progress" : 1.000000,
"critical_update" : true,
"version" : "1.9.2.2380",
"type" : "retail",
"opt_in_feedback" : true,
"session" : "4577714830806487036",
"authorization" : "DC92588DC80320A0B825E99F77CB7434"
02:21:33.5941 Firing Event: "database flush event"
02:21:33.5941 Agent is shutting down
02:21:33.6855 Database Remove: /option
02:21:33.6855 Database Remove: /agent
02:21:33.6855 Database Remove: /agent/download
02:21:33.6855 Queue 'download' Resource for delete
02:21:33.6855 Database Remove: /
02:21:33.6855 Database Remove: /register
02:21:33.6855 Queue 'registerroot' Resource for delete
02:21:33.6855 Database Remove: /game
02:21:33.6855 Queue 'gameroot' Resource for delete
02:21:33.6855 Database Remove: /repair
02:21:33.6855 Queue 'repairroot' Resource for delete
02:21:33.6855 Queue 'agentroot' Resource for delete
02:21:33.6855 Database Remove: /gamesession
02:21:33.6855 Queue 'gamesessionroot' Resource for delete
02:21:33.6855 Database Remove: /backfill
02:21:33.6855 Queue 'backfillroot' Resource for delete
02:21:33.6855 Database Remove: /spawned
02:21:33.6855 Deferred delete of 'download' Resource
02:21:33.6856 Queue 'spawnedroot' Resource for delete
02:21:33.6856 Deferred delete of 'download' Resource completed
02:21:33.6857 Queue 'optionroot' Resource for delete
02:21:33.6857 Deferred delete of 'registerroot' Resource
02:21:33.6857 Database Remove: /version
02:21:33.6857 Deferred delete of 'registerroot' Resource completed
02:21:33.6857 Queue 'versionroot' Resource for delete
02:21:33.6858 Deferred delete of 'gameroot' Resource
02:21:33.6858 Database Remove: /update
02:21:33.6858 Deferred delete of 'gameroot' Resource completed
02:21:33.6858 Queue 'updateroot' Resource for delete
02:21:33.6858 Deferred delete of 'repairroot' Resource
02:21:33.6858 Database Remove: /createshortcut
02:21:33.6858 Deferred delete of 'repairroot' Resource completed
02:21:33.6858 Queue 'createshortcut' Resource for delete
02:21:33.6858 Deferred delete of 'agentroot' Resource
02:21:33.6858 Database Remove: /uninstall
02:21:33.6858 Queue 'uninstallroot' Resource for delete
02:21:33.6858 Database Remove: /install
02:21:33.6858 Queue 'installroot' Resource for delete
02:21:33.6859 Queue 'root' Resource for delete
02:21:33.6859 Deferred delete of 'agentroot' Resource completed
02:21:33.6859 Restarting Agent: /Users/Shared/Battle.net/Agent/Agent.app
--switcherall
--locale=enUS
--session=4577714830806487036
02:21:33.6859 Deferred delete of 'gamesessionroot' Resource
02:21:33.6860 Deferred delete of 'gamesessionroot' Resource completed
02:21:33.6860 Deferred delete of 'backfillroot' Resource
02:21:33.6860 Deferred delete of 'backfillroot' Resource completed
02:21:33.6860 Deferred delete of 'spawnedroot' Resource
02:21:33.6860 Deferred delete of 'spawnedroot' Resource completed
02:21:33.6860 Deferred delete of 'optionroot' Resource
02:21:33.6860 Deferred delete of 'optionroot' Resource completed
02:21:33.6860 Deferred delete of 'versionroot' Resource
02:21:33.6860 Deferred delete of 'versionroot' Resource completed
02:21:33.6860 Deferred delete of 'updateroot' Resource
02:21:33.6860 Deferred delete of 'updateroot' Resource completed
02:21:33.6860 Deferred delete of 'createshortcut' Resource
02:21:33.6860 Deferred delete of 'createshortcut' Resource completed
02:21:33.6860 Deferred delete of 'uninstallroot' Resource
02:21:33.6860 Deferred delete of 'uninstallroot' Resource completed
02:21:33.6860 Deferred delete of 'installroot' Resource
02:21:33.6860 Deferred delete of 'installroot' Resource completed
02:21:33.6860 Deferred delete of 'root' Resource
02:21:33.6860 Deferred delete of 'root' Resource completed
02:21:34.0665 Deleting remaining resources

Similar Messages

Goes into shutdown without command

machine goes into shutdown without being commanded to do so. machine has been cleaned and all motherboard and card connections have been renewed. not sure if it is a hardware or software problem. have run 3 different antivirus and registery cleanings. can anyone advise? machine may run 15 minutes, 1 hour, or a whole day before malfunction occures. boots right back up like there is no problem. no error messages, blue screened once, but i think i caused that. geek squad was a waste of time(?!?). no other quirks occur.

Hi:
I doubt it is a software problem.
If you have not done so already, carefully inspect the capacitors (can shaped objects) on the motherboard for bulging tops/leaking electrolyte. If you find one, that is probably the problem.
If they all look OK, and you have more than one memory module installed, remove all but one and run the PC with the one chip in the required slot.
If the PC shuts down or whatever, remove that memory module and replace it with one of the ones you removed.
Keep doing that until you have tested all modules by themselves.
You may be able to isolate a flaky memory module which for the most part runs OK, but has its moments if the PC runs fine with all but one or two modules.
The only other thing I can think of that it might be, is the power supply has some kind of fault.
I don't know of any way to test that though.

Random Shutdown U300s

Hi
I have a Lenovo U300s, it started to randomly shutdown without a warning or an error message, even if I uncheck "Automatically restart" on System failure it still shutdown. even if the AC attached I get these random shutdowns.
I searched a lot and saw someone with similar problem and a reply suggested that he update his bios, so I did.
my BIOS now is Ver.43
but still the same problem
I did a full recovery by pressing the recovery button on the side of the notebook and gone throw the process selecting anything that give me a full recovery but still the same
so I don't think its a software matter, not sure tho.
is there anything I can try/test or do I have to make a trip to the dealer , I really perfer not to.
please help, Thanks

hi Amajed,
Welcome to Lenovo Community Forums!
Have you tested the CPU and GPU temperatures, If not yet then try installing HWMonitor.
check your Temp maybe it is the temperature increasing beyond normal.
You can post back your findigs here.
Regards
Solid Cruver
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Configuring Shutdown without logon, using command line or script

I´ve configured the shutdown without logon capability in Win2012/R2 using the GPEDIT.MSC
How cna i do that by command line?
In the past i could use the reg key ShutdownWithoutLogon, but i´ve configured in the GUI but nothing happened in the registry of the win2012/R2
C:\>reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v ShutdownWithoutLogon
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
ShutdownWithoutLogon REG_SZ 0
How can i do that, automated, to configure several computers in workgroup environment

Hi KayZerSoze,
Since there has no domain enviroment, remote access is more difficult. However, if the network allows this two workgroups can communicate with each other, you can try Powershell Remoting:
Server 1 remote access Server 2.
1) Run
Enable-PSRemoting –Force on server2
You need to run
Enable-PSRemoting –Force on server1, which gives you the rights to access and modify TrustedHosts setting, or you will receive the error “Set-Item : Access is denied.”
2) You can add the TrustedHosts entry on server1:
Set-Item WSMan:\localhost\Client\TrustedHosts –Value remoteipaddress
This command above configures Windows PowerShell Remoting so that you can connect to any computer, not just those inside trusted domain(s).
Then run the script below to change registry value on server2 with Powershell, which will change the value of "ShutdownWithoutLogon"
to "1":
Invoke-Command -ComputerName server2ipaddress -Credential admin -ScriptBlock {Set-itemproperty -path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" -name ShutdownWithoutLogon -value 1}
For more detailed information about Powershell Remoting, please Refer to this FAQ:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/f60a29ef-925e-4712-9788-1f95e12c8cfc/forum-faq-introduce-windows-powershell-remoting?forum=winserverpowershell
If there is anything else regarding this script, please feel free to post back.
Best Regards,
Anna Wang

Random Shutdown plagues Macbook Pro C2D as well?

Hello everyone,
I know the Macbooks suffer from random shutdowns, but I thought this issue was fixed in the recent models. Apparently, it's still a problem since my brand new macbook pro core 2 duo exhibits random shutdowns when it gets too hot. Yes, I have all my stuff up to date. No, the new firmware does not apply to the Core 2 Duo MBPs.
My question is, is this still a known problem? I haven't really hard of Macbook Pros suffering from this, is this also common with Macbook Pros?
My Macbook does not get extremely hot to the touch, contrary to some of the "Hot" threads on this board. But, I guess it's enough to short the circuit that causes immediate shutdowns. It's easy enough to avoid, but I'd like to push my Macbook to it's fullest without worry of shutdown.

Well, this is what I've found out ...don't know if that will mean anything to you, but does not seem very good to me. Note that this was prior to the date I received my MBP.
Nov 13 18:16:31 localhost kernel[0]: hi mem tramps at 0xffe00000
Nov 13 18:16:31 localhost kernel[0]: PAE enabled
Nov 13 18:16:31 localhost kernel[0]: 64 bit mode enabled
Nov 13 18:16:31 localhost kernel[0]: standard timeslicing quantum is 10000 us
Nov 13 18:16:31 localhost kernel[0]: vmpagebootstrap: 251691 free pages
Nov 13 18:16:31 localhost kernel[0]: migtable_maxdispl = 71
Nov 13 18:16:31 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Nov 13 18:16:31 localhost kernel[0]: ACPI CA 20060421
Nov 13 18:16:31 localhost kernel[0]: AppleIntelCPUPowerManagement: ready
Nov 13 18:16:31 localhost kernel[0]: AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
Nov 13 18:16:31 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
Nov 13 18:16:31 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Nov 13 18:16:31 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Nov 13 18:16:31 localhost kernel[0]: using 5242 buffer headers and 4096 cluster IO buffer headers
Nov 13 18:16:31 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Nov 13 18:16:31 localhost kernel[0]: Started CPU 01
Nov 13 18:16:31 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Nov 13 18:16:31 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Nov 13 18:16:31 localhost kernel[0]: Security auditing service present
Nov 13 18:16:31 localhost kernel[0]: BSM auditing present
Nov 13 18:16:31 localhost kernel[0]: disabled
Nov 13 18:16:31 localhost kernel[0]: rooting via boot-uuid from /chosen: 0DC7FF3D-D334-4F4C-914D-9FA50D95FDA5
Nov 13 18:16:31 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Nov 13 18:16:31 localhost kernel[0]: AppleYukon: 00000000,e00002bc PwrSavingsEED - failed to get EDGP
Nov 13 18:16:31 localhost kernel[0]: USB caused wake event (EHCI)
Nov 13 18:16:31 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 0017f2fffe814a26; max speed s800.
Nov 13 18:16:31 localhost kernel[0]: CSRHIDTransitionDriver::probe:
Nov 13 18:16:31 localhost kernel[0]: CSRHIDTransitionDriver::start before command
Nov 13 18:16:31 localhost kernel[0]: Extension "com.apple.driver.AppleUSBTCKeyboard" has no kernel dependency.
Nov 13 18:16:31 localhost kernel[0]: Extension "com.apple.driver.AppleUSBTCKeyEventDriver" has no kernel dependency.
Nov 13 18:16:31 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT2 @2/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDri ver/Hitachi HTS541612J9SA00 Media/IOGUIDPartitionScheme/Customer@2
Nov 13 18:16:31 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Nov 13 18:16:31 localhost kernel[0]: CSRHIDTransitionDriver::stop
Nov 13 18:16:31 localhost kernel[0]: HFS: created HFBT on Macintosh HD
Nov 13 18:16:31 localhost kernel[0]: IOBluetoothHCIController::start Idle Timer Stopped
Nov 13 18:16:31 localhost kernel[0]: Jettisoning kernel linker.
Nov 13 18:16:31 localhost kernel[0]: Resetting IOCatalogue.
Nov 13 18:16:31 localhost kernel[0]: display: family specific matching fails
Nov 13 18:16:31 localhost kernel[0]: Matching service count = 0
Nov 13 18:16:31 localhost kernel[0]: Matching service count = 1
Nov 13 18:16:31 localhost kernel[0]: Matching service count = 1
Nov 13 18:16:31 localhost kernel[0]: Matching service count = 1
Nov 13 18:16:31 localhost kernel[0]: Matching service count = 1
Nov 13 18:16:31 localhost kernel[0]: Matching service count = 1
Nov 13 18:16:31 localhost kernel[0]: display: family specific matching fails
Nov 13 18:16:31 localhost kernel[0]: ath_attach: devid 0x24
Nov 13 18:16:31 localhost kernel[0]: display: family specific matching fails
Nov 13 18:16:31 localhost kernel[0]: mac 12.10 phy 8.1 radio 12.0
Nov 13 18:16:31 localhost kernel[0]: display: family specific matching fails
Nov 13 18:16:31 localhost kernel[0]: Previous Shutdown Cause: 3
Nov 13 18:16:31 localhost kernel[0]: display: family specific matching fails
Nov 13 18:16:31 localhost mDNSResponder-108.2 (Aug 20 2006 04: 04:10)[57]: starting
Nov 13 18:16:31 localhost memberd[65]: memberd starting up
Nov 13 18:16:33 localhost lookupd[71]: lookupd (version 369.6) starting - Mon Nov 13 18:16:33 2006
Nov 13 18:16:35 localhost diskarbitrationd[63]: disk0s2 hfs F89B2CC8-63E3-337A-9EE4-346BAB54E7BB Macintosh HD /
Nov 13 18:16:35 localhost DirectoryService[72]: Launched version 2.1 (v353.5)
Nov 13 18:16:36 localhost kernel[0]: yukonosx: Ethernet address 00:17:f2:c2:38:10
Nov 13 18:16:36 localhost kernel[0]: AirPort_Athr5424: Ethernet address 00:17:f2:e7:66:7d
Nov 13 18:16:37 localhost lookupd[91]: lookupd (version 369.6) starting - Mon Nov 13 18:16:37 2006
Nov 13 18:16:39 localhost mDNSResponder: Couldn't read user-specified Computer Name; using default ‚ÄúMacintosh-0017F2C23810‚Äù instead
Nov 13 18:16:39 localhost mDNSResponder: Couldn't read user-specified local hostname; using default ‚ÄúMacintosh-0017F2C23810.local‚Äù instead
Nov 13 18:16:40 localhost kernel[0]: Registering For 802.11 Events
Nov 13 18:16:40 localhost kernel[0]: [HCIController][setupHardware] AFH Is Supported
Nov 13 18:16:40 localhost mDNSResponder: Adding browse lanain local.
Nov 13 18:16:43 localhost KernelEventAgent[56]: tid 00000000 received unknown event (256)
Nov 13 18:16:56 localhost /System/Library/PrivateFrameworks/Admin.framework/Resources/UpdateSettingsTool: UpdateSettings Error: makequeues -u returned 512
Nov 13 18:16:57 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Nov 13 18:38:50 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Nov 13 18:39:03 localhost /System/Library/CoreServices/Setup Assistant.app/Contents/MacOS/Setup Assistant: _MDSuspendIndexing() 1
Nov 13 18:39:05 localhost /System/Library/CoreServices/Setup Assistant.app/Contents/MacOS/Setup Assistant: starting movie now\n
Nov 13 18:39:33 localhost /System/Library/CoreServices/Setup Assistant.app/Contents/MacOS/Setup Assistant: movie done now (hide)
Nov 13 18:39:40 localhost mDNSResponder: Couldn't read user-specified Computer Name; using default ‚ÄúMacintosh-0017F2C23810‚Äù instead
Nov 13 18:39:40 localhost mDNSResponder: Couldn't read user-specified local hostname; using default ‚ÄúMacintosh-0017F2C23810.local‚Äù instead
Nov 13 18:40:34 localhost ntpdate[622]: no servers can be used, exiting
Nov 13 18:40:34 localhost ntpd[624]: bind() fd 11, family 30, port 123, addr fe80:5::217:f2ff:fee7:667d, in6is_addrmulticast=0 flags=0 fails: Can't assign requested address
Nov 13 18:40:38 localhost mDNSResponder: Couldn't read user-specified Computer Name; using default ‚ÄúMacintosh-0017F2C23810‚Äù instead
Nov 13 18:40:38 localhost mDNSResponder: Couldn't read user-specified local hostname; using default ‚ÄúMacintosh-0017F2C23810.local‚Äù instead
Nov 13 18:40:38 localhost configd[61]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Nov 13 18:40:38 localhost configd[61]: posting notification com.apple.system.config.network_change
Nov 13 18:40:38 localhost lookupd[627]: lookupd (version 369.6) starting - Mon Nov 13 18:40:38 2006
Nov 13 18:40:40 localhost mDNSResponder: Couldn't read user-specified Computer Name; using default ‚ÄúMacintosh-0017F2C23810‚Äù instead
Nov 13 18:40:40 localhost mDNSResponder: Couldn't read user-specified local hostname; using default ‚ÄúMacintosh-0017F2C23810.local‚Äù instead
Nov 13 18:40:42 localhost configd[61]: target=enable-network: disabled
First Crash --> computer suddenly OFF !
i've had 5 or six crashes since I received my MBP on Nov. 15th. Apple told me it must be a hardware problem. I have other stuff to read from the console if you're interested caus' quite frankly this does not make a lot of sense to me.

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

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

Random shutdowns X99S SLI Plus, ms-7885

Hello,
I'm trying to narrow down some random shutdowns. These seemed to be completely random and could happen with the computer idling. The computer just shutdowns and reboots. Nothing in the log, no BSOD. I have tried to trigger the problem by running CPU and GPU stresstests without success.
Until wither 3 came out. With witcher 3 the problem is 100% reproducible. Start witcher 3 => shutdown.
I can play other games for hours without any problems.
Can someone give a hint on how to find the problem?
/Tommy
Board: X99S SLI Plus
Bios: 1.8
VGA: Gainward titan X
PSU: Corsair RM750, 750W PSU ATX 12V V2.4, 80 Plus Gold, Modular, 4x 6+2-pin PC
CPU: Intel Core i7-5820K, Socket-LGA2011-3
MEM: Crucial DDR4 Ballistix Sport 32GB (8GBx4), 2400MHz (PC4-19200) CL16 SR x8 Unbuff
HDD: HyperX Predator SSD 240GB M.2 PCIe
COOLER: Cooler Master Seidon 120V v2 CPU
OC: none
OS: Windows 8.1

Some updates...
Tried to run with only two memory sticks, no problem with that. Even if I switch one it works. But with three it crashes after I exit witcher 3. Wierd since I can play the game without problem.
Ran some memtests one only one stick in. Only got errors in the "hammer test" which I guess is ok.
Put all four memories in again and ran memtest over the night. It ran one pass and after that the comp shut down and rebooted.
Downclocked memory to 1333 and ran 4 passes memtest without any crash. Some hammer test errors only.
I'm now trying to run at 2200 and it seems fine. I can play witcher and exit without any crash.
Is it the memory or the MB? Or just a bad combo?
/T

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: Locked Clockspeed, Processor Voltage Correlation?

I use Hardware Monitor to keep track of more sensor readouts than just temps. I recommend everyone install it. Using it, I've discovered some weird behavior in the processor clockspeed and voltage that correlates in a predictable with my typical macbook random shutdown problem. I wonder if others witness the same correlation.
Normally, according to my sensor readings, the clockspeed and cpu voltage fluctuate frequently and continually, presumably according to the demands on the processor. Clockspeed typically runs between 1333Mhz and 2000Mhz, voltage between 1.00 and 1.30V.
When running like this, it is subject to random shutdowns at any time, but most especially — indeed with absolute reliability, so to speak — within ten minutes of waking from sleep — regardless of whether i'm using mail, surfing, playing music, or running intense calculations and (so far as i can tell), regardless of how many or few processes are running simultaneously, and regardless of temperature readings. Indeed, now with the new firmware update my temps are quite low. In fact, since the computer most reliably shuts down soon after waking up, it's temp at shutdown often registers no more than the mid-50s (it'll shut down at 47).
After the macbook shuts down, it refuses to restart reliably with a simple press of the power button. Like many others, I have to hold down the power button for about ten seconds, until I hear the pained protracted beep, before the computer will enter into the normal booting process.
After it boots up like this from a shutdown — and this is what I haven't seen enough commentary on — the processor speed remains locked at 1000Mhz and the voltage at .99V until the computer goes to sleep again.
While the computer is locked into this slow-clockspeed-low-voltage mode, it is absolutely reliable. It never shuts down randomly. It runs much slower. Which is really noticeable and frustrating when using any graphics-intense or movie app.
So my questions are:
Does anyone else experience this sort of locking processor behavior?
Why would the processor lock like this?
Is it possible that the sensors are wrong? That in fact the processor is fluctuating normally but now the computer doesn't "know" it?
How would the processor's ability to vary its clockspeed and the voltage it draws affect its propensity to shutdown randomly?
I would be grateful for the observations of others regarding clockspeed and voltage at shutdown and after rebooting.
Thanks.
macbook 2.0 Ghz, 1.25GB, 80GB, week 20 Mac OS X (10.4.7)

hi
I have exactly same problems and symptoms.
It was a refurbished week 20 unit from apple uk it arrived in excellent condition and worked perfectly for two weeks without the fan comeing on at all it was perfectly quiet but hot.
As this was my first mac I was unaware that this was abnormal I had heard that they ran hot but being new to mac I was on a learning curve. Then two days after the remorse return period it began to shut down the first time was after a period of sleep just after I opened the lid. It then was and still is impossible to start it from warm or cold in the normal way, but only by holding the power down until beep. Then it will work for days at 27 deg c without a problem all be it at the 1 gig reduced speed which as you say is frustrating to say the least. Applecare UK don't acknowledge the problem at all they just want to treat it as a normal warrenty repair at my inconvenience. I am at present awaiting a more generous response from apple. I'm demanding a replacement unit but they just want we to fill out their standard web questionaire. (with non relavant tick boxs) If only one could speak to a real knowledgeable individual at apple I'm sure I'd get some satisfaction. But in this age of executive big bonuses what can one expect.
I hope Apple get real with this soon because the disscussion forums are getting overloaded with this issue its getting harder to login have you noticed.
yours unhappy customer.

My laptop Shutdown without warning

My new hp pavilion that I bout around october 2014'seem to be shutdown without warning. it shutdown with the shutdown window appear thou. it happen 3 times. please help

Hi @timotius ,
Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your HP Notebook and having it shut down without warning. Here is a link to restore the BIOS. Please note remove any and all USB devices, and remove memory cards from the card reader slot. Disconnect all non-essential devices.
Can get to safe mode with command prompt? sfc /scannow would scan your system for errors at the command prompt. You could check this Microsoft document on system recovery options.
Here is a link to the HP Support Assistant. Just download and run the application and it will help with the software and drivers on your system. If you needed an update this could cause what you have installed.
Did you install any software or hardware?
Hope this helps you.
Thanks.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

Macbook Pro 15 " 2.53GHZ mid 2009 random shutdowns

Hello,
I've a Macbook Pro 15" 2.53GHZ mid 2009 that have random shutdowns and when he shutdown he dont turn on in power button, because the button dont do nothing at all. Sometimes, only after hours the macbook pro automaticaly turn on. I have already clear the fans and replace the thermal paste but with no sucess because problem still exists.
What's the problem with this mac?
Regards

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
This procedure is a diagnostic test. It makes no changes to your data.
Please triple-click anywhere in the line below on this page to select it:
syslog -k Sender kernel -k Message CSeq 'n Cause: -' | tail | awk '/:/{$4=""; print}' | pbcopy
Copy the selected text to the Clipboard by pressing the key combination command-C.
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window by pressing the key combination command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.
Wait for a new line ending in a dollar sign ($) to appear below what you entered.
The output of the command will be automatically copied to the Clipboard. If the command produced no output, the Clipboard will be empty. Paste into a reply to this message.
The Terminal window doesn't show the output. Please don't copy anything from there.

Random shutdowns: my experience, and a suggestion

I own a BlackBook whose random shutdowns began a couple of weeks ago.
During my first trip to my local Genius Bar, the guy behind the counter reset the PMU and PRAM, and was unable to reproduce the problem, and sent me on my way.
The random shutdowns continued.
During my second trip to the Genius Bar, the guy was able to boot the machine from another drive, and was able to reproduce the problem. The machine was sent to the repair center for servicing. I got it back a few days later.
Random shutdowns have still occurred, but I find that if I reset the PRAM as the machine is booting, and wait for at least three startup chimes before letting go of the key combination (control-option-P-R), the machine seems to stabilize and not shut down on its own, at least so far.
Before repair, the machine was also exhibiting the "vertical colored lines at startup" problem. Before that, it needed a replacement power adapter and a replacement battery (the battery was refusing to take a charge or even be recognized by the computer).
Various theories for the cause or causes of the problem with random shutdowns have been suggested -- along with a number of magic-bullet solutions from different sources. My guess is that even Apple isn't sure what's causing the issue, and there's certainly no foolproof solution that the user can apply. We'll just have to wait and see what comes of the investigations.
Despite these problems, I still love the BlackBook and think it's perhaps the most beautifully designed computer ever made. I assume that once these growing pains subside, Apple will have a total winner on its hands.
MacBook (black) 13" Mac OS X (10.4.7)

I have a whitebook bought in June, shutdowns started about 6 weeks after I got it. Did the whole tech support line thing several times resetting various things etc. No change. Sent it in for repair with a strong encouragement that it would only take 48 hours. It is now 10 days later and repair is still on hold. Sent in several "why is this dragging on" and got nice automatic reponse saying they would respond in a day or two. No real responses yet. Called today the helpful tech said they would check and see what was holding things up and let me know when I called back in 48 hours. Assured me I would not be without my Macbook more than a week longer. Have missed work and have a presentation on Friday that I will have to do without it. Had I known it would take this long I would have taken my chance that it would not shut down mid stream in the presentation. I am very disapointed with Apple at this point. Have been a long time user and own stock etc. This is the worse customer service I have gotten on a computer problem, personal or business. Apple needs to realize they have a batch of lemons on their hands and bite the bullet and replace them. I am not encouraged to hear others are getting their books back repaired only to find the problem on going.

Random Shutdown Without Command

Similar Messages

Maybe you are looking for