Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mac Mini keeps randomly restarting multiple times a day. Problem Report Inside.
- Thread starter brasskey
- Start date
- Sort by reaction score
Maybe bad SSD, bad instillation...loose connector.
Did you do the instillation?
Crucial stands behind their SSDs. Give them a call.
I have the Crucial MX 100 512GB and it works fine and it has a 3 year warranty.
See if Crucial will ship you a new SSD. Glad to see it's not the logic board going kaput.
I may be a little behind .... but was your issue solved with a new SSD? I am experiencing the exact same "restart" behaviour from a same Mini Late-2012 2.3 i7 Quad configuration that I upgraded myself with 16G Crucial Ram (2X8G) and a Samsung EVO 850 500G SSD.
It actually ended up being the Crucial RAM. I had suspected that initially, so Crucial sent me a replacement. After seeing the issues again, I took it to a local shop and they said it was the logic board. I wasn't so sure, so I ended up taking it to Apple and they showed me how it worked fine with just one of the 8GB sticks in. So, I got another replacement for the other 8GB and it works fine now.
Alrighty! Thanks for taking time to reply. It is funny 'cause I also suspect the ram from the very beginning. Remember how they shown you that was working fine with just one ram stick? Where they using a special diagnose software tool other than "Apple Hardware Test" to point out the bad stick?
Yes, that's exactly what happened. They actually gave it to me still with only one stick in.
The panic is related to ram not the hdd generally. Could be bad memory or slot. I know your limited to the ram you have and you've had that swapped. I would try 1 stick in the upper slot see if the issue continues if it does move the stick to the lower slot. If one slot works and the other dosnt then you've found the issue. It can't be resolved and requires a new logic board.
I actually fixed my problem. It was bad RAM as I stated a few posts ago. I was just responding to StevenLast.
I have the same machine, Crucial RAM and similar issues. Though kernel panics aren't as frequent as they were for you. Out of curiosity, how long did it take to identify which stick of RAM was faulty? Did Crucial make you run particular diagnostics before sending a replacement?
I've never had problems with Crucial RAM over 15 years or so - 5 (soon to be 6) Macs, 4 or 5 PC's and I may have even bought some RAM for an entry-level Solaris box I had at one point in time. But the last time I bought RAM from them was in 2012 so maybe their quality is down. I have some on order now so we'll see.
SJCoupe, if you just want an answer from the OP, fine. If you want help trying to figure out if your problem (kernel panics) has the same cause or not, let us know.
SJCoupe, if you just want an answer from the OP, fine. If you want help trying to figure out if your problem (kernel panics) has the same cause or not, let us know.
I've also used Crucial RAM in many systems and my experiences have been good.
Treekram, thanks for the response. I'd be happy for a response from the OP or others that have diagnosed bad Crucial RAM on a Mac. I used to work in IT and had extra RAM kicking around for diagnostic purposes (usually with PCs). I don't have that luxury now, so am looking for tips on a) identifying bad RAM, and b) the shortest path to getting a replacement from Crucial, not having done this personally before.
I contacted Crucial some months ago and they told me to run AHD. I did that and there were no errors. In the last week I've run Memtest86 (via USB stick), which took ~8 hours and also showed no errors. So, maybe I'm barking up the wrong tree. My next step is to pull one 8 GB stick out and run with it for a while. (I had put the original Apple 4 GB back in for a few days, but performance was a problem for my usual workload, and it all but precludes running a VM.)
Should I start a new thread? Don't mean to hijack this one. Thanks.
Running the computer on one stick of 8GB and then the other is a good next step. If you ran memtest and it didn't show errors, you probably don't have bad RAM. How many iterations of memtest did you run? They suggest at least 3.
In the meantime, a couple of things would be helpful:
1) A chronology of when you started having the problems relative to when you put in the 8GB RAM sticks and also relative to any OS changes, new hardware and new software. Also, what OS version (10.XX.X) are you running?
2) How often do your kernel panics typically happen? If you can upload one of the files, that would be helpful. They are in /Library/Logs/DiagnosticReports and look like "Kernel_[date-time]_[host name].panic.
I think this thread had already run its course so I don't think it's a problem doing it here or starting a new one.
In the meantime, a couple of things would be helpful:
1) A chronology of when you started having the problems relative to when you put in the 8GB RAM sticks and also relative to any OS changes, new hardware and new software. Also, what OS version (10.XX.X) are you running?
2) How often do your kernel panics typically happen? If you can upload one of the files, that would be helpful. They are in /Library/Logs/DiagnosticReports and look like "Kernel_[date-time]_[host name].panic.
I think this thread had already run its course so I don't think it's a problem doing it here or starting a new one.
I've attached the only panic I have record of, due to having recently reinstalled 10.11.2. Apparently TimeMachine doesn't back up /Library/Logs/DiagnosticReports. It happened yesterday and I subsequently removed one DIMM.
It tends to panic while waking from sleep. Also, the machine has failed to wake from sleep twice since removing the other DIMM (yesterday), which is an old bad habit from months ago. I'm going to swap DIMMs, though will be away for a few days for the holidays, so I won't have anything to report immediately.
This machine was solid until I installed 10.10 in August, having upgraded from 10.9 and 10.8 before that. I uninstalled 3rd party kernel extensions, except for VirtualBox, at that time. The problems seemed to disappear until I installed 10.11 last month. Last week I uninstalled VirtualBox and now have no 3rd party kexts. I had been living with occasional crashes until last week, when the filesystem got corrupted badly enough to prevent booting. I tried a lot of troubleshooting via target disk mode and single user mode, but even fsck refused to fix the problem. (The OS couldn't be reinstalled via recovery mode.) Finally, I used Disk Warrior and that got me back up and running. Some things were broken (Apple apps, including Finder), but I was able to reinstall 10.11 and everything appeared to be flawless (whew!). So now I feel like I need to get to the bottom of this, because a lot of time was spent fooling around with an unusable computer.
I ran a single iteration of MemTest86, though will step that up to 3 if I need to repeat.
Thanks!
It tends to panic while waking from sleep. Also, the machine has failed to wake from sleep twice since removing the other DIMM (yesterday), which is an old bad habit from months ago. I'm going to swap DIMMs, though will be away for a few days for the holidays, so I won't have anything to report immediately.
This machine was solid until I installed 10.10 in August, having upgraded from 10.9 and 10.8 before that. I uninstalled 3rd party kernel extensions, except for VirtualBox, at that time. The problems seemed to disappear until I installed 10.11 last month. Last week I uninstalled VirtualBox and now have no 3rd party kexts. I had been living with occasional crashes until last week, when the filesystem got corrupted badly enough to prevent booting. I tried a lot of troubleshooting via target disk mode and single user mode, but even fsck refused to fix the problem. (The OS couldn't be reinstalled via recovery mode.) Finally, I used Disk Warrior and that got me back up and running. Some things were broken (Apple apps, including Finder), but I was able to reinstall 10.11 and everything appeared to be flawless (whew!). So now I feel like I need to get to the bottom of this, because a lot of time was spent fooling around with an unusable computer.
I ran a single iteration of MemTest86, though will step that up to 3 if I need to repeat.
Thanks!
I'm not sure that TM deletes the old crash reports - I think I couldn't access the system files and didn't spend the time to research it. I do know that going to a new OS does that. I wanted to keep my Yosemite crash logs and didn't save it before upgrading to El Capitan. Luckily, I had kept the old Yosemite clone drive and it had the crash logs.
So you've had the memory and everything was working well until you installed Yosemite? If the memory tests are OK, especially with 3 iterations, and you have problems with having either memory stick in alone, I think it's highly unlikely that the memory is bad.
Obviously, failing to wake from sleep with only 8GB when it works with 16GB indicates that it likes 16GB (check the memory usage to see if its using virtual memory with 8GB).
The kernel panic report doesn't point to a specific identifiable issue that I can see. I do see that you have a Wacom tablet. Do you use that in VirtualBox? You might try disconnecting it and see what happens. Also (you've probably done this), stay current with VirtualBox (I know nothing about the product except that it exists). If none of that works, you can try not putting the computer to sleep (you've probably thought of that).
I was having kernel panics with my 2012 i7 2.6 GHz mini with Yosemite 10.10.3-10.10.5. There was a thread that indicated that it was Yosemite+HD4000 related. I haven't had kernel panics with El Capitan. I don't have any unusual hardware or kernel extensions and a lot of the panics happened when I was running just vanilla software - Firefox, Safari, TextEdit, Terminal. There weren't a lot of people complaining so perhaps it was limited to the i7 or just the 2.6 GHz. I'm just bringing that up because it's a possibility, probably small, that with Yosemite you were having one issue and with El Capitan another.
So you've had the memory and everything was working well until you installed Yosemite? If the memory tests are OK, especially with 3 iterations, and you have problems with having either memory stick in alone, I think it's highly unlikely that the memory is bad.
Obviously, failing to wake from sleep with only 8GB when it works with 16GB indicates that it likes 16GB (check the memory usage to see if its using virtual memory with 8GB).
The kernel panic report doesn't point to a specific identifiable issue that I can see. I do see that you have a Wacom tablet. Do you use that in VirtualBox? You might try disconnecting it and see what happens. Also (you've probably done this), stay current with VirtualBox (I know nothing about the product except that it exists). If none of that works, you can try not putting the computer to sleep (you've probably thought of that).
I was having kernel panics with my 2012 i7 2.6 GHz mini with Yosemite 10.10.3-10.10.5. There was a thread that indicated that it was Yosemite+HD4000 related. I haven't had kernel panics with El Capitan. I don't have any unusual hardware or kernel extensions and a lot of the panics happened when I was running just vanilla software - Firefox, Safari, TextEdit, Terminal. There weren't a lot of people complaining so perhaps it was limited to the i7 or just the 2.6 GHz. I'm just bringing that up because it's a possibility, probably small, that with Yosemite you were having one issue and with El Capitan another.
This is why i get my ram from OWC. Im not saying all crucial ram is bad but I have had issues with it in the past and never have had issues with OWC.
[doublepost=1456369807][/doublepost]hi, noticed your discussion and wondered if you can advise me, am having same problems below is copy of my report:
Interval Since Last Panic Report: -49 sec
Panics Since Last Report: 2
Anonymous UUID: 6EBFFEAA-7E8C-0830-BDAE-68D6D205D928
Thu Feb 25 03:09:22 2016
panic(cpu 1 caller 0xffffff80188b8c44): Kernel trap at 0xffffef801883e2c0, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffef801883e2c0, CR3: 0x000000001b3d0000, CR4: 0x0000000000000660
RAX: 0x0000000000000000, RBX: 0xffffff80275d7718, RCX: 0xffffef801883e2c0, RDX: 0x0000000000000000
RSP: 0xffffff80c93e3fb8, RBP: 0x0000000000000000, RSI: 0x0000000000000000, RDI: 0xffffff8018e85ee0
R8: 0xffffff80c2fad078, R9: 0x0000000000989146, R10: 0xffffff80c93e3df0, R11: 0x0000000000000206
R12: 0xffffff80c2fad000, R13: 0xffffff8018e85ee0, R14: 0xffffff80285b25b0, R15: 0xffffef801883e2c0
RFL: 0x0000000000010246, RIP: 0xffffef801883e2c0, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffef801883e2c0, Error code: 0x0000000000000010, Fault CPU: 0x1
Backtrace (CPU 1), Frame : Return Address
0xffffff80c93e3c50 : 0xffffff801881d6d6
0xffffff80c93e3cc0 : 0xffffff80188b8c44
0xffffff80c93e3e90 : 0xffffff80188cf04d
0xffffff80c93e3eb0 : 0xffffef801883e2c0
BSD process name corresponding to current thread: kernel_task
Mac OS version:
12F2560
Kernel version:
Darwin Kernel Version 12.6.0: Wed Mar 18 16:23:48 PDT 2015; root:xnu-2050.48.19~1/RELEASE_X86_64
Kernel UUID: 3E1B7058-5CFD-38F3-8B25-4CCD9B29F764
Kernel slide: 0x0000000018600000
Kernel text base: 0xffffff8018800000
System model name: Macmini3,1 (Mac-F22C86C8)
System uptime in nanoseconds: 1413452463821
last loaded kext at 28423112201: com.apple.driver.AppleHWSensor 1.9.5d0 (addr 0xffffff7f9a60a000, size 36864)
last unloaded kext at 194311250638: com.apple.driver.AppleFileSystemDriver 3.0.1 (addr 0xffffff7f9a85a000, size 8192)
loaded kexts:
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.iokit.IOBluetoothSerialManager 4.1.7f6
com.apple.driver.AudioAUUC 1.60
com.apple.filesystems.autofs 3.0
com.apple.driver.AGPM 100.13.14
com.apple.driver.ApplePlatformEnabler 2.0.7d2
com.apple.driver.AppleHDA 2.4.7fc4
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.ApplePolicyControl 3.4.5
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.1.7f6
com.apple.driver.AppleLPC 1.6.3
com.apple.GeForce 8.1.6
com.apple.driver.AppleUpstreamUserClient 3.5.12
com.apple.driver.AppleMCCSControl 1.1.11
com.apple.driver.AppleIRController 320.15
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 34
com.apple.iokit.SCSITaskUserClient 3.5.6
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.3.5
com.apple.driver.AppleAHCIPort 2.6.6
com.apple.nvenet 2.0.19
com.apple.driver.AppleUSBHub 635.4.0
com.apple.driver.AirPortBrcm43224 600.36.17
com.apple.driver.AppleFWOHCI 4.9.9
com.apple.driver.AppleUSBOHCI 621.4.0
com.apple.driver.AppleUSBEHCI 621.4.6
com.apple.driver.AppleRTC 1.5
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleACPIButtons 1.8
com.apple.driver.AppleSMBIOS 1.9
com.apple.driver.AppleACPIEC 1.8
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 214.0.0
com.apple.nke.applicationfirewall 4.0.39
com.apple.security.quarantine 2.1
com.apple.driver.AppleIntelCPUPowerManagement 214.0.0
com.apple.iokit.IOSerialFamily 10.0.6
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 2.4.7fc4
com.apple.iokit.IOAudioFamily 1.9.2fc7
com.apple.kext.OSvKernDSPLib 1.12
com.apple.iokit.IOSurface 86.0.5
com.apple.iokit.IOBluetoothFamily 4.1.7f6
com.apple.driver.AppleGraphicsControl 3.4.5
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.AppleSMC 3.1.5d4
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.1.7f6
com.apple.iokit.IOFireWireIP 2.2.5
com.apple.driver.AppleHDAController 2.4.7fc4
com.apple.iokit.IOHDAFamily 2.4.7fc4
com.apple.driver.IOPlatformPluginFamily 5.4.1d13
com.apple.nvidia.nv50hal 8.1.6
com.apple.driver.AppleSMBusController 1.0.11d1
com.apple.NVDAResman 8.1.6
com.apple.iokit.IONDRVSupport 2.3.7
com.apple.iokit.IOGraphicsFamily 2.3.7
com.apple.iokit.IOUSBHIDDriver 623.4.0
com.apple.driver.AppleUSBComposite 621.4.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.5.6
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOAHCISerialATAPI 2.5.5
com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.6
com.apple.iokit.IOAHCIFamily 2.5.1
com.apple.iokit.IO80211Family 530.5
com.apple.iokit.IONetworkingFamily 3.0
com.apple.iokit.IOUSBUserClient 630.4.4
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.driver.NVSMU 2.2.9
com.apple.iokit.IOUSBFamily 635.4.0
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 1.8.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 220.4
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.DiskImages 346
com.apple.iokit.IOStorageFamily 1.8
com.apple.driver.AppleKeyStore 28.21
com.apple.driver.AppleACPIPlatform 1.8
com.apple.iokit.IOPCIFamily 2.8
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
Model: Macmini3,1, BootROM MM31.0081.B06, 2 processors, Intel Core 2 Duo, 2 GHz, 6 GB, SMC 1.35f0
Graphics: NVIDIA GeForce 9400, NVIDIA GeForce 9400, PCI, 256 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x0198, 0x393930353432382D3034332E413031472020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80AD, 0x484D54333235533643465238432D48392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x90), Broadcom BCM43xx 1.0 (5.10.131.36.16)
Bluetooth: Version 6.1.7f5 15859, 3 service, 13 devices, 3 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: WDC WD5000BPKX-80HPJT0, 500.11 GB
Serial ATA Device: OPTIARC DVD RW AD-5670S
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x04500000 / 2
USB Device: 2.4G Receiver, 0x1d57, 0xfa60, 0x06200000 / 3
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000 / 2
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8216, 0x06110000 / 4
if anyone can help would be greatly appreciated
It looks like you have a early-2009 Mini with Mountain Lion, 6GB RAM, 500GB HDD with no kernel extensions (at least none when the kernel panic occurred).
I would suggest running the Apple Hardware Test which would be on one of the install disks. If you don't have the disk, it can be downloaded but it would involve creating a bootable USB flash drive and running it from there. If you can run the AHT, you should run the extended tests, which may take a few hours.
https://support.apple.com/en-us/HT201257
It's unlikely the AHT will start by pressing the "D" key on startup, but you can try. Otherwise, following the instructions under "Using Apple Hardware Test on computers with OS X v10.7 and earlier".
Some questions which would help in diagnosing the problem:
1) Have you made any recent hardware/software changes?
2) How often do you have the kernel panics? Do the other reports have something different for the following lines:
"BSD process name corresponding to current thread: kernel_task"
"last loaded kext at 28423112201: com.apple.driver.AppleHWSensor ..." - (the time will be different)
3) Is there any pattern to the kernel panics in term of what software you're using or is there something the computer does just before the kernel panic happens?
4) What hardware do you have connected to the computer - keyboard, mouse, external drives, etc.? If you have an unusual monitor, it would be good to mention that.
I would suggest running the Apple Hardware Test which would be on one of the install disks. If you don't have the disk, it can be downloaded but it would involve creating a bootable USB flash drive and running it from there. If you can run the AHT, you should run the extended tests, which may take a few hours.
https://support.apple.com/en-us/HT201257
It's unlikely the AHT will start by pressing the "D" key on startup, but you can try. Otherwise, following the instructions under "Using Apple Hardware Test on computers with OS X v10.7 and earlier".
Some questions which would help in diagnosing the problem:
1) Have you made any recent hardware/software changes?
2) How often do you have the kernel panics? Do the other reports have something different for the following lines:
"BSD process name corresponding to current thread: kernel_task"
"last loaded kext at 28423112201: com.apple.driver.AppleHWSensor ..." - (the time will be different)
3) Is there any pattern to the kernel panics in term of what software you're using or is there something the computer does just before the kernel panic happens?
4) What hardware do you have connected to the computer - keyboard, mouse, external drives, etc.? If you have an unusual monitor, it would be good to mention that.