Error Code

ec2 wrote on 11/28/2007, 6:47 PM
Can anyone tell me what the following error code means and how to stop it?

Sony Vegas 4.0
Version 4.0e (Build 239)
Exception 0xC0000005 (access violation) WRITE:0x4420000 IP:0x2AF45E1
In Module 'sfasio.dll' at Address 0x2AE0000 + 0x145E1
Thread: GUI ID=0xCF4 Stack=0x12F000-0x130000
Registers:
EAX=00000000 CS=001b EIP=02af45e1 EFLGS=00210246
EBX=00000000 SS=0023 ESP=0012f7f8 EBP=0023a50c
ECX=00000200 DS=0023 ESI=0023a008 FS=003b
EDX=00000800 ES=0023 EDI=04420000 GS=0000
Bytes at CS:EIP:
02AF45E1: F3 AB 8B CA 83 E1 03 F3 ........
02AF45E9: AA 5F 8B C3 5B C2 0C 00 ._..[...
Stack Dump:
0012F7F8: 0023A500 00140000 + FA500
0012F7FC: 0023A508 00140000 + FA508
0012F800: 02AE6224 02AE0000 + 6224 (sfasio.dll)
0012F804: 0023A3DE 00140000 + FA3DE
0012F808: 04420000
0012F80C: 00000200
0012F810: 00000005
0012F814: 00000000
0012F818: 00000000
0012F81C: 0310B0F0 03090000 + 7B0F0
0012F820: 011A3556 01000000 + 1A3556 (vegas40k.dll)
0012F824: 00000005
0012F828: 58982DFE
0012F82C: 00000000
0012F830: 00000000
0012F834: 58982DFE
> 0012F840: 0118FD54 01000000 + 18FD54 (vegas40k.dll)
0012F844: 00000005
0012F848: 58982DFE
0012F84C: 00000000
0012F850: 00207A00 00140000 + C7A00
> 0012F858: 7C839AA8 7C800000 + 39AA8 (kernel32.dll)
> 0012F85C: 7C8025F8 7C800000 + 25F8 (kernel32.dll)
> 0012F864: 7C8025F0 7C800000 + 25F0 (kernel32.dll)
> 0012F868: 7C802532 7C800000 + 2532 (kernel32.dll)
> 0012F874: 7C80A049 7C800000 + A049 (kernel32.dll)
> 0012F88C: 011901A2 01000000 + 1901A2 (vegas40k.dll)
> 0012F890: 011901BF 01000000 + 1901BF (vegas40k.dll)
0012F894: 58982DFE
0012F898: 00000000
0012F89C: A0000000
0012F8A0: 58982DFE
> 0012F8B0: 006269FF 00400000 + 2269FF (vegas40.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 0067ABBA 00400000 + 27ABBA (vegas40.exe)
0012FFFC: 00000000

Comments

pwppch wrote on 11/28/2007, 7:12 PM
This looks to be an audio driver (ASIO specificly) problem.

What were you doing when this occured?

What audio hardware are you using? Do you have the latest ASIO drivers for your audio hardware?

Please fill out your system specifications in your user profile.

Peter
ec2 wrote on 12/1/2007, 12:32 AM
Using Vegas pretty hard with 55 tracks. But at the same time I just loaded 4 gig of ram only able to use 3.43. I have the following sound devices in my device manger menu:

Audio Codecs
E-mu E-Dsp 5.12.4.1104 10/22/2005
Legacy audio drivers
Legacy video capture devices
Media Control Devices
PreSonus Firestudio 3.0.0.70 9/5/2007
Video Codecs


pwppch wrote on 12/1/2007, 12:00 PM
Which card were you using in Vegas and do you have the latest ASIO drivers from the manufacture of the hardware?

The RAM limit is due to the OS. Vegas will only addres upto 2 gig under XP and Vista.

Once the world is on to Vista 64 and we release a 64 bit version of Vegas, then you will be able to address all of your RAM - with in the limits of the OS still.

Peter
ec2 wrote on 12/3/2007, 8:05 PM
When you say what card was I using. In the audio devices section I had selected was the PreSonus which is run into my sound card which came with the E-MU 1820. Where the PreSonus is firewire I did not think it would matter. I have the latest drivers pre the PreSonus web site. As well I am using Vegas 4.0e. Which brings up another issue I tried to reinstall Vegas via the web site. I tried to register with the serial number listed in my owners manual and was told I have registered the software to many times and that it was going to be on a 30 day trial basis. How do I fix this I now have 26 days left with Vegas?
pwppch wrote on 12/3/2007, 8:28 PM
You need to contact our customer support with regard to your registration issue.

Where you using the ASIO drivers? (The data dump indicates you were.) What were the settings you used?

Peter
ec2 wrote on 12/4/2007, 12:05 PM
I was using ASIO drivers. Where would I find the settings that you are asking about?

pwppch wrote on 12/4/2007, 4:47 PM
That depends on the audio card and its driver. The hardware usually has a control pannel type app that allows you to set the buffering sizes and other features of the hardware.

Even so, you are using a version of Vegas that is 4 behind the latest version. Even if this was a bug in our code, there is nothing that will be done about it as we are at version 8.0 currently.

My guess it is a driver specific issue that was either solved between versions 5 and 8 or a driver difference that was not available for us to test with during the developement of Vegas 4.

You should try using the demo version of Vegas 8 and see if the problem still occurs.

Peter