Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

beachmusic

macrumors regular
Original poster
Jan 12, 2013
232
9
St. George Island
In my late 2013 iMac 27" I tried upgrading to Catalina through the system pref. software update option. The install would get to 11 min remaining and then KP and start back to 30 min remaining. I let this run for 8 hours and it just did the same thing. I then created a usb boot stick and did a fresh install. This completed but now I get KP's every 10 min or so. This is with a bare system. The only app loaded is CCC. I will add that about a year ago the spinner part of my 3tb fusion drive died. I was able to split them and continued using the 120g ssd as a storage drive. I now boot from a 1tb crucial ssd in a Sargent usb 3.0 caddie . I did order a WD 1tb ssd and clean installed on it but same problem. I also tried a 1tb WD spinner but it did the same on it. I did capture a KP report from the fresh install which I can upload.

{"timestamp":"2019-10-30 09:47:43.18 -0400","bug_type":"210","os_version":"Mac OS X 10.15.1 (19B88)"}
{"macOSProcessedStackshotData":"bm8gb24gZGlzayBvciBzbGVlcC93YWtlIGZhaWx1cmUgcGFuaWMgc3RhY2tzaG90IGZvdW5k","macOSPanicString":"panic(cpu 0 caller 0xffffff7f9a98d238): \"IOAHCIBlockStorageDriver::CommandTimeout! reallocated sectors = 0x0, pending sectors = 0x0, power on hours = 0x0, fBuiltIn = 1, LBA = 0x0, Block Count = 0x0, Tag = 0x6, Operation Type = 0x7 fis[0]=0xE68027, fis[1]=0x0, fis[2]=0x0, fis[3]=0x0, fis[4]=0x0\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/IOAHCIBlockStorage\/IOAHCIBlockStorage-316.40.3\/IOAHCIBlockStorageDriver.cpp:6311\nBacktrace (CPU 0), Frame : Return Address\n0xffffff9222eeba70 : 0xffffff8017739a3b \n0xffffff9222eebac0 : 0xffffff8017870fe5 \n0xffffff9222eebb00 : 0xffffff8017862a5e \n0xffffff9222eebb50 : 0xffffff80176e0a40 \n0xffffff9222eebb70 : 0xffffff8017739127 \n0xffffff9222eebc70 : 0xffffff801773950b \n0xffffff9222eebcc0 : 0xffffff8017ed17f9 \n0xffffff9222eebd30 : 0xffffff7f9a98d238 \n0xffffff9222eebde0 : 0xffffff7f9a984213 \n0xffffff9222eebe20 : 0xffffff8017e44f79 \n0xffffff9222eebe90 : 0xffffff8017e44e99 \n0xffffff9222eebec0 : 0xffffff801777b625 \n0xffffff9222eebf40 : 0xffffff801777b151 \n0xffffff9222eebfa0 : 0xffffff80176e013e \n Kernel Extensions in backtrace:\n com.apple.iokit.IOAHCIBlockStorage(316.40.3)[D16B857E-1AFB-3E06-A190-6F0944BB81AF]@0xffffff7f9a97c000->0xffffff7f9a9a3fff\n dependency: com.apple.iokit.IOAHCIFamily(290.0.1)[0456322C-3677-3442-8F74-3171483F3886]@0xffffff7f9a951000\n dependency: com.apple.driver.AppleEFINVRAM(2.1)[A86937B2-6177-3699-BE65-6762DDC120C6]@0xffffff7f98f57000\n dependency: com.apple.iokit.IOStorageFamily(2.1)[A9967DFD-FCB3-3536-B071-F8B46494895B]@0xffffff7f9830c000\n\nBSD process name corresponding to current thread: kernel_task\nBoot args: kext-dev-mode=1 rootless 0\n\nMac OS version:\n19B88\n\nKernel version:\nDarwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29\/RELEASE_X86_64\nKernel UUID: 7503CD47-851F-321E-8747-50DB4299165F\nKernel slide: 0x0000000017400000\nKernel text base: 0xffffff8017600000\n__HIB text base: 0xffffff8017500000\nSystem model name: iMac14,2 (Mac-27ADBB7B4CEE8E61)\nSystem shutdown begun: NO\nPanic diags file available: NO (0xe00002bc)\n\nSystem uptime in nanoseconds: 1206098976845\nlast loaded kext at 1184351013898: @filesystems.afpfs\t11.1 (addr 0xffffff7f9b563000, size 360448)\nlast unloaded kext at 810239494265: @filesystems.msdosfs\t1.10 (addr 0xffffff7f9b545000, size 61440)\nloaded kexts:\n@filesystems.afpfs\t11.1\n@nke.asp-tcp\t8.0.2\n>AudioAUUC\t1.70\n@fileutil\t20.036.15\n>AGPM\t111.2.5\n>!APlatformEnabler\t2.7.0d0\n>X86PlatformShim\t1.0.0\n@filesystems.autofs\t3.0\n>!AMikeyHIDDriver\t131\n>!AMikeyDriver\t283.14\n@AGDCPluginDisplayMetrics\t4.5.9\n>!AHDA\t283.14\n>!AHV\t1\n|IOUserEthernet\t1.0.1\n|IO!BSerialManager\t7.0.1f1\n>!AUpstreamUserClient\t3.6.8\n>!A!IHD5000Graphics\t14.0.2\n>pmtelemetry\t1\n@GeForce\t14.0.0\n>!A!IFramebufferAzul\t14.0.2\n@Dont_Steal_Mac_OS_X\t7.0.0\n>!A!ISlowAdaptiveClocking\t4.0.0\n>eficheck\t1\n>!AThunderboltIP\t3.1.3\n>!ALPC\t3.1\n>!ASMCLMU\t212\n>!ABacklight\t180.1\n>!AMCCSControl\t1.13\n>!AVirtIO\t1.0\n@filesystems.hfs.kext\t522.0.9\n@!AFSCompression.!AFSCompressionTypeDataless\t1.0.0d1\n@BootCache\t40\n@!AFSCompression.!AFSCompressionTypeZlib\t1.0.0\n@private.KextAudit\t1.0\n@filesystems.apfs\t1412.41.1\n>!ASDXC\t1.7.7\n|!ABCM5701Ethernet\t10.3.5\n>AirPort.BrcmNIC\t1400.1.1\n>!AAHCIPort\t341.0.2\n>!ARTC\t2.0\n>!AACPIButtons\t6.1\n>!AHPET\t1.8\n>!ASMBIOS\t2.1\n>!AACPIEC\t6.1\n>!AAPIC\t1.7\n$!AImage4\t1\n@nke.applicationfirewall\t303\n$TMSafetyNet\t8\n@!ASystemPolicy\t2.0.0\n|EndpointSecurity\t1\n$SecureRemotePassword\t1.0\n>!AHIDKeyboard\t209\n@kext.triggers\t1.0\n>DspFuncLib\t283.14\n@kext.OSvKernDSPLib\t529\n|IOAVB!F\t800.17\n>!ASSE\t1.0\n@nvidia.driver.NVDAGK100Hal\t14.0.0\n@nvidia.driver.NVDAResman\t14.0.0\n|IOAccelerator!F2\t438.2.7\n>X86PlatformPlugin\t1.0.0\n@!AGPUWrangler\t4.5.9\n|IOSlowAdaptiveClocking!F\t1.0.0\n>!AThunderboltEDMSink\t4.2.1\n@!AGraphicsDeviceControl\t4.5.9\n>IOPlatformPlugin!F\t6.0.0d8\n>!ABacklightExpert\t1.1.0\n|IONDRVSupport\t568\n>!ASMBus!C\t1.0.18d1\n>!AHDA!C\t283.14\n|IOGraphics!F\t568\n|IOHDA!F\t283.14\n|IOAudio!F\t300.2\n@vecLib.kext\t1.2.0\n>!ASMBusPCI\t1.0.14d1\n@plugin.IOgPTPPlugin\t810.1\n|Broadcom!BHost!CUSBTransport\t7.0.1f1\n|IO!BHost!CUSBTransport\t7.0.1f1\n|IO!BHost!CTransport\t7.0.1f1\n|IO!B!F\t7.0.1f1\n|IO!BPacketLogger\t7.0.1f1\n>usb.!UHub\t1.2\n>usb.networking\t5.0.0\n>usb.!UHostCompositeDevice\t1.2\n|IOSerial!F\t11\n@filesystems.hfs.encodings.kext\t1\n|IOSurface\t269.6\n>!AThunderboltDPOutAdapter\t6.2.3\n>!AThunderboltDPInAdapter\t6.2.3\n>!AThunderboltDPAdapter!F\t6.2.3\n>!AThunderboltPCIDownAdapter\t2.5.2\n>!AThunderboltNHI\t5.8.0\n|IOThunderbolt!F\t7.4.6\n|IOAHCIBlock!S\t316.40.3\n|IOEthernetAVB!C\t1.1.0\n>usb.!UXHCIPCI\t1.2\n>usb.!UXHCI\t1.2\n|IO80211!F\t1200.12.2b1\n>mDNSOffloadUserClient\t1.0.1b8\n>corecapture\t1.0.4\n|IOSkywalk!F\t1\n|IOAHCI!F\t290.0.1\n|IOUSB!F\t900.4.2\n>!AEFINVRAM\t2.1\n>!AEFIRuntime\t2.1\n|IOSMBus!F\t1.1\n|IOHID!F\t2.0.0\n$quarantine\t4\n$sandbox\t300.0\n@kext.!AMatch\t1.0.0d1\n>DiskImages\t493.0.0\n>!AFDEKeyStore\t28.30\n>!AEffaceable!S\t1.0\n>!AKeyStore\t2\n>!UTDM\t489.41.1\n|IOSCSIBlockCommandsDevice\t422.0.2\n>!ACredentialManager\t1.0\n>KernelRelayHost\t1\n>!ASEPManager\t1.0.1\n>IOSlaveProcessor\t1\n|IOUSBMass!SDriver\t157.40.7\n|IOSCSIArchitectureModel!F\t422.0.2\n|IO!S!F\t2.1\n|IOUSBHost!F\t1.2\n>!UHostMergeProperties\t1.2\n>usb.!UCommon\t1.0\n>!ABusPower!C\t1.0\n|CoreAnalytics!F\t1\n>!AMobileFileIntegrity\t1.0.5\n@kext.CoreTrust\t1\n|IOTimeSync!F\t810.1\n|IONetworking!F\t3.4\n|IOReport!F\t47\n>!AACPIPlatform\t6.1\n>!ASMC\t3.1.9\n>watchdog\t1\n|IOPCI!F\t2.9\n|IOACPI!F\t1.4\n@kec.pthread\t1\n@kec.Libm\t1\n@kec.corecrypto\t1.0\n\n\n"}
 

