"iMac Pro" kernel crash

MFASM wrote:

Should I be concerned?

Yes. I have had countless Macs in my time and if you have a problem in a brand new purchase, take the problem to Apple either at an Apple Store or via telephone support.

If the problem persists or gets worse you have established that it was from the start and puts you in a much stronger position with Apple. If you simply put up with issues you may have them permanently.

Apple generally has good support and you have paid for it. Make sure that they take the responsibility for their products. There have been cases where there were serious flaws in Apple's designs and they chose to not reveal that because of the number of customers affected. Don't be one of the bunnies, always make it Apple's concern, not yours.

The good news, sort of, is that if there is a serious problem and Apple fixes it, it stays fixed. My 2011 27" iMac was one of those and I have been very happy with it after initial serious problems were fixed. I had previous 24" iMacs that also had serious problems and because I was unrelenting Apple finally bit the bullet and replaced them with reliable versions and checked that everything was running OK after the exchange. Never had an issue with them again. It is like my models have had a triple check to make sure they are OK. My two sons had problems with their white 24" iMacs, apparently a known overheating issue. One did nothing, the younger one I took it in hand and made sure it was repaired under warranty and it stayed fixed up until quite recently, so had a good long life. The other son had to eventually toss his out after over a year of putting up with incessant crashes and screen artefacts.

Peter

iMac Pros have USB 3.1 which has ample power to run almost anything, I shouldn't think an external hub would have any effect, but anything is possible with electronics.

One way to find out is detach everything that Apple didn't send you.

If it crashes then it is definitely Apple's doing.

If it comes back and still has the problem I'd escalate it with Apple.

I had an iMac quite a few years ago that underwent two major repairs in a row. I made it very clear that I was not happy that it was obviously a lemon and that I did not want to see that Mac ever again and demanded a replacement, and got it. Again Apple really followed that one up, but I have an inkling that Apple has a play book. They test how far they have to go with you to fix an issue, or whether they can leave you holding the baby. Show them you will not take sh*t and they pull out all stops to fix the problem so they do not have to deal with it again.

As I said after my replacement the iMac was golden, probably my most reliable Mac ever.

Peter

Does anyone on this thread have panic logs, crash logs or similar diagnostic information? Without looking at those, hard to say if these are all the same issue, such as a pagefault at the same address with the same stack trace, or a collection of disparate issues. These crash logs may have clues as to whether any third party drivers are implicated, they may show up in the stack traces.

I think these files get saved to /Library/Logs/DiagnosticReports, or show up in the "send to Apple" dialog box which appears after a restart, from where they can be cut and pasted.

A quick update on my journey so far.

