This looks like a hardware issue. I'd suggest resetting SMC and PRAM, but looking at your old thread it seems like you've tried that. The next step I'd try would be a test of your RAM. You'll need...
This looks like a hardware issue. I'd suggest resetting SMC and PRAM, but looking at your old thread it seems like you've tried that. The next step I'd try would be a test of your RAM. You'll need a USB key that you can wipe. Download memtest86 and restore it to your USB drive using Disk Utility. Reboot the system while holding the option key and select the USB drive from the list. Depending on how much RAM you have, this might take a few hours.
If your RAM is fine, the problem is likely in the motherboard, though power supply issues are possible.
It seems like post-2018 macs need Secure Boot disabled, and "Allow booting from external media" enabled. From what I can tell though, the drive should still show up in the startup menu, but when...
It seems like post-2018 macs need Secure Boot disabled, and "Allow booting from external media" enabled. From what I can tell though, the drive should still show up in the startup menu, but when you select it, it would say something to the effect of "you're not allowed to start up using this disk"
If the drive isn't showing up in the option-key menu, it might have been written to the drive incorrectly. Do you have another computer you can try booting off this USB key? Otherwise, if you have a windows PC available it might be a good idea to try the ImageUSB program included with memtest, or a program like rufus to write the image to the USB key.
ninjaedit: The user manual for memtest86 says to use the dd command to write the image to disk on MacOS. I'd avoid doing this unless you're comfortable in the terminal. You can find the instructions on page 6 of the PDF included in the download.
Sorry if this sounds condescending, but I have to ask. You're not flashing the ZIP file right, but you've unzipped it and are flashing the memtest86-usb.img file within it? I've never had an issue...
Sorry if this sounds condescending, but I have to ask. You're not flashing the ZIP file right, but you've unzipped it and are flashing the memtest86-usb.img file within it?
I've never had an issue with etcher, but maybe you might want to try the dd instructions just in case.
This screams "hardware issue" to me, and it's almost certainly either ram or motherboard. Since there's no way to test the motherboard directly, cross your fingers it's RAM, because that's cheap and easy to replace.
Damn. That rules that out I guess. Do you have any other devices plugged into the mac? USB devices, time machine backups, printers, webcams, anything like that? This is definitely a problem of...
Damn. That rules that out I guess.
Do you have any other devices plugged into the mac? USB devices, time machine backups, printers, webcams, anything like that? This is definitely a problem of hardware, but let's see if we can rule out any hardware not inside the mac.
It's kinda unlikely, but try unplugging everything that's not necessary and see if it still happens. The more things we can rule out, the better. Do you have a steelseries mouse, keyboard or...
They both connect via USB. I have a printer/scanner/fax
It's kinda unlikely, but try unplugging everything that's not necessary and see if it still happens. The more things we can rule out, the better.
Could this apply to my situation?
Do you have a steelseries mouse, keyboard or headset? Do you have an app called SteelSeries Engine installed? Any driver software is suspect here. Something is locking up the kernel, and typically userland software can't do that, only hardware and hardware drivers should be able to take down the whole system like this.
Hmm. If you can think of any other hardware you've plugged into your mac at any point, the driver for it might still be installed. I suppose we can make a list of all the third-party drivers...
Hmm. If you can think of any other hardware you've plugged into your mac at any point, the driver for it might still be installed. I suppose we can make a list of all the third-party drivers installed on your system, see if any of those might be the culprit.
If you open up a terminal and type kextstat | grep -v com.apple you'll get a list of all your kernel extensions (ie: drivers) that aren't from apple.
Looks like LuLu is a firewall. I guess you could try uninstalling it, but I'm sorta grasping at straws here. The only thing left I can suggest is reinstalling MacOS, which would eliminate software...
Looks like LuLu is a firewall. I guess you could try uninstalling it, but I'm sorta grasping at straws here.
The only thing left I can suggest is reinstalling MacOS, which would eliminate software as a potential cause. Otherwise, your last option would be to take it in to an apple store. :(
It appears some of it's still there and running in the background. Here's a page that shows how to remove it. No problem! You too. I've got my fingers crossed for you!
I uninstalled that many months ago.
It appears some of it's still there and running in the background. Here's a page that shows how to remove it.
Thanks for all your help!!!!!!!!!! Have a great weekend!!!!!
No problem! You too. I've got my fingers crossed for you!
This looks like a hardware issue. I'd suggest resetting SMC and PRAM, but looking at your old thread it seems like you've tried that. The next step I'd try would be a test of your RAM. You'll need a USB key that you can wipe. Download memtest86 and restore it to your USB drive using Disk Utility. Reboot the system while holding the option key and select the USB drive from the list. Depending on how much RAM you have, this might take a few hours.
If your RAM is fine, the problem is likely in the motherboard, though power supply issues are possible.
It seems like post-2018 macs need Secure Boot disabled, and "Allow booting from external media" enabled. From what I can tell though, the drive should still show up in the startup menu, but when you select it, it would say something to the effect of "you're not allowed to start up using this disk"
If the drive isn't showing up in the option-key menu, it might have been written to the drive incorrectly. Do you have another computer you can try booting off this USB key? Otherwise, if you have a windows PC available it might be a good idea to try the ImageUSB program included with memtest, or a program like rufus to write the image to the USB key.
ninjaedit: The user manual for memtest86 says to use the
ddcommand to write the image to disk on MacOS. I'd avoid doing this unless you're comfortable in the terminal. You can find the instructions on page 6 of the PDF included in the download.Sorry if this sounds condescending, but I have to ask. You're not flashing the ZIP file right, but you've unzipped it and are flashing the
memtest86-usb.imgfile within it?I've never had an issue with etcher, but maybe you might want to try the
ddinstructions just in case.This screams "hardware issue" to me, and it's almost certainly either ram or motherboard. Since there's no way to test the motherboard directly, cross your fingers it's RAM, because that's cheap and easy to replace.
Damn. That rules that out I guess.
Do you have any other devices plugged into the mac? USB devices, time machine backups, printers, webcams, anything like that? This is definitely a problem of hardware, but let's see if we can rule out any hardware not inside the mac.
This stackexchange thread and this reddit thread seem to point to SteelSeries drivers, which is a brand of mice and keyboards.
It's kinda unlikely, but try unplugging everything that's not necessary and see if it still happens. The more things we can rule out, the better.
Do you have a steelseries mouse, keyboard or headset? Do you have an app called SteelSeries Engine installed? Any driver software is suspect here. Something is locking up the kernel, and typically userland software can't do that, only hardware and hardware drivers should be able to take down the whole system like this.
Hmm. If you can think of any other hardware you've plugged into your mac at any point, the driver for it might still be installed. I suppose we can make a list of all the third-party drivers installed on your system, see if any of those might be the culprit.
If you open up a terminal and type
kextstat | grep -v com.appleyou'll get a list of all your kernel extensions (ie: drivers) that aren't from apple.Looks like LuLu is a firewall. I guess you could try uninstalling it, but I'm sorta grasping at straws here.
The only thing left I can suggest is reinstalling MacOS, which would eliminate software as a potential cause. Otherwise, your last option would be to take it in to an apple store. :(
It appears some of it's still there and running in the background. Here's a page that shows how to remove it.
No problem! You too. I've got my fingers crossed for you!
I'm really glad to hear that! I was at least 80% convinced it must be hardware, but super relieved to hear it wasn't. You too!