anthonymoody

macrumors 68040
Aug 8, 2002
3,079
1,161
Can someone please read the KP log and point me in the right direction on what to try next?

Can't help you there, but I can tell you that others are having KP issues too, and definitely at least a few with SSDs. There are a couple threads about this if you look back a page or 2 in the threads. In my case, I replaced the 2TB portion of my Fusion Drive - after it died - with an OWC 2TB SSD. Got KP's after Catalina. My KP's all seemed to be related to waking from sleep and/or screen turning off.

As a 'solution' I've turned off all the Eco settings so my Mac never sleeps and my screen never turns off. That's not a long term solution obviously, but, I will say that I've not had a KP since. So - at least in my case - it does seem to be tied directly to the sleep/wake or screen off/on cycle, perhaps tied to the SSD somehow.

FWIW I contacted OWC and they claim not to have had any other calls about this, and said I'd have to wait for Apple to release a patch since their POV is that the drives are compatible with Catalina, full stop. Frustrating but that's where things stand for me.
 

beachmusic

macrumors regular
Original poster
Jan 12, 2013
232
9
St. George Island
Can't help you there, but I can tell you that others are having KP issues too, and definitely at least a few with SSDs. There are a couple threads about this if you look back a page or 2 in the threads. In my case, I replaced the 2TB portion of my Fusion Drive - after it died - with an OWC 2TB SSD. Got KP's after Catalina. My KP's all seemed to be related to waking from sleep and/or screen turning off.

