Vegas 11 32bit crash on opening new Windows window

JMacSTL wrote on 3/10/2016, 2:25 PM
When Vegas 11 32bit (build 700) is running, and I open a new window (I am running Windows 7 Pro service pack 1) vegas crashes. i've reported this crash numerous times to Sony. If I go out of Vegas (shrink it down) and click on an already-open file window (say, to look for or copy a file or something), it's fine. But the moment I open a new window, BOOm crash.

Some days, it only does it once or twice. Other days, every single time.

Thoughts? anybody else had this issue?

Windows 7 Pro Svc pack 1
Intel i7
20GB Ram
Separate hard drives for system, audio, video.

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

Comments

john_dennis wrote on 3/10/2016, 2:41 PM
Are you running the 32 bit version because of plug-ins?
JMacSTL wrote on 4/29/2016, 9:17 AM
I get this same crash too. Windows 7. Vegas 11 most current build. I run 32bit because it imports AAF, and the 64bit doesn't. Yesterday I had no crashes, but today, already, two. Makes no sense. Windows hasn't updated itself, so it's not that.

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

musicvid10 wrote on 4/29/2016, 9:53 AM
Tried the Vegas Pro 13 trial?

JMacSTL wrote on 4/29/2016, 11:49 AM
I purchased 13.0 when it came out. It it totally unusable for me, since it no longer supports my Kona card, and since WAVES plugins are totally unstable and won't play glitch free. I've stuck with 32 bit 11.0 since it's the most stable and usable. Honestly, I"m gravitating most of my sessions to ProTools 11.0, since it's very good. I'll miss two things tho: being able to edit video, render video and place pretty much any video format on my timeline and any number of videos.

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

john_dennis wrote on 4/29/2016, 12:30 PM
"... I open a new window..."

I want to see if I understand exactly what you are doing. By "open a new window" you are starting a different application such as Windows Explorer and Vegas Pro 11 loses focus.

What is the state of these switches in Preferences?

Interesting Reading:
http://www.sonycreativesoftware.com/forums/showmessage.asp?forumid=4&messageid=836035
JMacSTL wrote on 5/17/2016, 10:09 AM
Thx for responding John:

You understand correctly. When Vegas is open, with a project loaded -- and keep in mind that I use Waves plugins in virtually every one of my projects for audio -- and I go to open a new Windows 7 Explorer window (whether a local drive to find a file, or a networked drive, it doesn't seem to make a difference with this issue), Vegas instantly crashes and gives me the error dialog box asking if I'd like to report the issue. Some days it happens first thing in the morning after booting the computer, some days it doesn't happen until later in the day after I've opened and closed half a dozen projects, and other days it doesn't do it at all.

My General Prefs match your screen shot: both of those boxes are currently checked. I've never changed them. Close Media Files when not the active application, and Close audio and MIDI ports when not the active application

The only midi device I'm using any more is a FaderPort, and Vegas has had a built-in driver for that for several years.

The only other thing my computer has running is Microsoft Security Essentials, but real-time protection is not turned on. We're behind multiple firewalls here at our studio and I've never (knock on wood) had any malware or viruses hit this computer.

I'd thought that perhaps WAVES plugins (I'm running Horizon bundle with iLock) was causing this, as WAVES still doesn't always play nice.

jmm

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

john_dennis wrote on 5/17/2016, 12:01 PM
I haven't used WAVES so I can't comment. When Vegas Pro pops the error and offers to send the error report, are there any details offered no matter how cryptic?
JMacSTL wrote on 6/9/2016, 10:18 AM
I've finally got better info on these crashes. Here is the crash report: Next time I get one, I'll compare and see if it is the same info.

Problem Description
Application Name: Vegas Pro
Application Version: Version 11.0 (Build 700)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files (x86)\Sony\Vegas Pro 11.0\vegas110.exe
Fault Address: 0x199E7300
Fault Offset: 0x199E7300

Fault Process Details
Process Path: C:\Program Files (x86)\Sony\Vegas Pro 11.0\vegas110.exe
Process Version: Version 11.0 (Build 700)
Process Description: Vegas Pro
Process Image Date: 2012-09-24 (Mon Sep 24) 21:08:00

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

john_dennis wrote on 6/9/2016, 11:46 AM
I hope you never get another one.
larry-peter wrote on 6/9/2016, 1:09 PM
I would suggest looking at your log files in Event Viewer ( i think it's named the same in Windows 7 - I'm on an XP station at the moment) Check out the application and System logs to see what was happening at the time of the crashes. It may give you some clues as to the cause.

JMacSTL wrote on 6/13/2016, 2:44 PM
Answer the last question about whether or not the info on the crash is identical each time? Yes. I just saved four crashes that occurred over the past week, and each was identical.

Problem Description
Application Name: Vegas Pro
Application Version: Version 11.0 (Build 700)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files (x86)\Sony\Vegas Pro 11.0\vegas110.exe
Fault Address: 0x199E7300
Fault Offset: 0x199E7300

Fault Process Details
Process Path: C:\Program Files (x86)\Sony\Vegas Pro 11.0\vegas110.exe
Process Version: Version 11.0 (Build 700)
Process Description: Vegas Pro
Process Image Date: 2012-09-24 (Mon Sep 24) 21:08:00

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

JMacSTL wrote on 6/17/2016, 10:45 AM
UPDATE:

The crash info is NOT all the same after all. It's often different in one location: this memory location keeps changing. Each of these is a different crash on a different day. jmm

Fault Address: 0x1F9F7300
Fault Offset: 0x1F9F7300

Fault Address: 0x1F9C7300
Fault Offset: 0x1F9C7300

Fault Address: 0x1FE17300
Fault Offset: 0x1FE17300

Fault Address: 0x199E7300
Fault Offset: 0x199E730

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

JMacSTL wrote on 6/17/2016, 10:45 AM
Spent an hour looking at every listing in these, and didn't really find much that coincided with the time of the crashes.

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

VEGAS_EricD wrote on 6/29/2016, 3:33 PM
Does the crash happen if you uncheck the preferences for:
1. Close media files when not the active application
2. Close audio and MIDI ports when not the active application.

If it stops crashing after unchecking those, it is possible that the crash happens when re-loading media, which would explain why the memory address is different in each report.
JMacSTL wrote on 7/20/2016, 8:46 AM
Hey Eric:

i'll give those two options a try and see what happens. Stand by.

thx.

jmm

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

JMacSTL wrote on 7/25/2016, 11:20 AM
Eric:

I have positive confirmation that unchecking those two boxes that you suggested did not solve the crashing issue when opening a new file explorer window. After unchecking the boxes and hitting APPLY, I then exited the application, restarted it, opened up a recent project, and then attempted to open a new explorer window....and that's when the crash always happens.

Sigh. Maybe Vegas 14 will work!. I"m all aboard for jumping to 14 this fall as long as support for my AJA Kona 3 still works. (Vegas 13 evidently removed this support, sadly.

jmm

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.