Macbook Pro Crashing Every 30 Minutes

Question

Level 1

8 points

Macbook Pro Crashing Every 30 Minutes

Every 30-45 minutes my Macbook pro 13" 2012 crashes and gets stuck on the screen I am on. It's running on Yosemite right now. I bought it to a mac repair store for them to do diagnostic check on it and they said it was the hard drive. I brought it to another place to verify and the guy there said the hard drive test came up fine. I didn't know what to believe so I did an AHT test (extended) and it came back fine. Checked with the disk utility and verified the hard drive and that came back fine too. I don't know what to do or what else it could be. Does anyone have any suggestions.

MacBook Pro, OS X Yosemite (10.10.4)

Posted on Jul 30, 2015 2:42 PM

Reply

Answer 1

Linc Davis

Level 10

209,541 points

Jul 30, 2015 2:46 PM in response to Boehm2

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Launch the Console 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 and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES ▹ All Messages

from the log list on the left. If you don't see that list, select

View ▹ Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Enter "BOOT_TIME" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.

If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.

When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Some private information, such as your name, may appear in the log. Anonymize before posting.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select

View ▹ Show Log List

from the menu bar.

There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

Reply

Answer 2

Boehm2 Author

Level 1

8 points

Jul 30, 2015 3:29 PM in response to Linc Davis

7/30/15 5:57:45.380 PM com.apple.xpc.launchd[1]: (com.teamviewer.desktop) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:57:45.410 PM virusbarriers[1939]: VirusBarrier X6 OK

7/30/15 5:57:45.598 PM com.apple.xpc.launchd[1]: (com.intego.VirusBarrierX6.scanner.daemon[1939]) Service exited due to signal: Killed: 9

