Hello Native Instruments Support,
After updating from Maschine 3.4 to 3.7.0, I started seeing a reproducible crash in the standalone application. If my Maschine MK3 is already powered on when I launch the software, successive launches alternate between crashing and working normally. This also happens with a completely blank project. I did not experience this behavior on 3.4.
Steps to reproduce
- Connect the Maschine MK3 via USB and power it on.
- Launch Maschine 3.7.0 standalone and open a blank project with no third-party plug-ins. Leave it idle.
- Shortly after the project opens, Maschine exits without any further input.
- Leave the MK3 powered on and relaunch Maschine. This time it works normally.
- Quit the software normally and launch it again, keeping the MK3 on throughout. The crash returns. Repeating the test produces the same crash → success → crash → success pattern.
Working startup sequence
If I launch Maschine first and power on the MK3 after the software has opened, the controller connects and I can use the same projects normally. This sequence has been consistently reliable in my tests.
System and troubleshooting
- Windows 10 Pro 22H2, build 19045.5965
- Maschine 3.7.0.0 standalone, with an RME Fireface UCX as the ASIO audio interface
- Maschine MK3 firmware 1.4.5, confirmed current by the NI firmware updater
- Reinstalled the MK3 Windows controller driver 5.0.1. The crash returned.
- Reproduced with a full project, my live template, and a completely blank project. All results in this report are from 3.7.0. I plan to test 3.7.2 separately.
Crash evidence
I have three Windows minidumps. All three report 0xC0000374 (STATUS_HEAP_CORRUPTION) in Maschine 3.exe, detected at ntdll.dll + 0xFF3C9. The blank-project dump is Maschine 3.exe.3404.dmp.
On one occasion, immediately after the application exited, all the MK3 lights turned white and froze. When I pressed a pad, the lights went out and the controller returned to standby. In another recorded crash, Windows logged an NIHostIntegrationAgent event 258 for the MK3 (onConnectionDropped) 34 seconds after the application error.
Could you check whether this startup sequence matches a known issue and whether 3.7.2 addresses it? I can provide all three minidumps and the Windows event logs. If a controller or hardware-service log would help, please let me know which one to capture during the alternating launches.
Thank you,
WithLight Studio