V10c hangs on load

jeffagwm wrote on 4/24/2011, 5:35 PM
Vegas Pro 10 c (build 469) is hanging on load. It was working fine last week. It hangs at the same point every time 'Initializing DirectX Plugins.....'

I tried to reinstall Vegas but still have the same problem. This is on a Dell XPS M1530 laptop with 4GB RAM and Win 7 Ultimate. Any insight would be appreciated to get Vegas running again.

Jeff

Comments

musicvid10 wrote on 4/24/2011, 6:13 PM
You have a plugin that Vegas will not load. You need to find what you installed recently, and rename the .dll extensions to something else until you find the offending plugin. Or do a system rollback.
jeffagwm wrote on 4/24/2011, 6:37 PM
Thanks for the quick reply. The only thing I have done since I was last able to run Vegas successfully is updated windows 7 which included Win 7 service pack 1
jeffagwm wrote on 4/24/2011, 6:38 PM
where are the DirectX plug-ins located?
jeffagwm wrote on 4/24/2011, 11:48 PM
I am going through un-installing the various Win 7 updates that have been applied over the weekend since I last successfully started Vegas. None makes a difference so far. The interesting thing is Acid starts fine. It also initiates DirectX plugins but doesn't hang, the problem is only in Vegas. Hmm

Here is the details of the error event:

Description:
A problem caused this program to stop interacting with Windows.

Problem signature:
Problem Event Name: AppHangB1
Application Name: vegas100.exe
Application Version: 10.0.0.469
Application Timestamp: 4d18e398
Hang Signature: d1ee
Hang Type: 6144
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Hang Signature 1: d1ee8a68d689a190f618e7c67528b9c7
Additional Hang Signature 2: f668
Additional Hang Signature 3: f668e449a8b32931134e604d51e27ca9
Additional Hang Signature 4: d1ee
Additional Hang Signature 5: d1ee8a68d689a190f618e7c67528b9c7
Additional Hang Signature 6: f668
Additional Hang Signature 7: f668e449a8b32931134e604d51e27ca9

Jeff
jeffagwm wrote on 4/25/2011, 1:30 AM
My problem seems to be going from bad to worse. I have uninstalled every windows update that had been installed since I last used Vegas but stall cannot start the program without it hanging when 'Initiating DirectX Plugins...' Acid and Sound Forge both start ok even though they both initiate DirectX plugins as well.

I tried completely uninstalling Vegas and cleaned the registry. Then did a fresh install only for the install to fail right at the end with Error Code 1603. Despite this error code, Vegas is there but when I try to start it, it hangs at the same point as before. I have started a ticket with Sony but am hoping that some one on this forum may have an idea as to what is going on.

Thanks in advance

Jeff
ushere wrote on 4/25/2011, 2:35 AM
possibly try reinstalling directx?
amendegw wrote on 4/25/2011, 3:01 AM
"possibly try reinstalling directx?"Or at least, start->run-dxdiag.exe

...Jerry

System Model: Alienware Area-51m R2
System: Windows 11 Home
Processor: Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz, 3792 Mhz, 8 Core(s), 16 Logical Processor(s)
Installed Memory: 64.0 GB
Display Adapter: NVIDIA GeForce RTX 2070 Super (8GB), Nvidia Studio Driver 527.56 Dec 2022)
Overclock Off

Display: 1920x1080 144 hertz
Storage (12TB Total):
OS Drive: PM981a NVMe SAMSUNG 2048GB
Data Drive1: Samsung SSD 970 EVO Plus 2TB
Data Drive2: Samsung SSD 870 QVO 8TB

USB: Thunderbolt 3 (USB Type-C) port Supports USB 3.2 Gen 2, DisplayPort 1.2, Thunderbolt 3

Cameras:
Canon R5
Canon R3
Sony A9

dcrandall wrote on 4/25/2011, 6:19 AM
I too was having hang problems running Windows 7 64-bit with Vegas 10c 32-bit. (Vegas 64-bit loaded OK) For me the problem Plug-ins were from NewBlue.
-Dan
  • Velocity Micro Z55 Desktop Computer
  • ASUS Prime Z270M-Plus Motherboard
  • Intel(R) Core(TM) i7-7700K CPU @ 4.2GHz
  • Memory: 16GB DDR4-2400MHz
  • 4GB NVIDIA GeForce GTX 1050 Ti Driver Version: Studio Driver 452.06
  • Windows 10 Home 64bit v1909
  • Vegas Pro 18.0 Build 284
VidMus wrote on 4/25/2011, 7:28 AM
Once you get everything working 100% again, get software that will make a clone of your system drive such as Casper and make two copies of your system drive to two other hard drives.

After you finished that, shut down the computer, remove your working system drive and make sure that the drives you cloned to actually work! Check that programs load and work on them.

Once you’ve verified that they both work, put the working system drive back in and THEN make whatever updates you want.

If something then goes wrong you can fall back on one of the drives you made a clone to. Use that drive to clone to the drive that was your working system drive to get it back to good again.

This is what I do and I have avoided a ton of headaches by doing so.

In the future, do make frequent clones (backups) of your working system drive so that the cloned-to drives are up to date. Do one drive at a time in case you discover something you missed you still have an older option in the other cloned-to drive.

Note: The reason why I said to test those cloned-to drives is because I used to use Norton Ghosts and it said that the clone was successful and all BUT when I tested the drive I cloned to it went through all the motions of booting up and got something like 99% of the way there and then froze! No matter what I tried I could not get a working cloned drive with Norton Ghosts!

I wonder how many people are making backups but have never tested them to make sure they REALLY work! You don’t want to find out when it is too late that it doesn’t!!!

As for your current problem, because you kept doing a crap-shoot by uninstalling this and that you will probably now need to do a complete system re-install and start over again.

jeffagwm wrote on 4/25/2011, 10:26 PM
I tried Dxdiag. It says I am running DirectX11 and everything is fine. I did also try reinstalling DirectX but it didn't make any difference.
ushere wrote on 4/25/2011, 10:44 PM
as above - do you have any newblue fx?