My brand-new iMac keeps freezing. HELP!!

Question

Level 1

5 points

My brand-new iMac keeps freezing. HELP!!

I just bought a new 27" iMac, 3.4GHz i7, 8GB RAM, 1TB Fusion Drive. After about a month, I started getting the spinning beach ball of death and the entire computer will freeze until I hard power off. This seems to happen at completely random times.

I have re-installed OSX, I have reset PRAM, I have verified/repaired disk and permissions...everything I have thought of and read about on forums.

It seemed like CrashPlan's backup software was causing the issue, but after uninstalling the software, the problem only happend much less frequently.

This is my first Mac, coming over from PC. I loved my iMac until I started having these issues...now I'm wondering if the almost $3,000 was well spent. I really hope I can get this issue resolved FOR GOOD!

iMac, OS X Mountain Lion (10.8)

Posted on Feb 28, 2013 11:02 PM

Reply

Answer 1

John Galt

Level 10

141,060 points

Feb 28, 2013 11:07 PM in response to joeholl

Why not call AppleCare? Your $3000 includes 90 days of free telephone support. Use it.

To avoid waiting on hold, call early in the morning. Or, they can call you back if you choose. Have your Mac's serial number ready. It can be found on the box, on your invoice, or by clicking  > About This Mac. Click the Version text twice and its serial number will appear.

Reply

Answer 2

Mar 1, 2013 3:05 AM in response to joeholl

To add to what John Galt recommended, purchase Apple Care. Apple Care extends your warranty to 3 years and gives you access to tech support and repairs if needed. You can purchase Apple Care during the 1 year that your warranty is in effect. I'd recommend the purchase sooner rather than later.

Reply

Answer 3

Shootist007

Level 6

16,703 points

Mar 1, 2013 3:34 AM in response to joeholl

Never mind.

Good Luck & Best Wishes.

Reply

Answer 4

joeholl Author

Level 1

5 points

Mar 1, 2013 7:33 AM in response to John Galt

I did call Apple Support and they had me uninstall CrashPlan. That seems to work until a few days later.

Reply

Answer 5

John Galt

Level 10

141,060 points

Mar 1, 2013 8:01 AM in response to joeholl

Call AppleCare again. Provide the Case ID they gave you from the previous call. If it is a hardware fault only Apple will be able to fix it.

To find your case number log in with your Apple ID here:

https://supportprofile.apple.com/

Click on "cases" - it looks like a folder icon.

When you restarted your Mac, did it present the following dialog?

Next time it does, click Report... Copy and paste the text that appears in a response here, and send the report to Apple. The report is de-identified and used to resolve potential problems with OS X. You will not get a response (not possible since the report is de-identified).

Check your System Preferences > Security & Privacy > Privacy. I recommend you configure it like so:

If the problem occurs due to software that you installed such as CrashPlan or modifications to OS X Apple will not care. If you think that is a possibility then reply and I will have another suggestion.

Reply

Answer 6

Linc Davis

Level 10

209,547 points

Mar 1, 2013 8:42 AM in response to joeholl

If you have more than one user account, these instructions must be carried out as an 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. Click Utilities, then Console in the icon grid.

Step 1

Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

View ▹ Show Log List

from the menu bar.

Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Select the messages logged before the boot, while the system was unresponsive or was failing to shut down. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V). Please include the BOOT_TIME message at the end of the log extract.

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

When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

Please do not indiscriminately dump thousands of lines from the log into this discussion.

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

Step 2

Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the entire contents of the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

Reply

Answer 7

joeholl Author

Level 1

5 points

Mar 1, 2013 9:05 AM in response to Linc Davis

3/1/13 11:12:59.744 AM CrashPlan[689]: 1: -Djava.class.path=/Applications/CrashPlan.app/Contents/Resources/Java/lib/com.b ackup42.desktop.jar:/Applications/CrashPlan.app/Contents/Resources/Java/skin:/Ap plications/CrashPlan.app/Contents/Resources/Java/lang:

3/1/13 11:12:59.744 AM CrashPlan[689]: 2: -Djava.library.path=/Applications/CrashPlan.app/Contents/MacOS

3/1/13 11:12:59.744 AM CrashPlan[689]: 3: -XstartOnFirstThread

3/1/13 11:12:59.745 AM CrashPlan[689]: 4: com.backup42.desktop.CPDesktopWrapper

3/1/13 11:12:59.745 AM CrashPlan[689]: Launch17

