iMac Pro restarting because of a problem?

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.

They are still working the problem over here. I demonstrated the crash/restart two days in a row and I finally uploaded the videofiles that made the computer crash/restart. What they are doing now, or will be doing in the very near future, is duplicate this event on a similar setup (using my videofiles) so that they can further analyse the problem.

So, we are still in the middle of the investigation.

Mc22cc: Now that they have told you something's up with the videocard, what do they advice you to do? It was obviously shipped to you this way. Do they see this as a thing that can happen to a machine, or do they think it's a potential problem every iMac pro with a Vega64-card can have? What did they advice you to do?

Chances are the engineers are going to arrive to the same conclusion in my case. My only hope is they will be able to duplicate the problem on their own machine. If that's the case, it will be the beginning of their own search for the cause of this problem. Bad hardware (AMD) or bad software (the OS)...

They did not say INvisibleArt, but I am so glad to hear your about your troubleshooting. That is the million dollar question is it hardware or OS. I think you test by engineers with your files will give us the answer. My answer was "the engineers see it is video card" and I read somewhere that new video cards (not stocked; old video cards) were the answer. Anxiously waiting your results. Please let us know what you find out. My logic board with video card is not in stock right now and I am waiting for tech service to get the board to replace mine. Not looking forward to that solution since it will mean I have to transfer all my files from Time Machine. I hope that is easy process.

It's a very easy process indeed. Just make sure that before you send your Mac in for repairs you 1. Make the TM backup and 2. You deactivate every license on every piece of software you're using (just the software you had to activate of course)

Been there, done that, i.e., total restores so many times over the last 25 years. Something inevitably seems to go awry even with the best of intentions. Make sure you have multiple clones, in addition to your TM backup

I seem to remember most Adobe apps being very sensitive to any changes, and in particular had to call Adobe's tech support to get PhotoShop up and running again. It took over an hour. I purchased the last produced DVD paid version of the creative suite, which I still have and is still licensed, as I don't need the latest subscription versions.

Quick question: Is there any quick, easy way to determine which apps may need to be deactivated, other than checking each and every one?

John

p.s. ....by any chance is anybody noticing any weirdness going on with their "keyboards?" Sometimes I'm experiencing latency, or odd misinterpreted keystrokes ??? It's probably me. I have one of those retro "old-school" http://matias.ca/tactilepro4/ click-keyboards. Not using Apple's stock keyboard on my iMac Pro.

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!

So, many of us have been contacted by technical support. Has anybody received results yet? My positive thinking concludes from the silence that support has indeed stumbled upon a large problem and that they are now trying to figure out how to solve it...

Hi MiguelF03,

Can you please post the first and last page of your crash log so we can each compare to our own. Many thanks.

I'll post mine below.

John

Beginning and end of one of my crash logs:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3 (15P3169)","timestamp":"2018-05-05 16:21:28.91 +0000","incident_id":"B0792C1D-2B0B-4EDF-9062-47143B23045A"}

{

"build" : "Bridge OS 2.3 (15P3169)",

"product" : "iBridge2,1",

"kernel" : "Darwin Kernel Version 17.5.0: Mon Feb 26 19:40:05 PST 2018; root:xnu-4570.50.296~7\/RELEASE_ARM64_T8010",

"incident" : "B0792C1D-2B0B-4EDF-9062-47143B23045A",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-05-05 16:21:28.59 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff0078bf984): macOS panic detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 15P3169\nKernel version: Darwin Kernel Version 17.5.0: Mon Feb 26 19:40:05 PST 2018; root:xnu-4570.50.296~7\/RELEASE_ARM64_T8010\nKernelCache UUID: 0CDF83C72AF002F7CBB7823A5714BB28\niBoot version: iBoot-4076.55.1\nsecure boot?: YES\nx86 EFI Boot State: 0xd\nx86 System State: 0x0\nx86 Power State: 0x0\nPaniclog version: 9\nKernel slide: 0x0000000001000000\nKernel text base: 0xfffffff008004000\nEpoch Time: sec usec\n Boot : 0x5aebb83e 0x000caca4\n Sleep : 0x5aedc9bc 0x000aa5c6\n Wake : 0x5aedc9db 0x00053ad2\n Calendar: 0x5aedd9f9 0x0000cf11\n\nPanicked task 0xffffffe0006de878: 2446 pages, 166 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe00098ed90, backtrace: 0xffffffe016e1b530, tid: 330\n\t\t lr: 0xfffffff0081f9580 fp: 0xffffffe016e1b670\n\t\t lr: 0xfffffff0080e15e4 fp: 0xffffffe016e1b680\n\t\t lr: 0xfffffff008113a44 fp: 0xffffffe016e1b9f0\n\t\t lr: 0xfffffff008113dd4 fp: 0xffffffe016e1ba50\n\t\t lr: 0xfffffff008115914 fp: 0xffffffe016e1ba70\n\t\t lr: 0xfffffff0078bf984 fp: 0xffffffe016e1bae0\n\t\t lr: 0xfffffff0078c1bc8 fp: 0xffffffe016e1bb80\n\t\t lr: 0xfffffff0078bf13c fp: 0xffffffe016e1bc00\n\t\t lr: 0xfffffff00787eaa4 fp: 0xffffffe016e1bc30\n\t\t lr: 0xfffffff008570a4c fp: 0xffffffe016e1bc60\n\t\t lr: 0xfffffff0085703a4 fp: 0xffffffe016e1bc90\n\t\t lr: 0xfffffff0080ec500 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 78704 **\n",

