VS 2018 crashes constantly, upgraded computer, still doing i

[Dacaur]

Ok, sorry, this is going to be long.....
So up untill recently I have been using a Sandy bridge i3 2100, 4gb ram, and a 550 TI (1MB) video card for my video editing.... Hey, it was a sweet computer when I built it.... In 2012.... At least I had an ssd in it (128gb) which is probably the only reason it lasted me so long.... I had plenty of storage drives, and just moved the video to the SSD while editing....

It's it was never great for video editing. When started editing videos for YouTube I was using Adobe premiere elements 7... It would crash without warning at times, normally when I had not saved my work for about 10-15 min....

Then I got corel videostudio 9 free with my new camera (Canon T6i, which is what I use to film) and then upgraded that to videostudio 2018 ultimate.... Things were ok... Still had to make sure I saved my work often, but I wasn't really doing much actual "editing" mostly just jump cutting.

So the last video I did, was a competition, and I wanted the scores on the screen the whole time. My computer did NOT like that. The program would close without warning about every 2 min... I swapped to an I5 2500k CPU, but it was still the same... I struggled through editing, saving every 20-30 seconds so I didn't lose too much when it inevitably crashed... Finally finished, and started rendering, came back and it had crashed. Tried again, came back, nothing, it had crashed again. This time I say and watched it render, it crashed at 65%.....
I added another 8gb of ram, (total of 12 mow) no change...

By this time I have been doing a lot of looking online and searching and determined it was probably my video card that was the (biggest) issue with only one gigabyte of RAM.... So I went to BestBuy and picked up a Radeon RX 580 8GB card, should be great, right?
Nope. No video output with the new card installed... Well, long story but short, (long version includes lots if swapping, a corrupted bios, and more) turns out my motherboard only supports pci-e 2.0 when a Sandy bridge (2nd gen) CPU is installed..... Everyone says it's backwards compatible but apparently not...
Arg.

So, I bit the bullet and ordered some stuff....
Gigabyte Z390 gamer X Mobo
16gb ddr4 3000 ram
500 gb M.2 pci-e hard drive
i3 8100cpu.
And if course, my rx580 8gb video card...

I even made sure I chose ram and my m2 drive off of gigabytes compatibility list, the WD black M2 I was going to get wasn't in there, so changed to a Samsung 970 500gb drive....

Got everything installed and, starting with a brand new copy of windows 10, I got to work. Installed the latest of all drivers, AVG anti virus, and Videostudio 2018 ultimate , updated to service pack 4. Litteraly all I have installed is Windows 10 with updates, AVG antivirus, and Videostudio 2018 ultimate. Time to get to work....

I had made a mistake in one of the clips in my last project, so decided to fix that..... Everything is fefinitely faster after the upgrade, but STILL crashed on me a couple times...

So what else could be causing this crash? It just randomly closes. No message, doesn't freeze, and I can immediately reopen the app, load my project, and go back to work. Sometimes it asks if I want it to recover my project, sometimes it doesn't.... So frustrated...

[tletter]

So what else could be causing this crash? It just randomly closes. No message, doesn't freeze, and I can immediately reopen the app, load my project, and go back to work.

VS occasionally crashes silently (viewtopic.php?f=1&t=62625). Without an application log that gives a chain of events leading up to the crash, it's a time consuming process of trial and error to see which file, filter or transition caused the problem.

Sometimes it asks if I want it to recover my project, sometimes it doesn't.... So frustrated...

I've learned to save the VSP after every change as even with the recover project feature enabled, you'll still lose work based on your chosen 'Automatic save interval' (default is 10 min).

tletter
https://www.youtube.com/user/tletter

[asik1]

Dacaur wrote:
Sometimes it asks if I want it to recover my project, sometimes it doesn't.... So frustrated...
I've learned to save the VSP after every change as even with the recover project feature enabled, you'll still lose work based on your chosen 'Automatic save interval' (default is 10 min).

** So why don't you set it to 1or2 min?

[cdoughertycd]

My VS 2018 crashes with no warning. It freezes then crashes when working on the audio track. I have it save every 1 minute and I do a manual save after most edits. Seems like older versions VS6, VS7 did not crash as much. I have 36 GB ram with 1 TB hard drive. Makes me nervous but if I do the saves I'm not losing data. Wish this issue could be fixed.

Candy

[tletter]

I have it save every 1 minute and I do a manual save after most edits.

I've also experienced VS2018 saving a corrupted VSP that can't subsequently be opened. Hence it's important to keep a copy of the last version of the VSP that was successfully opened unless you want to risk having to recreate the entire project

tletter
https://www.youtube.com/user/tletter

[tletter]

So why don't you set it to 1or2 min?

VS2018, doesn't update the source VSP whatever the 'Automatic save interval' is set to, nor does it save a copy to the configured 'Working Folder'. Instead it saves to a temporary folder named 'AutoSaveFolder' which may or may not survive a VS crash. In any event, I'd rather not give up control of when and where a save occurs as significant work can be lost if you only rely on auto-save.

tletter
https://www.youtube.com/user/tletter

[cdoughertycd]

Thanks tletter for this info.

Candy

[cdoughertycd]

More on my VS 2018 Ultimate crashing - Deep into project, trying to finish, 45 min long. It crashes almost every time I try an audio edit with the sound mixer, using the rubber bands, doing fine but then when I hit play while in the sound mixer to here the edit, it crashes.

2 hrs later - Discovered if I turn off the sound mixer before I hit play to here the edit, I don't get a crash, at least so far.



Candy