![]() |
Vegas Exception Error 0x7c90eddc
I was editing a project on Vegas 6d and got two error boxes saying "An error occurred during the current operation. An exception has occurred. View details." I click on details and there are none. Then the program closes and another error box comes up, saying:
"The exception unknown software exception (0xc00000fd) occurred in the application at location 0x7c90eddc. Click OK to terminate the program." I've tried moving the project file to a different directory and renaming it, which seemed to work once. I searched on google for any info on this error but could only find one thread suggesting it was an old Vegas5 glitch that was never fixed. Has anyone encountered this before? Does anyone know how to fix it? The problem just went away randomly for a while... and I saved the project multiple times under different names without errors, but then it came back, and all previous versions have the error. I have 3.25GB of RAM, WinXP with all the updates, P4 3.6 Ghz, I really don't think it's a problem with my system specs. Any ideas? |
Please does anyone know anything about this error? I just formatted my computer, and I can't get rid of the problem. I've tried Sony tech support, but they haven't got back to me.
|
I had this a while back
At the time I was working in 5 I believe, so I upgraded to 6 or a newer 5 version. But from D I think we are at 7 right? I wish I could be more helpful in this case.
|
Just upgrading fixed the problem? Well, thanks for posting. I really hope 7 fixes the problem whenever it comes out. I'm editing a feature film and starting over isn't really an option.
|
Will,
I've had errors in the past, one that I have well documented somewhere on this board. But the latest error I had was something, a process running in the background. I had another that was in the veg file itself, which Sony and I determined had something to do with the pathway of a specific part of the project through my computer's pagefile. I fixed that by rendering it, the same project, on a different computer. I would say that if you are getting the same error at the same point of action, i.e. same time frame in the render, or same time during the edit, then it might be file specific. If this error happens at random points, then it might be hardware related, or a background process. Just my 2cents. |
Thanks Steven. Could I ask, what process caused the problem? Were you using XP? The error seems random... sometimes, the project will load a certain way, sometimes, not at all, before the error even went away a couple times. I just tried using Win2000 instead of XP, and the same error happens... 2000 did give me some details...
Sony Vegas 6.0 Version 6.0d (Build 210) Exception 0xC0000005 (access violation) READ:0xC IP:0x572039 In Module 'vegas60.exe' at Address 0x400000 + 0x172039 Thread: GUI ID=0x1D8 Stack=0x12E000-0x130000 Registers: EAX=00000000 CS=001b EIP=00572039 EFLGS=00010297 EBX=05cadb01 SS=0023 ESP=0012efd0 EBP=0012f280 ECX=1e0b26a8 DS=0023 ESI=00000000 FS=003b EDX=0012efe4 ES=0023 EDI=00000000 GS=0000 Bytes at CS:EIP and the list of details go on, but I don't care to type anymore, and they're useless anyway. |
I wish I knew, I got so annoyed that I just started killing stuff, but If I had to guess, I think it would have either been my APC back up software, Itunes, or my Gigabyte Motherboard tuning software.
As for that one that kept crashing on render, which I could render on another machine, I still think that that was a page file issue. Either way, it's not my box itself, which is more than capable. |
0xC0000005 is a different error than you mentioned in the first post. That is a "memory access" error. If you can get the project loaded, can you copy and paste to a NEW project (i.e. Vegas opened twice), do a Save-As, and then see if the new one works?
Quote:
|
I would've copy/pasted all of the details, but for some reason, it wouldn't let me. I did finally "solve" the problem though... I unplugged my fourth hard drive... I shot HD and have four hard drives in my computer, three of which are being referenced in the project... apparently, it doesn't like the fourth one since unhooking it and not being able to find those files got rid of the error. I'm just wondering now if Vegas has some limit on the number of hard drives it can reference... which I may try unhooking the 3rd, leaving the 4th plugged in, and seeing if I still get errors (I bet I will). At least, I don't have to start from scratch... very few files in the project are from the fourth.
Oh, I forgot to say I did try copying and pasting from the problem project to a fresh one, but it wouldn't allow it... not enough memory or something. I do have huge HD files. I also tried breaking my large project into two smaller ones and still got the error. |
Were you editing the M2T files? If yes, people have reported problems after having so many m2t files on the timeline. Unfortunately the number seems to vary. The typical solution is to edit proxies instead.
Or... it could have possibly been a bad source file that was on that drive? |
I'm editing Raylight avi files made from HVX200's MXF files. I'm going to try a different hard drive with the same files and see if I get the error.
What are proxies? |
I tried a different hard drive with the same files and still got the error. It appears I can only edit with files from two of my hard drives.
Can someone please explain proxies? |
Can someone explain proxies?
I tried Vegas 7a... I'm still getting this random error. Anyone know when Vegas will add support for mxf files or Raylight avi ones so the program won't error out? Does it have some limit on the number of hard drives it can access without messing up? I used to love Vegas, but this thing obviously has some major issues with HD files. |
Proxy: a person who represents another person.
or in this case: a clip that represents another clip You would take your original clips and render them to something like DV-AVI. Then you do all your editing with the DV-AVI files. Once all editing is finished, you then replace the DV-AVI files with the ORIGINAL files and do the final render. The DV-AVI files, in this case, is the proxy. |
How do you replace all the files without having to literally re-edit? Just name the proxy files the same as the original, keep them in separate areas, and then when you're done, switch them around?
Why would the file not error out when doing the final render? If the problem is the program dealing with all those HD files, how would it not be avoided in the end? This sounds like a nightmare to go through and render every one of my HD files to a DV proxy... although it might be better than my current nightmare of random red error. I just don't understand this and why Sony makes no mention of this error on their website. |
You could right-click the clip in the Project Media, choose "Replace", and then pick the other file. OR you could use Gearshift by VASST to do the switching for you.
|
Thanks Ed. Is there an easy way to convert all your files into proxies? I made AVI files with Raylight.
|
Will, check out the Gearshift product on the VASST website. It was designed to create the proxies and switch back to the original files for you.
|
I looked at Gearshift and the VASST website, but even if I used proxies to edit the whole movie when I switch back to my HD files for the final render, wouldn't I still get this error? I don't think proxies will help, and Raylight actually has an option of setting the AVI files to lower quality, but that didn't help.
Have other people gone to proxies because of this error or am I the only one to experience this problem? I mean has anyone not used proxies and gotten a different kind of error? I know other people must have encountered this at some point. Has anyone tried buying those Sony support plans? Just curious how they work or if they work. |
Has anyone else gotten this exception error? Anyone know anything about it (when or why it occurs)?
Has switching to proxies helped anyone get rid of this error? |
I contacted Sony. This is what they told me to do:
That particular error message might indicate a corrupt installation. Therefore, I'm going to suggest that you un-install all of your Sony Media Software and older Sonic Foundry software. Do this by going to Start > Control Panel > Add or Remove Programs. Once un-installed, delete the following folders: C:\Program Files\Sonic Foundry C:\Program Files\Sonic Foundry Setup C:\Program Files\Sony (Do not delete this entire folder if you have other Sony applications installed such as Sonic Stage, Everquest, Star Wars Galaxies, etc. If that is the case then only delete the folder for the Sony Media Software application you are using as well as the Shared Plug-Ins folder.) C:\Program Files\Sony Setup Once un-installed, click over to your Windows Registry Editor (Start -> Run -> regedt32). WARNING: The Registry is a very sensitive area to work in. If you are not comfortable with advanced configuration and system changes, ask an administrator to help you with this. Once in there, delete the following registry entries: HKEY_CURRENT_USER\Software\Sonic Foundry HKEY_CURRENT_USER\Software\Sony Media Software HKEY_LOCAL_MACHINE\SOFTWARE\Sonic Foundry HKEY_LOCAL_MACHINE\SOFTWARE\Sony Media Software Next, disable everything under Startup in MSCONFIG. Do this by going to Start>Run 'MSCONFIG' - Startup Tab, Click Disable All, Click Apply, Click Close, Click Restart Now. After the computer is restarted, press Ctrl+Alt+Del at the same time and you will see a list of the programs currently running (some users will have to hit the "Task Manager" button). Move over to the Processes Tab and click the "Image Name" heading at the top left of this window to view these items in alphabetical order. Close everything showing on that list except for the items listed below. To end a process, highlight it and click the End Process button at the bottom of the window. End every process except for: alg.exe ccmexec.exe csrss.exe explorer.exe lsass.exe MsPMSPSv.exe services.exe smss.exe spoolsv.exe svchost.exe (there may be more than one of these, you can leave them all running) System Idle Process System taskmgr.exe winlogon.exe wmiprvse.exe You may have other Users logged into the system and displayed on this list, but make sure you log them off and close down their processes as well. This is a good opportunity to remind you to temporarily disable your system's anti-virus software. If running in the background while installing the application, it can be difficult for the system to update registry values needed to help the program run smooth. I did everything just like they said, and bingo, still got the error. Updating my Raylight codec to 1.05d seemed to help temporarily as I was able to open the project without error and keep it open indefinitely without error until about 3 weeks later when I decided I better not keep my computer on 24/7 for that long. After a reboot, the error was back. The codec now has another update out 2.01, and I'm going to try it. It even allows you to create separate self-contained AVIs, which I may try to see if that gets rid of the error. So far no luck though. Has anyone made a feature-length film with the HVX200 and used Raylight? |
Okay, get this. I bought a brand new computer. The Sony rep seemed to think it was a system-level issue. So $700 later brand new machine. And I'm not joking. I put my video drives in it since I need them to access all my HD files. Put Vegas 7 on... load the project file. It builds all the audio peaks (about 1,837), and finishes loading just fine. No error. I can save multiple copies of the project, edit, render, do whatever. After I close the project just once and try to reopen it or any of the saved copies, I get that first error box saying, "An error occurred during the current operation. An exception has occurred." Of course, no details. The program closes. I no longer get the error afterwards... the memory access error or whatever (ie NO "The exception unknown software exception (0xc00000fd) occurred in the application at location 0x7c90eddc"). All I get is that error box in Vegas.
I'm trying to keep this error and its status documented, because I'm hoping someout out there can help, and I'm hoping if I ever find a solution, other people who encounter this error can get help since obviously Sony pretends it doesn't exist (why else would it be missing from their knowledgebase?). |
If I could ask Steven Davis another question about the pagefile error he got.... what is a pagefile? I think my problem might be similar to yours... was Sony able to fix the pagefile issue (I guess not since you had to render it on a different machine)? My project has files on three different drives, and something incorrect is happening with how it references those drives. It's gotta be in the project itself I think... when I put it on a new machine with my video hard drives, it worked fine for a little bit... then I think I moved around a couple files, and the error came back. But then I tried restoring that computer's C drive to factory defaults and starting over, but the error was still there. Could my video hard drives have pagefiles that are causing the issue? Maybe if I got one massive hard drive... it'd have to be like a terabyte though...
Steven, you said you rendered the same project on a different computer, fixing the pagefile issue... so could you then open that project on the previous computer without an error? Rendering just somehow corrected the issue? |
Quote:
(In storage, a pagefile is a reserved portion of a hard disk that is used as an extension of random access memory (RAM) for data in RAM that hasn't been used recently. A pagefile can be read from the hard disk as one contiguous chunk of data and thus faster than re-reading data from many different original locations. Windows NT administrators or users can reset the system-provided default size value of the pagefile to meet their particular needs. Courtesy of SearchSMB.com) Using that line of thought, the pagefile issue was the only thing I could think of, since I was able to render this particular project on another machine, from the same source drive (s) from across my network. I was never able to get that particular project to render on the machine I created it on. The rest of that wedding did fine, but that one project had issues. If I was guessing, and guessing only, from what you describe, it sounds like the project itself. On thing you could try, if you really want to know what the problem is. You could recreate each project on a different drive, machine etc, do it piece by piece and see where you have problems. I hope this helps. |
Thanks for the reply Steven.
I was finally able to "solve" my problem... I broke my one 60min project file down into six 10min separate project files. All the individual project files always open without the error... just the massive one has problems. I tried making huge pagefiles on my drives... nothing helped, and my computer already has 4GB of ram. Vegas has serious issues, and if I hadn't already done so much work in it (and if I didn't like its setup so much), I'd be switching to Avid or FCP on a Mac, because this is ridiculous. Sony really needs to get the bugs worked out... I tried absolutely everything... buying a different computer, putting all my files on one 750gb internal drive, etc. and it seems pretty obvious the problem is clearly with the software. Next film I'm definitely not using Vegas. |
Will,
I have always maintained that Vegas should have better error reporting. Giving me an error which even the guys at Sony doesn't understand is ridiculous. I'm glad you were able to get the project finished. You should send sony this thread. |
Thanks Steven. I agree. Better error reporting would help a lot. I'd send Sony the thread if I thought it'd make a difference, but I did update their tech support on the situation, and I'm sure they did nothing about it.
|
I got the error again in one of my 10min segment files. But I was able to get rid of it by deleting some media bins and the files in them. Since I've reduced my project down to 10min segments, I no longer need all my media bins or all the files they link to (at least not in each segment).
So basically, Vegas = chock full of bugs. And never again am I using this ridiculous software. I notified Sony of the problem, and I'm sure they'll do nothing about it. |
Will, I had the same problem until about ten minutes ago. I have a 90 minute project and was resorting to breaking it down into mini-projects, some of which worked and some didn't. After a suggestion by Ed Troxel, I moved all of the media onto a separate hard drive...same problem. On a whim, I put my avi files in one folder on hard drive "a", my m2t files in another folder on hard drive "b", and seven mp3 files (soundtrack) into a separate folder on hard drive "c". I then opened up vegas and it couldn't find the files. It first asked for my m2t files...I directed it to that drive and didn't have a problem. Next it asked for my mp3 files...I directed it to that drive and Vegas disappeared. When I relaunched vegas, I chose to ignore the 7 mp3 files and open the other files...presto. Not sure which of the 7 mp3's was the problem yet, but it appears that it was one that an indie artist directed me to download from music.download.com. I'll let you know when I isolate it.
Hope that helps. |
Now you're getting somewhere. Is your mp3 plugin registered?
|
That's interesting. My error hasn't come back since I broke it down into 10min segments and got rid of extraneous media bins/files. Vegas seems to have some limit on the number of files you can have imported into it regardless of whether or not they're on the timeline.
|
“The exception unknown software exception (0xc00000fd) occurred in the application at location 0x7c90 eddc.”
I got the same error in Vegas 6.0 a few days ago when I opened up my program the day after I had transferred a high number of clips. My project has about 6 hours of transferred XL-1S DV footage in media bins, even though I’d only edited about a half hour. Anyway, I got the error the one day I accidentally selected to search for a missing file that I had intentionally deleted earlier rather than ignore all missing files, which I usually did. This may have had something to do with it. The error prevented me from opening my program and forced me to close Vegas. This error has occurred multiple times after I have restarted, un-plugged, and turned off my computer. I tried suggestions from Sony’s online knowledgebase and all of them failed. I tried un-installing and re-installing the software multiple times, opening a back-up file, renaming the file, disabling media manager, etc. My computer has plenty of space, so that shouldn't be the problem. I’m going to call Sony tomorrow. Hopefully, they won't be as worthless to me as they were in the past when I had problems with their software on an Alienware Aurora. By the way, that was the most worthless, money-wasting ineffective piece of trash excuse for an editing computer I ever got. It has also been the focus of the most intense, concentrated levels of hatred I have ever felt toward an object in my life. I recommend you stay away from their stuff or are at least cautious. Anyway, if I learn anything useful, I’ll let you know. I’m glad I found this thread; I’ll keep it in mind and for reference when I talk to Sony. |
Will,
Reading the thread you started sure did help me out. Thank you. I ended up pretty much solving my problem. What I did was save my project to a USB card. Then, I opened the project on another computer. None of my project files were on the computer so all I had were blank timeline markers and media labels. So, I deleted all the files in my project that weren’t on the timeline. Then, I opened up my project on my main editing computer (a Sony VGC-RC310G) and it opened up with no error. All my edited work was intact. Now all I have to do is re-import video files from my hard drive into Vegas that I want to use. I think you’re right. Vegas definitely seems to have a limit for heavy file loads. I ended up not calling Sony. I found out I’d probably have to pay for support anyway if I did call. But, I did send an e-mail to Sony with a link to this thread before I solved the problem. Maybe they’ll reconsider addressing this problem better, though I doubt it. Anyway, thanks again. |
Thanks. I'm glad it helped. That's why I kept this thread going, because this problem was incredibly frustrating for me, and sadly, Sony seems incapable of helping or solving this issue. Good luck with your project.
|
After I reimported a bunch of my media files into Vegas, I got the error message again. So, I removed all the files I wasn't working on at the moment and then Vegas worked fine again. It looks like I will have to shift media in and out of Vegas as I work in order to be able to finish my project. Less convenient, but at least I can work on it again. I also finally got a response from Sony, which I posted below. I didn't mess with this because I have already un-installed and re-installed the software several times. It basically looks like roughly the same sort of message Will got. I doubt doing this would help much.
"Thank you for contacting Sony Media Software Support. I suggest that you please do a clean reinstallation of the application following the instructions below. Registry warning: Note: it is always a good idea to backup your registry before making any changes to it. There is always the possibility of changing or deleting a critical setting causing you to have to reinstall the whole operating system. It's much better to be safe than sorry! How To Backup, Edit, and Restore the Registry in Windows XP http://support.microsoft.com/default.aspx?kbid=322756 How To Backup, Edit, and Restore the Registry in Windows 2000 http://support.microsoft.com/default...b;en-us;322755 How To Backup, Edit, and Restore the Registry in Windows 95, Windows 98, and Windows Me http://support.microsoft.com/default.aspx?kbid=322754 Uninstall warning: Note: Uninstalling Sony Media Software will wipe out/delete all user settings and preferences that were initially saved/applied to the program. To ensure that you get a proper installation of your software onto your system, we would ask that you un-install all of your Sony Media Software and older Sonic Foundry software. Do this from the Windows Control Panel's Add/Remove Programs Menu. Note: Uninstalling Sony Media Software will wipe out/delete all user settings and preferences that were initially saved/applied to the program. If you need to backup audio presets that you had made then we would recommend using our Preset Manager utility, which you can find at http://ww.sonymediasoftware.com/down...p2.asp?DID=469. For information about backing up custom Video FX and transition presets please see the following article: Title: How to recreate your custom presets on Video FX and transitions URL: http://www.custcenter.com/cgi-bin/so...ted=1020315600 Once un-installed, delete the following folders: C:\Program Files\Vegas 6.0 C:\Program Files\Vegas 6.0 Setup C:\Program Files\Sony (Do not delete this entire folder if you have other Sony applications installed such as Sonic Stage, Everquest, Star Wars Galaxies, etc. If that is the case then only delete the folder for the Sony Media Software application you are using as well as the Shared Plug-Ins folder.) C:\Program Files\Sony Setup Once un-installed, click over to your Windows Registry Editor (Start -> Run -> regedt32). WARNING: The Registry is a very sensitive area to work in. If you are not comfortable with advanced configuration and system changes, ask an administrator to help you with this. Once in there, delete the following registry entries: HKEY_CURRENT_USER\Software\Vegas 6.0 HKEY_CURRENT_USER\Software\Sony Media Software HKEY_LOCAL_MACHINE\SOFTWARE\Vegas 6.0 HKEY_LOCAL_MACHINE\SOFTWARE\Sony Media Software After removing all of the previous items, just download and re-install from the latest updated versions of software from this link - http://mediasoftware.sonypictures.co...p1.asp?CatID=2. These files will be the latest full installers for our software." |
Yeah, I'm sure that wouldn't help. That is just their token response. Reinstall. Oh, that didn't work? Update your drivers. Oh, no good? Uhm, it's your system. Buy a new computer. May I suggest a Sony.
That's a little harsh, but their tech support is pretty friggin worthless. |
The USB solution posted by Tristan Howard worked for me. I had slightly less than two hours of video on the timeline (probably about 5 hrs captured), the first hour of which was completely edited, so I decided to back that section up to tape. This worked, but the project would not open the next day. (When I selected ignore all missing files and clicked o.k., Vegas 7b crashed) I transferred the project file to another computer and hit the delete all unused media button and then put that version onto the USB drive and transferred it back to my editing computer, now it only had to load the material that was used and not the entire project. It opened the project with no problems and I have edited for two days without further problems.
|
This is the closest I can find to the problem I've got. I started a new project with just a long MP3 file on the timeline (about 2.5 hrs) I used the split function to divide it into a number of clips. When I got to about 20 clips it suddenly stopped playing properly (play but no sound). I closed the project and tried to re-open but it now just says the plugin is not registered. Now every time I try to open a project that has any mp3 file in it I get this message. It offers me the option to register the plugin but when I click it I get an exception error and Vegas 6d just closes. I'm really not very comfortable playing around with the registry (don't even know how) so if there's a simple workaround I'd be grateful.
Thanks |
All times are GMT -6. The time now is 06:50 PM. |
DV Info Net -- Real Names, Real People, Real Info!
1998-2025 The Digital Video Information Network