3/1/13 11:12:59.745 AM CrashPlan[689]: Java Directory: {

ClassPath = (

"$JAVAROOT/lib/com.backup42.desktop.jar",

"$JAVAROOT/skin",

"$JAVAROOT/lang"

);

JVMArches = (

i386,

ppc

);

JVMVersion = "1.5*";

MainClass = "com.backup42.desktop.CPDesktopWrapper";

StartOnMainThread = 1;

VMOptions = (

"-Dfile.encoding=UTF-8",

"-DappBaseName=CrashPlan",

"-Dsun.net.inetaddr.ttl=300",

"-Dnetworkaddress.cache.ttl=300",

"-Dsun.net.inetaddr.negative.ttl=0",

"-Dnetworkaddress.cache.negative.ttl=0",

"-Djava.net.preferIPv4Stack=true"

);

WorkingDirectory = "$APP_PACKAGE/Contents/Resources/Java";

}

3/1/13 11:12:59.746 AM CrashPlan[689]: NO Java Arguments

3/1/13 11:12:59.746 AM CrashPlan[689]: Arguments...

3/1/13 11:12:59.746 AM CrashPlan[689]: 0: /Applications/CrashPlan.app/Contents/MacOS/CrashPlan

3/1/13 11:12:59.746 AM CrashPlan[689]: 1: -Djava.class.path=/Applications/CrashPlan.app/Contents/Resources/Java/lib/com.b ackup42.desktop.jar:/Applications/CrashPlan.app/Contents/Resources/Java/skin:/Ap plications/CrashPlan.app/Contents/Resources/Java/lang:

3/1/13 11:12:59.747 AM CrashPlan[689]: 2: -Djava.library.path=/Applications/CrashPlan.app/Contents/MacOS

3/1/13 11:12:59.747 AM CrashPlan[689]: 3: -XstartOnFirstThread

3/1/13 11:12:59.747 AM CrashPlan[689]: 4: com.backup42.desktop.CPDesktopWrapper

3/1/13 11:14:04.686 AM Mail[695]: Using V2 Layout

3/1/13 11:14:05.023 AM librariand[697]: MMe quota status changed: under quota

3/1/13 11:14:05.221 AM com.apple.SecurityServer[15]: Killing auth hosts

3/1/13 11:14:05.221 AM com.apple.SecurityServer[15]: Session 100014 destroyed

3/1/13 11:14:05.233 AM com.apple.SecurityServer[15]: Session 100015 created

3/1/13 11:14:20.439 AM WindowServer[102]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff

3/1/13 11:16:43.179 AM iTunes[301]: _NotificationSocketReadCallbackGCD (thread 0x7fff7d69c180): Unexpected connection closure...

3/1/13 11:16:43.180 AM ath[388]: _NotificationSocketReadCallbackGCD (thread 0x7fff7d69c180): Unexpected connection closure...

3/1/13 11:17:08.382 AM com.apple.SecurityServer[15]: Session 100016 created

3/1/13 11:18:04.863 AM Messages[806]: [Warning] Updating typing guid on IMMessage from CA60D7BB-372A-4239-93B9-98AE00D85C0A to 77CDFA7E-5540-4969-8311-9B07D9761919

3/1/13 11:18:08.581 AM iTunes[301]: _NotificationSocketReadCallbackGCD (thread 0x7fff7d69c180): Unexpected connection closure...

3/1/13 11:18:08.582 AM ath[388]: _NotificationSocketReadCallbackGCD (thread 0x7fff7d69c180): Unexpected connection closure...

3/1/13 11:18:08.868 AM Messages[806]: [Warning] Updating typing guid on IMMessage from AB7135B4-0180-4E70-9976-924A614E20DB to 7C3AF677-64E2-4EC3-9C43-5A8D0B51AB57

3/1/13 11:18:15.021 AM Messages[806]: [Warning] Updating typing guid on IMMessage from C8D0F915-74A4-469F-9ACE-5EE3E01DDA59 to EEA18800-3E18-4B72-BA26-9C093DCE37ED

3/1/13 11:18:47.397 AM com.apple.SecurityServer[15]: Killing auth hosts

3/1/13 11:18:47.397 AM com.apple.SecurityServer[15]: Session 100016 destroyed

3/1/13 11:18:47.415 AM com.apple.SecurityServer[15]: Session 100017 created

3/1/13 11:21:19.757 AM java[81]: __TCCAccessRequest_block_invoke_040: Connection invalid

3/1/13 11:21:29.095 AM com.apple.launchd.peruser.501[228]: (0x7feed28010b0.anonymous.com.apple.dock.[334]) Unmanaged jobs may not make XPC Events requests.

3/1/13 11:21:29.095 AM com.apple.dock.extra[334]: Event channel check-in failed: com.apple.usernotificationcenter.matching: 0x1: Operation not permitted

3/1/13 11:21:29.096 AM com.apple.dock.extra[334]: Bug: 12C2037: libxpc.dylib + 35251 [FAC04D8B-680E-325F-8F0C-DD69859D0E01]: 0x1

