Constant crashing when rendering and at random times when playing

Stevepunk wrote on 10/20/2016, 4:06 AM
Extra Information
   File:                C:\Users\Stevepunk\AppData\Local\VEGAS Pro\14.0\dx_video_grovel_x64.log
   File:                C:\Users\Stevepunk\AppData\Local\VEGAS Pro\14.0\svfx_video_grovel_x64.log
   File:                C:\Users\Stevepunk\AppData\Local\VEGAS Pro\14.0\ocio_x64.log
   File:                C:\Users\Stevepunk\AppData\Local\VEGAS Pro\14.0\dx_grovel_x64.log
   File:                C:\Users\Stevepunk\AppData\Local\VEGAS Pro\14.0\gpu_video_x64.log
   File:                D:\Vegas Projects\factorio hardmode 1.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 14.0 (Build 161) 64-bit
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        
   Fault Address:       0x00000000BD7A71C0
   Fault Offset:        0x00000000BD7A71C0

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 14.0\vegas140.exe
   Process Version:     Version 14.0 (Build 161) 64-bit
   Process Description: VEGAS Pro

The constant crashing is very annoying. I have an intel 4ghz CPU, 32GB RAM (memtest came back ok), Gigabyte GTX 1070, and am rendering from/to a SSD (Intel M2 card). This is the only software I have problems with and it's getting really annoying. I'm really regretting purchasing the upgrade for $199.

I get random crashes during preview even at the lowest settings (though seems t0 happen more at higher preview quality).

But the most crashes come from rendering. Previously there were no rendering crashes but recently (today), it has crashed every single time. First at 16% then at 33% then at 37%. This is crazy. I have GPU rendering on and I know my card is up to the task so what's the problem?

Comments

set wrote on 10/20/2016, 4:13 AM
  1. Try Option>Preferences>Video tab> try change Dynamic RAM usage to 0
  2. also try turn off GPU acceleration of Video Processing.

 

Last changed by set on 10/20/2016, 4:13 AM, changed a total of 1 times.

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

Stevepunk wrote on 10/20/2016, 6:02 AM
I disabled GPU rendering and it has now rendered 2x in a row with no issues so the problem seems to be with the way Vegas uses the GPU. I have the latest drivers and everything. Win10 64bit. I had RAM usage for preview set to 16GB (when I started getting preview crashes though it didn't help much) and haven't changed it from there either so definitely a problem that Vegas has with GPUs. It seems I'm not the only one as the default answer on these boards and elsewhere seems to be "Disable GPU rendering". CPU rendering does seem to take 30% longer but I guess it's worth it until they fix the GPU crashes.
Wolfgang S. wrote on 10/20/2016, 6:10 AM

While it is true to we have to accept that you have an issue with the GTX 1070, I have here the situation that I do not see any issue with my R9 390X or my Quadro K4200. Typically I render with both GPU acceleration but also a dynamic ram review higher then 0.

To my opinion the development team will have to pay some attention to the GPU issue with some of the latest graphic cards. We know that this aspect of the software was not updated in the (I think) last two years or so. I hope they will do so, since as user you cannot do anything else beside changing the hardware. But it has to work with your hardware too.

Last changed by Wolfgang S. on 10/20/2016, 6:12 AM, changed a total of 1 times.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

set wrote on 10/20/2016, 6:11 AM

So only change Dynamic RAM usage to 0 didn't help? Need to totally turn off GPU usage?

 

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

Stevepunk wrote on 10/20/2016, 7:38 AM

So only change Dynamic RAM usage to 0 didn't help? Need to totally turn off GPU usage?

 

I haven't tried that yet actually. I tried turning off the GPU rendering before reading your post and it worked.
Next time I'll try setting Dynamic RAM to 0.

Also, maximium threads is set to 16, but when I look at the specs of my card I see:
Maximum number of threads per multiprocessor: 2048
Maximum number of threads per block: 1024

And when I look at my CPU I see:
4 Cores
8 Threads

So not really sure what to do with the thread setting either..

NickHope wrote on 10/20/2016, 9:07 AM

The findings in this post indicate that, in VP14 version 161, leaving dynamic RAM preview at 200MB is optimal and that 0 will siginificantly slow down your render: https://www.vegascreativesoftware.info/us/forum/dynamic-ram-allocation-in-vegas-14-impact-on-rendering--104102/ But obviously if it saves a crash then it might be worth considering.

So not really sure what to do with the thread setting either..

Probably just leave them. I haven't heard of anyone with any PC configuration improving their Vegas render speeds by setting those figures above the default.

george-sealy wrote on 10/20/2016, 10:00 PM

Trying to get over this rendering crash problem. Setting dynamic ram to 0 and GPU off greatly increases rendering time.  It is obnoxious.  I run VP13 and I have no issues whatsoever.  So how can this get worse?  It took 56 mins to render a simple 5 minute video.  And I have a new HP system with tons of memory and a fast processor!  This has to be fixed.  Usually my videos have 3-4 video tracks, and 2-3 additional audio tracks.  There are tons of effects and transitions.  I can't work with extremely long render times.  I never had these problems until this version of the software.  It is simply not ready for prime time and should not have been sold.