Thanks Jerry but I should elaborate...I installed a video card/drivers that claimed to be designed for AMD processors. A day later I installed another card but wondering if some of those nasty remnants could be causing an issue.

I got the same crash after upgrading to v10.0e

is this a new bug?

I got the same crash after upgrading to v10.0e

If so, I sure hope it's as fun as the replaced media bug.... AAARRRRGH!!!!

New bug? Give me a break!

Why are people so quick to scream BUG when only one or two people have the problem? If it WERE a bug, then hundreds or more users would be experiencing the same problem.

MSVCR90.dll is loaded by any program install that uses the Microsoft Visual Services (VB, VC, VC++). If you do a search from the root of your system drive, you will find several copies. Some are in the AMD64 folder and more in the X86 folder. (There are 33 copies on my system in various application folders).

Do not fall for the MSVCR90.dll fix-it scams.

I would simply roll-back to a restore point before the last installation was run.

You can try to repair it by replacing the bad copy with one of the others on your PC. You can also just delete it and see what application crashed, then reinstall that application.

But, it's not a bug.

If it WERE a bug, then hundreds or more users would be experiencing the same problem.

Well that's not the case with the "replaced media" syndrome Steve but fortunately support has reported they are working on it.
Thanks for your reply though, I'll try your suggestions!

Steve said: "If it WERE a bug, then hundreds or more users would be experiencing the same problem."In addition to being unhelpful, that is not factually correct. A quick search both on this forum and on the Internet turned up quite a few instances of people reporting this problem. Here are some from just this forum:

Save as type: QuickTime7

VEGAS PRO 10c CRASHES AT STARTUP

How do I grab a full frame?

Render as MP3 Vegas Pro 10

Any Other Options?

9.0b is here ....

And here are some others, which may help shed more light on the subject, from other forums. I limited these mostly to editing forums, and mostly about Vegas, but there are quite a few similar reports for Adobe Premiere and also other applications:

Vegas 9.0 64-bit crash on "Render As"

Vegas 10 crashes

Vegas 10 crashes

I could keep on going for dozens of pages. Here is the Google result, and you can look at more links. In skimming through some of the information above, I found quite a few good suggestions of things to try.

Google Search Results

So, good luck and please post back here when you find a solution. It is quite clear that you are definitely not alone and that many other people have had similar problems, despite what was posted above.

I was referring to the small number of users with the MSVCR90.dll problem. I never said anything about the "replaced media" bug. It is a bug and does affect more than a small number of users. The problem with that one is that it isn't repeatable. If SCS can't duplicate the problem, they can't do much to fix it.

I was referring to the small number of users with the MSVCR90.dll problem.I guess you didn't read any of the links that I posted. They are ALL about the MSVCR90.dll problem, and it was this problem, and the fact that MANY users have reported it, that I was responding to.

So, I never said anything about the "replaced media bug, and neither did anyone else, except for one person who merely said "I sure hope it's as fun as the replaced media bug.... AAARRRRGH!!!!"

The MSVCR90.DLL problem is quite real and apparently widespread. It is probably not a bug directly in Vegas, but it certainly has something to do with how Vegas interacts with the various multiple versions of the MSVCR90.DLL that exist on most computers.

John - almost all of those are "Unmanaged Exception", which is almost always a driver issue.

And just because Vegas was running code in the runtime DLL for Visual C doesn't mean that the DLL is at fault. It just means that the program was in the DLL when Windows crashed.

MSVCR90.dll is probably one of the most-often called dll's in all the Microsoft runtime libraries. It's no surprise that it shows up often in a Google search. You can't write a VC, VB or VC++ program that *doesn't* call subroutines in MSVCR90.dll. That would be analogous to writing a Vegas script without "using System;".

A genuine bug will effect more than just two or three users.

A genuine bug will effect more than just two or three users.Really? I didn't know that.

Did you know that Vegas Pro 10.0a did not read DV video created by the MainConcept DV encoder? Well, it didn't. I reported it, and SCS confirmed the bug. No one in this forum has ever mentioned it. I perhaps was the only person affected.

But, I guess since I was the only one affected, it couldn't possibly have been a bug, even though I have an email from SCS confirming it.

[edit]Oh yes, they did fix it.

Why are people so quick to scream BUG when only one or two people have the problem?

Why are you so prone to deny early bug reports in SCS forums ??? When I discussed about the gamma compensation error with PNG images sequences you did the same (bug acknowledged by support). It is that difficult to admit that some people have had many tries to reproduce and isolate an issue and then report it as a bug to make others aware of it or attempt to get a workaround ?

If it WERE a bug, then hundreds or more users would be experiencing the same problem.

Oh yes of course !!! And I was apparently the only one to notice the 6dB level increase with Elastique pro in V10 x64. (bug acknowledged by SCS, again...)

"But, I guess since I was the only one affected, it couldn't possibly have been a bug, even though I have an email from SCS confirming it."

Using the inverse logic doesn't work here. just because ONE person may report a possible bug in the forums doesn't automatically mean that it doesn't affect all users similarly. It just means that only one person reported it as a bug.

My point is that I tire of people who scream that "IT CAN'T BE MY PC, IT MUST BE A BUG IN VEGAS" when no one can repeat the problem.

"Oh yes of course !!! And I was apparently the only one to notice the 6dB level increase with Elastique pro in V10 x64. (bug acknowledged by SCS, again...)"

Again, as I told John, few reports does not automatically mean that the problem is not a bug. It only means that few people encounter the problem or posted about it on the forum. If you detailed the steps to replicate the problem, chances are pretty good that other users would in fact, replicate the problem. As SCS likely did.

However, in John's list of places on the forum where MSVCR90.dll is implicated, most of them are preceded with the Windows error: "Unmanaged Exception", which is almost always a driver problem (or a bad memory location reserved by the driver). Just because the PC happened to be running a program, Vegas, that was calling a function in a very common DLL (which in turn was probably trying to do something with a driver) when the Unmanaged Exception occurred does not point to a problem in the calling program or process. It simply indicates that "This is what was going on when Windows crashed".

i've just had a series of crashes trying to render to QuickTime and MSVCR90.dll was listed as the problem in Details.

running 10e... going back to 10a for now.

note: it didn't crash if the file was short (90 seconds or less), but whenever i tried a longer one ( 2 mins and up), i got the crash reqardless of what type of file i was rendering, or which drive i rendered to.