As a 'solution' I've turned off all the Eco settings so my Mac never sleeps and my screen never turns off. That's not a long term solution obviously, but, I will say that I've not had a KP since. So - at least in my case - it does seem to be tied directly to the sleep/wake or screen off/on cycle, perhaps tied to the SSD somehow.

FWIW I contacted OWC and they claim not to have had any other calls about this, and said I'd have to wait for Apple to release a patch since their POV is that the drives are compatible with Catalina, full stop. Frustrating but that's where things stand for me.

Thanks for the response anthonymoody. I did take your advice and turned all the settings off. I'm slowly adding apps and twicks back one at a time. So far so good.
 

kemo

macrumors 6502a
Oct 29, 2008
821
201
Since .1 was released I tried to download it via App Store and install, received KP as well. This is a sign such system is far from ready to be used on daily basis. I wish I could help you but, honestly only thing you can do is wait. I reported the issue to Apple. They will fix that, eventually.

forgot to mention my machine is MBP 15'' 2017.
 

beachmusic

macrumors regular
Original poster
Jan 12, 2013
232
9
St. George Island
Well... Since changing the Energy Saver options I have not had any KP's. I have even managed to get 2 good CCC backups with no problems.
 

anthonymoody

macrumors 68040
Aug 8, 2002
3,079
1,161
Well... Since changing the Energy Saver options I have not had any KP's. I have even managed to get 2 good CCC backups with no problems.

