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

DinkThifferent

macrumors 6502a
Original poster
Oct 18, 2018
813
2,889
The Netherlands
Hi!

I woke up around 5 this morning and walked downstairs to get a sip of water. When I walked past my 27" 5K 2019 iMac (3Ghz Core i5) I was unpleasantly surprised to see a blinking folder icon with a '?' on its display.

I always put my iMac to sleep when I am going to sleep, but every now and then it turns itself on. I didn't understand why but I learned that I still had 'Power Nap' enabled. I have just turned that off.

To my knowledge a blinking folder with a '?' on it means the Mac can't find the harddrive. After pressing the on/off button for about 10 seconds the Mac turned off, and after waiting a few seconds I turned it back on by pressing the button again. I got the notification in multiple languages that my 'Mac had to restart due to a problem' and that i had to press any key to continue. After pressing that button my Mac booted up normally.

After booting up I got a long crash report. I wanted to copy its text and paste it in Pages, but it took forever to start Pages. The icon kept bouncing, and the Notes app acted in the same way. I left my mac to do its thing, and went back to bed. But obviously couldn't sleep anymore. Now, an hour later, my Mac acts normally again. Fast and smooth, just like it did yesterday.

I don't run any special programs, only use legally acquired software and haven't seen this issue before. I gotta say that I have sometimes issues with simply turning my iMac off, but that's a known Catalina issue from what I have heard. (Icons and dock disappear but the wallpaper remains visible and the Mac doesn't shut itself down)

I just ran First Aid in Disk Utility and it said 'Operation Successful"

Running First Aid on “Macintosh HD” (disk2s5)

Verifying the startup volume will cause this computer to stop responding.

Verifying file system.
Volume could not be unmounted.
Using live mode.
Performing fsck_apfs -n -l -x /dev/rdisk2s5
Checking the container superblock.
Checking the fusion superblock.
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking the Fusion data structures.
Checking volume.
Checking the APFS volume superblock.
The volume Macintosh HD was formatted by diskmanagementd (1412.101.1) and last modified by apfs_kext (1412.141.1).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking snapshot 1 of 13 (com.apple.TimeMachine.2020-09-01-122750.local)
Checking snapshot 2 of 13 (com.apple.TimeMachine.2020-09-01-132801.local)
Checking snapshot 3 of 13 (com.apple.TimeMachine.2020-09-01-150020.local)
Checking snapshot 4 of 13 (com.apple.TimeMachine.2020-09-01-160028.local)
Checking snapshot 5 of 13 (com.apple.TimeMachine.2020-09-01-165911.local)
Checking snapshot 6 of 13 (com.apple.TimeMachine.2020-09-01-191432.local)
Checking snapshot 7 of 13 (com.apple.TimeMachine.2020-09-01-201511.local)
Checking snapshot 8 of 13 (com.apple.TimeMachine.2020-09-01-220228.local)
Checking snapshot 9 of 13 (com.apple.TimeMachine.2020-09-01-225921.local)
Checking snapshot 10 of 13 (com.apple.TimeMachine.2020-09-02-001507.local)
Checking snapshot 11 of 13 (com.apple.TimeMachine.2020-09-02-020657.local)
Checking snapshot 12 of 13 (com.apple.TimeMachine.2020-09-02-060704.local)
Checking snapshot 13 of 13 (com.apple.TimeMachine.2020-09-02-070122.local)
Checking the extent ref tree.
Checking the fsroot tree.
Verifying allocated space.
The volume /dev/rdisk2s5 appears to be OK.
File system check exit code is 0.
Restoring the original state found as mounted.

Operation successful.


Does anyone know what this error report means? I'm running the latest version of MacOS Catalina