"macOSPanicFlags" : "0x4",

"macOSPanicString" : "Panic(CPU 2, time 4102823901337): NMIPI for unresponsive processor: TLB flush timeout, TLB state:0x0\nRAX: 0xffffffa3d2036000, RBX: 0xffffffa3f325bd94, RCX: 0x00000000ffffffff, RDX: 0x00000000000005a5\nRSP: 0xffffffa3f325bad0, RBP: 0xffffffa3f325baf0, RSI: 0x00000000000005a5, RDI: 0xffffffa3d2036000\nR8: 0x0000000000000000, R9: 0x00000000000000f3, R10: 0x0000000060000000, R11: 0x0000000000000000\nR12: 0x0000000000000000, R13: 0xffffff83559ae000, R14: 0x0000000000000000, R15: 0xffffffa3f325bd94\nRFL: 0x0000000000000286, RIP: 0xffffff7f9fcee52e, CS: 0x0000000000000008, SS: 0x0000000000000010\nBacktrace (CPU 2), Frame : Return Address\n0xffffff83b5f06f70 : 0xffffff801b788204 \n0xffffff83b5f06fd0 : 0xffffff801b620336 \n0xffffffa3f325baf0 : 0xffffff7f9fcee4e5 \n0xffffffa3f325bb30 : 0xffffff7f9fd3a0be \n0xffffffa3f325bbe0 : 0xffffff7f9fd39b9d \n0xffffffa3f325bc20 : 0xffffff7f9fd6ab92 \n0xffffffa3f325bc60 : 0xffffff7f9fd2a91a \n0xffffffa3f325bce0 : 0xffffff7f9fd6b306 \n0xffffffa3f325bd30 : 0xffffff7f9fcebc83 \n0xffffffa3f325bd80 : 0xffffff7f9fad5e2d \n0xffffffa3f325bda0 : 0xffffff7f9fa6c568 \n0xffffffa3f325be00 : 0xffffff7f9f9d2615 \n0xffffffa3f325be50 : 0xffffff7f9f9dc387 \n0xffffffa3f325be90 : 0xffffff7f9f9dbb89

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

"binaryImages" : [["0cdf83c7-2af0-02f7-cbb7-823a5714bb28",18446743936270598144,"U"],["00000000-0 000-0000-0000-000000000000",0,"A"],["3ec0635d-0d6a-38d6-8c8a-22d201212492",64424 50944,"S"]],

"notes" : ["Source: \/dev\/rdisk1","29 unindexed user-stack frames from 18 pids: 26,27,28,29,30,36,37,38,40,41,43,45,47,48,56,61,62,68"]

}

Model: iMacPro1,1, BootROM 15.3169.0, 8 processors, Intel Xeon W, 3.2 GHz, 32 GB, SMC

Graphics: Radeon Pro Vega 56, Radeon Pro Vega 56, PCIe

Memory Module: NODE 1/CPU1_DIMM_A0, 8 GB, DDR4, 2666 MHz, Hynix, HMA81GR7AFR8N-VK HMA81GR7AFR8N-VK HMA81GR7AFR8N-VK HMA81GR7AFR8N-VK

Memory Module: NODE 1/CPU1_DIMM_B0, 8 GB, DDR4, 2666 MHz, Hynix, HMA81GR7AFR8N-VK HMA81GR7AFR8N-VK HMA81GR7AFR8N-VK HMA81GR7AFR8N-VK

