kernel panics on in...
 
Notifications
Clear all

kernel panics on intel imac

Page 1 / 2
(@fiveaces)
Active Member

I'm on a 2014 imac with big sur 11.6.4 

I have thunderbay 4 connected (controlled by softraid) along with a bunch of other RAIDs that are controlled by disk utility 

I've been getting very random kernel panics, I can't seem to find a pattern in the shutdowns. Softraid seems to keep showing up in the crash logs though. I'm also seeing softraid freaking out in the console, when I look at the system.log this message is appearing repeatedly every few seconds.

Mar 2 0705 alexs-iMac com.apple.xpc.launchd[1] (com.softraid.softraidd[60505]): Service exited with abnormal code: 2
Mar 2 0705 alexs-iMac com.apple.xpc.launchd[1] (com.softraid.softraidd): Service only ran for 3 seconds. Pushing respawn out by 7 seconds.

 

I'll attach the report from a kernel panic too if that helps 

 

This topic was modified 9 months ago 2 times by SoftRAID Support
Quote
Topic starter Posted : 02/03/2022 8:58 am
(@softraid-support)
Member Admin

As you notice saved panic logs are nonsense now. Best way to capture one is "report to Apple" and save that to text edit, convert to plain test and save. then you can attach the file and it will have reasonable formatting.

 

I searched for this panic and saw a couple things:
parallels with Boot camp

and issues with apps "scanning" the system for file sync. Are you running either?

https://discussions.apple.com/thread/252215159?answerId=254249075022#254249075022

You can also run etrecheck and see if it finds anything:

https://discussions.apple.com/docs/DOC-250000632

 

 

 

 

 

ReplyQuote
Posted : 02/03/2022 11:56 am
(@fiveaces)
Active Member

Luckily it just crashed again so here's a brand new crash report that should be easier to read. Also I am not running bootcamp. 

I'll post the ETrecheck report too. 

 

 

panic(cpu 0 caller 0xffffff80087c4356): Kernel trap at 0xffffff7f9a01d078, type 14=page fault, registers:

 

This post was modified 9 months ago by SoftRAID Support
ReplyQuote
Topic starter Posted : 03/03/2022 9:14 am
(@softraid-support)
Member Admin

@fiveaces 

I don't see enough to understand the causes. There have been multiple kernel panics, all for different reasons. I do not see SoftRAID in the backtrace on any of them.

It does not appear all the panics are at shutdown, correct?

ReplyQuote
Posted : 03/03/2022 10:04 am
(@fiveaces)
Active Member

@softraid-support Yes I'm pretty sure the kernel panics all happened at shut down. 

Did my etrecheck log not get included? I'll post that again. 

I'm also seeing this message appear repeatedly in the console every few seconds. 

Mar 3 0926 alexs-iMac com.apple.xpc.launchd[1] (com.softraid.softraidd[16601]): Service exited with abnormal code: 2
Mar 3 0926 alexs-iMac com.apple.xpc.launchd[1] (com.softraid.softraidd): Service only ran for 6 seconds. Pushing respawn out by 4 seconds.

 

EtreCheckPro version: 6.5.6 (6F041)

 

This post was modified 9 months ago by SoftRAID Support
ReplyQuote
Topic starter Posted : 03/03/2022 10:20 am
(@softraid-support)
Member Admin

@fiveaces 

I removed it from the post, as it is way too long. I prefer panic logs also as text (In Text Edit, Make plain text)

otherwise the forum is unreadable.

The SoftRAID daemon relaunching is annoying but not the cause.

I am not sure what is causing the panics. They seem to be different triggers, mostly.

Etrecheck used to point to conflicts and crappy apps/extensions, it no longer appears to do so, perhaps litigation reasons.

the last panic top lines are:

kernel trap: Predicted Bounds mismatch
(cannot find any similar crashes on Apple forums)

(twice) CPU Caller: Possible Memory corruption

Does your system have all factory RAM?

ReplyQuote
Posted : 03/03/2022 10:42 am
(@fiveaces)
Active Member

@softraid-support That's a shame etrecheck can't point those out anymore. 

I upgraded my RAM to 32GB years ago with a kit that I bought from OWC. It's not apple RAM but I'm pretty sure the OWC kit is highly recommended for macs. I also ran Rember on that RAM and it all seems to be okay. 

When these crashes first started happening I thought my internal SSD was failing. I replaced it but that hasn't fixed anything. Could those memory issues you are seeing be related to the SSD or is that strictly RAM?

ReplyQuote
Topic starter Posted : 03/03/2022 11:34 am
(@softraid-support)
Member Admin

@fiveaces 

Is "All" the RAM now OWC? that would be OK. Sometimes mixed brands do not work as well, in particular Apple and Micron memory, as even though Apple uses Micron, it has slightly different firmware, so has problems.

No, this is not likely an SSD problem, that would not be in the RAM descriptor in the kernel panic, as far as macOS knows, HDD and SSD's are mostly the same, an external storage device.

