Vegas 4b error message

Chessmaster wrote on 4/11/2003, 2:26 AM
Okay, here is the error message I get when upgrading from V4 to V4b, I have tried everything from just upgrading to deleting directories, I re-imaging my system back to the fully working orginal V4 install. I still get the same problem no matter how I try to install V4b.

When I click on any video type file, mpeg, avi, the following error comes up and shuts down the program. I have given two examples of the program error messages


Sonic Foundry Vegas 4.0
Version 4.0b (Build 174)
Exception 0xC000001D (illegal instruction) IP:0x52CED96
In Module 'MCMPGDEC.DLL' at Address 0x52C0000 + 0xED96
Thread: GUI ID=0xFFF3B86B Stack=0xE0B000-0xE10000
Registers:
EAX=000000ff CS=017f EIP=052ced96 EFLGS=00210287
EBX=000000ff SS=0187 ESP=00e0b854 EBP=06333a44
ECX=05343af0 DS=0187 ESI=06332fbc FS=1317
EDX=00000000 ES=0187 EDI=06333070 GS=1326
Bytes at CS:EIP:
052CED96: 0F 4C C2 88 04 0A 42 81 .L....B.
052CED9E: FA 7F 02 00 00 7E DB E8 .....~..
Stack Dump:
00E0B854: 00000000
00E0B858: 05352672 05350000 + 2672 (MPEGIN.DLL)
00E0B85C: 00E0B880 00D00000 + 10B880
00E0B860: 00000000
00E0B864: 0631C4BC 06260000 + BC4BC
00E0B868: BFF00000 BFEE5000 + 1B000
00E0B86C: 0631C4BC 06260000 + BC4BC
00E0B870: 05360A75 05350000 + 10A75 (MPEGIN.DLL)
00E0B874: 05361D80 05350000 + 11D80 (MPEGIN.DLL)
00E0B878: 00000000
00E0B87C: 00000000
00E0B880: FFFFFFFF
00E0B884: 05363184 05350000 + 13184 (MPEGIN.DLL)
00E0B888: 0631C4BC 06260000 + BC4BC
00E0B88C: 00000000
00E0B890: E2556B28
> 00E0B898: 053F5FFC 05350000 + A5FFC (MPEGIN.DLL)
> 00E0B89C: BFF92D08 BFF70000 + 22D08 (KERNEL32.DLL)
00E0B8A0: 0631C4BC 06260000 + BC4BC
> 00E0B8A4: 78028E00 78000000 + 28E00 (MSVCRT.DLL)
00E0B8A8: 645C3A64 637B0000 + E13A64
> 00E0B8C4: 63732067 636F0000 + 42067 (RNCO3260.DLL)
> 00E0B8D8: 66800079 66800000 + 79 (SHELL32.DLL)
> 00E0B8DC: 6680867C 66800000 + 867C (SHELL32.DLL)
> 00E0B8E0: 6680FDBC 66800000 + FDBC (SHELL32.DLL)
> 00E0B910: 00696E69 00400000 + 296E69 (VEGAS40.EXE)
- - -
00E0FFF0: 48F71326 48070000 + F01326
00E0FFF4: 830EEFEC 830CB000 + 23FEC
00E0FFF8: BFF89DD5 BFF70000 + 19DD5 (KERNEL32.DLL)
00E0FFFC: 00000000