• Kenrel panics continued (always when i'm away from the computer)
• was contacted by apple care outreach and phoned several times with them onece they collected the information about the computer and the crash logs i didn't hear back from them
• Reinstalled the os after running disk repair. This fixed the crypto_val errors i was seeing
• Removed all 3rd Party Kernel Extensions (two werde file system related: Paragon NTFS and Paragon ExtFS
• Fewer crashes now, but interestingly no longer any crash reports etc. I just notice that the mac botted while i was awy by seeing the login screen and not the lock screen in the morning. Chrome also tells me that it was shutdown unexpectedly. But no longer any Send a crash report to Apple Pop- UP or panic-full Files at the console level.
• Still seing a lot of activite in the consoloe log
• Especially a tremendous amount of warnings from deleted and sandboxd (see below)

fehler 07:35:07.783846 +0100 deleted volume validation failed for <>fehler 07:35:07.784017 +0100 deleted volume validation failed for <>fehler 07:35:07.788226 +0100 deleted volume validation failed for <>fehler 07:35:07.788410 +0100 deleted volume validation failed for <>fehler 07:35:07.792639 +0100 deleted volume validation failed for <>fehler 07:35:07.792800 +0100 deleted volume validation failed for <>fehler 07:35:07.945576 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.945589 +0100 sandboxd Sandbox: deleted(519) deny system-fsctl 0x4a12 [Duplicate; no report will be generated.] fehler 07:35:07.947231 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.947324 +0100 sandboxd Sandbox: deleted(519) deny system-fsctl 0x4a12 [Duplicate; no report will be generated.] fehler 07:35:07.948544 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.948577 +0100 sandboxd Sandbox: deleted(519) deny system-fsctl 0x4a12 [Duplicate; no report will be generated.] fehler 07:35:07.949894 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.949936 +0100 sandboxd Sandbox: deleted(519) deny system-fsctl 0x4a12 [Duplicate; no report will be generated.] fehler 07:35:07.951242 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.951274 +0100 sandboxd Sandbox: deleted(519) deny system-fsctl 0x4a12 [Duplicate; no report will be generated.] fehler 07:35:07.952528 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.952576 +0100 sandboxd Sandbox: deleted(519) deny system-fsctl 0x4a12 [Duplicate; no report will be generated.] fehler 07:35:07.953809 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.953812 +0100 sandboxd Sandbox: deleted(519) deny system-fsctl 0x4a12 [Duplicate; no report will be generated.] fehler 07:35:07.955244 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.955208 +0100 sandboxd Sandbox: deleted(519) deny system-fsctl 0x4a12 [Duplicate; no report will be generated.] fehler 07:35:07.955572 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.955638 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.955701 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.955751 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.955796 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.955841 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.955886 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.955929 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.955990 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956040 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956132 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956216 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956278 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956344 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956387 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956435 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956517 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956586 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956726 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956815 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956900 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956949 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.956999 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957047 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957093 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957140 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957190 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957254 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957318 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957396 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957446 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957523 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957619 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957668 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957771 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957876 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.957962 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.958014 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.958106 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.958168 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.958221 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.958312 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.958510 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.958635 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.958760 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584 fehler 07:35:07.958929 +0100 deleted fsctl error: Operation not permitted, using HARDCODED low disk threshold 10737418240 for volume_size: 1000240963584

I have this issue. I contacted Apple support about a month ago. Kernel panic every time I was exporting 4k video. It was a repeatable issue. Apple had me create a new volume and install a new copy of MacOS. Still occurred. Took it into Apple Store for Genius to assess. They said it was a memory issue and replaced the memory. I am exporting 4k video for the 1st time since I've had the memory replaced....and crash! If it continues to happen I'll open up another ticket I guess.

The only update from me is that removing Crashplan stopped my particular crashes. It's been almost a week with not a single crash.

Or flip that on its ear, does it still crash turning off WiFi? I've looked in /Var/Log and there's a boatload of WIFi logs with all kinds of errors... apparently there's a lot of reconnects on my AirPort Extreme, there are messages that are not being authenticated, etc etc. All of them could cause issues between the Ethernet and the WiFi, and a garbled packet that has to retransmit over a link that just went down and now has to shift to a different route... you can guess where that's going...

I have a universal audio Apollo 8 daisy chained with a satellite quad dsp box. After turning off file vault, unlock with Apple Watch and app nap things are much better so I don’t think the daisy chaining is the issue, it’s one of or all of those things combined. That said I still have occasional kernel panics like every 3rd day.

Thx - sysengr-2 🙂

So far so good - 2nd day without a crash / panic during sleep wake up period!

In the past 10 days I had in average 3 panics / crashes per night and no problems during

day / work time!!!

Looks like, that the wake up process during sleep time - caused by the system (either ethernet or power nap or whatsoever) causes the problems, especially by iMac Pros. My regular iMac wasn't rebooted for more than 30 days!

IMHO it is somehow related with the new storage, hibernation mode and / or wake over ethernet.

probable cause a)

when the system changes from different hibernation modes (typically after 3 hours of sleep) and tries to write the memory image to disc

probable cause b)

system gets an wake up event other than USB / bluetooth e.g ethernet or powernap

In both cases somehow the new (high speed) storage is involved this would explain why

- only iMac Pros affected

- the energy settings would have impact on dead or alive 😁

Pls keep in mind that everybody who is desperately waiting for 10.3.4 (as I was) will be disappointed, because I've already tested 10.3.4 Beta 7 without any success! (see my earlier post)

Anyway I'm happy that I do not have to swap my machine (at least for now).

I agree with Happy Puppy this problem occurs with nothing connected to iMac Pro and even after the SSD was reformatted (APFS), system restored and updated to OS 10.13.4 and nothing else installed or migrated to the iMac Pro and no email services activated. My computer was thoroughly checked by authorised Apple Service Centre a few days ago and passed all the tests thrown at it. However the problem persists with kernel panics occurring when the unit is in sleep mode. This problem is out-of-box problem with many (if not all) iMac Pros affected. There is some evidence that attempts were made to address the issue in OS 10.13.4. (Eg. Bridge OS 2.0.1 (15P2542) was upgraded to Bridge OS 2.3 (15P3169) in OS 10.13.4.)