panic(cpu 0 caller 0xffffff7f97058231): nvme: "Fatal error occurred. CSTS=0x1 US[1]=0x0 US[0]=0x25 VID=0x144d DID=0xa806
. FW Revision=DXZ77A0Q\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-470.100.17/IONVMeController.cpp:5320
Backtrace (CPU 0), Frame : Return Address
0xffffffa3f2f5b9e0 : 0xffffff801531a65d
0xffffffa3f2f5ba30 : 0xffffff8015454a75
0xffffffa3f2f5ba70 : 0xffffff80154465fe
0xffffffa3f2f5bac0 : 0xffffff80152c0a40
0xffffffa3f2f5bae0 : 0xffffff8015319d27
0xffffffa3f2f5bbe0 : 0xffffff801531a117
0xffffffa3f2f5bc30 : 0xffffff8015ac1abc
0xffffffa3f2f5bca0 : 0xffffff7f97058231
0xffffffa3f2f5bcc0 : 0xffffff7f97043362
0xffffffa3f2f5be20 : 0xffffff8015a32329
0xffffffa3f2f5be90 : 0xffffff8015a32249
0xffffffa3f2f5bec0 : 0xffffff801535c605
0xffffffa3f2f5bf40 : 0xffffff801535c131
0xffffffa3f2f5bfa0 : 0xffffff80152c013e
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[28183FA3-6A50-3611-BC20-A0717B657AAC]@0xffffff7f97035000->0xffffff7f97077fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[5922E20B-D148-30DC-ABBA-0E99B3BE6940]@0xffffff7f95d87000
dependency: com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7f95f01000
dependency: com.apple.driver.AppleEFINVRAM(2.1)[D9C4809C-7B20-3663-A9C8-4DBC261AAD86]@0xffffff7f96109000
dependency: com.apple.iokit.IOStorageFamily(2.1)[3581A46A-F3F3-3CE7-BA52-7046E8D66C32]@0xffffff7f95c65000
dependency: com.apple.iokit.IOReportFamily(47)[8F7948CF-5C25-33F4-A687-67F8A5B7906E]@0xffffff7f95e2f000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
19G2021

Kernel version:
Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64
Kernel UUID: 1D3A0F3D-D908-397B-BD16-8F48C0823A2E
Kernel slide: 0x0000000015000000
Kernel text base: 0xffffff8015200000
__HIB text base: 0xffffff8015100000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 93958173510980
last loaded kext at 91896398188448: >!UAudio 323.4 (addr 0xffffff7f99fe7000, size 434176)
last unloaded kext at 92082857622615: >usb.cdc 5.0.0 (addr 0xffffff7f978a0000, size 28672)
loaded kexts:
com.avast.PacketForwarder 2.1
com.avast.FileShield 4.0.0
com.rim.driver.BlackBerryUSBDriverInt 2.2.16
>!ATopCaseHIDEventDriver 3430.1
>!AUpstreamUserClient 3.6.8
@kext.AMDFramebuffer 3.1.0
@kext.AMDRadeonX4000 3.1.0
@kext.AMDRadeonServiceManager 3.1.0
>!AGraphicsDevicePolicy 5.2.6
>AudioAUUC 1.70
@AGDCPluginDisplayMetrics 5.2.6
@fileutil 20.036.15
>!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.6f7
>BCMWLANFirmware4355.Hashstore 1
>AGPM 111.4.4
>X86PlatformShim 1.0.0
>!APlatformEnabler 2.7.0d0
>pmtelemetry 1
>BCMWLANFirmware4377.Hashstore 1
>!AHDA 283.15
>!A!IKBLGraphics 14.0.7
@Dont_Steal_Mac_OS_X 7.0.0
>BCMWLANFirmware4364.Hashstore 1
@kext.AMD9500!C 3.1.0
>!AThunderboltIP 3.1.4
|!ABCM5701Ethernet 10.3.5
>!ABCMWLANBusInterfacePCIe 1
>!AGFXHDA 100.1.429
>eficheck 1
>!A!IPCHPMC 2.0.1
>!ASMCLMU 212
>!A!ICFLGraphicsFramebuffer 14.0.7
>!A!ISlowAdaptiveClocking 4.0.0
>!AMCCSControl 1.14
@filesystems.autofs 3.0
>!AVirtIO 1.0
@filesystems.hfs.kext 522.100.5
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
>!ASDXC 1.7.7
@filesystems.apfs 1412.141.1
>!AAHCIPort 341.140.1
@private.KextAudit 1.0
>!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
>!AHIDKeyboard 209
>!AActuatorDriver 3440.1
>!AMultitouchDriver 3440.1
>!AInputDeviceSupport 3440.8
>!AHS!BDriver 3430.1
>IO!BHIDDriver 7.0.6f7
@kext.AMDRadeonX4400HWLibs 1.0
@kext.AMDRadeonX4000HWServices 3.1.0
>!AGraphicsControl 5.2.6
|IOAVB!F 850.1
@plugin.IOgPTPPlugin 840.3
>DspFuncLib 283.15
@kext.OSvKernDSPLib 529
>!AHDA!C 283.15
|IOHDA!F 283.15
@!AGPUWrangler 5.2.6
|IOEthernetAVB!C 1.1.0
>!ABCMWLANCore 1.0.0
>mDNSOffloadUserClient 1.0.1b8
>IOImageLoader 1.0.0
|IO80211!FV2 1200.12.2b1
>corecapture 1.0.4
|IONDRVSupport 576.1
>!ASMBusPCI 1.0.14d1
|IO!BHost!CUARTTransport 7.0.6f7
|IO!BHost!CTransport 7.0.6f7
|IO!B!F 7.0.6f7
|IO!BPacketLogger 7.0.6f7
>!A!ILpssUARTv1 3.0.60
>!A!ILpssUARTCommon 3.0.60
>!AOnboardSerial 1.0
|IOSkywalk!F 1
@kext.AMDSupport 3.1.0
@!AGraphicsDeviceControl 5.2.6
|IOAccelerator!F2 438.7.3
>X86PlatformPlugin 1.0.0
>IOPlatformPlugin!F 6.0.0d8
|IOSlowAdaptiveClocking!F 1.0.0
>!ASMBus!C 1.0.18d1
|IOGraphics!F 576.1
@kext.triggers 1.0
>Core!S 551
>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
|IOAHCIBlock!S 316.100.5
>!AThunderboltPCIDownAdapter 2.5.4
>!AThunderboltDPInAdapter 6.2.6
>!AThunderboltDPAdapter!F 6.2.6
>!AHPM 3.4.4
>!A!ILpssI2C!C 3.0.60
>!A!ILpssDmac 3.0.60
>!A!ILpssI2C 3.0.60
>!AThunderboltNHI 5.8.6
|IOThunderbolt!F 7.6.1
|IONVMe!F 2.1.0
|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
|IOUSBMass!SClass 4.0.4
>!UComposite 900.4.2
|IOUSB!F 900.4.2
>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
|IOTimeSync!F 840.3
|IONetworking!F 3.4
|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
|IOReport!F 47
>!AACPIPlatform 6.1
>!ASMC 3.1.9
>watchdog 1
|IOPCI!F 2.9
|IOACPI!F 1.4
@kec.pthread 1
@kec.Libm 1
@kec.corecrypto 1.0

