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

Not-so-techy person needs help, please

T

TorontoJen

macrumors member
Original poster
May 17, 2016
55
40
Toronto
Hi guys,
You all seem very knowledgeable beyond the basics in this group and I could use a little help.
I’m on deadline writing a book and my computer has thrown up a kernel panic, making ME panic. 🥺 I’ve never had one in years of owning Macs.
I have a 2017 27” iMac running Catalina.
I saved the log from it, but it is gibberish to me. Can someone take a peek? I’d really appreciate it.
Thanks so much.


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

CR0: 0x000000008001003b, CR2: 0x0000000400205c41, CR3: 0x0000000031686000, CR4: 0x00000000003626e0

RAX: 0x0000000000000080, RBX: 0xffffff8044e06430, RCX: 0xffffff8132565000, RDX: 0x000000000000003e

RSP: 0xffffff915d14bdd0, RBP: 0xffffff915d14be20, RSI: 0xffffff8043713950, RDI: 0x0000000400205c19

R8: 0xffffff8043a0e000, R9: 0x0044165a00000025, R10: 0x000000000044165a, R11: 0x0000000000000001

R12: 0x0000000000000000, R13: 0x0000000000000060, R14: 0xffffff8044e06000, R15: 0xffffff80437e4940

RFL: 0x0000000000010246, RIP: 0xffffff801c63dc08, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0x0000000400205c41, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1



Backtrace (CPU 0), Frame : Return Address

0xffffff915d14b830 : 0xffffff801bf1a65d

0xffffff915d14b880 : 0xffffff801c054a75

0xffffff915d14b8c0 : 0xffffff801c0465fe

0xffffff915d14b910 : 0xffffff801bec0a40

0xffffff915d14b930 : 0xffffff801bf19d27

0xffffff915d14ba30 : 0xffffff801bf1a117

0xffffff915d14ba80 : 0xffffff801c6c1abc

0xffffff915d14baf0 : 0xffffff801c0469aa

0xffffff915d14bc70 : 0xffffff801c0466a8

0xffffff915d14bcc0 : 0xffffff801bec0a40

0xffffff915d14bce0 : 0xffffff801c63dc08

0xffffff915d14be20 : 0xffffff7f9f129214

0xffffff915d14be50 : 0xffffff7f9f0d8bd9

0xffffff915d14beb0 : 0xffffff7f9f111607

0xffffff915d14bee0 : 0xffffff801c62d54d

0xffffff915d14bf30 : 0xffffff801c62be1e

0xffffff915d14bf70 : 0xffffff801c62b416

0xffffff915d14bfa0 : 0xffffff801bec013e

Kernel Extensions in backtrace:

com.apple.iokit.IOAcceleratorFamily2(438.7.3)[9D052246-9911-3EB3-89E9-BDF771949C45]@0xffffff7f9f0d7000->0xffffff7f9f19bfff

dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[CA079DB9-6FDB-3AB5-A5E5-506459E3F12E]@0xffffff7f9cf9d000

dependency: com.apple.iokit.IOPCIFamily(2.9)[B130A8B7-967F-330E-942F-E0BB93C71C56]@0xffffff7f9c931000

dependency: com.apple.iokit.IOSurface(269.11)[8AF51385-7435-3E2F-9724-6CD27894229D]@0xffffff7f9f0a5000

dependency: com.apple.iokit.IOGraphicsFamily(576.1)[92A3DAC1-1745-37AC-88DE-FA87B5EB2526]@0xffffff7f9d2f1000

dependency: com.apple.iokit.IOReportFamily(47)[8F7948CF-5C25-33F4-A687-67F8A5B7906E]@0xffffff7f9cccc000



BSD process name corresponding to current thread: kernel_task



Mac OS version:

19G73



Kernel version:

Darwin Kernel Version 19.6.0: Sun Jul 5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64

Kernel UUID: 783946EA-6F11-3647-BF90-787AEA14B954

Kernel slide: 0x000000001bc00000

Kernel text base: 0xffffff801be00000

__HIB text base: 0xffffff801bd00000

System model name: iMac18,3 (Mac-BE088AF8C5EB4FA2)

System shutdown begun: NO

Panic diags file available: YES (0x0)



System uptime in nanoseconds: 14964779276447

last loaded kext at 4126453171490: >!ATopCaseHIDEventDriver 3430.1 (addr 0xffffff7fa0d0d000, size 61440)

last unloaded kext at 5202230945277: >!AHIDKeyboard 209 (addr 0xffffff7fa0c8f000, size 36864)

loaded kexts:

@filesystems.smbfs 3.4.4

>AudioAUUC 1.70

