>Do you think your crashes are still caused by "Crash after about 3 minutes of editing "nvopencl64.dll" error"?
>That still is the topic subject where you still are complaining about the program.
>If not, than I advice you to make other forumposts with your questions and concerns.

I am not "complaining about the program" I am trying to come up with a solution. I am complaining about the absolute lack of support by the developer. Oh! and I did make another thread about Tech support not responding ....no one even bothered to come by and insult my intelligence or imply I was an idiot because of what I use this NLE for..dead silence..

"nvopencl64.dll" error" Yes. Do you think making a new thread is going to get me any closer to fixing this. what am I going to call it? "Random crashing no one can fix"

Maybe someone here will see the video log of the crash X3 and come up with something I am missing, because the actual people that sold me this are not going too.

Well, not really practical to change "topic subject" and start again now.

Progress has been made. The OP can now reproduce the issue fairly regularly (i.e. Vegas UI locks-up after series of zooms and mouse clicks) as can bee seen from the screen captures. Would be good for someone with Vegas 17 to try to reproduce the issue. (I am only using v16.))

@joseph-desaavedra

Next step would be process of elimination.

For example: https://www.vegascreativesoftware.info/us/forum/faq-troubleshooting-crashing-and-stability--104785/

Best not to take short cuts in this procedure, but if it were me, I would be looking for a software conflict with something running in the background, or to do with your input devices (mouse?) You know it has to be something fairly unique to your system or many others would be complaining about this.

You should also file a bug report with one of the screen captures attached.

Edit: I did see a recent post implicating 59.94 frame rate media. Can you try with regular 29.97 media?

>>your system or many others would be complaining about this.

Yeah I don't have much on the system that is unusual. Perhaps my NVME PCI ad on card is the only think I would consider...

>> 59.94 frame rate media. Can you try with regular 29.97 media?

I could do my next video in 20.97 next week, would be interesting

>>Next step would be process of elimination.

yeah, like in the old days when motherboards were not so forgiving as they are today

joe

One step to elimination could be to turn off Close media files when not the active application. It seem to be turned on.

Hmm, okay will try that.. thanks for taking the time to look at my session video..

Here is some advice about OBS settings: https://www.vegascreativesoftware.info/us/forum/faq-what-obs-studio-settings-work-well-with-vegas-pro--109925/

That really well and I posted the results.

I am complaining about the absolute lack of support by the developer.

@joseph-desaavedra WTF? You are in contact with 2 VEGAS developers and tons of personal messages without any support ticket (only with the desire to help you.). I am sorry to read this. 😔

>>@joseph-desaavedra WTF? You are in contact with 2 VEGAS developers and tons of personal messages >>without any support ticket (only with the desire to help you.). 😔

You and others here have been very helpful, and I thank you for that! and I mean it. You get nothing in return for your effort. I refer to the official support tickets I made and get no response. In the course I have learned a lot of about the platform in the process, even know it continues to crash' I like it even more for it's simplicity. I feel like I will beat it at some point with enough time and persistence.

Things will be trying on this weeks video

Going to go back through the basic trouble shoot guide again (hardware ect.)

Going to try using proxy's to see if it helps stabilizing while editing.

Going to screen capture my next session again and post..

Try some of the suggestions in this thread over the last few days.

I'm not giving up..sometimes get discouraged and frustrated.

Joe d

I am complaining about the absolute lack of support by the developer.

@joseph-desaavedra WTF? You are in contact with 2 VEGAS developers and tons of personal messages without any support ticket (only with the desire to help you.). I am sorry to read this. 😔

you must have pull someplace, got a response on my last ticket today. Maybe getting someplace. will update. I got another night to work on my real job.

@joseph-desaavedra

He's one of the developers.

I see...I did not have any idea.."Magix" "Pascal" should have been my first clue. will update.

@joseph-desaavedra
Dear user, stop all this nonsense and start first beginning to learn all the options of Vegas Pro to know what they are doing (or not) and if not necessary>>>> switch them off. (In 17 blue by default is switced on).

The Magix employees/VEGAS Team members can be recognized from this hexagon graphic attached to their avatar. Green means he/she is online.

@joseph-desaavedra
Dear user, stop all this nonsense and start first beginning to learn all the options of Vegas Pro to know what they are doing (or not) and if not necessary>>>> switch them off. (In 17 blue by default

There is no need to be nasty to me. It serves no purpose.

The Magix employees/VEGAS Team members can be recognized from this hexagon graphic attached to their avatar. Green means he/she is online.

thanks. I live and learn.

test #1

Dynamic RAM enable, file explorer window disabled, reinstalled as the hidden administrator feature in windows10 as per Technical support. It ran much longer and smoother but ultimately crashed and continues to crash. I have the screen grab. the last two videos are where it crashed. Any help is welcome, I feel like I am getting closer,I still have a video to finish and post. will leave dynamic RAM feature off as I continue to edit. I shot it in 60fps sorry. The next video I will try in 30fps as a second trouble shoot.

Extra Information
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\fileio_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\dx_video_grovel_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\svfx_video_grovel_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\ocio_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\dx_grovel_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\gpu_video_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\00000013.restored.veg
   File:                E:\culvers pretzel Burger\data\culvers pretzel Burger-02.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 321)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_650f8f5c2e0fc6d0\nvopencl64.dll
   Fault Address:       0x00007FFF9CFAF1A0
   Fault Offset:        0x00000000000DF1A0

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
   Process Version:     Version 17.0 (Build 321)
   Process Description: VEGAS Pro
   Process Image Date:  2019-09-18 (Wed Sep 18) 23:59:10

