Vegas Pro 19 KernelBase.dll error while rendering


Catherine-Ravenscroft wrote on 9/19/2021, 11:01 AM

@RogerS The plugin used to read the MOV files was the Quicktime plugin in the deprecated filed tab of preferences, without this ticked, VEGAS wont even read the files:

The program used to make the gifs into MOVs was none other than VEGAS pro 19 itself, the render took a lot longer when they were still GIFS and I was able to render them individually in VEGAS pro 19 as .mov files, doing so made the render take a lot less time.

The render settings I used to do this:

fr0sty wrote on 9/19/2021, 11:15 AM

Try encoding those mov clips into apple prores instead. It's a better intermediate format to use, it decodes easier.

Last changed by fr0sty on 9/19/2021, 11:15 AM, changed a total of 1 times.



AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10


ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Catherine-Ravenscroft wrote on 9/19/2021, 11:41 AM

@fr0sty I'm happy to do that in future, but VEGAS still crashes when I render files without ANY of the GIFs, so doing this is unlikely to fix the root of the issue

andyrpsmith wrote on 9/19/2021, 2:17 PM

Keep going Catherine, you have two of the best forum members on your case with Fr0sty and Roger. I'm sure you will find a solution eventually. The grovel files are where Vegas reports the various stages it's going through during start up, for example it will go through you plugin folder and load the various FX plugins and tell you if it is successful or if it fails so this can be useful to know what errors it finds. at least you would know if every step has been successful with no errors found. Yes the files can be long but you only need to focus on any failures. BW Andy

RogerS wrote on 9/19/2021, 7:07 PM

Next test I suggest is a project identical to what you are using but substitute GIFs and the GIF video for anything else that doesn't use QTPlug and see if it renders. I think QuickTime is likely the problem here.

Not sure where the GIFs came from or why you use that format but for transparency PSD might be a better option and Vegas supports PSDs well. If you don't need transparency jpg works fine too.

If that isn't it, still need to establish what the difference is between projects that render and projects that fail.

Catherine-Ravenscroft wrote on 9/30/2021, 11:42 AM

Hi again all, its been a while but I thought I'd check back in and address a couple of things:

Firstly, to @RogerS the problem is not the gifs or Quicktime, I have tried rendering videos without the gifs or videos that use the QTPlug and they have failed as well. The issue isn't about the gifs, it's about Vegas crashing during very long renders. The gifs are irrelevant. Vegas seems to last throughout small 2-5min renders but seems to get a random % of the way through longer renders and just crashes with the following crash report:

I've looked through the Grovel files and only found one instance of something failing in the C:\Users\FiercePC\AppData\Local\VEGAS Pro\19.0\vegas_script_x64.log

Right at the bottom of the image here. This is the very top of the file.

Secondly, I'm shocked and appalled that it has taken the tech support team over a month and I STILL haven't had a response to my support ticket. I actually took the time to ring the sales team 3 times to find out what was going on and they assured me they'd get to it that day with no response. How there is no support line I can call is an absolute mystery to me...

I'm just so drained from chasing this issue. I'm being held up from my job because of trying to troubleshoot this error. I just want to be able to use VEGAS and for it to not waste HOURS of my time hoping it'll get through a render.

If anyone knows any potential way of fixing this crash please let me know. I'm absolutely desperate :(

RogerS wrote on 10/1/2021, 12:22 AM

What's the difference between a long and short render?

Is it hitting thermal limits (do you see the GHz speed drop below the base clock speed in task manager/performance?) I've had Vegas throw errors once that happens (though not crashing outright, just corrupt renders).

I see you are now in VP 19.381 which is good.

Maybe one of the VCS engineers will see this and have an idea.

VEGASDerek wrote on 10/1/2021, 6:18 AM

@Catherine-Ravenscroft 90% of the time, these KERNELBASE.DLL crashes are due to some UI/.Net issue. It would help us if you put some identification in the text field when sending the error report so we can more easily search for this crash in our database.

Catherine-Ravenscroft wrote on 10/3/2021, 7:41 AM

@VEGASDerek Thanks for the response, I've sent off this same crash report multiple times using the requirements asked (dating back to a month ago) and haven't had any response from it as of yet. I can send another one if needs be?

@RogerS Cheers for getting back to me. I haven't noticed (honestly it can take hours for the error to occur so waiting hours for the render to do it's thing while staring at task manager isn't really a realistic prospect for me) But I can imagine this could be happening. Do you have any suggestions on how I can prevent that from happening?

RogerS wrote on 10/3/2021, 8:00 AM

I'd try Derek's solution first and try to update any .net drivers.

For throttling, you could chop up the renders into pieces and reassemble later with other software.

I'd confirm overheating and power throttling is happening by opening task manager/performance when you render and come back after 20 or 30 min. and see what the CPU frequency is.

You can clean the fans. Set the system to run the fans as much as possible. A tool like HWINFO64 can give readouts of temperature sensors in real time. Beyond that, repaste the CPU. Put in a better cooling system. Use cable ties to keep cables out of the way of the fans and air intakes. Thermal management is a bit of an art, if that is an issue for your system. The better you control temperatures the faster the render will complete, but I can't say it will solve this crash.

Catherine-Ravenscroft wrote on 10/3/2021, 8:15 AM

@RogerS So I can confirm that during a render my GHZ speed (sits around 2.8 - 3.0GHZ during render) is below the Base speed (3.5GHZ)

