|
|
restart + kernel panic
|
|
|
|
Fresh-Faced Recruit
Join Date: May 2005
Status:
Offline
|
|
After using my iMac for a couple of days [OS 10.11.4] if I restart, I get a kernel panic: mysterious white letters in the upper left and a refusal to restart. Things can be set to right by using the recovery option. All's well again for a few days, and then, again, a restart produces the same refusal to mount the disk. Any help will be much appreciated. ALanSteven
|
|
|
|
|
|
|
|
|
Administrator
Join Date: Jun 2000
Location: California
Status:
Offline
|
|
Kernel panics today are almost always caused by hardware issues. Are you within warranty?
Reboot while holding down the 'D' key. This will give you the hardware tests, run them.
|
|
|
|
|
|
|
|
|
Moderator
Join Date: Apr 2000
Location: Gothenburg, Sweden
Status:
Offline
|
|
This. Also my favorite hint, especially if the iMac is getting old: Clean the air vents, they tend to get clogged up over time.
|
The new Mac Pro has up to 30 MB of cache inside the processor itself. That's more than the HD in my first Mac. Somehow I'm still running out of space.
|
|
|
|
|
|
|
|
Fresh-Faced Recruit
Join Date: May 2005
Status:
Offline
|
|
Originally Posted by reader50
Kernel panics today are almost always caused by hardware issues. Are you within warranty?
Reboot while holding down the 'D' key. This will give you the hardware tests, run them.
Thanks for the suggestion. I have run the hardware tests: no problems. The next-to-last time I had one of those kernel panics, I used the recovery partition to reinstall ElCapitan. I then restarted fifteen times. Each time I worked with only one of the apps I regularly use (plus the printer), and each time I was able to restart without difficulty. I then simply avoided restarting until today, which is to say that I've been using the computer for a week or so, and there it was: another kernel panic. I'm completely lost. I have no idea why this is happening. If this helps, the only programs I've used are: Thunderbird, Google Chrome, Easy Find, Fantastical, Calendar, Disk Warrior, SuperDuper and Painter. Thanks for any help. As for cleaning the air vents, my iMac is just a couple of months old.
|
|
|
|
|
|
|
|
|
Administrator
Join Date: Jun 2000
Location: California
Status:
Offline
|
|
What model/year of iMac are you using? It could also help if you posted the panic text for us. The logs are stored in:
/Library/Logs/DiagnosticReports/Kernel_(datestamps)_(computername).panic
|
|
|
|
|
|
|
|
|
Fresh-Faced Recruit
Join Date: May 2005
Status:
Offline
|
|
I've tried to post the panic text, but I get the message that it's much too long, and it does go on and on. I'm using a late 2015 27" iMac. Will some particular part of the panic text do the job? Thanks, Alan Steven
|
|
|
|
|
|
|
|
|
Administrator
Join Date: Jun 2000
Location: California
Status:
Offline
|
|
Try the first 100 lines or so.
|
|
|
|
|
|
|
|
|
Fresh-Faced Recruit
Join Date: May 2005
Status:
Offline
|
|
Okay, here goes:
Process: mds_stores [197]
Path: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Support/mds_stores
Identifier: mds_stores
Version: 972.29.1
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: mds_stores [197]
User ID: 0
Date/Time: 2016-04-30 16:14:07.064 -0400
OS Version: Mac OS X 10.11.4 (15E65)
Report Version: 11
Anonymous UUID: 50D4A244-0E94-A909-A3CC-7D3ADA0C000D
Time Awake Since Boot: 27 seconds
System Integrity Protection: enabled
Crashed Thread: 4 Dispatch queue: com.apple.metadata.spotlightindex.Set Attributes scheduler for index at /.Spotlight-V100/Store-V2/89D842E0-ACB2-4B66-8949-ADDAB
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000004
Exception Note: EXC_CORPSE_NOTIFY
VM Regions Near 0x4:
-->
__TEXT 000000010ecb2000-000000010ecf7000 [ 276K] r-x/rwx SM=COW /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Support/mds_stores
Application Specific Information:
Initializing
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8521cf72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8521c3b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff966de1c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff966dd68c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff966dced8 CFRunLoopRunSpecific + 296
5 mds_stores 0x000000010ecb5f05 0x10ecb2000 + 16133
6 libdyld.dylib 0x00007fff8a7565ad start + 1
Thread 1:
0 libsystem_kernel.dylib 0x00007fff852235e2 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8a106578 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff8a104341 start_wqthread + 13
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff85223efa kevent_qos + 10
1 libdispatch.dylib 0x00007fff83e64165 _dispatch_mgr_invoke + 216
2 libdispatch.dylib 0x00007fff83e63dcd _dispatch_mgr_thread + 52
Thread 3:
0 libsystem_kernel.dylib 0x00007fff852235e2 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8a106578 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff8a104341 start_wqthread + 13
Thread 4 Crashed:: Dispatch queue: com.apple.metadata.spotlightindex.Set Attributes scheduler for index at /.Spotlight-V100/Store-V2/89D842E0-ACB2-4B66-8949-ADDAB
0 com.apple.spotlight.index 0x00007fff941d084e ContentIndexWritable + 4
1 com.apple.spotlight.index 0x00007fff940ce794 si_initialIndexingEndedQueueOnFlush + 543
2 com.apple.spotlight.index 0x00007fff940edd6c runLoop + 109
3 com.apple.spotlight.index 0x00007fff94100f91 work_fun + 691
4 libdispatch.dylib 0x00007fff83e76324 _dispatch_block_async_invoke_and_release + 610
5 libdispatch.dylib 0x00007fff83e5e40b _dispatch_client_callout + 8
6 libdispatch.dylib 0x00007fff83e6303b _dispatch_queue_drain + 754
7 libdispatch.dylib 0x00007fff83e69707 _dispatch_queue_invoke + 549
8 libdispatch.dylib 0x00007fff83e63200 _dispatch_queue_drain + 1207
9 libdispatch.dylib 0x00007fff83e69707 _dispatch_queue_invoke + 549
10 libdispatch.dylib 0x00007fff83e63200 _dispatch_queue_drain + 1207
11 libdispatch.dylib 0x00007fff83e69707 _dispatch_queue_invoke + 549
12 libdispatch.dylib 0x00007fff83e61d53 _dispatch_root_queue_drain + 538
13 libdispatch.dylib 0x00007fff83e61b00 _dispatch_worker_thread3 + 91
14 libsystem_pthread.dylib 0x00007fff8a1064de _pthread_wqthread + 1129
15 libsystem_pthread.dylib 0x00007fff8a104341 start_wqthread + 13
|
|
|
|
|
|
|
|
|
Administrator
Join Date: Jun 2000
Location: California
Status:
Offline
|
|
The search indexing thread crashed - that's Apple code and shouldn't have any bugs. My guess is either a RAM issue or a problem with the HD / SSD, whichever you have. Have you added RAM? If yes, try putting the original RAM back and running for a while. See if the problem goes away.
If you haven't added RAM, your system is stock and any issue would fall under warranty. Assuming you have two RAM sticks, you can try removing one for a few days. Then switching to the other stick for a few days.
Are you using any external drives, or remote drives? The indexer will always work on the boot drive first, and the crashes happen right after boot, so an external drive is a long shot. But might as well ask.
|
|
|
|
|
|
|
|
|
Managing Editor
Join Date: Jul 2012
Status:
Offline
|
|
What version of DiskWarrior?
|
|
|
|
|
|
|
|
|
Fresh-Faced Recruit
Join Date: May 2005
Status:
Offline
|
|
Originally Posted by Mike Wuerthele
What version of DiskWarrior?
I'm using DiskWarrior 5.0. I gather that's the latest version.
|
|
|
|
|
|
|
|
|
Fresh-Faced Recruit
Join Date: May 2005
Status:
Offline
|
|
Originally Posted by reader50
The search indexing thread crashed - that's Apple code and shouldn't have any bugs. My guess is either a RAM issue or a problem with the HD / SSD, whichever you have. Have you added RAM? If yes, try putting the original RAM back and running for a while. See if the problem goes away.
If you haven't added RAM, your system is stock and any issue would fall under warranty. Assuming you have two RAM sticks, you can try removing one for a few days. Then switching to the other stick for a few days.
Are you using any external drives, or remote drives? The indexer will always work on the boot drive first, and the crashes happen right after boot, so an external drive is a long shot. But might as well ask.
I ran the hardware tests as you originally suggested, so I assume that takes care of the RAM and the SSD. I'll have to discover how to remove a RAM stick. Neither of my external drives is connected unless I'm doing a backup.
|
|
|
|
|
|
|
|
|
Administrator
Join Date: Jun 2000
Location: California
Status:
Offline
|
|
Diagnostics have trouble catching intermittent faults. RAM tests often have extended versions, which you leave running overnight to try and catch intermittent failures.
An iMac this new shouldn't be crashing like this, especially when it's in stock config. The RAM can be diagnosed further because it's something you can reach. If it's an intermittent fault with the SSD, you can't reach that. It's already passed basic diagnostics, and gotten an OS reinstall without fixing the issue.
At this point I'd take it to a genius bar and invoke the magic word: warranty.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Forum Rules
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|