ATI RX580 crashing Vegas 11-14

uvasonar wrote on 5/16/2017, 3:40 AM

I just wanted to let you know, that I didn't get my ASUS RX580 (8 GB) to work with Vegas Pro 12-14 - latest ATI drivers (17.5.1), latest patches (Windows 7 x64, Vegas 12/14). So if anyone is considering the latest AMD Polaris cards, you'd better stay away from them until this is sorted out. Even when GPU acceleration is switched off, Vegas will only run once after a Ctrl-Shift-start and crash during every other following startup.

It reports an unmanaged exeption in the ati driver.

Or has anyone managed to get a RX5x card to work properly?

EDIT/LATEST INSIGHT:

The startup crash just occurs, when the Vegas Pro 12/14/14 main applicaton window is starting up on an Intel internal VGA display with one or more ATI extended desktop displays enabled - regardless if GPU acceleration in Vegas prefs is enabled or not.

Quick Fix: As soon as the main application window starts up/has been saved on an ATI display while quitting VP, the problem is gone and VP doesn't crash at startup.

Back to post

Comments

uvasonar wrote on 5/23/2017, 8:19 AM

So I guess the startup crashing I have experienced might also occur when using older drivers/other ATI cards. This didn't happen with my old NVIDIA GTX580, very same system and configuration (and yes, I have deinstalled all prior drivers properly and cleaned up with DDU).

RedRob-CandlelightProdctns wrote on 5/23/2017, 7:24 PM

Since installing my NVIDIA GeForce GTX 750, my performance in Vegas has only been "meh".

Reading what everyone has been writing here, I'm thinking of getting an RX480. A few questions:

RX480 4-GB RAM vs. 8-GB RAM... any comparisons on preview and render differences?
RX480 vs RX580... same question
Power Requirements -- my power supply isn't extremely beefy which is why I stuck with the GTX750... anyone know what the requirements are for these cards?

mmcswnavy24 wrote on 5/23/2017, 8:18 PM

The "Reference" style RX 480's all used a standard 6-Pin PCI-E power connection. This caused AMD some grief initially due to the Power Draw of these cards. It was supposedly fixed with a driver update. I have the Asus Strix RX 480 8 GB OC version, and it uses the 8-Pin PCI-E power connection. No problems, and from what I have seen of most of the Add-In Board/Add-In Card (AIB/AIC) manufacturers, is that they also utilized 8-Pin power. Possibly some of the "really high-end" cards, possibly like a Zotac AMP Extreme or the Gigabyte Aorus Extremes might need both an 8 & 6-Pin connections. Mine is running on an X99 Haswell-E platform, with Windows 10 64-Bit, with the Crimson ReLive 17.4.4 drivers.

As for whether 4 or 8 GB of RAM, you would be the best to determine that based on your workflow and needs. Plus, $$$$$$$$$$ could possibly play a small part in it!😉 Did some render tests between this card and an MSI GTX 1070 Armor, and the Asus typically won on all five tests I ran. The test was posted on the Movie Studio Zen website forum, in the hardware section.

NickHope wrote on 5/23/2017, 10:42 PM

@uvasonar If you don't have it already, I suggest you install .NET Framework 4.6.2. That is known to solve some display issues with Vegas in Windows 7.

Also, I would start with driver 16.12.2, which worked for john_dennis's RX480 in Windows 7.

MarcinB wrote on 5/24/2017, 3:06 AM

Power Requirements -- my power supply isn't extremely beefy which is why I stuck with the GTX750... anyone know what the requirements are for these cards?

Recommendation for my RX580 is 500W power supply. Single 8 pin power connector is required.

More overclocked models require 6+8 power connectors.

Cheers

Marcin

uvasonar wrote on 5/24/2017, 5:46 AM

@Nick Hope: Thank you very much! I will give .NET 4.6.2 a whirl ASAP, as was not aware of .NET playing a role in this game.

NickHope wrote on 5/24/2017, 10:07 AM

@Nick Hope: Thank you very much! I will give .NET 4.6.2 a whirl ASAP, as was not aware of .NET playing a role in this game.

Don't expect too much. This is the classic issue with Windows 7 & VP14: Case 1, case 2, case 3. But I think it solved a display-related issue for someone else. Can't remember the details though.