7/30/15 5:57:49.697 PM com.apple.xpc.launchd[1]: (com.teamviewer.service[1959]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/MacOS: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:57:49.697 PM com.apple.xpc.launchd[1]: (com.teamviewer.service) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:57:53.000 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

7/30/15 5:57:53.645 PM com.apple.iCloudHelper[1961]: objc[1961]: Class FALogging is implemented in both /System/Library/PrivateFrameworks/FamilyCircle.framework/Versions/A/FamilyCircl e and /System/Library/PrivateFrameworks/FamilyNotification.framework/Versions/A/Famil yNotification. One of the two will be used. Which one is undefined.

7/30/15 5:57:53.658 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

7/30/15 5:57:54.950 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

7/30/15 5:57:55.385 PM com.apple.xpc.launchd[1]: (com.teamviewer.desktop[1964]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/Helpers: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:57:55.385 PM com.apple.xpc.launchd[1]: (com.teamviewer.teamviewer[1963]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/MacOS: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:57:55.386 PM com.apple.xpc.launchd[1]: (com.teamviewer.desktop) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:57:55.386 PM com.apple.xpc.launchd[1]: (com.teamviewer.teamviewer) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:57:59.701 PM com.apple.xpc.launchd[1]: (com.teamviewer.service[1965]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/MacOS: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:57:59.701 PM com.apple.xpc.launchd[1]: (com.teamviewer.service) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:05.393 PM com.apple.xpc.launchd[1]: (com.teamviewer.desktop[1966]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/Helpers: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:05.393 PM com.apple.xpc.launchd[1]: (com.teamviewer.teamviewer[1967]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/MacOS: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:05.393 PM com.apple.xpc.launchd[1]: (com.teamviewer.desktop) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:05.394 PM com.apple.xpc.launchd[1]: (com.teamviewer.teamviewer) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:09.707 PM com.apple.xpc.launchd[1]: (com.teamviewer.service[1968]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/MacOS: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:09.707 PM com.apple.xpc.launchd[1]: (com.teamviewer.service) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:15.430 PM com.apple.xpc.launchd[1]: (com.teamviewer.desktop[1969]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/Helpers: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:15.430 PM com.apple.xpc.launchd[1]: (com.teamviewer.teamviewer[1970]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/MacOS: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:15.431 PM com.apple.xpc.launchd[1]: (com.teamviewer.desktop) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:15.431 PM com.apple.xpc.launchd[1]: (com.teamviewer.teamviewer) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:17.338 PM virusbarriers[1956]: VirusBarrier X6 OK

7/30/15 5:58:17.997 PM com.apple.xpc.launchd[1]: (com.intego.VirusBarrierX6.scanner.daemon[1956]) Service exited due to signal: Killed: 9

7/30/15 5:58:19.714 PM com.apple.xpc.launchd[1]: (com.teamviewer.service[1978]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/MacOS: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:19.715 PM com.apple.xpc.launchd[1]: (com.teamviewer.service) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:25.437 PM com.apple.xpc.launchd[1]: (com.teamviewer.teamviewer[1981]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/MacOS: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:25.437 PM com.apple.xpc.launchd[1]: (com.teamviewer.desktop[1980]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/Helpers: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:25.437 PM com.apple.xpc.launchd[1]: (com.teamviewer.teamviewer) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:25.437 PM com.apple.xpc.launchd[1]: (com.teamviewer.desktop) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:29.721 PM com.apple.xpc.launchd[1]: (com.teamviewer.service[1982]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/MacOS: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:29.721 PM com.apple.xpc.launchd[1]: (com.teamviewer.service) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:35.442 PM com.apple.xpc.launchd[1]: (com.teamviewer.teamviewer[1983]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/MacOS: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:35.443 PM com.apple.xpc.launchd[1]: (com.teamviewer.desktop[1984]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/Helpers: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:35.443 PM com.apple.xpc.launchd[1]: (com.teamviewer.teamviewer) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:35.443 PM com.apple.xpc.launchd[1]: (com.teamviewer.desktop) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:39.727 PM com.apple.xpc.launchd[1]: (com.teamviewer.service[1986]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/MacOS: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:39.727 PM com.apple.xpc.launchd[1]: (com.teamviewer.service) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:45.477 PM com.apple.xpc.launchd[1]: (com.teamviewer.teamviewer[1987]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/MacOS: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:45.477 PM com.apple.xpc.launchd[1]: (com.teamviewer.teamviewer) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:45.477 PM com.apple.xpc.launchd[1]: (com.teamviewer.desktop[1988]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/Helpers: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:45.478 PM com.apple.xpc.launchd[1]: (com.teamviewer.desktop) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 5:58:49.733 PM com.apple.xpc.launchd[1]: (com.teamviewer.service[1991]) Service could not initialize: Unable to set current working directory. error=2, path=/Applications/TeamViewer.app/Contents/MacOS: 14E46: xpcproxy + 12761 [1285][7D917364-B96E-3F93-B923-A89B5BF5736D]: 0x2

7/30/15 5:58:49.733 PM com.apple.xpc.launchd[1]: (com.teamviewer.service) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

7/30/15 6:01:12.000 PM bootlog[0]: BOOT_TIME 1438293672 0

Process: airportd [4423]

Path: /usr/libexec/airportd

Identifier: airportd

Version: ???

Code Type: X86-64 (Native)

Parent Process: launchd [1]

Responsible: airportd [4423]

User ID: 0

Date/Time: 2015-07-29 20:03:17.674 -0400

OS Version: Mac OS X 10.10.4 (14E46)

Report Version: 11

Anonymous UUID:

Time Awake Since Boot: 1700 seconds

Crashed Thread: 0

Exception Type: EXC_CRASH (Code Signature Invalid)

Exception Codes: 0x0000000000000000, 0x0000000000000000

kernel messages:

VM Regions Near 0x7fff7c2470a0 (cr2):

__LINKEDIT 00007fff6b9ce000-00007fff6b9e2000 [ 80K] r--/rwx SM=COW /usr/lib/dyld

--> Submap 00007fff70000000-00007fff80000000 [256.0M] r--/rwx SM=PRV process-only VM submap

unused shlib __DATA 00007fff7a604000-00007fff7cc04000 [ 38.0M] rw-/rw- SM=COW system shared lib __DATA not used by this process

Thread 0 Crashed:

0 dyld 0x00007fff6b95f000 _dyld_start + 0

Thread 0 crashed with X86 Thread State (64-bit):

rax: 0x000000000000000d rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000

rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007fff5361ce60

r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000

r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000

rip: 0x00007fff6b95f000 rfl: 0x0000000000000201 cr2: 0x00007fff7c2470a0

Logical CPU: 0

Error Code: 0x020000f4

Trap Number: 133

Binary Images:

0x7fff6b95e000 - 0x7fff6b994837 dyld (???) <72A99D0F-0B56-3938-ABC5-67A0F33757C4> /usr/lib/dyld

External Modification Summary:

Calls made by other processes targeting this process:

task_for_pid: 0

thread_create: 0

thread_set_state: 0

Calls made by this process:

task_for_pid: 0

thread_create: 0

thread_set_state: 0

Calls made by all processes on this machine:

task_for_pid: 1455

thread_create: 0

thread_set_state: 0

VM Region Summary:

ReadOnly portion of Libraries: Total=300K resident=300K(100%) swapped_out_or_unallocated=0K(0%)

Writable regions: Total=8420K written=0K(0%) resident=12K(0%) swapped_out=0K(0%) unallocated=8408K(100%)

REGION TYPE VIRTUAL

=========== =======

STACK GUARD 56.0M

Stack 8192K

VM_ALLOCATE 8K

VM_ALLOCATE (reserved) 8K reserved VM address space (unallocated)

__DATA 228K

__LINKEDIT 80K

__TEXT 220K

mapped file 1104K

shared memory 4K

=========== =======

TOTAL 65.6M

TOTAL, minus reserved VM space 65.6M

Reply

Answer 3

OGELTHORPE

Level 9

57,305 points

Jul 30, 2015 3:33 PM in response to Boehm2

Log and post the kernel panic report using these directions:

https://support.apple.com/en-us/HT201753

Ciao.

Reply

Answer 4

Linc Davis

Level 10

209,541 points

Jul 30, 2015 3:51 PM in response to Boehm2

Remove the Intego product by following the instructions on this page . If you have a different version, the procedure may be different.

Back up all data before making any changes. Never install any "anti-malware" program again.

Reply