Am sure its pool issue side… as a few of us have started getting it today.
I’ve reported the issue with Genoil:
1 Like
Will force a reconnect upon “job not found” in next release.
4 Likes
Sounds good, can you do the same for one value 0 sol that happens sometimes and need a restart?
My RX480’s jump from 15 - 30 Sol/s
I’m only running 3 GPUs, so my average reported Sol rate is around 80S/s
I had to flash back to STOCK FACTORY BIOS for the RX470/RX480. Its very unstable any other way.
Maybe others had luck with the modified bioses but not me, it freezes the system to the point where you need to pull the plug from the wall.
Likewise
- Clean install of AMD 16.10.3
- ATIWinFlash back to Stock ROM
- Running @boysie123 's WattMan settings
Feedback:
Running this on Gigabyte HD 7970 and R9 270 on Win 7 with latest drivers.
HD 7970 giving between 24 to 32 Sol/s (1150 core, 1500 memory)
R9 270 giving between 18 to 23 Sol/s ( 1100 core, 1500 memory)
I went out and after 3 hours, I found the miner giving 0, guess it crashed, running it with autoscript now, also the gpu usage for 7970 is at 65% constant, for r9 270, it’s at 78%. Memory usage is 1800 and 1600 respectively.
Looking forward to smoothing out the miner for best performance 
1 Like
(Message deleted postet to wrong forum) sorry
I’m running an 8 gig 470 on one rig and four 4 gig 470s on another; There isn’t much of a difference…they’re within about 10 percent of each other (the 8 gig just slightly higher). I suppose that could change as new miners are released, but there’s not much difference right now.
I’m running 6x stock ref RX480 getting 20-30 sol/s on all but one (it gets 10-14), I think I have a bad riser on it.
core clock is at 1350
memory is at 2100
using afterburner to mod clocks
total watts at wall are 735
Regarding Pitcairn/Tahiti,
You are suppose to NOT use “-k zec zec” correct?
Instead leave it out or use “-k zec” instead because using “-k zec zec” results in 1 or 2SOl/s and crazy crashing issues.
Yeah, same here, on Pitcairn and Tahiti was getting very low Sol/s with -k zec zec, not using it at all or just using -k zec is ok.
Ok good.
Seems the rates can vary from 20Sol/s with a slow Single core Sempron CPU all the way to 30Sol/s with an i3 using the exact same 280x.
Either way, it results in at least 2x profits compared to ETH mining since these Tahiti really were bad due to DAG file slowdowns.
Hi good script.
I put another thing in findsrt because my miner some times have bad job (21) and i add in findsrt this other option.
In one rig with 79xx cards some times genoil crash at start and script doesn’t work because i i dont click in close program and the output.txt don’t make nothing script don’t work for restart miner.
Do you know how to put in script one option if output.txt dont put new lines in 20 seconds make a kill and start miner another time?
Tnx for share this script 
Npt sure if its the pool or the miner but having a ton of trouble keeping the miner up , from crashes of the app machine reboots
and the dreaded not found and 0 sols error.
Never had this problem on eth, so going back to that until stability issues can be resolved, I wil donate some eth once I recoup this weekends losses
Claymore just published
Yeah I got working miner today but I don’t want to release it until I get at least 100h/s on 390, it will take some more time.
You are correct, with such drop in price it seems everyone will mine ETH again when I release ZEC miner Smiley
Very unstable to mine with genoil right now… all 4 of my rigs were down in the morning… I had restart script on all 4 set to 20 minutes but it seems it’s not enough to restart software… now I’ll up script to reboot the whole computer every half an hour let’s see what happens.
The ETH difficulty certainly took a big hit:
100+ down to 76.37 over night
1 Like
it feels to be extremely CPU intensive…under various conditions.
being connected to my rig on vlan(openvpn) now being in the same physical lan I’ve just seen that it actually made it look like the connection was dropped I was sure that the machine rebooted, yet it didn’t!
looks like threads/processes in win10 never got their turn, I’d guess because of something fishy going on a driver level…