Stuck with KONTROL S88 MK3 Updater ... conflicting instructions??

124»

Answers

  • Rob Ainscough
    Rob Ainscough Member Posts: 61 Member

    Unfortunately Jeremy's attempt failed, same issue. I'm not sure what your development team is doing to require such an "unique" firmware update process, but I know there is a better way. I've updated Raspberry Pi, Arduino's and more from my Win11 PCs without issue using generic Win11 USB drivers.

    Rob.

  • Erwinew
    Erwinew Member Posts: 69 Member
    edited August 9

    @Rob Ainscough Thank you so much for sharing! The update was now successful as you described according to the link:

    https://support.native-instruments.com/hc/en-us/articles/16567321051805-How-Can-I-Update-the-Driver-and-Firmware-of-My-Kontrol-S88-MK3-on-Windows

    I do not understand why this link is so hard to find, or I used incorrect keywords.

    After wasting a full evening again, I have my S88 Mk3 as MIDI controller back, because still crashing REAPER with updated version Komplete Kontrol 3.3.2.

    Will test tomorrow. Thanks again.

  • Erwinew
    Erwinew Member Posts: 69 Member
    edited August 10

    First crashlog already reported after Kontakt 7.10.6 update doing nothing special. Kontakt native crashed on Windows 10 within 10 minutes using it:

    Then you have to figure out yourself how to report this crashlog as there is no link suggestion showed.

  • Rob Ainscough
    Rob Ainscough Member Posts: 61 Member

    You'll need to navigate to the file listed in the error and open it with Notepad. Scan thru the file and look for possible hints at source of the error. Otherwise, send the nicrash file to NI support for analysis.

    Rob.

  • Erwinew
    Erwinew Member Posts: 69 Member
    edited August 11

    Nothing useful as it is a binary file. Only hint which is scary:

    The configuration data for this product is corrupt. Contact your support.

    I've forwarded it to NI support, rebooted the PC and Kontakt and did not see this crash anymore.

  • Rob Ainscough
    Rob Ainscough Member Posts: 61 Member
    edited August 11

    Are you sure it’s a binary file? It’s not “normal” to generate a “crash log” that is binary … memory dumps are binary, but logs are usually text files.

    Did you check the OS event log? That could give you more hints.

  • Erwinew
    Erwinew Member Posts: 69 Member

    This is how a screenshot of the generated nicrash file which looks like a memory dump:

    Windows eventlog entry around that time:

    Faulting application name: ScanPluginsApp3_x64.exe, version: 3.3.2.0, time stamp: 0x66b36d99
    Faulting module name: ntdll.dll, version: 10.0.19041.4522, time stamp: 0x8a1bb6f3
    Exception code: 0xc0000374
    Fault offset: 0x00000000000ff439
    Faulting process ID: 0x1aac
    Faulting application start time: 0x01daeb09b7a05e1f
    Faulting application path: C:\Program Files\Common Files\Native Instruments\Komplete Kontrol\ScanPluginsApp3_x64.exe
    Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
    Report ID: 0cb7f684-0756-4278-b602-b2bd3ec88641
    Faulting package full name: 
    Faulting package-relative application ID: 
    

  • Rob Ainscough
    Rob Ainscough Member Posts: 61 Member

    Looks like you’re running AMD system … what chipset/CPU/MB?

    Identified the executable that triggered the error … if I were to hazard a guess you have a plugin that NI isn’t gracefully managing an exception.

    0xc0000374 is Heap corruption … the Heap is dynamically reserved memory location to hold larger data structures (objects), if the object being placed at this location exceeds the bound of allocation then you get Heap corruption (it can be other issues, but this is the most common).

    The “log” (incrash) file does indeed seem to be a memory dump. These types of issues are very difficult to diagnose … there are several approaches, one is to do remote debugging where a developer can connect to your computer and “attach to process” … there is a lot of configuration (on both ends) that needs to happen for this to be viable. The other approach is more aggressive exception handling in the ScanPluginsApp3_x64.

    Assuming your hardware is good (no memory failures when running Prime95 stress test), you might also want to run sfc /scannow at CMD prompt (run as admin). If you get errors keep running it until all is clear. If that fails you can run DISM (several command line options for this).

    What DAW do you use?

    I’m currently using Digital Performer 11.x and it has rejected one of my NI plugins but it simply makes them not available when I’m using DP.

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 12,431 mod

    @Erwinew This Kontakt crash seems unrelated, it would be beneficial to craete a new post. Just for users who have issues witht he S88 mk3, this unrelated issue only clutters the thread.

  • Erwinew
    Erwinew Member Posts: 69 Member

    @Jeremy_NI You're right, it accidentally slipped into the wrong thread. Feel free to delete last unrelated messages as I cannot do this.

  • Rob Ainscough
    Rob Ainscough Member Posts: 61 Member

    I'm happy to report the latest Firmware updater worked on my S88 without me having to do any special setup/processing.

    I see the developers at NI did indeed produce a new update. Big thank you! Komplete 15 Collection installed without a hitch also.

    Cheers, Rob.

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,404 mod

    Microsoft is in the process of rolling out a resubmitted (but otherwise effectively identical) driver that should resolve the prior issues for those affected. This could still take weeks to months to reach all users (we have no control over this).

  • Erwinew
    Erwinew Member Posts: 69 Member

    We've successfully upgraded our studio computer from Windows 10 to 11 with a fresh installation of the OS and existing NI products. Firmware v1.8.4 upgrade performed without any issues during the S88 MK3 firmware update process. This is a great step forward in user experience. However, we keep further NI investments on hold until the KK VST3 REAPER crash has been resolved. Thank you.

Back To Top