iMac Pro restarting because of a problem?

Happens with absolutely nothing running other than whatever Mac OS starts out of the box, brand new with no apps installed and nothing on the screen. Not even linked to my iCloud account as AppleCare stated the problem might be content related (if that were truly true then it would make these new Macs worse than useless).

Problem appears related to sleep/wake (happens on one of those two events) cycle, not sure which.

Oddly enough if I leave iTunes up and running it "appears" to occur less (anecdotal).

On two occasions the AppleCare guys said it's hardware, then replaced the iMac and then washed their hands of it (closed the ticket) even when I said the problem was still occurring (told me to contact AppleCare and restart the process). Honestly they're just padding their stats (closing tickets as fast as possible) and not really concerned with solving the root problem.

Really not happy with Apple on this one, not sure how to escalate this however, if anyone knows anyone let me know, there's a letter to be sent their way.

P.S. running build 17E202, problem still occurs...

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3 (15P3169)","timestamp":"2018-05-24 07:30:01.91 +0000","incident_id":"A1855AE4-2E78-4523-9068-1B9DB5EC9DDA"}

<snip>

to current thread: kernel_task\n\nMac OS version:\n17E202\n\nKernel version:\nDarwin Kernel Version 17.5.0: Fri Apr 13 19:32:32

<snip>

Ok everybody, I escalated this to engineering. I have a job that reproduces the problem every time. It is not content related because the restart or the freezing doesn't happen on a late 2014 iMac with the same os and apps installed and the same job performed. I can even reproduce it on a clean installation of the iMac Pro with only compressor and final cut pro x installed.

So now I'll have to wait until engineering contacts me. The Senior Apple Care guy told me he was very intrigued by this. Let's see how far I can crawl down this rabbit hole.

Keep you posted...

I covered the whole thread, here maybe 10-15 people complaining , I believe apple sold a lot iMac's Pro but only one thread with 10-15 users that experince the problem and I noticed its from Feb

All this is weird, but there is a gib but, I see people here got replace 3 times their Macs , probably different batches and every time same issue.

So logically the problem in all iMacs Pro, but then again , where all the complaining customers ?

I just finished with apple diagnostics and there is no issues in my iMac , so it looks like a software issue (I hope).

Well, presuming that everyone's using the exact same MacOS software and build (as far as I know this is true) and accepting that clean, brand new, boxed iMac Pros are experiencing the FCR issues, I would agree with your conclusion that there's a bad "lot" or "batch" of them out there.

Still, there are no hard indisputable final conclusions or solutions, albeit lots of anecdotal evidence that "something" is wrong.

Sure hope it's just a software/firmware issue and not a hardware issue.

Let's give Apple a change to respond next week with their take on all this, and go from there.

All the best,

John

Ocean City, NJ

My conclusion was a bit different, if people got their Mac replaced for 3 times they probably not from the same "lot", the issue report started a couple month back and if mine brand new Mac has same issue then its defiantly not from same "lot"

so I'm leaning towards software issue conclusion, I very hope.

What bothers me is, that issue is at least 4 month old, why apple checking it only now.

Yep, this is not a third party software issue, lots of people including myself have experienced the problem with nothing installed out of the box iMac Pros.