Memory Module: NODE 1/CPU1_DIMM_C0, 8 GB, DDR4, 2666 MHz, Hynix, HMA81GR7AFR8N-VK HMA81GR7AFR8N-VK HMA81GR7AFR8N-VK HMA81GR7AFR8N-VK

Memory Module: NODE 1/CPU1_DIMM_D0, 8 GB, DDR4, 2666 MHz, Hynix, HMA81GR7AFR8N-VK HMA81GR7AFR8N-VK HMA81GR7AFR8N-VK HMA81GR7AFR8N-VK

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Mar 2 2018 22:40:24 version 9.130.18.8.32.2.34 FWID 01-e4041647

Bluetooth: Version 6.0.5f3, 3 services, 27 devices, 1 incoming serial ports

Network Service: Ethernet, Ethernet, en0

Network Service: Wi-Fi, AirPort, en1

PCI Card: pci1b4b,9182, AHCI Controller, Thunderbolt@183,0,0

PCI Card: pci1b21,612, AHCI Controller, Thunderbolt@187,0,0

Serial ATA Device: ST1000LM024 HN-M101MBB, 1 TB

Serial ATA Device: HGST HUS724030ALE640, 3 TB

Serial ATA Device: ST1000LM024 HN-M101MBB, 1 TB

USB Device: USB 3.0 Bus

USB Device: USB3.0 Hub

USB Device: USB3.0 Hub

USB Device: USB3.0 Hub

USB Device: USB3.0 Hub

USB Device: USB3.0 Hub

USB Device: LAPDOCK

USB Device: USB2.0 Hub

USB Device: USB 2.0 Hub

USB Device: Wacom Intuos Pro M

USB Device: USB2.0 Hub

USB Device: Matias Keyboard

USB Device: USB2.0 Hub

USB Device: USB2.0 Hub

USB Device: USB2.0 Hub

USB Device: USB2.0 Hub Controller

USB Device: HL-L2380DW

USB Device: HL-L2380DW

USB Device: DYMO LabelWriter 450

USB Device: USB2.0 Hub

USB Device: USB2.0 Hub

USB Device: USB2.0 Hub

USB Device: USB2.0 Hub

USB Device: USB PnP Audio Device

USB Device: Smart-UPS 1500 FW:UPS 09.3 / ID=18

USB Device: Magic Trackpad 2

USB Device: ColorQube 8570DN

USB Device: iBridge Bus

USB Device: Headset

USB Device: iBridge ALS

USB Device: iBridge FaceTime HD Camera (Built-in)

USB Device: iBridge

Thunderbolt Bus: iMac Pro, Apple Inc., 33.2

Thunderbolt Bus: iMac Pro, Apple Inc., 33.2

Thunderbolt Device: Little Big Disk, LaCie, 3, 22.3

Apple should ask you to use a special program called Capture Data (they will email you the link to download the program), then you will download these huge log files from your computer (mine were enormous - 4 files > 1 gig zipped) and then Apple's engineers will look at the files and let you know if you have the same problem I am having which a bad Radeon Pro 64 graphic card that is embedded on your logic/motherboard. If so you will need a new logic board like I am waiting to receive. There are comments out there that the wait is for a new "fixed" motherboard to be produce since the ones in stock are similar to the one I already have. Until other folks get the same answer that I did we will not know if this is truly the problem. I run very clean machine also except I do use two monitors.

John it looks like we are all getting the same crash logs. Here is mine. I am not Miguel but MCC.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3 (15P3169)","timestamp":"2018-05-19 19:49:37.50 +0000","incident_id":"36364B35-B104-4FD2-8805-E7D50838ED80"}