@fileutil 20.036.15

>!APlatformEnabler 2.7.0d0

>AGPM 111.4.4

>X86PlatformShim 1.0.0

@filesystems.autofs 3.0

@kext.AMDRadeonServiceManager 3.1.0

>!AUpstreamUserClient 3.6.8

@kext.AMDFramebuffer 3.1.0

>!AHDA 283.15

@kext.AMDRadeonX4000 3.1.0

>!AGraphicsDevicePolicy 5.2.6

@AGDCPluginDisplayMetrics 5.2.6

>!AHV 1

|IOUserEthernet 1.0.1

|IO!BSerialManager 7.0.6f7

>pmtelemetry 1

@Dont_Steal_Mac_OS_X 7.0.0

>!A!IKBLGraphics 14.0.7

>!AMCCSControl 1.14

>eficheck 1

>!AThunderboltIP 3.1.4

@kext.AMD9500!C 3.1.0

>!A!IKBLGraphicsFramebuffer 14.0.7

>!A!ISlowAdaptiveClocking 4.0.0

>!ASMCLMU 212

>!AGFXHDA 100.1.429

|Broadcom!B20703USBTransport 7.0.6f7

>!A!IPCHPMC 2.0.1

>!AVirtIO 1.0

@filesystems.hfs.kext 522.100.5

@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1

@BootCache 40

@!AFSCompression.!AFSCompressionTypeZlib 1.0.0

@filesystems.apfs 1412.141.1

>!ASDXC 1.7.7

|!ABCM5701Ethernet 10.3.5

>AirPort.BrcmNIC 1400.1.1

@private.KextAudit 1.0

>!AAHCIPort 341.140.1

>!AACPIButtons 6.1

>!ARTC 2.0

>!ASMBIOS 2.1

>!AACPIEC 6.1

>!AAPIC 1.7

$!AImage4 1

@nke.applicationfirewall 303

$TMSafetyNet 8

@!ASystemPolicy 2.0.0

|EndpointSecurity 1

@kext.triggers 1.0

>DspFuncLib 283.15

@kext.OSvKernDSPLib 529

@kext.AMDRadeonX4200HWLibs 1.0

@kext.AMDRadeonX4000HWServices 3.1.0

>!AGraphicsControl 5.2.6

|IOAVB!F 850.1

@!AGPUWrangler 5.2.6

>X86PlatformPlugin 1.0.0

|IOAccelerator!F2 438.7.3

|IOSlowAdaptiveClocking!F 1.0.0

@kext.AMDSupport 3.1.0

@!AGraphicsDeviceControl 5.2.6

|IONDRVSupport 576.1

>!AHDA!C 283.15

|IOGraphics!F 576.1

|IOHDA!F 283.15

>!ASMBus!C 1.0.18d1

|Broadcom!BHost!CUSBTransport 7.0.6f7

|IO!BHost!CUSBTransport 7.0.6f7

|IO!BHost!CTransport 7.0.6f7

|IO!B!F 7.0.6f7

|IO!BPacketLogger 7.0.6f7

>IOPlatformPlugin!F 6.0.0d8

>!ASMBusPCI 1.0.14d1

@plugin.IOgPTPPlugin 840.3

>usb.networking 5.0.0

>usb.!UHostCompositeDevice 1.2

|IOAudio!F 300.2

@vecLib.kext 1.2.0

|IOSerial!F 11

|IOSurface 269.11

@filesystems.hfs.encodings.kext 1

>!AThunderboltDPInAdapter 6.2.6

>!AThunderboltDPAdapter!F 6.2.6

>!AThunderboltPCIDownAdapter 2.5.4

>!AHPM 3.4.4

>!A!ILpssI2C!C 3.0.60

>!A!ILpssDmac 3.0.60

|IOAHCIBlock!S 316.100.5

>!AThunderboltNHI 5.8.6

|IOThunderbolt!F 7.6.1

|IOEthernetAVB!C 1.1.0

|IONVMe!F 2.1.0

|IO80211!F 1200.12.2b1

>mDNSOffloadUserClient 1.0.1b8

>corecapture 1.0.4

|IOSkywalk!F 1

>!A!ILpssI2C 3.0.60

|IOUSB!F 900.4.2

|IOAHCI!F 290.0.1

>usb.!UXHCIPCI 1.2

>usb.!UXHCI 1.2

>!AEFINVRAM 2.1

>!AEFIRuntime 2.1

|IOSMBus!F 1.1

|IOHID!F 2.0.0

$quarantine 4

$sandbox 300.0

@Kext.!AMatch 1.0.0d1

>DiskImages 493.0.0

