New answers tagged

0

From the details you provided. It sounds as if the kernel panic is due to to an issue in the firmware of your device. There are two things you can do: (before doing any of the solutions, always have a backup of your files, especially the important ones) Use the App Store to see if there is an update for your firmware. Just and fyi, you should update your ...


0

It looks like you have a 2010 MacBook Pro, (MacBookPro6,2). These were known to have a bad NVIDIA graphics chip. Apple was replacing the motherboards for free but I believe the free repairs have ended. If you didn't have your MBP repaired as part of that program then it looks like your graphics chip is causing the problem. If you still have AppleCare ...


1

I have exactly the same problem, with exactly the same error message, on the same model of Macbook. Initially I thought that the AMD discrete graphics was damaged; this is a frequent issue with those machines. However, I found out that if I force the Mac to use only the AMD discrete graphics, then the problem does not occur anymore. It might be, therefore, ...


1

The reason for the crash is listed at the top of those reports: zalloc: zone map exhausted while allocating from zone buf.8192, likely due to memory leak in zone kalloc.256 (620851200 total bytes, 2420408 elements allocated)"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3248.40.184/osfmk/kern/zalloc.c:2628 And this one: zalloc: zone map exhausted ...


0

As with most of you, I just had the same issue. I combined a couple of different suggestions (e.g., Capt G) from this thread to find a solution for me: Open Internet Accounts Select the "Exchange" account if you have one set-up. Uncheck the Notes app in the window to the left showing the apps associated with the Exchange account. Keep this window open. ...


-1

Shutdown cause -128 is an unknown shutdown cause. That means the system doesn't know what's the reason why the computer shutdown.


0

On first glance, it appears that your memory is going (or has gone) bad. The way to fully diagnose it, is to remove all but one "stick" of memory from your MBP. Rerun the memory diagnostic software and/or AHT and see if the error persists. Make a note of the address where it fails. Then, remove that stick, and replace with another and repeat the test. ...


0

I was able to resolve this issue by opening the file in Numbers for iOS (synced via iCloud) and making some modifications. The updated version then opened correctly on my Mac.


1

Your best bet is to report a bug in Apple Numbers using this form: http://www.apple.com/feedback/numbers.html Be sure to include the exact version of Numbers you're running as well as the complete crash log, or at least this part of the stack trace: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.iWork.Numbers ...


0

Create a new user account, and run Pages from there. If that works, then the problem is localized to your user account. If that is the case, quit Pages and try deleting the cache file at ~/Library/Caches/com.apple.iWork.Pages where ~ stands for your user account. Use the Finder’s “Go To Folder” command to get to ~/Library/Caches and then look for the ...



Top 50 recent answers are included