{

"binaryImages" : [

[

"0cdf83c7-2af0-02f7-cbb7-823a5714bb28",

18446743936270598144,

"U"

],

[

"00000000-0000-0000-0000-000000000000",

0,

"A"

],

[

"3ec0635d-0d6a-38d6-8c8a-22d201212492",

6442450944,

"S"

]

],

"build" : "Bridge OS 2.3 (15P3169)",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-05-19 19:49:37.00 +0000",

"incident" : "36364B35-B104-4FD2-8805-E7D50838ED80",

"kernel" : "Darwin Kernel Version 17.5.0: Mon Feb 26 19:40:05 PST 2018; root:xnu-4570.50.296~7\/RELEASE_ARM64_T8010",

"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 476928 **\n",

"macOSPanicFlags" : "0x4",

"macOSPanicString" : "Panic(CPU 8, time 431996010987319): NMIPI for unresponsive processor: TLB flush timeout, TLB state:0x0\nRAX: 0x00000000ffffffff, RBX: 0xffffff811bd9c830, RCX: 0x000000000000c1a8, RDX: 0x00000000ffffffff\nRSP: 0xffffff8e37b5b340, RBP: 0xffffff8e37b5b350, RSI: 0xffffffce409fa1a8, RDI: 0xffffffce409ee000\nR8: 0xffffff801f2154f0, R9: 0xffffff811a7f60f8, R10: 0xffffff8e0ad64034, R11: 0x000000000000ffff\nR12: 0xffffff811bfb5400, R13: 0x0000000000000000, R14: 0xffffff8e37b5b610, R15: 0x0000000000625c17\nRFL: 0x0000000000000082, RIP: 0xffffff7fa2e01cca, CS: 0x0000000000000008, SS: 0x0000000000000010\nBacktrace (CPU 8), Frame : Return Address\n0xffffff8e23468f70 : 0xffffff801ed88204 \n0xffffff8e23468fd0 : 0xffffff801ec20336 \n0xffffff8e37b5b350 : 0xffffff7fa2e01c98 \n0xffffff8e37b5b380 : 0xffffff7fa2aecdac \n0xffffff8e37b5b3c0 : 0xffffff7fa2aecc25 \n0xffffff8e37b5b400 : 0xffffff7fa2e01d0d \n0xffffff8e37b5b430 : 0xffffff7fa2aeacf4 \n0xffffff8e37b5b460 : 0xffffff7fa2aea75c \n0xffffff8e37b5b4a0 : 0xffffff7fa2aea610 \n0xffffff8e37b5b4f0 : 0xffffff7fa41f7465 \n0xffffff8e37b5b540 : 0xffffff7fa30ad8fe \n0xffffff8e37b5b5e0 : 0xffffff7fa30bf4f8 \n0xffffff8e37b5b600 : 0xffffff7fa3071ee7 \n0xffffff8e37b5b6d0 : 0xffffff7fa2fd8937 \n0xffffff8e37b5b710 : 0xffffff7fa30aa7bb \n0xffffff8e37b5b730 : 0xffffff7fa30ab116 \n0xffffff8e37b5b750 : 0xffffff7fa3009f96 \n0xffffff8e37b5b790 : 0xffffff7fa300a6bc \n0xffffff8e37b5ba40 : 0xffffff7fa30096ac \n0xffffff8e37b5ba90 : 0xffffff7fa30094b7 \n0xffffff8e37b5bae0 : 0xffffff7fa30086aa \n0xffffff8e37b5bb20 : 0xffffff801f2c2218 \n0xffffff8e37b5bb70 : 0xffffff801f2cae07 \n0xffffff8e37b5bcb0 : 0xffffff801ed44a84 \n0xffffff8e37b5bdc0 : 0xffffff801ec73680 \n0xffffff8e37b5be10 : 0xffffff801ec509dd \n0xffffff8e37b5be60 : 0xffffff801ec634eb \n0xffffff8e37b5bef0 : 0xffffff801ed735ad \n0xffffff8e37b5bfa0 : 0xffffff801ec20986 \n Kernel Extensions in backtrace:\n com.apple.kext.AMDSupport(1.6.6)[F99557BD-05E5-3CBF-AB9E-

that is my thoughts exactly; I suspect it takes some time to correct, build, and "re-embed" a video card into motherboard; I am really disappointed in Apple not being more up front with us. If they called me and said, we found the problem, it is big one and we will make things right. Trust us, hang in there, a fix is coming but it will take time. That would trust and loyalty.

For the record, one of my kernel panic logs:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3 (15P3169)","timestamp":"2018-05-02 15:56:20.49 +0000","incident_id":"BFCB12FA-6857-42C8-819B-F538B8F558CB"}

{

"binaryImages" : [

[

"0cdf83c7-2af0-02f7-cbb7-823a5714bb28",

18446743936270598144,

"U"

],

[

"00000000-0000-0000-0000-000000000000",

0,

"A"

],

[

"3ec0635d-0d6a-38d6-8c8a-22d201212492",

6442450944,

"S"

]

],

"build" : "Bridge OS 2.3 (15P3169)",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-05-02 15:56:20.21 +0000",

"incident" : "BFCB12FA-6857-42C8-819B-F538B8F558CB",

"kernel" : "Darwin Kernel Version 17.5.0: Mon Feb 26 19:40:05 PST 2018; root:xnu-4570.50.296~7\/RELEASE_ARM64_T8010",

"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 606768 **\n",

"macOSPanicFlags" : "0x4",

"macOSPanicString" : "Panic(CPU 9, time 1293901019448): NMIPI for unresponsive processor: TLB flush timeout, TLB state: ...

...

System Profile:

Serial ATA Device: HGST HTS541010A9E680, 1 TB

Serial ATA Device: WDC WD3003FZEX-00Z4SA0, 3 TB

Bluetooth: Version 6.0.5f3, 3 services, 27 devices, 1 incoming serial ports

Model: iMacPro1,1, BootROM 15.3169.0, 10 processors, Intel Xeon W, 3 GHz, 64 GB, SMC

Thunderbolt Bus: iMac Pro, Apple Inc., 33.2

Thunderbolt Bus: iMac Pro, Apple Inc., 33.2

Boot Volume File System Type: apfs

Graphics: Radeon Pro Vega 64, Radeon Pro Vega 64, PCIe

USB Device: USB 3.0 Bus

USB Device: 4-Port USB 3.0 Hub

USB Device: 4-Port USB 3.0 Hub

USB Device: 4-Port USB 2.0 Hub

USB Device: Logitech Extreme 3D

USB Device: 4-Port USB 2.0 Hub

USB Device: KB700M Kinesis Freestyle for Mac

USB Device: Hub

USB Device: DATACOMP USB Keypad

USB Device: USB Receiver

USB Device: USB-C to DisplayPort Cable in 4K 60Hz

USB Device: Apple USB SuperDrive

USB Device: iBridge Bus

USB Device: Headset

USB Device: iBridge ALS

USB Device: iBridge FaceTime HD Camera (Built-in)

USB Device: iBridge

Memory Module: NODE 1/CPU1_DIMM_A0, 16 GB, DDR4, 2666 MHz, Micron, 18ASF2G72PZ-2G6D2 18ASF2G72PZ-2G6D2 18ASF2G72PZ-2G6D2 18ASF2G72PZ-2G6D2

Memory Module: NODE 1/CPU1_DIMM_B0, 16 GB, DDR4, 2666 MHz, Micron, 18ASF2G72PZ-2G6D2 18ASF2G72PZ-2G6D2 18ASF2G72PZ-2G6D2 18ASF2G72PZ-2G6D2

Memory Module: NODE 1/CPU1_DIMM_C0, 16 GB, DDR4, 2666 MHz, Micron, 18ASF2G72PZ-2G6D2 18ASF2G72PZ-2G6D2 18ASF2G72PZ-2G6D2 18ASF2G72PZ-2G6D2

Memory Module: NODE 1/CPU1_DIMM_D0, 16 GB, DDR4, 2666 MHz, Micron, 18ASF2G72PZ-2G6D2 18ASF2G72PZ-2G6D2 18ASF2G72PZ-2G6D2 18ASF2G72PZ-2G6D2

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Mar 2 2018 22:40:24 version 9.130.18.8.32.2.34 FWID 01-e4041647

Network Service: Ethernet, Ethernet, en0

Network Service: Wi-Fi, AirPort, en1

PCI Card: pci1b21,625, AHCI Controller, Thunderbolt@68,0,0

PCI Card: pci1b21,625, AHCI Controller, Thunderbolt@67,0,0

Thunderbolt Device: ThunderBay 43, Other World Computing, 3, 26.2

I think this 'video card is the problem' could be a red herring. None of the log files in this and other threads suggest a video issue that I can see - but rather issues related to stalled / deadlocked processors / threads and issues with a processor's translation look aside buffer (TLB) - which could be any process / driver / extension?

My past experience with Apple support is that even going up 3 levels of engineer still does not get you someone who understands hardware and OS issues deeply enough to diagnose the types of things reported in these logs.

So, I think we just need to hold off on speculation (mine included!) and simply accepting one support guy's "graphics problem" statement and instead keep sending Apple crash/panic logs so that they have lots of data to help them track this down.

The ONE thing in common I keep seeing, but it may be totally unrelated to the ReStart issue are the "Bug Type 210" and the "Bridge OS" items which seem to always show up at the beginning of the crash log.

This however may be normal for lots of issues, I have no idea.

John

bug_type":"210","os_version ":"Bridge OS 2.3 (15P3169)

Assuming this is not in violation of Apple's policies or guidelines, please feel free to join the discussion on SLACK in the iMacProUserGroup here using the password iMacProgroup123: Create Account | Slack

If this posting is considered inappropriate in any way I apologize in advance.

Hope this helps,

John

Ocean City, NJ