>!AFDEKeyStore 28.30

>!AEffaceable!S 1.0

>!ASSE 1.0

>!AKeyStore 2

>!UTDM 489.120.1

|IOSCSIBlockCommandsDevice 422.120.3

>!ACredentialManager 1.0

>KernelRelayHost 1

>!ASEPManager 1.0.1

>IOSlaveProcessor 1

|IOUSBMass!SDriver 157.140.1

|IOSCSIArchitectureModel!F 422.120.3

|IO!S!F 2.1

|IOUSBHost!F 1.2

>!UHostMergeProperties 1.2

>usb.!UCommon 1.0

>!ABusPower!C 1.0

|CoreAnalytics!F 1

>!AMobileFileIntegrity 1.0.5

@kext.CoreTrust 1

|IOTimeSync!F 840.3

|IONetworking!F 3.4

|IOReport!F 47

>!AACPIPlatform 6.1

>!ASMC 3.1.9

>watchdog 1

|IOPCI!F 2.9

|IOACPI!F 1.4

@kec.pthread 1

@kec.corecrypto 1.0

@kec.Libm
 
Are you getting this kernel panic every time you turn on your machine? If not, I wouldn't worry about it too much. If you are unable to turn on your machine without receiving this kernel panic, you can try booting into safe mode. To do that follow these instructions (from Apple Support):

  1. Turn on or restart your Mac, then immediately press and hold the Shift key as your Mac starts up.
  2. Release the key when you see the login window, then log in to your Mac.
  3. You might be asked to log in again. On either the first or second login window, you should see ”Safe Boot” in the upper-right corner of the window.
Then transfer the necessary files off of the machine onto another drive or upload it to an online storage solution of your choice.
 
  • Like
Reactions: TorontoJen
It’s my second kernel panic in a few days. I didn’t even realize what the first one was, to be honest.
I just wondered if anyone could determine from the code if it’s something trivial or serious.
 
Do you keep a backup of the internal drive?
If not, you'd better start one... right away.
Just for "insurance".

I always recommend either CarbonCopyCloner or SuperDuper for bootable cloned backups.
I DO NOT recommend time machine, ever.
 
  • Like
Reactions: TorontoJen
Kernel panics can be due to a wide variety of causes - usually software, sometimes hardware (and when it's hardware, often external hardware).

So far, the only advice you've received is "back up" (or "backup while in Safe Boot"). It's great advice, especially if you're in the midst of an important project, but it doesn't move you closer to a solution. This Apple support article can get you started: https://support.apple.com/HT200553

I'm hardly expert at interpreting logs, but... This panic seems to be related to the OS, rather than a particular app or external hardware. To me, that suggests a reinstall of macOS (which is one of Apple's suggested steps) may turn out to be fruitful (although software updates come before full reinstalls).

Still, two incidents is not a lot. There haven't been enough of them for you to detect a pattern (executing a particular action, opening a particular app, etc.), which can also make it hard to troubleshoot. Maybe the two incidents are unrelated to each other - just a coincidence that they both happened in close succession after a very long period of having none at all. Maybe there's a pattern that has yet to emerge. So for now, backup now and backup frequently. If these continue save each panic report - a pattern may then emerge.
 
  • Like
Reactions: TorontoJen
lilcosco08 said:
Sounds like a graphics issue to me

Try running a utility like https://www.geeks3d.com/20121129/gp...nchmark-furmark-gimark-stress-test-videocard/ with the dGPU enabled/disabled and see if you get any artifacting/KPs with the dGPU on
Click to expand...
You do realize that we're talking about a 27" iMac here, right? Good luck "disabling" the dedicated Radeon GPU on this one ;)

I doubt it's a GPU issue. Those tend to make themselves visible with weird screen artifacts or system freezes with graphical glitches on-screen long before they cause a kernel panic. Following what has already been said by apple pie (@ApfelKuchen) they are mostly likely caused by either software running in kernel mode (re: faulty drivers) or external hardware. @TorontoJen, do you have any external hardware attached to your iMac?
 
  • Like
Reactions: TorontoJen
I couldn’t get the test thing to work :-/

I have an SSD I use for time machine backups, a HyperX keyboard, and one of those USB things for a mouse plugged into the back USB ports.


mj_ said:
mj_ said:
You do realize that we're talking about a 27" iMac here, right? Good luck "disabling" the dedicated Radeon GPU on this one ;)

I doubt it's a GPU issue. Those tend to make themselves visible with weird screen artifacts or system freezes with graphical glitches on-screen long before they cause a kernel panic. Following what has already been said by apple pie (@ApfelKuchen) they are mostly likely caused by either software running in kernel mode (re: faulty drivers) or external hardware. @TorontoJen, do you have any external hardware attached to your iMac?
Click to expand...
Click to expand...
 