Thanks a lot for your help!
 

Taz Mangus

macrumors 604
Mar 10, 2011
7,815
3,504
Looks like the crash might have been do to the Avast and possible the RIM software you have installed. Have you checked for an update on either of those software?

After something like that happening I would do a SMC and PRAM reset. I would suggest unplugging your external drives before doing the reset as a precaution. You might also want to consider doing a restart to Safe Mode to recreate your system caches. It is something I do.
 
Last edited:

DinkThifferent

macrumors 6502a
Original poster
Oct 18, 2018
813
2,889
The Netherlands
Looks like the crash might have been do to the Avast and possible the RIM software you have installed. Have you checked for an update on either of those software?

After something like that happening I would do a SMC and PRAM reset. I would suggest unplugging your external drives before doing the reset as a precaution. You might also want to consider doing a restart to Safe Mode to recreate your system caches. It is something I do.

Hey thanks a lot for your reply. My Avast is up to date (double checked) and i havent used RIM (Blackberry!) software in ages! I switched macs last year, upgrading from a Mid 2011 to a 2019 5K model and used Time Machine to restore everything onto my new iMac. That's the only explanation i could give you as to why there is RIM software on my iMac.

I have searched my mac and found some old Blackberry files from a sync program i used 1000 years ago. I have deleted those.

Should i be worried about this mishap or is it 'just' a kernel panic?
 

Taz Mangus

macrumors 604
Mar 10, 2011
7,815
3,504
Hey thanks a lot for your reply. My Avast is up to date (double checked) and i havent used RIM (Blackberry!) software in ages! I switched macs last year, upgrading from a Mid 2011 to a 2019 5K model and used Time Machine to restore everything onto my new iMac. That's the only explanation i could give you as to why there is RIM software on my iMac.

I have searched my mac and found some old Blackberry files from a sync program i used 1000 years ago. I have deleted those.

Should i be worried about this mishap or is it 'just' a kernel panic?

I would not worry too much about if it does not happen that often. If it does happen again, look in the crash log and see what might have caused it. Make sure that the RAM software is not residing is ~/Library/LaunchAgents, /Library/LaunchAgents or /Library/LaunchDaemons. Also, once the Rim software has been completely removed I would suggest you restart your computer.
 
  • Like
Reactions: DinkThifferent

DinkThifferent

macrumors 6502a
Original poster
Oct 18, 2018
813
2,889
The Netherlands
I would not worry too much about if it does not happen that often. If it does happen again, look in the crash log and see what might have caused it. Make sure that the RAM software is not residing is ~/Library/LaunchAgents, /Library/LaunchAgents or /Library/LaunchDaemons. Also, once the Rim software has been completely removed I would suggest you restart your computer.
Great thanks for the advice. I will do what you’ve suggested and hope that this was a one time occurrence.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.