On more than one occasion and on more than one Mac (as I've gone through the process a number of times), it was not connected to my iCloud account and there was no restore done from Time Machine, just Mac OS and a new user account. Left it running overnight and by the time I went to use it in the morning it had restarted.

So no, it's not your software, or your peripherals.

My only thought is that some peripherals or software may exacerbate the problem but it happens even without those.

I've gone through the troubleshooting process with Apple twice and on both occasions they said it's a hardware problem and shipped me a new iMac, problem with their process however is they then close the ticket and "fuggitaboutid", when I tried to follow up to say the new iMac hadn't solved the problem they told me to open a new ticket and after the second replacement I couldn't be bothered.

If INvisibleART got it escalated beyond second level, good for him and us!!!

One more voice/machine to add to this thread. I'm on build 17E202 (10.13.4) - and while some version numbers differ from the OP, the report contents are the same. Restarted during the night - 3 day of ownership - with no active apps. Only thing that would/should happen would be power nap waking up to check to see if a Time Machine backup was needed, or to check online for updates.

Difference from OP's crash report is that mine refers to Bridge OS 2.3 (15P3169) and Darwin Kernel 17.6.0. Panic Flag is 0x4; Panic String is "SleepVWake hang detected".

I have nothing special connected to the machine yet (still transferring/loading content) - a scanner and USB 3 drive for Time Machine.

Really unhappy that Apple is taking so long to address this and other iMac Pro issues. (The number of error messages in the Console log is insane - grows worse with each MacOS release, rather than Apple fixing their own software components.)

I put off purchasing this iMac Pro because of this and other threads, but took a chance that maybe the group on this thread was having a unique experience. Hopefully, 10.13.5 will be released before my 14 day return window is over and will fix things, or at least be encouraging. My Early 2008 Mac Pro didn't stop suffering from crashes/panics until a full year after delivery when an OS release finally fixed everything. Not sure I want to go through that experience again.

Apple should be ashamed. Software quality on all of their platforms has really suffered the last few years.

newmediagroup wrote:

Another stupid question. When you get your new motherboard, I assume the SSD(s) can simply be swapped out from the old to the new motherboard not necessitate doing any kind of a "restore" or any other complications or adjustments?

My understanding, John, is that the content of the SSD's cannot be read by another motherboard/machine because of the encryption performed by the T2 chip - keys unique to the chip on each motherboard (?) ... which is a separate encryption from FileVault. Apple has warnings in various places to be sure that we backup via Time Machine and/or other means saying that the content of the SSDs cannot be recovered. Not the same as the old days with Mac Pro's - swap drives into bays of a new machine.

No change in my crashes. I was so hoping the new OS would fix this. I have "clean mac" and again as I said in my post above Apple engineers say something is wrong with my video card and based on number of complaints I am not unique. Shoot, 10.13.5 OS did not fix.

Sorry to be a party-pooper here ...

I'm not sure how root-causing INvisibleART's issue is going to provide a general solution to all this. Not that it shouldn't be pursued in its own right, but it's a crash caused under specific circumstances, with additional software in use. It won't explain why brand new, vanilla iMac Pros, straight out of the box with no third party software or files installed, are crashing with Kernel Panics during sleep.

Likewise, mc22cc has had the crashing issue diagnosed as a Vega 65/motherboard problem - yet crashes are happening for folks with the 'base' Vega 56 card too. If the Apple engineers are right about all of this being caused by some degree of incompatibility between the initial batch of Vega cards and the motherboards, then they should be doing a full recall to all models sold, and providing new-for-almost-new working replacements, rather than sending out techs to crack open anyone's $thousands brand new Mac, to put a new motherboard & g/card in. Not good enough!

It's been a while since I've shared my progress, it's now at a point that it's probably worth sharing.

A LONG story short: I got to the top tier technical support, and uploaded a few images from Capture Data. Feedback from the technical team is that they recognize there is a problem, and that they have said a fix is forthcoming.

When I asked when I could expect a patch to fix it, all they could tell me was "not the next update, and maybe not the next patch either".

So, it seems as though there is light at the end of the tunnel, but we don't know how long the tunnel is.

Hopefully this feedback helps others here..

I disabled all of the except the first one which prevents the computer from automatically sleeping when the screen is off.

So, the computer hasn't restarted on its own when sleeping since Wednesday. While exporting 4K video with the Apple Care representative watching worked, today I exported a new 4K video and it restarted again. So these settings only fix the sleep issue.

Has anyone updated from 10.13.5 to the newly released 10.13.6 yet?

Any improvements, any problems?

John

Ocean City, NJ

==== ==== ==== ==== ==== ==== ====

UPDATE ALERT FROM APPLE:

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA256

APPLE-SA-2018-7-9-4 macOS High Sierra 10.13.6, Security Update

2018-004 Sierra, Security Update 2018-004 El Capitan

macOS High Sierra 10.13.6, Security Update 2018-004 Sierra, and

Security Update 2018-004 El Capitan are now available and address

the following:

AMD

Available for: macOS High Sierra 10.13.5

Impact: A malicious application may be able to determine kernel

memory layout

Description: An information disclosure issue was addressed by

removing the vulnerable code.

CVE-2018-4289: shrek_wzw of Qihoo 360 Nirvan Team

APFS

Available for: macOS High Sierra 10.13.5

Impact: An application may be able to execute arbitrary code with

kernel privileges

Description: A memory corruption issue was addressed with improved

memory handling.

CVE-2018-4268: Mac working with Trend Micro's Zero Day Initiative

ATS

Available for: macOS High Sierra 10.13.5

Impact: A malicious application may be able to gain root privileges

Description: A type confusion issue was addressed with improved

memory handling.

CVE-2018-4285: Mohamed Ghannam (@_simo36)

CFNetwork

Available for: macOS High Sierra 10.13.5

Impact: Cookies may unexpectedly persist in Safari

Description: A cookie management issue was addressed with improved

checks.

CVE-2018-4293: an anonymous researcher

CoreCrypto

Available for: OS X El Capitan 10.11.6, macOS Sierra 10.12.6

Impact: A malicious application may be able to break out of its

sandbox

Description: A memory corruption issue was addressed with improved

input validation.

CVE-2018-4269: Abraham Masri (@cheesecakeufo)

DesktopServices

Available for: macOS Sierra 10.12.6

Impact: A local user may be able to view sensitive user information

Description: A permissions issue existed in which execute permission

was incorrectly granted. This issue was addressed with improved

permission validation.

CVE-2018-4178: Arjen Hendrikse

IOGraphics

Available for: macOS High Sierra 10.13.5

Impact: A local user may be able to read kernel memory

Description: An out-of-bounds read issue existed that led to the

disclosure of kernel memory. This was addressed with improved input

validation.

CVE-2018-4283: @panicaII working with Trend Micro's Zero Day

Initiative

Kernel

Available for: OS X El Capitan 10.11.6, macOS Sierra 10.12.6, macOS

High Sierra 10.13.5

Impact: Systems using Intel® Core-based microprocessors may

potentially allow a local process to infer data utilizing Lazy FP

state restore from another process through a speculative execution

side channel

Description: Lazy FP state restore instead of eager save and restore

of the state upon a context switch. Lazy restored states are

potentially vulnerable to exploits where one process may infer

register values of other processes through a speculative execution

side channel that infers their value.

An information disclosure issue was addressed with FP/SIMD register

state sanitization.

CVE-2018-3665: Julian Stecklina of Amazon Germany, Thomas Prescher of

Cyberus Technology GmbH (cyberus-technology.de), Zdenek Sojka of

SYSGO AG (sysgo.com), and Colin Percival

libxpc

Available for: OS X El Capitan 10.11.6, macOS Sierra 10.12.6, macOS

High Sierra 10.13.5

Impact: An application may be able to gain elevated privileges

Description: A memory corruption issue was addressed with improved

memory handling.

CVE-2018-4280: Brandon Azad

libxpc

Available for: macOS High Sierra 10.13.5

Impact: A malicious application may be able to read restricted memory

Description: An out-of-bounds read was addressed with improved input

validation.

CVE-2018-4248: Brandon Azad

LinkPresentation

Available for: macOS High Sierra 10.13.5

Impact: Visiting a malicious website may lead to address bar spoofing

Description: A spoofing issue existed in the handling of URLs. This

issue was addressed with improved input validation.

CVE-2018-4277: xisigr of Tencent's Xuanwu Lab (tencent.com)

Additional recognition

Help Viewer

We would like to acknowledge Wojciech Reguła (@_r3ggi) of SecuRing

for their assistance.

Help Viewer

We would like to acknowledge Wojciech Reguła (@_r3ggi) of SecuRing

for their assistance.

Help Viewer

We would like to acknowledge Wojciech Reguła (@_r3ggi) of SecuRing

for their assistance.

Help Viewer

We would like to acknowledge Wojciech Reguła (@_r3ggi) of SecuRing

for their assistance.

Kernel

We would like to acknowledge juwei lin (@panicaII) of Trend Micro

working with Trend Micro's Zero Day Initiative for their

assistance.

Security

We would like to acknowledge Brad Dahlsten of Iowa State University

for their assistance.

I updated to 10.13.6 last night (UK), as I'd had a message from the Mac Rumors forum that it fixes the issue of (non-auto adjusted) screen brightness resetting to 90% after a reboot. Sure enough, that issue is now resolved.

One other thing I've noticed is that my two external drives (a LaCie 2-Big Thunderbolt on a 2-3 adaptor, and a WD Elements on USB) now spin down and go to sleep, when I sleep the iMac Pro (previously, they would repeatedly spin down, then fire up again, then spin down, and so on ... even though the iMac Pro was sleeping).

Can't comment on the Kernel Panics shutdowns/restarts, as I've not had any now for several weeks (in fact, since I wiped the machine and re-installed 10.13.4 from Internet Recovery). That said, I haven't given mine any hard work to do (no 4K video conversions or encoding). For the last few weeks, I've had Powernap enabled, as well as 'wake for network access' and 'put hard drives to sleep when possible' - all the things that, early on, I'd disabled to try to prevent the shutdowns.

At the risk of tempting fate, mine seems to be stable at present. May even re-enble 'unlock with Apple Watch'...