Hey there guys,
Been using SMS X8 since it's release with no issues until recently (last 2 weeks or so).
It has started to crash whenever I change VST instruments (only does it with 3rd party vsts - Cherry Audio & GForce synths).
I have checked that the programme is fully up to date and that all the synths are updated to their latest versions.
I have also uninstalled and re-installed the programme.
Anyone any idea what might be causing this and how I might resolve it.
Thanks.
@Steven-Wood Try resetting the program settings to their default values via the Help menu. That's like a clean, fresh install.
Thanks for the reply
Yep have done that......didn't work.
I have removed all of the 3rd party VSTs and the programme seems to function normally with just Magix own instruments and FX.....so I'm going to re-install the 3rd party stuff one at a time and see which one(s) might be causing the issue.
Update.......in case anyone has encountered a similar issue.
It seems that the latest update of windows seemed to make this program extremely unstable, literally crashing everytime I changed or removed any 3rd party VST from a project.
I have uninstalled this update and the issue seems to have mostly gone away.......... still the occasional crash but nowhere near as many as I was getting.
The programme seems stable enough that I can use it for now......awaiting version X9.
Update (the sequel)......again, just in case anyone else has encountered this problem
So, the issue has returned (pretty much crashing every time I remove or change a VST on a track in projects)
I only use VST3 versions of any 3rd party synths....and always installed to default folders/locations.
So i wondered whether the windows update, if that is the problem.(the issue started just after I installed the latest update of Windows !!), had affected the way VST3's are loaded into the DAW.....i installed a couple of the synths in VST2 versions to test this......the crashing still occured.
I also re-installed a previous version of SMS ( SMS 2023) and the issue was the same.
I wonder if the windows update has affected the way Magix programmes handle 3rd party VSTs.....just guess work at this point.
One final thing......I have done a complete re-set of my laptop and re-installed everything "clean"......it did not solve the issue.
All my other programmes/apps seem to be functioning completely normally.......only my magix software seems to have been affected.
@Steven-Wood Does Music Studio simply close itself? Then check the Windows Reliability Monitor for errors. It will record a crash description for every crash. There might be some helpful information in there, for example in which DLL the crash happens.
@SP. yeah it just shuts down completely. Occasionally it will "hang" for a second or so and a splash screen is shown momentarily which has an error code. but that disappears almost immediately and the programme shuts off.
Sorry......i feel like I'm spamming the forum but I keep trying a bunch of different stuff to resolve this issue (without success).
I have managed to capture the error code box in case that helps anyone here come up with a solution that I haven't thought of yet. I have also managed to video capture the crash happening.....but I cant seem to be able to get the video to upload here.
Here's the screen grab of the error code splash screen
@Steven-Wood Have you checked the Windows Reliability Monitor for error message descriptions like I suggested? Do they show some helpful details like in which DLLs the crash occurred?
The error message above basically says that, that Music Studio tries to access memory which lies somewhere outside of your system specifications. For example hexadecimal FFFF in can address 64 kB in memory, FFFF FFFF could already address 4 GB of memory. Each additional F increases the address count exponentially 16 times.
@Steven-Wood Some additional things you could try:
Open cmd.exe as administrator (it's best to enter cmd in the Windows search and then right-click the search result to start as administrator), type DISM.exe /Online /Cleanup-image /Restorehealth and press Enter.
Windows will now get an up-to-date restore image from the Microsoft servers.
If this is done type sfc /scannow and press Enter.
Windows will now check its system files and tries to repair them by using the new image.
See here for details:
@SP. Once again, thanks for the reply
Is this the same as the Windows (repair version)?......if so, I downloaded and installed this yesterday and I have done sfc /scannow.
@Steven-Wood I never heard of Windows (repair version). What's that?
On Windows 11.......in settings/windows update /update history/recovery.....there is an option to "Fix problems using Windows Update.
When you hit installl now it brings up a box saying We'll repair components and system files.
When you hit OK, and allow the process to complete, the Update appears in Update History as Widows 11,version**** (repair version).
I'd never come across it before but it appears to be a different process than regular Windows Updates and the "Reset this PC" recovery process.
I tried your method and, so far, no crashes......but i only tested it a couple of times.
Will give it a more intensive test tomorrow.
Thanks for all your help so far.
@Steven-Wood Some additional things you could try:
Open cmd.exe as administrator (it's best to enter cmd in the Windows search and then right-click the search result to start as administrator), type DISM.exe /Online /Cleanup-image /Restorehealth and press Enter.
Windows will now get an up-to-date restore image from the Microsoft servers.
If this is done type sfc /scannow and press Enter.
Windows will now check its system files and tries to repair them by using the new image.
See here for details:
@SP......Arrrrrrggggghhhhhh
Thought your suggestion had sorted the problem as it seemed to ok for a while (well about 20 mins) and then the crashes started happening again.
A user on the the Samplitude forums had suggested that I try removing a the loaded vst first and then loading in the new one but that crashes it every time.
Still haven't had any reply to my support ticket from Magix support, which is a little frustrating, but greatly appreciate you guys taking the time to try and sort this for me.
Not sure what else I can try at this point.
@Steven-Wood Please check the Windows Reliability Monitor and post the crash description here.
Regarding Magix support, it seems it's currently undergoing a complete reset following the acquisition of Magix by a new owner at the end of 2024. I'm not sure how fast they will answer your tickets.
This is the most recent crash description from the Reliability monitor
Source
Samplitude Music Studio
Summary
Stopped working
Date
30/06/2025 17:58
Status
Report sent
Description
Faulting Application Path: C:\Program Files\MAGIX\Samplitude Music Studio X8\MusicStudio_x64.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: MusicStudio_x64.exe
Application Version: 19.2.2.24222
Application Timestamp: 6761734c
Fault Module Name: StackHash_9ccd
Fault Module Version: 10.0.26100.4484
Fault Module Timestamp: fe7feb61
Exception Code: c0000374
Exception Offset: PCH_D9_FROM_ntdll+0x0000000000162924
OS Version: 10.0.26100.2.0.0.768.101
Locale ID: 2057
Additional Information 1: 9ccd
Additional Information 2: 9ccd1b39c6e15d43724203a5c8c99cf0
Additional Information 3: 87f7
Additional Information 4: 87f743d0990e8f56de08c17289636668
Extra information about the problem
Bucket ID: 562ea016437461fb396ceb9000ef7a56 (1832098152156461654)
And this is the one prior to that
Source
Samplitude Music Studio
Summary
Stopped working
Date
29/06/2025 18:50
Status
Report sent
Description
Faulting Application Path: C:\Program Files\MAGIX\Samplitude Music Studio X8\MusicStudio_x64.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: MusicStudio_x64.exe
Application Version: 19.2.2.24222
Application Timestamp: 6761734c
Fault Module Name: StackHash_60bb
Fault Module Version: 10.0.26100.4484
Fault Module Timestamp: fe7feb61
Exception Code: c0000374
Exception Offset: PCH_6F_FROM_ntdll+0x0000000000162924
OS Version: 10.0.26100.2.0.0.768.101
Locale ID: 2057
Additional Information 1: 60bb
Additional Information 2: 60bb132dfd24d948d2777415c722439c
Additional Information 3: e214
Additional Information 4: e214d4e2bc77fd0089cc3462f815a577
Extra information about the problem
Bucket ID: 3aa1e2eda59fc7a5611938957f809fea (1232078187802959850)
@Steven-Wood Thanks. Do you have some programs in the background running while using Music Studio?
@Steven-Wood Thanks. Do you have some programs in the background running while using Music Studio?
Nope nothing major.
I usually remain online whilst using Music Studio ( mainly cos I forget to turn off wi-fi ) so windows defender is running and cloud back up too.....but scrolling down Task Manager nothing appears to be using too much RAM.
There's obviously a long list of background processes most of which are using 0% RAM.....one or two are using 0.1 - 0.5 or thereabouts.
In truth, I wouldn't know which background processes can be disabled safely so I tend to leave well alone.
@Steven-Wood It's okay. Standard background processes shouldn't be a problem.
Maybe we can try something different. Which audio driver are you using? An ASIO driver? Does it make a difference if you switch to WDM or MME or does it crash as well? Be aware, if you choose something different than an ASIO driver you'll lose live monitoring. But if crashes no longer occur, the problem might be the audio driver.
Also make sure you don't use devices like Bluetooth speakers/headsets. Also sometimes USB microphones are problematic. Do you have an external USB audio interface?
I mainly use ASIO4all as my audio driver for all "in the box" recordings in SMS (Drum Sampler/ synths)
I did try the Magix Low Latency driver....crashed with that too.
If I'm recording guitars.....i use a Boss GT-1000 which acts as a recording interface and uses it's own propriety audio drivers.(again....not been connected since I started having this issue.
I input midi via a midi controller keyboard (akai MPC mini).....though that hasn't been connected at all whilst I've been having this issue.
I don't use any additional "wireless" devices such as Headphones, USB interfaces, speakers/monitors or mics.
Nothing, as far as I'm aware, is different in my set up or how I was using the software......the programme just began crashing suddenly and unexpectedly..
Hi
. . . . and cloud back up too . . . .
Are you using Microsoft OneDrive?
If so check in the programs settings, folder paths, if they are pointing to the 'cloud' then this may be the problem.
John EB
@Steven-Wood Ok, it would be good to know if you can get Samplitude to crash with WDM or MME drivers.
Maybe also try another ASIO driver. For example, if you install the free demo version of FL Studio it also installs the FL Studio ASIO driver. In my experience, this driver usually works fine if there are some problems with ASIO4ALL. You can uninstall FL Studio again without uninstalling the FL Studio ASIO driver because it has its own uninstaller.
Hi
. . . . and cloud back up too . . . .
Are you using Microsoft OneDrive?
If so check in the programs settings, folder paths, if they are pointing to the 'cloud' then this may be the problem.
John EB
Hi John,
Nope, none of the folder paths are pointing to OneDrive.........i did have OneDrive enabled as a start up programme but have switched it off ( I'm assuming that leaves it "asleep" until I wake it up and it no longer runs in the background)
@Steven-Wood Ok, it would be good to know if you can get Samplitude to crash with WDM or MME drivers.
Maybe also try another ASIO driver. For example, if you install the free demo version of FL Studio it also installs the FL Studio ASIO driver. In my experience, this driver usually works fine if there are some problems with ASIO4ALL. You can uninstall FL Studio again without uninstalling the FL Studio ASIO driver because it has its own uninstaller.
HI
Tried both WDM and MME......crash still occuring.
I did notice that in the the VST/ReWire section of System Preferences that the Plug In Buffer preset box was blank, and there is an option to select Default (Best peformance), so was wondering whether this might be part of the issue......also the Maximum VST Buffer size is set at -2 (is that normal?)
Note......both of the above settings were after I reset the programme to default and re-started.
I have to head out to work so I'll try FL studios driver later.
I did notice that in the the VST/ReWire section of System Preferences that the Plug In Buffer preset box was blank, and there is an option to select Default (Best peformance), so was wondering whether this might be part of the issue......also the Maximum VST Buffer size is set at -2 (is that normal?)
It's the same in my settings. But I don't have any crashes.
Since it also crashed with WDM and MME I assume the program crashes are not caused by the audio driver.
Do you have a performance option under the System Settings? In Samplitude Pro X8 I can set the number of CPU cores there. Some users encountered problems because the core number was set too high. Then it's recommended to set it to a low number, for example three cores.