Kontakt 7 causing Kernel panic shutoff on Mac Studio! (KT-8785)
Answers
-
M2 Max Studio. Updated to 14.5 and Kontakt 7.10.2 still crashes as stand-alone and crashes DAWs. I have not been able to get Kontakt 7 to launch successfully even one time. :(
This is not OK.
1 -
Where is the Kontakt 7 beta available? The link above is a generic link.
0 -
Is this related to this thread's specific issue?
0 -
Yes. You mean kernel panic? M2 Max Studio. If I try to load Kontakt 7 in a DAW with multichannel output it crashes the Mac. If I try to load with stereo version it crashes the DAW only. If I try to load K7 as stand-alone it crashes, but no kernel panic since updating to 14.5. Will continue to test.
0 -
Ah I see. Very interesting. Which version of Native Access do you have, is it the latest? Also, do you own more than one DAW? Are able to test in other DAWs? Which DAW is it crashing in?
0 -
Thanks, yes. Yes, tried two DAWs so far, Logic 11 and DP11. It "crashes inspection" in Logic's Plugin Manager. But does not crash Logic when it is inspecting. Since it fails inspection, Logic will not load it.
In Digital Performer 11.3, K7 passes inspection as AU (unlike Logic). As VST3 it fails inspection and crashes DP immediately when doing so. As it passes inspection as AU, when I try to load it in an instrument track it crashes DP immediately.
Yes, I'm using latest Native Access, redownloaded it, uninstalled K7, removed preferences files, redownloaded K7 with the newest Native Access. No improvement.
MOTU Support is suggesting I contact NI Support, as K7 crashes stand-alone as well. MOTU Support is also suggesting I try with older versions of DAWs. We'll see.
I suspect it's a K7 bug that doesn't work with my particular M2 chip combined with Sonoma.
It's a new Mac (sine January) and K7 has NEVER worked. In previous versions of K7 and Sonoma it caused crashes and kernel panics. Since updating to Sonoma 14.5 no kernel panics.
0 -
Thanks for being so thorough! That's really interesting. I'm on a 2023 Mac Studio M2 Ultra, 64GB UM, 1TB SSD w/ external 40Gbs NVMe enclosure for sample library, running Sonoma 14.5 and LPX 10.8.1 with no issues whatsoever now. No kernel panics, no crashing from K7, and I own a ****** ton of plug-ins too and they all seem to be working fine (as of right now).
Are you loading in a particular plug-in or is it just simply K7 that fails to load? Does it change with multi-channel or is it stereo as well? Have you double checked to make sure you don't have another instance of K7 installed elsewhere on your hard drive/s? Have you ran in safe mode and loaded K7 in standalone? Have you specifically tried a re-install of Logic 10.8.1 after the release of Sonoma 14.5? I've heard some issues related to Logic 11, so I'm hesitant to go to that, but that also might be a contributing factor.
What exactly are your Mac specs/setup? Also, does it yield a crash report? What does the crash report say?0 -
Hi,
I'm experiencing the same issue, unfortunately the problem was not fixed after installing Sonoma 14.5, which I was really hoping for. I'm kinda desperate and disappointed, because my main monitor is ultrawide and I can't work properly on it. This issue was not occuring under Sonoma 14.4 where it worked in flawlesly.
MacBook Pro Max M3, Sonoma 14.5, Cubase 13.0.30, Kontakt 7.10.2, Samsung 57" Odyssey Neo G9 (connected by DisplayPort or HDMI - niether of them work, same as changing the Hz from 120 to 60 or resolution from 8K to 4K doesn't help get it running - not crashing).
0 -
Hmmm, some differences here I think: you have an MBP (mine is a Mac Studio), also your UW is different than mine: LG 34WN80C-B specifically. Additionally (and I don't know if this matters at all), but I'm on an M2 Ultra as opposed to the M3 Max.
What does your kernel panic crash log say specifically?
Have you tried using USB-C display instead of HDMI?0 -
Hey,
It's the same root of this error, trust me. I was reading lot of different articles and comments, and the results are very similar when you update higher version of Kontakt 7.9 and higher version of Sonoma 14.4.
HDMI vs. Display Port, frequencies, resolutions - it doesn't help.
Try to downgrade to Kontakt 7.9 - it's not perfect, but better for me now.
It's
panic(cpu 0 caller 0xfffffe00171e02a8)
0 -
Gotcha. What's the actual thread that's crashing, what does it say on the reason?
0 -
if you think this:
Panicked task 0xfffffe24f07deba8: 16183 pages, 26 threads: pid 159: WindowServer
Panicked thread: 0xfffffe1b5709cf90, backtrace: 0xfffffe6c5b9bb100, tid: 2877
lr: 0xfffffe002d74ff18 fp: 0xfffffe6c5b9bb190
lr: 0xfffffe002d89c040 fp: 0xfffffe6c5b9bb200
lr: 0xfffffe002d89a4a0 fp: 0xfffffe6c5b9bb2d0
lr: 0xfffffe002d6ff8cc fp: 0xfffffe6c5b9bb2e0
lr: 0xfffffe002d74f80c fp: 0xfffffe6c5b9bb690
lr: 0xfffffe002df561d4 fp: 0xfffffe6c5b9bb6b0
lr: 0xfffffe002ec882a8 fp: 0xfffffe6c5b9bb730
lr: 0xfffffe002fda1a44 fp: 0xfffffe6c5b9bb760
lr: 0xfffffe002fda4a24 fp: 0xfffffe6c5b9bb790
lr: 0xfffffe002fda4394 fp: 0xfffffe6c5b9bb820
lr: 0xfffffe002deadba8 fp: 0xfffffe6c5b9bb860
lr: 0xfffffe002deadee8 fp: 0xfffffe6c5b9bb9f0
lr: 0xfffffe002d86725c fp: 0xfffffe6c5b9bbb10
lr: 0xfffffe002d756e78 fp: 0xfffffe6c5b9bbbb0
lr: 0xfffffe002d72aae4 fp: 0xfffffe6c5b9bbc10
lr: 0xfffffe002d741fc0 fp: 0xfffffe6c5b9bbcb0
lr: 0xfffffe002d742430 fp: 0xfffffe6c5b9bbd90
lr: 0xfffffe002d88fadc fp: 0xfffffe6c5b9bbe40
lr: 0xfffffe002d89a8a8 fp: 0xfffffe6c5b9bbf10
lr: 0xfffffe002d6ff8cc fp: 0xfffffe6c5b9bbf20
lr: 0xfffffe002d6ff894 fp: 0x0000000000000000
Kernel Extensions in backtrace:
com.apple.iokit.IOMobileGraphicsFamily(343.0)[AF502C07-259C-31D5-AA1C-9FE809898E15]@0xfffffe002fd94200->0xfffffe002fdd6953
dependency: com.apple.driver.AppleARMPlatform(1.0.2)[111F012A-F12D-349B-A25C-6EC373681EBF]@0xfffffe002e0fd730->0xfffffe002e15174f
dependency: com.apple.driver.AppleM2ScalerCSCDriver(265.0.0)[F5A94589-C093-3A1E-8EE3-9337B8AF8138]@0xfffffe002eb70e90->0xfffffe002ec02993
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[01C95951-C0A2-3F11-BEB9-7290CA8EFE4F]@0xfffffe002ec9bc80->0xfffffe002ecccbf3
dependency: com.apple.iokit.IOAVFamily(1.0.0)[DC469449-16EE-33D6-A8A6-95040609B9DF]@0xfffffe002f8bd3d0->0xfffffe002f94723f
dependency: com.apple.iokit.IOSurface(352.50.1)[405AD4ED-22CC-339C-A58F-2F81660DE066]@0xfffffe002ffa46a0->0xfffffe002ffd1daf
com.apple.driver.AppleMobileDispT603C-DCP(140.0)[42A8F18C-70D2-3193-92B6-51A177ABC778]@0xfffffe002ec7c9f0->0xfffffe002ec9bc7f
dependency: com.apple.AUC(1.0)[F128F377-8A56-35D3-B42C-B2695B4E38A0]@0xfffffe002e058df0->0xfffffe002e05e693
dependency: com.apple.driver.AppleARMPlatform(1.0.2)[111F012A-F12D-349B-A25C-6EC373681EBF]@0xfffffe002e0fd730->0xfffffe002e15174f
dependency: com.apple.driver.AppleM2ScalerCSCDriver(265.0.0)[F5A94589-C093-3A1E-8EE3-9337B8AF8138]@0xfffffe002eb70e90->0xfffffe002ec02993
dependency: com.apple.driver.AppleSEPManager(1.0.1)[F7625BBC-EEE7-322D-ADAA-C8959CBEDDA2]@0xfffffe002ee84000->0xfffffe002eeb3347
dependency: com.apple.driver.IOSlaveProcessor(1)[D401BF31-9BE9-3AC1-9AED-4D1D0B3ADE9C]@0xfffffe002ff7a630->0xfffffe002ff7bfe3
dependency: com.apple.driver.RTBuddy(1.0.0)[3AFF8486-DFCE-3FEF-903E-888D72F170DC]@0xfffffe00305417e0->0xfffffe00305856f7
dependency: com.apple.iokit.IOAVFamily(1.0.0)[DC469449-16EE-33D6-A8A6-95040609B9DF]@0xfffffe002f8bd3d0->0xfffffe002f94723f
dependency: com.apple.iokit.IOMobileGraphicsFamily(343.0.0)[AF502C07-259C-31D5-AA1C-9FE809898E15]@0xfffffe002fd94200->0xfffffe002fdd6953
dependency: com.apple.iokit.IOMobileGraphicsFamily-DCP(343.0.0)[06D2564B-483E-30E6-967B-14D66D5135AA]@0xfffffe002fd524a0->0xfffffe002fd941f3
dependency: com.apple.iokit.IOSurface(352.50.1)[405AD4ED-22CC-339C-A58F-2F81660DE066]@0xfffffe002ffa46a0->0xfffffe002ffd1daf0 -
Here's the kernel extension list related to your error:
com.apple.iokit.IOMobileGraphicsFamilycom.apple.driver.AppleARMPlatformcom.apple.driver.AppleM2ScalerCSCDrivercom.apple.driver.AppleMobileFileIntegritycom.apple.iokit.IOAVFamilycom.apple.iokit.IOSurfacecom.apple.driver.AppleMobileDispT603C-DCPcom.apple.AUCcom.apple.driver.AppleSEPManagercom.apple.driver.IOSlaveProcessorcom.apple.driver.RTBuddy
It's definitely display-related, but I don't know for sure. I would recommend reporting it to Apple and NI in a separate ticket as well. If I find any solutions, I'll reply back!
1 -
Thank you!
I'm aware that it's display-related because when I use different external monitors, everything is okay. It's happening only on my ultra-wide monitor (57" Odyssey Neo G9). It worked with Sonoma 14.3 (and 14.4, I think) without any problems, but after updating Sonoma to 14.4.1 (or 14.4), it started to crash every time I open the Kontakt instance. And it's not just in Cubase; it crashes after opening the standalone app as well.
Currently, I have version 7.9 of Kontakt version, as I mentioned that it's better, unfortunately, it's not. I was testing it, and it worked for a few minutes (which is weird), but now it behaves like Kontakt version 7.10.2 again.
0 -
You're very welcome!
And yeah, it sounds like it's related to the MBP and M3 Max specifically because my computer works fine. Based off of your comments as well as Tommyd's, I'm wondering if this is related to the "Max" chips. I'm not sure if anyone else with the Max chips are experiencing this as well as they haven't explicitly said. I'm just speculating here…0
Categories
- All Categories
- 19 Welcome
- 1.4K Hangout
- 60 NI News
- 735 Tech Talks
- 3.9K Native Access
- 15.9K Komplete
- 1.9K Komplete General
- 4.1K Komplete Kontrol
- 5.5K Kontakt
- 1.5K Reaktor
- 364 Battery 4
- 817 Guitar Rig & FX
- 416 Massive X & Synths
- 1.2K Other Software & Hardware
- 5.5K Maschine
- 7K Traktor
- 7K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators