Really?  135 watts, wow, how are you measuring this? 
Also, what do you mean intensities at 2016 and 1736, how are you setting these?

I quit using wattman becuase it seems flaky, I'm not using custom tables because it forces the settings from registry on every startup and each card seems to have different tolerance to OC.  Do you know where we can find an editor to tune these?
Otherwise, this is a great way to get stuck in a loop, if your card can't handle those settings, IMO.
I switched to OverDriveNtool, which has a command line to set params each time and I can tune while running then save

Are you using xmr_cast-vega?
I have OC Mem AT 935/900mv and get 1950-1975 for all 5, but my watts measured at the wall are bout 200W each 
   No GPU clock adjusting seems to make any difference in hash or power.   I can get to 2050ish with 950, but can't keep em stable
   BlockChain Aug 23 drivers, stock 56 bios, no power adjust, 60deg target/ 70 max 


   

Start isolating.  -- I'm assuming you are using windows for now.
A: Prove both cards work and both risers work
Do some research before you make changes
     Does device manager see both cards as enabled?
     Do tools like HVINFO, OverdriveNtool.exe recognize both cards?
     
     if Not, you likely have a hardware issue (Weakest link is a riser problem, or not enough power given to PCI motherboard connections)
     There are alot of posts about risers quality, I had one fail myself.

After you have ensured both cards are recognized by these tools, suspect the driver.
This sight was a great help to me to get started


http://vega.miningguides.com/#Script

Post some details, miners here can help , but also isolate and change things 1 at a time.

Ex: Stop Stak mining until you have cast-xmr working stable, then re-introduce it.
Don't overclock until system is stable, Keep Vega Cards running < 60, etc...
Start simple with Miner options (Just use what the pool needs, usually -S miner -u <public wallet> -p x or <email>  -G 0
Make sure your pool responds happily -- Connected

Get stable first, then start optimizing for speed, quantity, performance.

Vega Drivers seem easily confused and cast does not recover well when this happens.



I learned alot early about Vega Mining here - I did not choose to mod bios and still get 1950 Vega 56, 2050 Vega 64
http://vega.miningguides.com/#Script

I had this problem too until I turned off the crossfire support
Regedit:  
Search for EnableUlps = set to 0
Search for EnableCrossfire - set to 0
[Enable Crossfire is the setting above EnableULPS - don't just search for crossfire there are more unimportant settings, these 2 tell the driver not to look for or use crossfire]

Also, don't forget to export registry and do a system restore point if you think you might make a mistake...

That fixed all my squirrly monitor artifacts and 0.0 hashrate issues.

Did you disable crossfire?

from Commandline: Regedit: 
Search for EnableULPS - set to 0
Search for EnableCrossfire - set to 0
[Do this for each card]

I have 5 Vegas that settled down immediately after ...
[Hint : Be sure to export registry or set a windows 10 restore point just in case you muck up the registry ]

Finally got single MSI Vega 56 to run stable with xmr-cast-vega.  My key was getting the temp right <65 to stay stable and keep MEM < 950
Block chain drivers and reset driver prior to running.  Very stable.

Freq: -8%
Mem: 945
Power +10
Rate:  1980
Fan: ~3400 min
Temp: 64
Ave Search 45 secs, no errors

or

Freq -8%
Mem: 935
Power +0
Rate 1950
Fan: ~2500 min
Temp: 62

Not bad, both very stable, but I have not been able to get to the fabled 2000


Here's my question.  I mined 24 hrs with nicehash
Nicehash reports between 1.33 and 2.2 at any given time and is quite variable on their BTC profitability curve through the day.
anyone have good/bad NiceHash experience or can explain this phenomenon?

Or, suggest a more profitable pool to point to?

Thanks