Quote from: fullzero on June 25, 2017, 02:41:12 AM

Quote from: Nexillus on June 25, 2017, 01:49:08 AM

Quote from: fullzero on June 25, 2017, 01:03:40 AM

Quote from: Nexillus on June 24, 2017, 09:54:01 PM

Quote from: fullzero on June 24, 2017, 06:32:37 PM

Quote from: Nexillus on June 24, 2017, 12:21:01 PM

Quote from: fullzero on June 24, 2017, 12:34:00 AM

Quote from: Nexillus on June 24, 2017, 12:24:41 AM

Quote from: fullzero on June 23, 2017, 11:49:20 PM

Quote from: Maxximus007 on June 23, 2017, 08:54:59 PM

Quote from: Nexillus on June 23, 2017, 07:45:14 PM

I'm really confused now, it just happened on VER15 within 15 minutes... With a different USB drive...

To my knowledge this should not be happening since these are 8GB cards and it will hit 3GB DAG file next year for ETH...

I've had these errors once too, but it was OC. Your temps are nice so that's not the issue. Lower both OC and MC with 100, see if it is stable then. If so, go up with 50, MC first.

I would try Maxximus007's suggestion.

Let me know if you keep getting these errors.

It is also possible that having less free space contributes to these errors with claymore; I think I am going to increase the size of the primary partition to very close to 16gb for the next version for this reason.

Optimally for claymore you should have up to 16gb of free space and use it as virtual memory, I am considering pushing the size to 32gb and implementing this in an alternative build for better ethash mining.

I changed the OC by mem by 15 and it has been solid for the last 90 minutes. I just think it is very odd since it was on the OC for almost a week. I didn't know you changed the primary partition, I think many of us are using 32GB USB keys too.

You can extend the primary partition on any key, by connecting it to a computer with nvOC that has already booted and clicking the ubuntu launcher at the top left and typing

gp

then click Gparted. Find the sdb drive select the larger partition; it it is mounted unmount it; then rightclick and select resize and set the max size.

click the green checkmark to execute the change, wait for completion and it should be ~17gb larger.

I will do this + add the cmds to enable Claymore to use 16gb VM in the next version.

This is starting to be very frustrating overall, after 8 hours it just "froze" no crash, no failure just frozen... Had to hard reset it.

Another question is, what is people's variance on hashrate? I have my go up and down quite often between 177-180. Sometimes goes down to 175. Anyone else have variance with mining? Is this caused by dual mining?

I am starting to think a possible hardware failure somewhere with the lack of stability in the rig..

Dual mining is always less stable, especially with OC and powerlimit. What ram, PSU, and CPU are you using?

Humm something to consider, when I use to do this dual mining wasn't even an option. Here is the info you requested:
PSU: Seasonic 1050
CPU: Intel Celeron g3930
RAM: Crucial 4GB.

Might be more stable with 16gb of virtual ram; Claymore intermittently uses the CPU intensively and 4GB might not always be enough of a buffer for your cards.

To increase stability you could also try raising your powerlimit slightly and lowering dcri,

I have raised the powerlimit on all the cards, which I think helped. Do you think adding more RAM would help it? Could get at least another 4GB DIMM.

Most likely; but its one of those things that's almost impossible to isolate; so its hard to say what actually makes the difference.

Well RAM is cheap it wouldn't hurt not including, can never have enough DIMMs sitting around lmao. Just ordered and will have it on Tuesday. Love amazon prime. Thanks fullzero