Did you attach a SoftRAID support file anywhere? I don't see one. I did note Etrecheck commented that the SSD was "slow", I don't know what that means. These were the key findings:

    SSD too slow - SSD is showing poor performance.
    Heavy RAM usage - Apps are using a large amount of RAM.
    Small backup drive - Time Machine backup drive is too small.
    Apps crashing - There have been numerous app crashes.
    Apps with heavy CPU usage - There have been numerous cases of apps with heavy CPU usage.
    Unsigned files - There are unsigned software files installed. Apple has said that unsigned software will not run by default in a future version of the operating system.
    System modifications - There are a large number of system modifications running in the background.
    Runaway user process - A user process is using a large percentage of your CPU.
    Vintage hardware - This computer may be considered vintage.
    Heavy I/O usage - Your system is under heavy I/O use. This will reduce your performance.
    Kernel extensions present - This computer has kernel extensions that may not work in the future.
    Sharing enabled - This computer has sharing services enabled that could be a security risk.
 

I think Disk Warrior was what was using too much CPU, which it does.

the unsigned third party extensions, are ones you should remove.

You may want to test with a clean install.

ReplyQuote
Posted : 03/03/2022 11:54 am
(@fiveaces)
Active Member

@softraid-support Yep all the RAM currently installed is the same brand from OWC. 

I'll attach the softraid support file. I'm currently running version 6.2. I was running the latest version, including version 6.2.1 b13. I thought I'd try running an older version but I'm getting the same issues no matter which version I run. 

The SSD might have been slow since I was exporting some video while running the etrecheck test. I also read that the SATA cable can go bad and cause that problem so I ordered a new cable. (one reason I thought the SSD was bad was because sometimes when the mac tried to startup it didn't recognize the drive. I got the file folder with a question mark in it on startup. This only happened intermittently though)

I'll work on removing the third part extensions. Then I am at that point where I will probably try a fresh install of macos. 

ReplyQuote
Topic starter Posted : 03/03/2022 12:37 pm
(@softraid-support)
Member Admin

@fiveaces 

Here are my recommendations:

Update or remove (out of date):
/Library/Extensions/CIJUSBLoad.kext
/Library/Extensions/SATSMARTDriver.kext

Remove:
/Library/Extensions/HoRNDIS.kext

 

To remove via terminal:
sudo rm -r /Library/Extensions/HoRNDIS.kext

Then refresh the extensions cache:
sudo kmutil clear-staging
sudo kextcache -i /

You have others, but these are the ones I would eliminate.

ReplyQuote
Posted : 03/03/2022 1:11 pm
(@fiveaces)
Active Member

@softraid-support Thanks for the tip. I removed all of those and it seemed to help, but not totally fix the problem. 

I just had another crash. These are the remaining Kexts that I have installed. 

com.owc.driver.SCSI-Device0E 1.1.0b16
com.softraid.driver.SoftRAID 6.2
com.owc.driver.SCSI-Device 1.1.0b16
com.owc.driver.SATA-Command 8.1.0b16
com.promise.driver.stex 6.2.13

ReplyQuote
Topic starter Posted : 14/03/2022 12:21 pm
(@softraid-support)
Member Admin

@fiveaces 

Can you attach a panic log? (save as plain text in text edit, so you can attach it)

 

ReplyQuote
Posted : 14/03/2022 12:43 pm
(@fiveaces)
Active Member

@softraid-support

 

ReplyQuote
Topic starter Posted : 14/03/2022 1:06 pm
(@softraid-support)
Member Admin

@fiveaces 

Its a pretty "generic" kernel panic. I don't see any cause, except kernel_task

Kernel trap at 0xffffffa0a714be00, type 14=page fault, registers
Process name corresponding to current thread: kernel_task

there is this line:
Fault CR2: 0xffffffa0a714be00, Error code: 0x0000000000000011, Fault CPU: 0x3 Kernel NX fault, PL: 0, VF: 2

Maybe run the built in hardware test (command d) and see if anything registers. I did some searching on the Apple forums, but not much that gives any clues.

ReplyQuote
Posted : 14/03/2022 1:19 pm
(@fiveaces)
Active Member

@softraid-support Now I am working on a new macbook air with the M1 chip. (All my previous problems were on a 2014 imac) I am getting the same kernel panics on this new macbook air and this computer never used to crash. 

The only difference in the way that I'm using the macbook is that I'm plugging in my RAIDs to it now, (I used to only edit off of an external SSD). The RAIDs that I'm using are a thunderbay 4 controlled by softraid and a g-speed studio, which uses a promise driver. It was not plugged in during the last crash though, so the softraid kext was the only 3rd party kext loaded. 

I also just re-installed macos monterey from scratch on the macbook. 

 

ReplyQuote
Topic starter Posted : 20/03/2022 9:49 am
Page 1 / 2
Share:
close
open