3/1/13 11:21:29.096 AM com.apple.dock.extra[334]: Got bogus event on event stream listener connection. You may have called xpc_set_event_stream_handler() more than once for the same stream: <error: 0x7fff7cc60ca0> { count = 1, contents =

"XPCErrorDescription" => <string: 0x7fff7cc60c20> { length = 18, contents = "Connection invalid" }

}

3/1/13 11:21:50.786 AM Messages[806]: [Warning] Updating typing guid on IMMessage from CA00CC8A-51EA-4B96-8906-EB70051264A6 to 65FBFC5F-8B5C-4156-B995-92B8CB95F4E6

3/1/13 11:22:10.424 AM Dock[276]: CGSSetWindowTransformAtPlacement: Singular matrix [inf 0.000 0.000 inf]

3/1/13 11:22:10.643 AM Dock[276]: Unable to open IOHIDSystem (e00002bd)

3/1/13 11:22:10.000 AM kernel[0]: virtual bool IOHIDEventSystemUserClient::initWithTask(task_t, void *, UInt32): Client task not privileged to open IOHIDSystem for mapping memory (e00002c1)

3/1/13 11:25:11.055 AM iTunes[301]: _NotificationSocketReadCallbackGCD (thread 0x7fff7d69c180): Unexpected connection closure...

3/1/13 11:25:11.056 AM ath[381]: _NotificationSocketReadCallbackGCD (thread 0x7fff7d69c180): Unexpected connection closure...

3/1/13 11:30:28.188 AM lsboxd[304]: @AE relay 4755524c:4755524c

3/1/13 11:31:00.781 AM iTunes[301]: _NotificationSocketReadCallbackGCD (thread 0x7fff7d69c180): Unexpected connection closure...

3/1/13 11:31:00.782 AM ath[388]: _NotificationSocketReadCallbackGCD (thread 0x7fff7d69c180): Unexpected connection closure...

3/1/13 11:43:25.000 AM bootlog[0]: BOOT_TIME 1362156205 0

Reply

Answer 8

joeholl Author

Level 1

5 points

Mar 1, 2013 9:07 AM in response to Linc Davis

Process: DashboardClient [408]

Path: /System/Library/CoreServices/Dock.app/Contents/Resources/DashboardClient.app/Co ntents/MacOS/DashboardClient

Identifier: DashboardClient

Version: 1.8 (1.8)

Code Type: X86 (Native)

Parent Process: Dock [190]

User ID:

Date/Time: 2013-02-24 00:36:03.322 -0500

OS Version: Mac OS X 10.8.2 (12C2037)

Report Version: 10

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c0008d40

VM Regions Near 0xc0008d40:

Stack 00000000bf79e000-00000000bff9e000 [ 8192K] rw-/rwx SM=PRV

-->

CG shared images 00000000c000c000-00000000c0014000 [ 32K] rw-/rw- SM=PRV

Application Specific Information:

/Users/Family/Library/Widgets/iStat pro.wdgt/

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 com.apple.CoreGraphics 0x93b0873f CGSWindowByID + 102

1 com.apple.CoreGraphics 0x93b79090 CGSOrderWindowListWithGroups + 226

2 com.apple.AppKit 0x96c65140 -[NSWindowBatchOrdering performBatchOrderingForTripletsInRange:] + 410

3 com.apple.AppKit 0x96c64f45 -[NSWindowBatchOrdering performRelativeToWindow:] + 349

4 com.apple.AppKit 0x96c88fae __67-[NSApplication _copyBatchWindowOrderingPerformerForToken:release:]_block_invoke_01413 + 43

5 com.apple.AppKit 0x96c64cd3 -[NSApplication _performBatchWindowOrdering:release:] + 66

6 com.apple.AppKit 0x96c644b4 -[NSApplication _deallocHardCore:] + 577

7 com.apple.AppKit 0x96c60ee4 -[NSApplication terminate:] + 2623

8 com.apple.AppKit 0x96c8b477 -[NSApplication _terminateFromSender:askIfShouldTerminate:saveWindows:] + 457

9 com.apple.AppKit 0x96c96954 __52-[NSApplication(NSAppleEventHandling) _handleAEQuit]_block_invoke_0 + 104

10 libdispatch.dylib 0x954fff8f _dispatch_call_block_and_release + 15

11 libdispatch.dylib 0x954fbc82 _dispatch_client_callout + 46

12 libdispatch.dylib 0x955012e3 _dispatch_main_queue_callback_4CF + 223

13 com.apple.CoreFoundation 0x95d3d1d5 __CFRunLoopRun + 1845

14 com.apple.CoreFoundation 0x95d3c63a CFRunLoopRunSpecific + 378

15 com.apple.CoreFoundation 0x95d3c4ab CFRunLoopRunInMode + 123

16 com.apple.HIToolbox 0x9640f15a RunCurrentEventLoopInMode + 242