Sonic Foundry Vegas 4.0
Version 4.0b (Build 174)
Exception 0xC000001D (illegal instruction) IP:0x566ED96
In Module 'MCMPGDEC.DLL' at Address 0x5660000 + 0xED96
Thread: GUI ID=0xFFF448FB Stack=0xE0B000-0xE10000
Registers:
EAX=000000ff CS=017f EIP=0566ed96 EFLGS=00210287
EBX=000000ff SS=0187 ESP=00e0b854 EBP=03436a98
ECX=056e3af0 DS=0187 ESI=03436010 FS=12a7
EDX=00000000 ES=0187 EDI=034360c4 GS=4ec6
Bytes at CS:EIP:
0566ED96: 0F 4C C2 88 04 0A 42 81 .L....B.
0566ED9E: FA 7F 02 00 00 7E DB E8 .....~..
Stack Dump:
00E0B854: 00000000
00E0B858: 056F2672 056F0000 + 2672 (MPEGIN.DLL)
00E0B85C: 00E0B880 00D00000 + 10B880
00E0B860: 00000000
00E0B864: 033F31A8 032D0000 + 1231A8
00E0B868: BFF00000 BFEE5000 + 1B000
00E0B86C: 033F31A8 032D0000 + 1231A8
00E0B870: 05700A75 056F0000 + 10A75 (MPEGIN.DLL)
00E0B874: 05701D80 056F0000 + 11D80 (MPEGIN.DLL)
00E0B878: 00000000
00E0B87C: 00000000
00E0B880: FFFFFFFF
00E0B884: 05703184 056F0000 + 13184 (MPEGIN.DLL)
00E0B888: 033F31A8 032D0000 + 1231A8
00E0B88C: 00000000
00E0B890: 00000000
> 00E0B898: 05795FFC 056F0000 + A5FFC (MPEGIN.DLL)
> 00E0B89C: BFF92D08 BFF70000 + 22D08 (KERNEL32.DLL)
00E0B8A0: 033F31A8 032D0000 + 1231A8
> 00E0B8A4: 78028E00 78000000 + 28E00 (MSVCRT.DLL)
00E0B8A8: 645C3A64 5E3B0000 + 6213A64
> 00E0B8E8: 00B96384 00AC0000 + D6384 (SFS4RW.DLL)
- - -
00E0FFF0: 58BF4EC6 48070000 + 10B84EC6
00E0FFF4: 8352AFEC 8350B000 + 1FFEC
00E0FFF8: BFF89DD5 BFF70000 + 19DD5 (KERNEL32.DLL)
00E0FFFC: 00000000



Comments

NukleoN wrote on 4/11/2003, 6:16 AM
VEGAS is BUGGY.

I am getting all kinds of exception errors when trying to work in Vegas 4 (not the B upgrade). It's by far the buggiest software I've ever used. Does anyone else have this problem?

My system is a dual PIII 1 Gigahertz, 1.6MB RAM, Super micro mobo (P6DGU), Intel chipset, Windows XP pro-SP 1. The audio is an M-Audio Delta 1010 with ASIO which works fine for Sonar and other apps.

Not sure what Vegas' problem is, but it's a crash monkey. Crashes about 5-6 times a session, sometimes more. I thought I fixed the problem but apparently not.

Looks like I'll have to switch to Premiere 6.5 unless something gets fixed quickly.

Sad, because I really really love the Vegas interface..but software that crashes this much is just a disaster.

Dan
matt24671 wrote on 4/11/2003, 8:32 AM
I used to have a very similar system, dual proc Pentium III with Supermicro motherboard, and ended up getting rid of it. The VIA chipset issues never were resolved. After switching to an Intel P4 system, all my problems were resolved.

So, it may not be Vegas that is your problem....
Bear wrote on 4/11/2003, 9:25 AM
I almost fell off my chair when I read your message. I have a hard time believing it is Vegas. I have used most everything and Vegas 4 is by far the most stable software I have ever used. I say with a lot of confidence that your hardware must be the problem it sure is not vegas 4, I am sure most anyone on this board would repeat this message. I would suggest yo take thw software to another machine and try it.
Paul_Holmes wrote on 4/11/2003, 9:32 AM
I have an Athlon 1800 that I put together. It's been so long and my computer has run so trouble-free that I forgot whether it's a VIA. Anyways, when I first put it together I had all kinds of problems until I went to the motherboard manufacturer's web site and downloaded the latest drivers.

Vegas is probably the least buggy software ever written. Never used a piece of software that was so trouble-free. So make sure you have the latest driver's for your motherboard.

Also, I've seen posts by Earl Foote about avoiding VIA like the plague!
sharonjax wrote on 4/23/2003, 1:24 AM
dang! i have the same problem as Chessmaster. problem is, even Vegas 3.0 is giving the same messages. this was NEVER a problem before. i even reinstalled windows XP but the problem is still the same. it's not the hardware, i believe because, like i said, things were alright before.

weird, but Quicktime movies load just fine. loading an MPG file is when the software shuts down.

Chessmaster, did you install another software recently? i am not 100% sure but maybe it has a conflict with the Power DVD sfotware player. i am still trying to determine the real solution but as of now, i'm baffled.

help tech support!!!
mikkie wrote on 4/23/2003, 6:35 AM
"MCMPGDEC.DLL" is the mainconcept mpeg stream decoder, & a version is shipped with several other prog. besides VV4b. Search your hard drives for this file name, rename everyone you find to MCMPGDEC.bak, & then install/use VV4b.

To further diagnose the problem, as something else will now likely not work, rename the 'MCMPGDEC.bak' files to MCMPGDEC.DLL one by one and see which one breaks VV4. When you find the culprit, try substituting the version that came with VV4, or don't use the mpeg compression with whatever program uses that particular file.