arn said:
any chance this is related?

www.macrumors.com

VMware Engineer Confirms macOS Catalina 10.15.6 Bug Causes Crashes with Virtualization

macOS Catalina 10.15.6 seems to have introduced a bug that causes system crashes, especially when using virtualization software such as VirtualBox or...
www.macrumors.com www.macrumors.com
Click to expand...
That article doesn't say whether the crashes are kernel panics or manifest differently (delving into the original thread at the vmware communities provides a more complete picture). There are "crashes" and then there are "crashes" - it's such an imprecise term.

The "any chance" would of course depend on the OP running that version of the OS as well as running virtualization software.

Overall, with the countless causes for a computing crash, this kind of "Flavor of the Month" question is not likely to hit the mark. We see it all the time, though. "Oh, you must be having the same problem I just had/read about."

There are just 32 posts in that vmware communities thread, with about a half-dozen actual participants, so I don't quite get the "many users" mentioned in the MR article. At the moment, the most recent post in that thread is, "I see Mac Rumors is reporting the problem now," which is the ultimate in echo chamber effect.
 
ApfelKuchen said:
That article doesn't say whether the crashes are kernel panics or manifest differently (delving into the original thread at the vmware communities provides a more complete picture). There are "crashes" and then there are "crashes" - it's such an imprecise term.

The "any chance" would of course depend on the OP running that version of the OS as well as running virtualization software.

Overall, with the countless causes for a computing crash, this kind of "Flavor of the Month" question is not likely to hit the mark. We see it all the time, though. "Oh, you must be having the same problem I just had/read about."

There are just 32 posts in that vmware communities thread, with about a half-dozen actual participants, so I don't quite get the "many users" mentioned in the MR article. At the moment, the most recent post in that thread is, "I see Mac Rumors is reporting the problem now," which is the ultimate in echo chamber effect.
Click to expand...

Digging into the support threads, it manifests as both hangs and kernel panics.

It affects non VMWare virtualization too: https://forums.virtualbox.org/viewtopic.php?f=8&t=99161
 
arn said:
Digging into the support threads, it manifests as both hangs and kernel panics.

It affects non VMWare virtualization too: https://forums.virtualbox.org/viewtopic.php?f=8&t=99161
Click to expand...

However, the panic reports are quite different, so no, it's not likely the same issue.

From vmware (emphasis added):
panic(cpu 2 caller 0xffffff7f845a1ad5): userspace watchdog timeout: remoted connection watchdog expired, no updates from remoted monitoring thread in 61 seconds, 7430 checkins from thread since monitoring enabled 148641 seconds ago after loadservice: com.apple.logd, total successful checkins since load (148642 seconds ago): 14864, last successful checkin: 10 seconds ago

service: com.apple.WindowServer, total successful checkins since load (148581 seconds ago): 14831, last successful checkin: 110 seconds ago
Click to expand...

from this thread:
panic(cpu 0 caller 0xffffff801c0469aa): Kernel trap at 0xffffff801c63dc08, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0x0000000400205c41, CR3: 0x0000000031686000, CR4: 0x00000000003626e0

RAX: 0x0000000000000080, RBX: 0xffffff8044e06430, RCX: 0xffffff8132565000, RDX: 0x000000000000003e

RSP: 0xffffff915d14bdd0, RBP: 0xffffff915d14be20, RSI: 0xffffff8043713950, RDI: 0x0000000400205c19

R8: 0xffffff8043a0e000, R9: 0x0044165a00000025, R10: 0x000000000044165a, R11: 0x0000000000000001

R12: 0x0000000000000000, R13: 0x0000000000000060, R14: 0xffffff8044e06000, R15: 0xffffff80437e4940

RFL: 0x0000000000010246, RIP: 0xffffff801c63dc08, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0x0000000400205c41, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1
Click to expand...
 
  • Like
Reactions: arn
mj_ said:
You do realize that we're talking about a 27" iMac here, right? Good luck "disabling" the dedicated Radeon GPU on this one ;)
Click to expand...

Haha, I thought you could swap between the iGPU/dGPU like you can with Macbooks


TorontoJen said:
I couldn’t get the test thing to work :-/
Click to expand...

Anyways I did a little digging & have good news & bad news. The good news is your hardware is (probably) fine ("type 14=page fault", either the system is trying to illegally access a memory location (more likely), or you have faulty memory. (unlikely) ) Try running a RAM test. The bad news is that this could be an unpatched kernel bug, so I'm not sure how to proceed from here
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back