https://www.dropbox.com/s/l19glhf9arbfjnx/2019-10-09-settings.mp4?dl=0
https://www.dropbox.com/s/ki60enj4vesn64c/crash4-001.mp4?dl=0
https://www.dropbox.com/s/n3nufl3bz608y3r/crash4-002.mp4?dl=0
https://www.dropbox.com/s/yhoc69so4hvypqi/crash4-003.mp4?dl=0
https://www.dropbox.com/s/q8u9bhktvkf1hzz/crash4-004.mp4?dl=0
https://www.dropbox.com/s/mp3qefgi9vpyk97/crash4-005.mp4?dl=0
https://www.dropbox.com/s/og1vxalowd7yir7/crash4-006.mp4?dl=0
https://www.dropbox.com/s/641iwsgy2nsnev6/crash4-007.mp4?dl=0

test #1

Dynamic RAM enable, file explorer window disabled, reinstalled as the hidden administrator feature in windows10 as per Technical support. It ran much longer and smoother but ultimately crashed and continues to crash. I have the screen grab. the last two videos are where it crashed. Any help is welcome, I feel like I am getting closer,I still have a video to finish and post. will leave dynamic RAM feature off as I continue to edit. I shot it in 60fps sorry. The next video I will try in 30fps as a second trouble shoot.

Extra Information
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\fileio_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\dx_video_grovel_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\svfx_video_grovel_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\ocio_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\dx_grovel_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\gpu_video_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\00000013.restored.veg
   File:                E:\culvers pretzel Burger\data\culvers pretzel Burger-02.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 321)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_650f8f5c2e0fc6d0\nvopencl64.dll
   Fault Address:       0x00007FFF9CFAF1A0
   Fault Offset:        0x00000000000DF1A0

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
   Process Version:     Version 17.0 (Build 321)
   Process Description: VEGAS Pro
   Process Image Date:  2019-09-18 (Wed Sep 18) 23:59:10

https://www.dropbox.com/s/l19glhf9arbfjnx/2019-10-09-settings.mp4?dl=0
https://www.dropbox.com/s/ki60enj4vesn64c/crash4-001.mp4?dl=0
https://www.dropbox.com/s/n3nufl3bz608y3r/crash4-002.mp4?dl=0
https://www.dropbox.com/s/yhoc69so4hvypqi/crash4-003.mp4?dl=0
https://www.dropbox.com/s/q8u9bhktvkf1hzz/crash4-004.mp4?dl=0
https://www.dropbox.com/s/mp3qefgi9vpyk97/crash4-005.mp4?dl=0
https://www.dropbox.com/s/og1vxalowd7yir7/crash4-006.mp4?dl=0
https://www.dropbox.com/s/641iwsgy2nsnev6/crash4-007.mp4?dl=0

Thanks for your screen captures, @joseph-desaavedra. We encountered problems with NVDEC (NVIDIA video decoder) when too many video streams are being decoded simultaneously. We are working on that.

thanks, hopefully there is a fix coming, in the start of the video I was using only two but when I added the third cam it started unraveling. Dynamic RAM on or off seems to make no difference. I really like that feature though. thanks for your time. Do you think proxy might help me out?

Well, as I said I was going to try a number of variations from the trouble shooting list and some things I read in the forum to try to stabilize VP17. Last night it crashed as I showed in the post above. This is what I did tonight.

1: With Dynamic RAM 0 (tried on and off last night and it crashed)

2: file explorer turned off like I did last night (and it crashed last night)

3: VP17 has been reinstalled from the hidden administrator account as per instructions from Tech support (and it crashed last night but seemed to take longer to do so) not it means anything.

4: I made proxy files before editing, it took well over an hour to do so. For the first time since getting VP17 I did not have a crash. Thought I had it beat.. Oh NO.. went to render and it hung at 40%. I have never had a render hang or any issue with render as long as I have been using VP any version.

5: I did only two primary video tracks in this as last night I had three.

right now it keeps sticking at 40% so I am going to see about removing the offending clip so I can get past it and get my video post.. I thought it was too good to be true, and it was..Oh well at least I am finally getting some different behavior from VP. This is only one video and does not mean that much but I can grasp at hope where ever I can get it.

joe d

Extra Information
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\fileio_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\dx_video_grovel_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\svfx_video_grovel_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\ocio_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\dx_grovel_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\gpu_video_x64.log
   File:                E:\The Makita 18V LXT hedge trimmer\data\makita-01.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 321)

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
   Process Version:     Version 17.0 (Build 321)
   Process Description: VEGAS Pro
   Process Image Date:  2019-09-18 (Wed Sep 18) 23:59:10

took the offending clip out and it renders now, could get be a corrupt clip who knows.Time will tell, can't judge off of one video, will proxy a few videos and see if it helps or at least till VP17 fixes this, it takes a long time to proxy all my primary video files before a render. Will update and of course welcome all suggestions.

Update:

I made my second video without a crash, I again made a proxy off all source files before edit and used all other settings including dynamic RAM preview enabled. No Crash!! This seems a good work around until developers straighten out problems with NVDEC (NVIDIA video decoder). It will be nice when it is fixed and I won't have to spend over an hour making proxy files before I can start the edit. But how nice it is not having to endure crash after crash on every edit when I am up against the clock getting my youtube video out.

Ans special thanks to MagixPascal for being patient and honest with me. (information rules) and some of the others that gave me good advice and resisted the urge to snipe at me when I was frustrated.

Joe