Undo Buffer Error!?!?!?

Grazie wrote on 1/12/2005, 12:56 AM
OMG!

Just got a :

"An Error occurred while processing the Undo Buffer. You should save your work immeadiately using a new project filename and restart Vegas

The reason for this error could not be detrermined"

HELP! ! ! !

Comments

Liam_Vegas wrote on 1/12/2005, 1:14 AM
Can't help much... but I guess you haven't been able to do what is suggests?

That sucks.... What a load of smelly poo.
Grazie wrote on 1/12/2005, 1:32 AM
Liam . .thanks . .
Just read the stuff her
5ac
e on the Search .. I did use a one single JPG, thought that would be a culprit. Removed it .. still hasn't cured it.

Here is the full error execption report ..

Sony Vegas 5.0
Version 5.0b (Build 160)
Exception 0xC0000005 (access violation) READ:0x40 IP:0x4AB009
In Module 'vegas50.exe' at Address 0x400000 + 0xAB009
Thread: GUI ID=0x25C Stack=0x12F000-0x130000
Registers:
EAX=00000001 CS=001b EIP=004ab009 EFLGS=00010202
EBX=06e87a4f SS=0023 ESP=0012fb70 EBP=00000000
ECX=00000000 DS=0023 ESI=035e86d0 FS=003b
EDX=06e87a4f ES=0023 EDI=00000000 GS=0000
Bytes at CS:EIP:
004AB009: 8B 47 40 8B 4F 44 89 44 .G@.OD.D
004AB011: 24 18 03 C3 89 44 24 10 ...D$.
Stack Dump:
0012FB70: 1D8BA4B8
0012FB74: 035E86D0 034C0000 + 1286D0
0012FB78: FFFFFFFF
0012FB7C: 00000000
0012FB80: 000004F9
0012FB84: 000002C3
0012FB88: 0012FC00 00030000 + FFC00
0012FB8C: 77FB4DA6 77F50000 + 64DA6 (ntdll.dll)
0012FB90: 0012FB98 00030000 + FFB98
0012FB94: 00000018
0012FB98: 014801C8 01450000 + 301C8
0012FB9C: 00000021
0012FBA0: 004AE898 00400000 + AE898 (vegas50.exe)
0012FBA4: 035E86D0 034C0000 + 1286D0
0012FBA8: 00000000
0012FBAC: 06E87A4F 069A0000 + 4E7A4F
> 0012FBCC: 004B4376 00400000 + B4376 (vegas50.exe)
0012FBD0: 035E86D0 034C0000 + 1286D0
0012FBD4: E95CD597
0012FBD8: FFFFFFFF
0012FBDC: 00000000
> 0012FBF4: 004B43C2 00400000 + B43C2 (vegas50.exe)
0012FBF8: 0000
587
0060
0012FBFC: 00000288
0012FC00: 000000EA
0012FC04: 00000000
> 0012FC14: 004B56B0 00400000 + B56B0 (vegas50.exe)
0012FC18: 035E86D0 034C0000 + 1286D0
0012FC1C: 00000000
0012FC20: 00000288
0012FC24: 000000EA
> 0012FC38: 004B23BF 00400000 + B23BF (vegas50.exe)
0012FC3C: 00000010
0012FC40: 00000020
0012FC44: 00000288
0012FC48: 000000EA
> 0012FC50: 77D446A8 77D40000 + 46A8 (USER32.dll)
> 0012FC54: 77D5806D 77D40000 + 1806D (USER32.dll)
> 0012FC5C: 00462056 00400000 + 62056 (vegas50.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 0072DE90 00400000 + 32DE90 (vegas50.exe)
0012FFFC: 00000000



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


I've NO idea what to do now .. . I'm in a mess!

Grazie .. .

. . ugghhh
Grazie wrote on 1/12/2005, 3:22 AM
I'm doing a Check Disc on F: - this is the drive with the caprtured footge. After speaking with my PC people I was able to discover - not conclusive yet - that Media taken from the D: drive does NOT relicate the error.

Hopefully Check Disc will discover an error on F: . .. still checking . .. . .still checking .. . .. .

Grazie
Grazie wrote on 1/12/2005, 3:51 AM
Did a Factory Default... CTRL+SHIFT on openning V5 .. seems to be holding ... waiting for the other shoe to drop ...

Grazie
Ron-Goodman wrote on 5/7/2020, 1:17 AM

I've experienced this bug on a regular basis since early Vegas versions... and I still have the problem frequently in Vegas 17.

michael-harrison wrote on 5/7/2020, 3:13 PM

I've had this happen a 1-2 times in the last few months. Just restarted and things seemed fine.

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia RTX 3060 Studio driver [most likely latest]
Resolution        3840 x 2160 x 60 hertz
Video Memory 12G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

MauRam wrote on 1/1/2024, 6:58 PM

Vegas 21, same error. Seems there is something not been figured out in almost 20 years. Jumping out of this as soon my subscription ends. It's a bugs bag.

Grazie wrote on 1/1/2024, 11:50 PM

@MauRam - Using VP21 and its solid as a rock. Using an 11 hour long stress test Veg and it’s very fast and stable.

MauRam wrote on 1/2/2024, 12:16 AM

Not here, i9g12, 32GB GPU, All storage are Samsung NVMe m.2 PROs, 128GB RAM and it gets stuck at the point I need to reboot for a 3 mins edit with 4 lanes, can't drop a New FX Titler cause it blows . Kinda frustrating. Lucky you.

Grazie wrote on 1/2/2024, 12:18 AM

Wow! This thread is almost 20 years old. A lot of water under the Bridge. Several PC Rigs later and my knowledge base about Media and Systems has majorly improved.

@MauRam is on subscription, so I don’t seen this User coming back anytime soon. Also, the name that came through as an Alert wasn't this one, so …..

TAXI!

Grazie wrote on 1/2/2024, 12:21 AM

@MauRam - Ah, you did respond! Yes, I’m lucky and have stayed with the program pushing and pushing. But if you’ve made up your mind, to move on, I wish you well 😉.

Reyfox wrote on 1/2/2024, 8:29 AM

First time I've seen anyone else report this error in how long?

 

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.3.2

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

MauRam wrote on 1/2/2024, 5:10 PM

@MauRam - Ah, you did respond! Yes, I’m lucky and have stayed with the program pushing and pushing. But if you’ve made up your mind, to move on, I wish you well 😉.

I've seen DaVinci managing multiple editing lanes and NEVER got stuck. The other usual suspects Nah!, they are the reason I got into Vegas since the Sony era. I keep updating until v17 when many plugin developers moved to OpenFX (NewBlue and Boris) so I stopped buying it.

Back on version 20, I learned OpenFX was finally in and got back to Vegas, then: issues, support, logs, back and forward etc.. then v21 landed with multiple fixes as mentioned in the promo, my options 1. purchase again the software. 2. follow the flow into the subscription world, so I paid one year cause the media and text to speech goodies.

Experiencing an issue which it first post was back to 2005 and seeing it's not resolved on 2024 gives you "A bad feeling about this".

Productions are already past due almost every time, and every minute counts. If you pay for a PRO product, it should work as a PRO product, It will have bugs yes ...but this one ... should have the longevity award.

Grazie wrote on 1/3/2024, 12:06 AM

If you pay for a PRO product, it should work as a PRO product, It will have bugs yes ...but this one ... should have the longevity award.
 

@MauRam - I hear you and so does the rest of the Forum so, what next?

EricLNZ wrote on 1/3/2024, 1:03 AM

As @Reyfox said "First time I've seen anyone else report this error in how long?" So it's not something common to many users so @MauRam if you'd like to provide details of your system and media hopefully others can help find the cause of your problem. Start with Section C here https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

There's a wealth of expertise here. Look how long @Grazie has been around 😀

Grazie wrote on 1/3/2024, 1:18 AM

Look how long @Grazie has been around 😀

@EricLNZ - And you too! Thank you for your warm mention not just now but over the decades too. Moving on . . . you do make really useful and practical observations:

So it's not something common to many users so @MauRam

and then followed by a way forward too:

. . . so @MauRam if you'd like to provide details of your system and media hopefully others can help find the cause of your problem. Start with Section C here https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

Applying Signature Details: Might I also add, that @MauRam would benefit from applying his/her details in the "Signature" field, so not only can we make suggestions/remedies but the DevTeam may read them too.

RogerS wrote on 1/3/2024, 3:20 PM

I saw audio fx triggering this issue over the past year but that's been cleared up.

Any clue as to what's triggering the issue in this case? If it is only New Blue report the issue to them so they can work with VEGAS to fix it.