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/17/2025, 5:03 PM

@SteveMTNO You can try running Sound Forge first. DISM should give you newer repair files. SFC used the ones already stored on your computer. Maybe that was enough.

SteveMTNO wrote on 2/17/2025, 5:03 PM

I just tried going thru my standarad workflow and it crashed again, so I'm assuming SFC by itself didn't fix anything...

I'm running DISM now.

SP. wrote on 2/17/2025, 5:05 PM

@SteveMTNO Ok, run sfc /scannow again after dism has finished.

SteveMTNO wrote on 2/17/2025, 5:06 PM

DISM completed successfully (no other info given).. running SFC now...

SteveMTNO wrote on 2/17/2025, 5:11 PM

Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

Tried SF again... crashed on the first copy/paste...

SP. wrote on 2/17/2025, 5:13 PM

@SteveMTNO What does the Windows Reliabilty Monitor say about the crash?

Press Windows + R on your keyboard, type perfmon /rel and press Enter. You can find all crashes by locating a red X icon.

SteveMTNO wrote on 2/17/2025, 5:24 PM

I just checked the Windows Reliability Monitor.

SF16 (the version I used the most) has crashed 227 times since June 10th, mostly from "FaultTolerantHeap" or "Stopped working"..

SF17 crashed 12 times since December 23... all "Stopped working"

SF18 crashed 42 times since Januray 16 (this year).. all were "Stopped working" or "Stopped responding and was closed"

SP. wrote on 2/17/2025, 5:29 PM

@SteveMTNO Can you double click on the most recent crashes and copy and paste the description here or upload a screenshot?

SteveMTNO wrote on 2/17/2025, 5:35 PM

here are the last two.. let me know if you want/need more:

Description
Faulting Application Path: C:\Program Files\SOUND FORGE\SOUND FORGE Pro 18\Forge18.exe

Problem signature
Problem Event Name:    APPCRASH
Application Name:    Forge18.exe
Application Version:    18.0.0.21
Application Timestamp:    65faaabc
Fault Module Name:    StackHash_1e97
Fault Module Version:    10.0.19041.5438
Fault Module Timestamp:    ab0dece3
Exception Code:    c0000374
Exception Offset:    PCH_4A_FROM_ntdll+0x000000000009E044
OS Version:    10.0.19045.2.0.0.256.48
Locale ID:    1033
Additional Information 1:    1e97
Additional Information 2:    1e975e1e4797d28eaea91a955ace4bf8
Additional Information 3:    617b
Additional Information 4:    617bd1bf6c73052dee4941ae5249ba54

Extra information about the problem
Bucket ID: fab15cc3d931e04cfa7770cf5c1382e0 (1907117003120018144)

Description
Faulting Application Path: C:\Program Files\SOUND FORGE\SOUND FORGE Pro 18\Forge18.exe

Problem signature
Problem Event Name:    APPCRASH
Application Name:    Forge18.exe
Application Version:    18.0.0.21
Application Timestamp:    65faaabc
Fault Module Name:    StackHash_09f3
Fault Module Version:    10.0.19041.5438
Fault Module Timestamp:    ab0dece3
Exception Code:    c0000374
Exception Offset:    PCH_4A_FROM_ntdll+0x000000000009E044
OS Version:    10.0.19045.2.0.0.256.48
Locale ID:    1033
Additional Information 1:    09f3
Additional Information 2:    09f379ad1ab45f79dbb23c6d99ef6db5
Additional Information 3:    20e5
Additional Information 4:    20e5dcbceed7d658cd74f833873b37c4

Extra information about the problem
Bucket ID: 254f3311ec35e4da6116b8907e6061cf (1231374478867456463)

(I'm gonna get some dinner.. I'll be back soon - thanks for all your help!)

SP. wrote on 2/17/2025, 6:09 PM

@SteveMTNO Hmm, looks like it simply crashes in Sound Forge. The comments I found on Google on the topic of Fault Module Name: StackHash aren't really helpful. For some it was solved by running the app in compatibility mode, for some by disabling Windows Data Execution Prevention, for another by uninstalling some incorrect drivers.

I'm assuming that you installed the pending Windows updates (not the newest Windows 11 version(!), it seems to make problems) and restarted the computer (by clicking Restart and not Shut down) regularly, correct?

There is a tool called Snappy Driver installer Origin which can automatically find all drivers for your hardware. I personally used Snappy Driver Installer (without the Origin) some years ago to automatically get the newest drivers for my computers and it worked fine. It seems like the Origin version is better because it doesn't want to install additional software.

So, you could try that. Maybe it can find something that needs to be updated: https://www.glenn.delahoy.com/snappy-driver-installer-origin/

SteveMTNO wrote on 2/17/2025, 6:26 PM

Yeah, SF is the only program that I have problems with. Everything else works great.

And yes, I'm up to date on all of my Windows Updates (Win10 not 11).

I just grabbed Snappy Driver Installer Origin. I'll try it later tonght (or tomorrow) when I have more time. Thanks again for all your help, SP!