I also have the latest .NET framework drivers installed (4.8) so that shouldn't be the problem.

I don't think overheating is the issue either, I've checked my temps and they're sat around what they usually are.

(Also I genuinely do appreciate your repeated responses. You've been more than helpful!)

vegas-pro-user wrote on 10/3/2021, 8:27 AM

for information only,
according to the Internet, the maximum operating temperature for the Athlon X4 845 is ca. 71,30 degrees celsius

RogerS wrote on 10/3/2021, 8:32 AM

If it's running under base clock I assume it is protecting itself from heat, but it's better to check. AMD Overdrive is a tool from AMD that reports thermal margins: The lower the thermal margin in degrees, the hotter it is running.

Hopefully Vegas staff can help you further with this issue.

Catherine-Ravenscroft wrote on 10/3/2021, 11:21 AM

I have checked the temps during rendering and it doesn't go above 50C averaging around 45c.

If any Vegas staff could help me out that would be incredible.

VEGASDerek wrote on 10/4/2021, 10:24 AM

One thing to's a shot in the dark at this to change an internal preference, "GPU acceleration for Window Presentation Foundation", to FALSE.

I can say that we have received the error reports you submitted, however crashes in the .Net layer are often difficult to diagnose and to this point we have not been able to recover any good information from the reports as to the cause of the problem.

Catherine-Ravenscroft wrote on 10/4/2021, 10:42 AM

@VEGASDerek Thanks for the clarification, I'll give that a go and keep my fingers crossed.


Is there any extra information I can give you to help diagnose it?

Catherine-Ravenscroft wrote on 10/7/2021, 1:20 PM

I have heard back from the support team (24 days later than advertised...) and was told simply to update to the latest build... A build that DIDNT EXIST when I submitted my ticket and a build that STILL throws out the same error... and they didn't give me any explanation onto what the error actually was so I can't go and self diagnose either to try new things...

I'm fuming, I'd be willing to PAY a member of VEGAS staff in order to get this fixed. I'm just tired of it all... Please if anyone is able to suggest anything I'd be incredibly grateful!

SirPurgatory wrote on 3/25/2022, 1:13 PM

i don't know how current the thing is, i usually do it when the program gives up encoding, select everything in vegas ctrl + c then ctrl + tab I open a new vegas and when I open ctrl + v so far so everything is decoded without error. however, I would be interested in why this works. 

Malte-Feistmann wrote on 8/5/2022, 4:20 PM

Solved for now !


Im somewhat happy and not that i have found a thread about a problem similar to mine, sadly even after trying these fixes i cant seem to render any of my Videos. Im getting similar crashes with the cause beeing the windows Kernel.dll At random time stamps of rendering a Video.

After doing some basic windows repair mesurements the crash got stable now, only taking about 4 minutes of rendering to pop up.

My computer does not crash while doing so, only Vegas does.

My hardwear does not fail, does not run hot or anything like it.

I have all the "right" drivers installed, yes my nvidia driver is the studio driver.

This comment is here to get the first attention if anyone is willing to help out, im happily providing you guys as much information about my system and so on if needed.

At the same time im warning you that i have tried almost everything you could think of in the last 7 days of trying ot fix this non stop.

With best regards.



Ps: Excuse my terrible spelling, english is not my first language :)

Malte-Feistmann wrote on 8/5/2022, 7:25 PM

After restarting windows not once but thrice after repearing it via console ( sfc /scannow ) i do not get anymore Kernel errors, another thing i found thanks to afterburner is that my paging file space (i believe thats what its called in english) went full as long as i let windows handle it automatically. Since it goes up to over 60 GB when im working on my big 4k 30 fps project... i have manually raised it to 90 GB now. The reason for this to happen lays in my 16 GB prob not beeing what vegas wants me to have :D hope this helps, see ya

Tomorrow i will know for sure... Rendering this Vid is gonna take half of the night...

Malte-Feistmann wrote on 8/6/2022, 2:09 AM

Success !!! I just found a completed Video.

For anyone wondering... those pagin file space went up to a maximum of 75 GB of which 68 came from Vegas Pro, absolutly insane ^^.

dape wrote on 8/6/2022, 9:59 AM

Nvidia GPUs have game ready and studio drivers, you want the latest studio driver,

Hey, i tried both studio and game drivers and there seem to be no difference in quality or speed of rendering for my rtx3080..

dape wrote on 8/6/2022, 10:01 AM

Apologies for bumping this but I could really do with some help. I've done a clean install of the latest NVIDIA studio drivers and it's still doing the issue.


Is there anything else I can do?

Few weeks ago i had the same error, same kernel error, same weird random range of encoding before crashing, i was almost certain there was a problem with latest windows updates, i have sent all error logs to vegas team but in the end i solved MY problem with encoding with Voukoder without problems instead of the native Magix..

Malte-Feistmann wrote on 8/8/2022, 10:54 AM

Have you looked at the pagin file space used by your computer during the rendering ? Windows normally handels it automatically but Vegas (at least for me) uses A LOT of pagin file space so that windows does not handle it properly thus creating kernel errors because of pagin file space overflow. I enlarged the pagin file space of windows manually in order to fight this. From then on i've had no problems.

Other thing that might help when you are having kernel errors is checking your windows

For that go into the cmd of windows with adming priviliges acitvated and put in: sfc /scannow


That wil automatically run a self diagnosis routine from windows.

Hope this may help you out.