Glad to hear it. Hopefully with .2 we can turn the various energy savers back on.
 

Ethosik

Contributor
Oct 21, 2009
7,829
6,761
Are you using external monitors? I found out my kernel panics are due to having two extra monitors connected via DisplayPort to USB-C. If I just have one, I won’t get any kernel panics regardless of my power settings and regardless which monitor, cable, or port.

Turns out, my Radeon 5700XT eGPU connected to both extra displays resolves the issue too.
 

beachmusic

macrumors regular
Original poster
Jan 12, 2013
232
9
St. George Island
Are you using external monitors? I found out my kernel panics are due to having two extra monitors connected via DisplayPort to USB-C. If I just have one, I won’t get any kernel panics regardless of my power settings and regardless which monitor, cable, or port.

Turns out, my Radeon 5700XT eGPU connected to both extra displays resolves the issue too.

No . Just a late 2013 27" iMac. I do have 3 usb hard drives connected . 1 for the os and 2 for cloner backups .
 

SoYoung

macrumors 65816
Jul 3, 2015
1,457
846
Seriously get yourself a favour and don't update. Its one of the buggiest update I've ever seen. Even Windows Vista was more stable for me. I really regret upgrading and seriously consider to downgrade back to Mojave.
 

SteveLV702

macrumors 6502
Oct 15, 2007
338
31
Las Vegas, Nevada
I am having same issue with my 2013 15" MacBook Pro.. So I just turned off all energy saving features to test on mine. I sure hope OWC comes out with some kind of update soon..


UPDATE: tried turning off Energy Saving features.. Except turned on a screensaver and with screensaver on still experience issue.. But really dont wanna turn off screen saver and have everything burn into my screen... god hope OWC comes out with a fix soon.
 
Last edited:

Dc2006ster

macrumors 6502
Jun 9, 2011
311
125
Alberta, Canada
I had similar issues with Mojave on my 27” IMac. Eventually traced it to a faulty OWC ram stick,
verified this using MemTest, a free app, and OWC gave me a free replacement. Since than I have had no issues with Mojave or with Catalina.
 

Sedulous

macrumors 68030
Dec 10, 2002
2,530
2,577
If not bad RAM, could it be corrupt update image? If RAM were bad, would this not affect routine operation as well?
 

Dc2006ster

macrumors 6502
Jun 9, 2011
311
125
Alberta, Canada
If not bad RAM, could it be corrupt update image? If RAM were bad, would this not affect routine operation as well?
In my case it did. I would get frequent KPs at various and unpredictable times. Once I removed all the OWC ram the iMac ran flawlessly for 2 weeks. I put the owc ram back in and in a day or so I got a KP.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.