I'd lay odds that it's a version of this file in your system32 folder inside your windows xp installation folder, as winxp *Knows* about this file whenever it {XP} is running. If this is the case, try moving this file to the program folder for whatever app uses it.

There is also a chance that this is not the file at fault, that it is one of the other associated mainconcept mpeg files... I picked on this one because it was mentioned in your error message. It is possible that one of the other mainconcept files (probably also in your windows system32 folder) is causing the "MCMPGDEC.DLL" to malfunction. If renameing this file doesn't work, go here: C:\Program Files\Sonic Foundry\Shared Plug-Ins\File Formats\MCMPEG (assuming default install folder) and search your drive for any of the filenames in that folder, eliminating them as well by renameing one at a time.

Background: this is not at all uncommon as companies like Ligos and Mainconcept sell their codecs in different forms to several different companies. The file names remain the same, but the versions are not always compatible. If your winxp folder contains one of these incompatible files, then when Vegas asks for it winxp will try to load the file it finds first, the one inside the winxp install folder.

As a last resort (in the unlikely event that you still have problems), up above I mentioned install/use VV4b after renameing these files. Installing VV4b should set the winxp registry to try and use the mainconcept files that come with VV4b. In case it does not, and/or in case winxp still wants to use another version of these files to decode all mpeg files in winmedia player for example (I've seen both happen), then it's probably necessary to unregister/register some files manually. Note that this is in addition to the above steps, and that you will most likely have to remove at least one mainconcept file from the windows system32 folder regardless.

The easiest way to register & unregister files in winxp is to download a program just for that from the XTEQ site. It adds an item to the right click context menu, so right clicking on a file you can select register or unregister library. All the VV4b dlls in the shared plugin folder listed above should be registered. You want to unregister any files of the same name elsewhere. If you can narrow it down to just one file at one location, unregister that file, relocate it into the program folder for the app that uses it, then register it at this new location only if the other program fails to use it properly.

And of course if the other program that supplied the incompatible mainconcept file is unimportant, &/or you don't want to use it's mainconcept mpeg features, you can stop when you get VV4b working, skipping all steps to relocate whatever files etc.

luck
mike
Blackout wrote on 4/23/2003, 6:52 AM
um....whats the chance you ppl with the problems are overclocking eh?

have you opened up your pc and checked that the fans are all spinning ok and not clogged and full of dust? i had crashes constantly with my Via until i found that on some bootups, the Via chipset fan would not spin up, getting caught on the dust it had collected.

Also with vias you need to re-install the 4-in-1 drivers every few months or so...seems some programs you put on and off take some of the 4-in-1 key files with them. :/

Vegas is one of the most stable programs i have ever used...ditto. Its not the program im afraid.

Blackout-

mikkie wrote on 4/23/2003, 8:20 AM
FWIW...

I've encountered at least one instance myself, and seen it reported one or twice here in the forums I think, where the Vegas 4 install for whatever reason did not put in the registry settings that it should have in XP Pro SP1. So yeah, it's possible for the install to screw up & not be the prog.s fault. In this case, registry entries may or may not be involved.

I've also personally encountered problems with multiple versions of mpeg2 encoders installed, both Ligos and Mainconcept. There was a conflict between the ligos mpeg stuff Ulead apps installed and used versus the stuff SOFO used before they switched to mainconcept. There's also a conflict between the mainconcept stuff prem uses and that which ships with VV4. In my opinion, the problem is the way prem installs their mainconcept files in the system folder and registers it with windows xp pro.

And, part of the problem can be what windows recognizes and uses for decoding & playback of mpeg2 files. There are several DVD player and authoring programs out there, and each of these has it's own decoder, often enough mainconcept. If windows associates a particular version of mainconcept decoder software with mpeg2, and VV4b needs another, it can conflict. [open an mpeg2 file in wmplayer and check properties in wmplayer to see which decoder is in use].

Whether this has anything to do with Chessmaster's prob. I can only guess, but as the error message mentioned the mainconcept file, it's where I'd start.
sharonjax wrote on 4/25/2003, 11:23 PM
thanks for all the info, mikkie. i'll be trying out your suggestions this afternoon. btw, what does "FWIW" mean? =)
Grazie wrote on 4/26/2003, 1:58 AM
FWIW! FWIW = For What Its Worth!!

Grazie
mikkie wrote on 4/26/2003, 6:02 AM
FWIW -> my way of shuffling the toe of my boot in the sand, trying to humbly say: "but what do I know?..."

mike