Dinner awaits...

SteveMTNO wrote on 2/17/2025, 9:13 PM

There are 66 driver packs available for my computer. Are there any in particular that I should look for and/or install?

SP. wrote on 2/18/2025, 7:53 AM

@SteveMTNO Screenshots would be helpful. You only downloaded the indices, correct? If you cannot see a list of devices that have updates available please try restarting Snappy Driver Installer and it should show you a list of components where newer drivers are available. You can also enable Expert mode on the left side.

I think for you, most relevant drivers could be audio and graphic card drivers. Snappy Driver Installer will then only download the relevant packages. This can take a while because they are distributed via file sharing.

SteveMTNO wrote on 2/18/2025, 8:16 AM

All I've done so far is download, install and run the program. Here's what I'm seeing:

johnebaker wrote on 2/18/2025, 8:23 AM

@SP., @SteveMTNO

. . . . Snappy Driver Installer will then only download the relevant packages. This can take a while because they are distributed via file sharing . . . .

This sets alarm bells ringing with me.

Downloading drivers files from unknown/verified sources, ie if they are distributed 'file sharing' or, as the SDI webpages suggest, are already preloaded in SDI for use offline, is not, IMHO, good practice or without risks.

Far better is to go to the audio/graphics chipset/card/device makers websites to get the latest drivers if Windows Update is not providing them.

John EB
Forum Moderator

SteveMTNO wrote on 2/18/2025, 8:29 AM

@SP., @SteveMTNO

Hi

. . . . Snappy Driver Installer will then only download the relevant packages. This can take a while because they are distributed via file sharing . . . .

This sets alarm bells ringing with me.

Downloading drivers files from unknown/verified sources, ie if they are distributed 'file sharing' or, as the SDI webpages suggest, are already preloaded in SDI for use offline, is not, IMHO, good practice or without risks.

Far better is to go to the audio/graphics chipset/card/device makers websites to get the latest drivers if Windows Update is not providing them.

John EB
Forum Moderator

I agree. I don't have a problem going to the individual websites to download the drivers.

The thing I liked about SDI is that it tells me at a glance which drivers need to be updated (assuming of course that it's accurate). I just want to update the drivers that actually need to be updated for me to use SF without crashing...

Thanks for your feedback, John...

SP. wrote on 2/18/2025, 8:32 AM

@SteveMTNO I would update the Realtek High Definition Audio, Realtek ASIO Component, Realtek Audio Effects Component, Realtek Audio Universal Service, Realtek Hardware Support Application and Nvidia High Definition Audio.

And then I would test Sound Forge and test if this helped.

SteveMTNO wrote on 2/18/2025, 8:36 AM

@SteveMTNO I would update the Realtek High Definition Audio, Realtek ASIO Component, Realtek Audio Effects Component, Realtek Audio Universal Service, Realtek Hardware Support Application and Nvidia High Definition Audio.

And then I would test Sound Forge and test if this helped.

That's what I figured too. I'll grab the drivers from the respective websites and report back..

Thanks, SP!

SteveMTNO wrote on 2/18/2025, 9:47 AM

Well, I updated the drivers. Rebooted (just in case I needed to). Still crashing... :(

john_barr wrote on 2/18/2025, 10:39 AM

@SteveMTNO

Sound Forge sales are few. For this reason, Magix does not fix the issues.

john_barr wrote on 2/18/2025, 10:44 AM

I hope Sound Forge 19 has fewer issues.

SteveMTNO wrote on 2/18/2025, 10:48 AM

@SteveMTNO

Sound Forge sales are few. For this reason, Magix does not fix the issues.

Apparently they don't reply to support tickets for SF either. I opened one the same day I started this thread in the forum and have yet to hear from anyone at Magix...

Forum users have been MUCH more helpful.

SteveMTNO wrote on 2/18/2025, 11:25 AM

OK, here's the latest...

After installing the updated drivers, SF was still crashing. Went into iZotope to try doing things in there, and the program went into an endless loop of "not responding" then I'd wait for it, then I'd get "not responding" again, wait, same thing.. Had to kill the program. Restated it again - same thing.

I just did a system restore to put the drivers back to what I had. SF is still crashing (of course), but at least I can use iZotope again (there are things that iZotope does better/faster than SF).

I also tried going into Device Manage to update the drivers that way. Windpws tells me that I have the best/latest drivers.

Now if I could just get SF to do what it's supposed to do..

SP. wrote on 2/18/2025, 11:49 AM

@SteveMTNO It also looks like you have a Xeon workstation with a Quadro card. I'm not sure if this makes a difference. Could be, but that's just speculation.

Would be interesting to know if you have this problem on other computers as well.

Since it crashes on nearly half a dozen versions of Sound Forge (14-18) it's definitely caused by something that hasn't changed in many years (and likely won't change in version 19).

Do the crashes happen with all audio files or only with certain audio files? Maybe there is a problem with the files you want to edit.