Topic: Need help trying to get vega rig back on track (Read 213 times)

Alright.. been wrestling with this all week and still no luck

I'm literally at my wits end now.  I've tried multiple versions of windows and multiple amd drivers and that one card will still not run without crashing. 
Sometimes it will go as long as 12-14 hours and sometimes it crashes just after an hour.

I've altered every setting I can on overdriventool, memory frequency up and down, voltage up and down and core frequency/voltage up and down.

Really hoping someone has an answer for this before I bung it out the window.

You know what, this makes perfect sense as there is a bad grape in the bunch.  I had to use the 75% softpowerplay instead on that particular card.
i'm going to give this a try before a reformat I think.

Only thing to work out now is the lower performance.  Getting an average of 1200-1300h/s depending on the algorithm.

Thanks man, you may have saved me from further headache.

I dunno if this helps, but I spent hours swearing at one Vega rig, only to discover that the card indexes had changed after an update. So if you're using overdriveN tool to OC, you might be overclocking the wrong card (I had a mix of 56/64, and used one on a lower clock as an output). You situation might be different, but once I'd figured that out mine has been rock solid since (touch wood)! Blockchain drivers, of course.

I did actually follow advice on disabling windows update.
There were a number of places to disable it including registry and these were all taken care of and windows still managed to force update.

I will take your advice on cloning though, this was something I thought about but didnt follow through on.
Going to do a fresh install on it this weekend.  Is it worth trying to use one of the later windows builds or should i just stick with 1703 and blockchain drivers?

@GordoLui  I did try 2 other drivers other than blockchain and had no luck, but willing to try if i can get stable.

@MahaBTC I dont think it was a miner issue, rather something with some of the settings somewhere but honestly will use any miner that works.

Maybe you need to update the vega drivers? I really liked the march drivers vs the august ones. They feel much more stable to me.

google this:
prevent windows 10 update


and
when you have rock solid system with all settings tweaked which ever way you go with reinstall or other miner-program:

clone the disk and make it possible to reinstall system.
(I presume the system is dedicated to mining and not used by a user at times.)

there are free programs like:
https://www.macrium.com/reflectfree
https://www.easeus.com/backup-software/tb-free.html


Good luck!

Why don't you try SRBMiner, is giving me rock solid stability and 2k+ average on my 56's

https://bitcointalksearch.org/topic/srbminer-cryptonight-amd-gpu-miner-v193-native-algo-switching-3167363

Read on and you can use the OverdiveNtools settings it works for me

Okay, so the story goes like this.

Back last year I followed the main guides to get a vega rig running on windows 10 1703 and the blockchain drivers.  It was mining flawlessly on monero etc at 1950 h/s average per card.
Earlier this year windows 10 1803 I think it was came along and wrecked everything...  It literally screwed up every rig I have.   I have my rx580 rigs running on smos for a few months flawlessly now but obviously cant use it for the vega rig.

So it's stuck running roughly 1200-1300 per card depending on the algorithm, and worse than that one card keeps crashing several times a day.  To make matters worse that rig is sat in my fathers house, so most of what i have to do is done remotely... i have very limited time to get it hands on.

Things i've tried...
Used cast, xmr stak and xmrig.  xmr stak seems to be the most stable, but its still crashing that card several times a day. 
I've updated to the latest version of windows as well as trying a few different amd drivers.

Questions I have, do you think I need to update the power tables again?
Do you think i should just start from scratch, format, go for windows 1703 again and HOPE that windows doesnt force it to update?

Any other things I can try remotely?

Hope you guys can help me... been driving me nuts for a number of months now