SFPro continually crashes - versions 14-18

SteveMTNO wrote on 2/12/2025, 11:34 AM

I've been dealing with continual crashing with multiple versions of Sound Forge Pro. This has been occurring since at least v14.

I have registered 64-bit versions of the following installed on my computer:

SFPro Suite 18.0.0 (build 21)
SFPro Suite 17.0.2 (build 109)
SFPro 16.1.2 (build 55)
SFPro 15.0 (build 161)
SFPro 14.0 (build 140)

The same behavior occurs in all of them. It doesn't happen all of the time, but it DOES happen about 80-90% of the time. Super frustrating.

Things that trigger a crash:

- placing a marker in a .wav file (ctrl-M)
- copy/pasting a selected region to a new file (double left click to select the region, ctrl-c, ctrl-e)
- placing the cursor anywhere in a file, then hitting the spacebar to start playing
- any other random editing activity (applying a fade, mixing copy/pasted sections, etc etc)
- trying to save a file (and then IF the program recovers it after the crash, you may or may not be able to save it, overwrite the existing file, etc)

If it crashes during a save on a recovered file, sometimes it will say that I don't enough room or access to save the file (when I clearly have access and terrabytes of room). At this point, the program will delete the recovered file. If I don't try to save it again, the file is lost.

All files being edited are 24/192 .wav format.

Each time this has happened, I've upgraded to the newest version, thinking that will fix things. It does for a while, then the same behavior starts again. SFPro18 Suite did the same thing from the beginning - it never has worked without issue.

I've been using SF since v4, back when it was owned by Sonic Foundry. It's a continual source of frustration. I use the program daily. If I'm lucky, I can save what I'm doing after every edit. I'm not always so lucky. Sometimes, it will crash as soon as I make ANY type of edit or try to save what I'm doing.

I'm running Win10 with all the latest updates, 64GB of RAM. I ran the memory diagnostics yesterday, thinking maybe I had some defective RAM - nope, all good there.

I've uninstalled and reinstalled all of the various versions of the programs multiple times.

I've also tried resetting all of the program defaults to no avail. All that does is make me redo all of my workspace changes. The crashes contnue.

Does anyone have any suggestions on how to remedy this ongoing problem?

Thanks in advance,

SteveMTNO

Back to post

Comments

SP. wrote on 2/21/2025, 6:06 PM

@SteveMTNO If everything works fine, I don't think it's necessary to upgrade to a new computer. As far as I see it, people are currently somewhat disappointed about new processors and GPU generations. They are expensive but don't bring much more bang for the buck than the previous generation. And the current chip manufacturing processes are getting into more and more physical limits to increase transistor density.

Microsoft will also start to offer an extended lifetime for Windows 10 updates during 2025 were individuals can buy an additional year of security updates for about $30 without the need to upgrade to Windows 11. So, technically you could stay some more years on Windows 10.

SteveMTNO wrote on 2/21/2025, 8:44 PM

I haven't really heard anything negative about Win11, nothing great either tho. Mostly just "meh"..

I'm definitely not looking to buy a new PC. Especially if there is no great improvements in processor speed, etc. My current PC is still pretty fast - at least fast enough for what I need to do on it.

I heard about the $30 extension. I doubt I'll be doing that either, just on principle. Most likely, I'll just wait till it gets closer to October and then upgrade (assuming everything is fine till then). Hopefully SF12 will continue working too.. ;)

scott-james wrote on 2/4/2026, 12:21 PM

Jumping in here as I'm having much the same issue. I got a new Geekom IT15 mini PC with Windows 11 and installed Sound Forge Pro 18 on it.

Like Steve, one of my tasks is recording audio from my turntable to the PC - sending the audio into the phono input on a Yamaha amplifier and out to the PC via one of the line level outputs - and since the PC doesn't have a line in (sad), I got an Art Pro II USB interface which has its own ASIO driver. Prior to that, when I was just using Sound Forge for editing and playback of existing files, it was using the Realtek speaker output via the Windows Classic Wave profile, and everything worked fine.

As soon as I connected the USB interface, though, the Realtek drivers seemed to disappear, and every time I tried to open Sound Forge, it would crash with the same Unhandled Exception error. I also tried ASIO4ALL and the Realtek ASIO driver with the same results.

As of now, after many failed system restores due to a pesky iTunes file error of some sort (luckily I do external system backups regularly), I'm back to the original non-ASIO configuration, but of course I can't record from the turntable, since the PC has no analog input.

I've tried Audacity and Audition, and they seem to be able to handle an ASIO setup, but I much prefer the Sound Forge Pro interface as I've been using it since Sonic Foundry days and can work much more quickly with it.

SP. wrote on 2/4/2026, 12:37 PM

@scott-james Audacity doesn't support ASIO as far as I know, because it is distributed under an incompatible license. It's odd that it works fine with your setup while SF Pro 18 doesn't.

Just in case, do you maybe have the Magix Low Latency ASIO driver installed? This is a pretty old version of ASIO4ALL and can cause crashes on modern operating systems.

Does your turntable has an USB-out? Maybe you can simply connect it to your computer and select it as a microphone input.

scott-james wrote on 2/4/2026, 1:09 PM

I think you may be right about ASIO support in Audacity; I've been messing around with so many different possible solutions that my brain is prone to short circuiting. As for the low latency driver, I don't think I've seen references to that on my system. And, no, the turntable only has an analog output, switchable between phono and line - currently using phono, as it's plugged into a dedicated phono input which takes a lower level signal.

When I get a minute to myself, I'm going to do an up to date backup, then a clean Windows reinstallation, and connect the Art Pro as the very first thing I do, followed by Sound Forge, and see what happens, just for fun. I'll report back on the results