What would cause this?

Jessariah67 wrote on 1/6/2010, 11:51 AM

Hey all,

I've been working on a large project, and I've been saving to different file names (day # & letter) progressively.

Ysterday, I'm working on "5c" and I get a blue screen. The computer reboots and I can't open 5c anymore - I get an error message and it closes Vegas down. So I go back to "5b" and it opens fine. I immediately save as 5d and continue to work. By the time I'm done, I'm up to 5i.

This morning, I go to work and get the same error messages when trying to open 5i. 5h doesn't open either. But then I try 5i again and it does open. so I save as a safety and then open 5i in Vegas 8 (I'm editing in 7 on this project). Now, none of them will open (from 5c on) in either version of Vegas.

I can't make heads or tails out of this. I mean, a file is either corrupt or it isn't. I was thinking maybe V7 got corrupted when the computer crashed, but I'm getting the same error message (at the same point of loading - 31%) in V8.

Any insight on this would be appreciated. My biggest concern is redoing the work and not being able to open the file later - weird, considering the other files that are crashing were built from a previous file that wasn't even open when the computer blue screened.

Here's the error message:

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) READ:0x190 IP:0x5173B8
In Module 'vegas80.exe' at Address 0x400000 + 0x1173B8
Thread: GUI ID=0xB74 Stack=0x284000-0x2D0000
Registers:
EAX=0000002f CS=0023 EIP=005173b8 EFLGS=00210202
EBX=00000003 SS=002b ESP=00284a88 EBP=00000000
ECX=10351a38 DS=002b ESI=0a55b978 FS=0053
EDX=00000000 ES=002b EDI=0000006f GS=002b
Bytes at CS:EIP:
005173B8: 8B 92 90 01 00 00 3B FA ......;.
005173C0: 7F 02 8B FA 3B 7C 24 20 ....;|
Stack Dump:
00284A88: 04040ACE 04010000 + 30ACE
00284A8C: 0A010AC7 0A000000 + 10AC7
00284A90: 7D816F6B 7D800000 + 16F6B (GDI32.dll)
00284A94: 0A55B978 0A3C0000 + 19B978
00284A98: 00000012
00284A9C: 0000006F
00284AA0: 00000178
00284AA4: 03396918 032F0000 + A6918
00284AA8: 00000128
00284AAC: 00000000
00284AB0: 00000002
00284AB4: 00000002
00284AB8: 00000179
00284ABC: 00000196
00284AC0: 000001B7
00284AC4: 7D816F7D 7D800000 + 16F7D (GDI32.dll)
> 00284AD4: 00517FD7 00400000 + 117FD7 (vegas80.exe)
00284AD8: 00000006
00284ADC: 0A010AC7 0A000000 + 10AC7
00284AE0: 00000000
00284AE4: 0A010AC7 0A000000 + 10AC7
> 00284AEC: 7D816501 7D800000 + 16501 (GDI32.dll)
> 00284B20: 01407F0D 01310000 + F7F0D (vegas80k.dll)
> 00284B24: 016170B0 01310000 + 3070B0 (vegas80k.dll)
00284B28: 0A010AC7 0A000000 + 10AC7
00284B2C: 00284BE0 001D0000 + B4BE0
> 00284B30: 00FFFFFF 00400000 + BFFFFF (vegas80.exe)
00284B34: 00000000
00284B38: 00000000
00284B3C: 00000000
00284B40: 00000000
> 00284B64: 00610052 00400000 + 210052 (vegas80.exe)
> 00284B68: 00650074 00400000 + 250074 (vegas80.exe)
- - -
002CFFF0: 00000000
002CFFF4: 00000000
002CFFF8: 0083F20B 00400000 + 43F20B (vegas80.exe)
002CFFFC: 00000000

Comments

fldave wrote on 1/6/2010, 12:02 PM

Sounds more like a memory or hard disk problem to me. A file is either corrupt or it is not.

I would copy everything to multiple drives so you don't loose much if your hard drive fails. Can you try to open the files from another computer?

xberk wrote on 1/6/2010, 12:07 PM

I agree. Test the memory and harddrive.

musicvid10 wrote on 1/6/2010, 12:50 PM

I've seen this.

I'm guessing the problem is either with your video drivers or a bad video card.
The dumps at 0028 support my suspicion. Try the drivers first, but . . .

Jessariah67 wrote on 1/6/2010, 7:02 PM

Weird.

I updated my video driver and installed Vegas onto another computer. Tried to open the file from the backup (USB) drive on my editing computer (before updating the driver), and it crashed. Tried to open the file on my other computer, and it crashed. Tried to open the file on my editing computer after updating the driver, and it opened (but the display settings were all messed up). Once I configured the display settings, the file crashes from both the working drive and the backup drive.

Just one of those things to file under "shouldn't be doing this" I guess...

Thanks for the input.

K

musicvid10 wrote on 1/6/2010, 7:44 PM

What media are in your project? Anything weird like divx, huge jpegs or tiffs, or files from Final Cut?
What version of Quicktime is installed?

Grazie wrote on 1/6/2010, 11:31 PM

2 PCs, same Project? Has to be the Media.

Y'know, as Vegas is sold on the basis of it being able to deal with most stuff that is thrown at it, wouldn't it be just hilarious(great) if Vegas had a utility that did a pre-Project audit of the media OR on import into Project Media it flagged what media could be a problem? Something along the lines of:

"Hey, Grazie, now you just KNOW that I can deal with the 3gbs of stuff you just threw at me! But this last TIFF! And the size of your JPEG - well you're just having a "Turkish" with me!! Get real sonny!"

Y'know, that kinda thing? Too much to ask? Or even a utility that did a diagnostic of just WHAT was making Vegas get all uppity with me - and, yeah that other thing, my "creativity"?

And to "borrow" a phrase: "Sony Diagnostic? - That was my idea!"

Grazie

Jessariah67 wrote on 1/8/2010, 8:03 AM

All images are PSD and under 2K in either dimension. I've rebuilt and seem to have a stable VEG. That was just weird to have a file open "sometimes"

Thanks for the input.

K

musicvid10 wrote on 1/8/2010, 9:24 AM

I've rebuilt and seem to have a stable VEG.

Glad to hear it.

I've had random crashes with .psd images in my projects. Now I convert all to .png (often with alpha) in Photoshop and no more problems. Might be something to try if the problem comes back.