Vegas Pro 11 & K-Lite Codec Pack

[Mike Kujbida]

[George tsiripas] “But where I want to conclude is that can a Codec pack like K-lite provoke such a big issue on my computer?”

Yes it can. Search this forum and you’ll read some horror stories from users who installed the K-lite pack 🙁
Format your drive once again, install Vegas (and nothing else) and let us know if you still have problems and, if so, what they are.

“My pc is quite strong”

What are your specs (OS, RAM, # and size of hard drives, video card model, power supply rating)?

[George Tsiripas]

Can’t believe it. 🙁 And it used to work just fine. Thing is that I actually install the codec pack, I do not trigger any option for it with vegas, don’t know if it’s automatically done or how this thing works.

K-lite however has been extremely useful to me. It made WMP play every single format and I didn’t really need any other. Is there any other codec pack you have to suggest or generally codecs should be avoided?

Win7
3 GB Ram
Geforce 9800 GT 1GB
500 GB Hard disc free
400W Coolermaster

Thanks for the help.

[Mike Kujbida]

K-Lite can overwrite the good codecs that Vegas installs with inferior ones.
If you find that you need a codec to play a specific file, use a free tool like GSpot or MediaInfo to determine which one is needed and then install ONLY that codec from a reputable site.
https://www.headbands.com/gspot/
https://mediainfo.sourceforge.net/en

[George Tsiripas]

If I install a greater media player which by default will possibly play the files I want, do they come with codecs as well? Will the media player overwite again codecs?

[Mike Kujbida]

VLC and MediaPlayer Classic are great alternative players that will handle most files and, more importantly, not mess up anything on your computer.
https://www.videolan.org/vlc/
https://mpc-hc.sourceforge.net/

[George Tsiripas]

Okay, will try them. Thanks for your time.

[Nigel O’neill]

I have to admit (quite sheepishly) that when I first started using Vegas (SVP10) I installed the K-lite CODEC pack and did not have one issue. I was using it so I could import this AVI file that would not import or play in Vegas unless I installed K-lite. I then rendered out to the DVDA template. Having said that, when I rebuilt my computer (as part of my 3 yearly refresh), I did not reinstall K-lite.

For Vegas to blue screen your computer at ANY time, it has to be pretty serious. The only time I have ever had blue screen issues with Windows 7 was when I was using a USB video card on my backup system whilst the primary system was being upgraded. I deduced the problem was related to a video driver update, and once I rolled it back to the version that shipped with Windows 7, the blue screens stopped.

Unless you post some information about what the blue screen error is saying, it is going to be hard to work out what the actual problem is. Most likely you have unknowingly downloaded a suggested Windows 7 update which has caused this issue.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[George Tsiripas]

Hello sir,

As I said previously, K-lite was just working fine with Vegas for a long time, possibly an updated version of the codecs started to tuin things? I am not really sure.

I got the Blue screen error right after formating my PC so I don’t thing there’s something wrong with my windows7.

Last, I do not get the error at any time. I do get it only when rendering.

Here is the photo of the blue screen error i get.
https://i1261.photobucket.com/albums/ii594/tsiripas/DSC00226.jpg

Thanks for the help.

[Nigel O’neill]

George, that screen shot was actually very helpful. I don’t think Vegas is the culprit.

Stop 0xoA errors are generally caused by a hardware fault or something interfering with the driver.

One typical cause is memory. You could try reseating the memory (remove and reinsert) to see if that helps.

As computers get switched on and off, they heat and cool, and the expansion and contraction causes minor movements, enough for parts such as memory modules, to pop up. If you don’t feel comfortable with reseating your memory, you could just try firmly pressing it down. You may hear a small click or creak at the memory gets reseated into the slots.

Make sure you switch your PC off. If the blue screens continue, your memory could be faulty and in need of replacement. You can run a utility called memtest to check.

Some other forums suggest the fault could be caused by malware in the form of a rootkit that has infected one of your drivers, which can be removed. For more information about TDSKILLER, go to:

https://support.kaspersky.com/viruses/solutions?qid=208280684

[George Tsiripas]

Someone told me that it could be a memory issue. I used the windows memory diagnostic tool but no errors were detected. Do you believe the memtest can give a better result? In any case, I will follow what you suggested and will look deeper on this issue.

Thanks a lot for your time and help.