Vstudio.exe application error

Moderator: Ken Berry

Post Reply
cyrusd
Posts: 2
Joined: Sat Jun 06, 2009 8:42 pm

Vstudio.exe application error

Post by cyrusd »

I installed Videostudio PRO X2 and when I click on the icon, the splash screen appears, when I select VideoEditor, I get "vstudio.exe Application Error: The instruction at xxx referenced memory at xxx. The memory could not be 'read'"

The program will not start. I have posted the problem at the support center but have not been successful. I have been trying to make Videostudio X2 work since March 2009.

Please help or suggest.

Thank you
sj1805
Posts: 145
Joined: Wed Sep 20, 2006 5:15 pm
operating_system: Windows XP Pro
System_Drive: E
32bit or 64bit: 32 Bit
motherboard: Equium P200-178
processor: Intel Pentium Dual-Core Processor T2080
ram: 2 GB
Video Card: Intel 945 Express
sound_card: Intel GMA 950
Hard_Drive_Capacity: 1160 GB
Location: Birmingham UK

Post by sj1805 »

The first thing to try is uninstall/reinstall.
[img]http://www.steve-jones.pwp.blueyonder.co.uk/sjjsig09.png[/img]
cyrusd
Posts: 2
Joined: Sat Jun 06, 2009 8:42 pm

Post by cyrusd »

sj1805, I have tried that 5 times now. I have cleaned all the pertinent directories associated with Videostudio as suggested by Support Services. I have deleted the Registry entries too It has not worked. I even install the Install shield engine as suggested bt Support Services.

Could it have anything to do with Microsoft's Visual studio or VB. All my other programs are running fine.

Thanx for your prompt reply
drbob
Posts: 2
Joined: Sat Jun 13, 2009 10:32 pm

same error different situation

Post by drbob »

v Studio 9, win2k, have made and burnt DVDs in past w/no prob, this time I'm getting error message "vstudio.exe has generated errors bla bla bla", I've tried using install disk to "repair" with no changes, have read prev post concerning similar issues... with no changes. The process starts, gets anywhere from 10% to 28% completed when error message pops up and program shuts down. The only thing I have done differently from prev burns is in that I've included pics and video taken from my cell phone, 3g formats, have done a file conversion prior to adding to time line, can't seem to get video and sound to jive, so I've separated video from sound and have been able to add one or the other to time line. Don't know if this is the issue or not. Rendering and putting into a file goes smooth, burning gets nowhere. Anyone with any ideas? Thanks in advance.
User avatar
Ken Berry
Site Admin
Posts: 22481
Joined: Fri Dec 10, 2004 9:36 pm
operating_system: Windows 11
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: Gigabyte B550M DS3H AC
processor: AMD Ryzen 9 5900X
ram: 32 GB DDR4
Video Card: AMD RX 6600 XT
Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
Location: Levin, New Zealand

Post by Ken Berry »

Rendering and putting into a file goes smooth
Hi drbob -- welcome to the forum! :lol:

Could you please give us more detail on what you mean by the above. Are you rendering your project in the Editing module? If so, what format are you rendering it to? And is 'putting into a file' the same as rendering? Or is it some other sort of file?
Ken Berry
drbob
Posts: 2
Joined: Sat Jun 13, 2009 10:32 pm

Post by drbob »

Hi Ken, upon opening prog. I load my vsp file to the edit time line, click on 'create disk' which brings up the create disk screen. If I go to 'next' button pick a title and start a burn, it always fails. I recently tried once again to render movie into a file by closing the 'create disk' screen leaving me with the 'share' tab screen, then rendering through the 'create video file' and giving file a new name. Tried this before to end up in failure, tried it again since posting, opened prog. did not load origional file, went directly to 'create disk' clicked on 'add video' chose the new previously rendered file, clicked on 'burn' and "walla" it worked...I think!, haven't tried to watch DVD on home player yet but looking good so far. This could all be the infamous "user error" senario. I admit I don't use the program more than maybe 2xs per year, maybe I just forgot all the steps.
Thanks for the reply and I'll let you know later if it plays correctly.

drbob
User avatar
Ken Berry
Site Admin
Posts: 22481
Joined: Fri Dec 10, 2004 9:36 pm
operating_system: Windows 11
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: Gigabyte B550M DS3H AC
processor: AMD Ryzen 9 5900X
ram: 32 GB DDR4
Video Card: AMD RX 6600 XT
Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
Location: Levin, New Zealand

Post by Ken Berry »

The alternative you *think* you found sounds like the right one to me -- though it seems a curiously circuitous way of getting there at the same time!! :lol: :roll: Our recommended workflow is to do your editing and then simple select Share > Create Video File > DVD (or Custom if you project is more than an hour or so in length). That will render your project into a DVD-compatible mpeg-2.

Note that after you produce your new mpeg-2, you go to File > New Project. Don't worry about giving your new project a name. The objective is just to clear the timeline of your current project.

Once that is done, you select Share > Create Disc > DVD. The burning module will open. Use the Add Media button at the top to insert your new mpeg-2 in the burning timeline. Then go to the middle of the three icons in the bottom left of the burning screen. There is a little box beside the words 'Do not convert compliant mpeg files'. Make sure that box is ticked (it usually is by default). That way, your already compliant mpeg file will not be re-encoded. Then build your menus and burn.

As it is, you are jumping straight to the burning module with the project vsp file being inserted instead of video. In the past, this workflow caused many users a lot of headaches. It worked for some, but not everyone. The situation has improved with recent versions of VS, but not totally, as your own case seems to show. So try the above and see if that works for you...
Ken Berry
Post Reply