In OS 10.13.3: {"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_versio n":"Bridge OS 2.0.1 (15P2542)","timestamp":"2018-03-28 00:33:46.63 +0000" …

In OS 10.13.4: {"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_versio n":"Bridge OS 2.3 (15P3169)","timestamp":"2018-04-05 12:51:01.05 +0000" …

Crypto Val error is easily cleared by erasing your SSD and reinstalling the proprietary Apple Software and updating to the latest OS version. Painfull but at least one issue resolved. However this will not eliminate the kernel panics caused by Bug_Type 210 error. The crashes will continue even if you have nothing connected to your iMac Pro and nothing installed with the exception of the Apple proprietary software. The frequency of the crashes (when in low energy mode) may vary depending on your setup but they will continue to occur.

I placed a call into Apple (mostly to get it on record that I have this issue). They couldn't seem to find anything in their system relating to this issue, and the tech searched for about 20 minutes while I was on the phone. But I convinced him to keep the ticket open and escalate it. I sent him a collection of my error messages as part of the ticket, and now I'm in wait mode for the response to come back from them.

Incidentally after never having experienced this issue since the launch of the system, I've experienced it multiple times a day for the last week. During this time, I had iPhotos open restoring from iCloud because my iPhoto library had become corrupt on my hard drive. Since it completed restoring yesterday, I've gone a day and a half with no crashes. Not sure if the two are related, but that's really the only difference in the last two days I can think of.

Interesting, I had the same issue when I was connecting two display port displays (one 4k & one 1440p) in the TB ports, albeit only once or twice a week.

I stopped doing two external screens because it was causing the iMac's Pro builtin display to stay off after coming back from sleep (so only the external screens were working and a reboot was needed to get back the builtin display), Apple support was useless...

So now I only use an additional screen, since then I also cant recall having a kernel crash either.

One thing that I have noticed that will cause a sleep reboot and Kemal panic, is if I leave Google Chrome open. Since I have done all of the os reloads and turned off some of the sleep settings, the only time I get an issue is if I leave Google in the background and the iMac goes to sleep

Count me in as well. 10 core Radeon Pro Vega 64 owner here.

I returned my first iMac Pro during the grace period for having the same reboot issue right out of the gate. It rebooted several times in the first three days right out of the box. Second one has had the same issues but I was so deep in a big project I couldn't afford to be without it.

Machine reboots or shuts down on it's own. Sometimes while using it, sometimes it is shut down when I return to it. Even though I have enabled "Prevent Computer from sleeping automatically when display is off." I can pretty much cause it to reboot if I run a h.264 through Compressor and compress it into h.264. After that the machine reboots constantly until I let it cool down. I called Apple Support after a Compressor induced reboot. They had me boot into the Recovery OS and run Disk First Aid in Disk Utility. While waiting on the phone with DU idle, the machine rebooted, I was on hold with the Support Rep at the Login Screen and it rebooted again. After that reboot I logged in while I was on hold to see if I got a Kernel Panic report to share. While I had Text Edit open copying out the report, the machine rebooted again.

Kernel Panic reports: {"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_versio n":"Bridge OS 2.3.1 (15P5064)","timestamp":"2018-07-06 17:20:27.93 +0000","incident_id":"E42E2C96-5621-4870-A5A6-BAD76C4BA723"}

I've also had intermittent static come through audio no matter what the playback is, Spotify, Web Browser, Quicktime, FCPX, and then playback jumps to something like 10x, only a reboot will remedy. I've connected with another user on Twitter who is having this same problem.

I'm thinking this is a GPU thermal error. I was really hoping that the Support call would get me through to speak with an engineer so I could relay some info and help them figure things out. Instead I was told to make a Genius appointment and take it in. Obviously since this happened with 2 separate machines, and others are having the same issue, this is a core design problem either in the base hardware or software. I'm worried that they will chase their tail replacing components and nothing will get done except me being without the machine for days at a time.

I've used Macs for 25 years, and this is a huge disappointment for a machine I payed $7k for to be reliable. I'm seriously considering building a PC workstation now, which I would have never considered before.