SF15Pro crashing repeatedly

Comments

SP. wrote on 9/9/2022, 1:23 AM

@SteveMTNO Other options that may be helpful:

Install the 64 bit and 32 bit C++ Redistributables https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

Update all your drivers

Install all pending Windows updates

Contact technical support and let them check your computer https://www.magix.info/us/support/article/how-do-i-contact-technical-support--1513/

Check the Windows Event viewer for more information about the crash

Use tools like Process Monitor to check what happens during a crash

 

rraud wrote on 9/9/2022, 9:53 AM

Try uninstall> reinstall again .. but use a third-party uninstaller like 'Revo Uninstall' that can remove left-over registry entries and other pertinent data the default uninstall leaves behind which is usually the root cause of issues that reoccur when an app is reinstalled.
There are pro and freeware versions of Revo Uninstall, the free version is adequate in most cases. Use the advanced scan mode but be careful not delete shared data if another version of Magix Sound Forge is installed.

SteveMTNO wrote on 9/9/2022, 10:35 AM

@SteveMTNO Other options that may be helpful:

Install the 64 bit and 32 bit C++ Redistributables https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

Update all your drivers

Install all pending Windows updates

Contact technical support and let them check your computer https://www.magix.info/us/support/article/how-do-i-contact-technical-support--1513/

Check the Windows Event viewer for more information about the crash

Use tools like Process Monitor to check what happens during a crash

 

Thanks for your additional reply, SP. All of my drivers, operating system, etc are up to date. I'm gonna try uninstalling and reinstalling again using Revo and report back. If that doesn't fix it, I'll open a support ticket.

SteveMTNO wrote on 9/9/2022, 2:18 PM

So far, so good. I uninstalled using Revo and reinstalled. No crashing yet, but the cursor isn't working properly. If I'm playing a file and move the cursor to another spot, it starts playing from that spot. I don't want that to happen. I want to be able to put the cursor anywhere in the file and NOT have it start playing from that spot.

Anyone know where the setting is for that? I can't find it....

john_barr wrote on 9/9/2022, 2:23 PM

In Options, unmark: Seek Cursor on Playback.

SteveMTNO wrote on 9/9/2022, 4:26 PM

In Options, unmark: Seek Cursor on Playback.

That worked.. thanks!

Unfortunately, when I went to close the program, it crashed, with this error:

Extra Information
   File:                C:\Users\Steve Marshall\AppData\Local\MAGIX\SOUND FORGE Pro\15.0\dx_grovel_x64.log
   File:                C:\Users\Steve Marshall\AppData\Local\MAGIX\SOUND FORGE Pro\15.0\vst_grovel.log

Problem Description
   Application Name:    SOUND FORGE Pro
   Application Version: Version 15.0 (Build 161) 64-bit
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\SOUND FORGE\SOUND FORGE Pro 15.0\forgek.dll
   Fault Address:       0x00000001801FF5F5
   Fault Offset:        0x00000000001FF5F5

Fault Process Details
   Process Path:        C:\Program Files\SOUND FORGE\SOUND FORGE Pro 15.0\Forge150.exe
   Process Version:     Version 15.0 (Build 161) 64-bit
   Process Description: SOUND FORGE Pro
   Process Image Date:  2021-12-17 (Fri Dec 17) 03:09:36

SteveMTNO wrote on 9/11/2022, 8:53 PM

Still crashing.. this is beyond frustrating at this point...

I just created a support ticket.

dnulf wrote on 9/28/2022, 3:54 PM

@SteveMTNO -- Hi, I am getting a lot of crashes in SF15 dealing with Markers and Regions.

SteveMTNO wrote on 9/28/2022, 4:25 PM

@SteveMTNO -- Hi, I am getting a lot of crashes in SF15 dealing with Markers and Regions.

After contacting Magix support, they suggested that I update to the latest version. I'm currently on v16.1.2 (build 55), 64-bit.

I've been using this for almost a week now and I'm happy to report that I haven't crashed once since the update. Hopefully it stays that way...