Vegas Pro has stopped working

cbarg wrote on 4/11/2014, 2:56 AM
Error when rendering Mainconcept MPEG output.
Started happening on a regular basis today.
Anyone else seen this.

Get a popup, (sent the info to Sony), then Vegas ends.

Found a "getaround":
Break the timeline into smaller chunks during render by rendering a selection.

Copy of the info from the popup window:
Extra Information
File: C:\Users\cbarg\AppData\Local\Sony\Vegas Pro\12.0\dx_video_grovel_x64.log
File: C:\Users\cbarg\AppData\Local\Sony\Vegas Pro\12.0\svfx_video_grovel_x64.log
File: C:\Users\cbarg\AppData\Local\Sony\Vegas Pro\12.0\ocio_x64.log
File: C:\Users\cbarg\AppData\Local\Sony\Vegas Pro\12.0\dx_grovel_x64.log
File: C:\Users\cbarg\AppData\Local\Sony\Vegas Pro\12.0\vst_grovel.log
File: C:\Users\cbarg\AppData\Local\Sony\Vegas Pro\12.0\gpu_video_x64.log
File: C:\Users\cbarg\AppData\Local\Sony\Vegas Pro\12.0\00000002.restored.veg
File: V:\Taken\Jacob&Jesse.veg

Problem Description
Application Name: Vegas Pro
Application Version: Version 12.0 (Build 770) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Windows\system32\nvopencl.dll
Fault Address: 0x000007FEE206527C
Fault Offset: 0x00000000000B527C

Fault Process Details
Process Path: E:\AppsW7\Sony\vegas120.exe
Process Version: Version 12.0 (Build 770) 64-bit
Process Description: Vegas Pro
Process Image Date: 2013-11-20 (Wed Nov 20) 21:45:00

Comments

ushere wrote on 4/11/2014, 3:36 AM
have you got gpu rendering turned on?

if so, try turning it off.
Grazie wrote on 4/11/2014, 3:47 AM
If you turn it off and you get success, then this indicates an issue related to the GPU, but won't solve the issue. If you get success then consider your nVidia driver. The line in that error report:

Fault Module: C:\Windows\system32\nvopencl.dll

indicates this.

Grazie

ushere wrote on 4/11/2014, 4:44 AM
alternatively keep your fingers crossed that 13 has all gpu mess ironed out;-)

btw. grazie is perfectly right - it's a nvidia thing according to the bug report. either way, it shouldn't be happening....
cbarg wrote on 4/11/2014, 8:00 AM
Thanks, I'll try turning off the GPU.
This started happening after the last Windows Update ran.

Solved it. Thanks again.
Looks like Windows Update updated the Nvidia driver under the covers.
set wrote on 4/11/2014, 8:06 AM
This started happening after the last Windows Update ran.

That's the biggest problem, possibly one of the component didn't really work well... Don't auto-update, turn it off. I have stopped having Windows Updates too here.

You can restore your system back to condition just before updating procedure started.

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.

Grazie wrote on 4/11/2014, 10:04 AM
Could be that nVidia driver snuck under the fence. I've noticed THAT to happen! Check to see what date your nVidious Driver was installed. If it was the same date as your issues, then that's gotta be good for your attention.

G

Steve Mann wrote on 4/11/2014, 11:11 PM
"Unmanaged Exception" is always* a driver issue.

*(No one has demonstrated otherwise.)