17 com.apple.HIToolbox 0x9640eec9 ReceiveNextEventCommon + 374

18 com.apple.HIToolbox 0x9640ed44 BlockUntilNextEventMatchingListInMode + 88

19 com.apple.AppKit 0x96a37a3a _DPSNextEvent + 724

20 com.apple.AppKit 0x96a3726c -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119

21 com.apple.AppKit 0x96a2d6cc -[NSApplication run] + 855

22 com.apple.dashboard.client 0x00067b92 0x63000 + 19346

23 libdyld.dylib

Reply

Answer 9

MichelPM

Level 10

80,958 points

Mar 1, 2013 9:22 AM in response to joeholl

It looks to me you still have stuff in your system from Crash Plan.

How did you completely uninstall this?

Does Crash Plan have a dedicated uninstaller?

Sometimes with apps that have an uninstaller, you simply can't drag the app to,the trash and empty it.

Parts of the app my linger. You need to use the app's uninstaller if it has one.

Crash Plan maybe still causing your issues.

You need to just uninstall this completely and get it off your Mac.

Reply

Answer 10

Linc Davis

Level 10

209,547 points

Mar 1, 2013 9:32 AM in response to joeholl

Your attempt to uninstall CrashPlan wasn't successful.

Any third-party software that doesn't install by drag-and-drop into the Applications folder, and uninstall by drag-and-drop to the Trash, is a system modification.

Whenever you remove system modifications, they must be removed completely, and the only way to do that is to use the uninstallation tool, if any, provided by the developers, or to follow their instructions. If the software has been incompletely removed, you may have to re-download or even reinstall it in order to finish the job.

Here are some general guidelines. Suppose you want to remove something called “BrickYourMac.” First, consult the product's Help menu, if there is one, for instructions. Finding none there, look on the developer's website, say www.brickyourmac.com. (That may not be the actual name of the site; if necessary, search the Web for the product name.) If you don’t find anything on the website or in your search, contact the developer. While you're waiting for a response, download BrickYourMac.dmg and open it. There may be an application in there such as “Uninstall BrickYourMac.” If not, open “BrickYourMac.pkg” and look for an Uninstall button.

You may have to log out or reboot in order to complete an uninstallation.

If you can’t remove software in any other way, you’ll have to erase your boot volume and perform a clean reinstallation of OS X. Never install any third-party software unless you're sure you know how to uninstall it; otherwise you may create problems that are very hard to solve.

Trying to remove complex system modifications by hunting for files by name often will not work and may make the problem worse. The same goes for "utilities" that purport to remove software.

Reply

Answer 11

joeholl Author

Level 1

5 points

Mar 1, 2013 10:12 AM in response to joeholl

I had reinstalled crashplan because I still experienced the issue after uninstalling.

Reply

Answer 12

MichelPM

Level 10

80,958 points

Mar 1, 2013 10:42 AM in response to joeholl

(Throwing my hands in the air) If your iMac was running better when you uninstalled this software, why on Earth would you reinstall it????

Obviously, this software was causing part of your issue.

If you need backups, buy an external hard drive and use Apple's Time Machine.

Something else, in addition to CrashPlan, is causing your system to freeze.

Reply

Answer 13

joeholl Author

Level 1

5 points

Mar 1, 2013 10:52 AM in response to MichelPM

"Something else, in addition to CrashPlan, is causing your system to freeze."

CrashPlan worked fine for about a month after my iMac purchase. Then, all the sudden, it supposedly was causing the computer to freeze. Then, I uninstall it, and my system still freezes, just not as often.

I'm trying to figure out what that something else is. If the software is the problem, how did it work fine for a month?

Reply

Answer 14

Linc Davis

Level 10

209,547 points

Mar 1, 2013 10:56 AM in response to joeholl

Please read this whole message before doing anything.

This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.

Step 1

The purpose of this step is to determine whether the problem is localized to your user account.

Enable guest logins* and log in as Guest. For instructions, launch the System Preferences application, select Help from the menu bar, and enter “Set up guest users” (without the quotes) in the search box. Don't use the Safari-only “Guest User” login created by “Find My Mac.”

While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.

Test while logged in as Guest. Same problem?

After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

Step 2

The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:

Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
When you see the gray Apple logo, release the shift key.
If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.

Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The next normal boot may also be somewhat slow.

The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

*Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode.

Test while in safe mode. Same problem?

After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of steps 1 and 2.

Reply

Answer 15

joeholl Author

Level 1

5 points

Mar 1, 2013 5:42 PM in response to Linc Davis

I believe I found the problem. when I would run an anti-virus scan or a backup, when the application would start scanning the files in my Bootcamp partition it would freeze the system. I don't know why this is happening, but for now all I have to do is set the applications to not scan that partition.

It only has Windows and some games on it anyway, so it's not critical to have them backed up.

Reply