Topic: [ mining os ] nvoc - page 313. (Read 418549 times)

Same question as before but with pictures, miner is hashing away when suddenly the whole OS slows down to a snail pace where i have to wait for 20 seconds for every action to go through and the hash rate is cut by 50% with the GPUs doing this strange hashing pattern:
https://i.imgur.com/wts4CgG.jpg

Please advise, this happens on any pool i try, in both dual mining and ETH only mode, across multiple overclocks..

This is a soft crash; if you have already tried lower OC; it is most likely being caused by too low of a powerlimit.

What GPUs / clocks / powerlimits are you using?

7 x gigabyte 1070 FE, each at 120 pl and clocked +200/+1600, turns out this also happens in ETH only mode, not just dual mining.

any suggestions?

If you want to keep that OC, you will need more power. 120 is not enough to maintain that OC (based on from my experience with my 1070s) I had to give them at least 135-145 to do +200/1600 solo mining ETH.

i see, i was going by UberDaemon's settings since i ended up getting the same parts as his build.

I have dialed my 1070 FE cards back a bit in order to find higher stability. My current settings below have been running on my 1070 FE rig for 121 hours (for ETH-only mining):

core OC: 0 (I see absolutely no hashrate increase when mining ETH and OCing core speed)
Mem OC: 1450

Power Limit: 120W

Fan speed 90% (these Founders Ed. cards run very hot compared to my EVGA and MSI cards. I had one die on me a few days ago after running avg temps of 62C. I don't know if it was heat-related, but I bumped up my fan speeds after that just in case).

One died with avg temps of 62?!? holy hell i've been running these fuckers at 70c round the clock! these are an overheating nightmare indeed, i've been planing on buying 4 140mm case fans and slapping them on the intake side of the rid, cant hurt...

UberDaemon

newbie

Activity: 51

Merit: 0

Quote from: Nexillus on June 28, 2017, 03:02:49 PM

Same question as before but with pictures, miner is hashing away when suddenly the whole OS slows down to a snail pace where i have to wait for 20 seconds for every action to go through and the hash rate is cut by 50% with the GPUs doing this strange hashing pattern:
https://i.imgur.com/wts4CgG.jpg

Please advise, this happens on any pool i try, in both dual mining and ETH only mode, across multiple overclocks..

This is a soft crash; if you have already tried lower OC; it is most likely being caused by too low of a powerlimit.

What GPUs / clocks / powerlimits are you using?

7 x gigabyte 1070 FE, each at 120 pl and clocked +200/+1600, turns out this also happens in ETH only mode, not just dual mining.

any suggestions?

If you want to keep that OC, you will need more power. 120 is not enough to maintain that OC (based on from my experience with my 1070s) I had to give them at least 135-145 to do +200/1600 solo mining ETH.

i see, i was going by UberDaemon's settings since i ended up getting the same parts as his build.

I have dialed my 1070 FE cards back a bit in order to find higher stability. My current settings below have been running on my 1070 FE rig for 121 hours (for ETH-only mining):

core OC: 0 (I see absolutely no hashrate increase when mining ETH and OCing core speed)
Mem OC: 1450

Power Limit: 120W

Fan speed 90% (these Founders Ed. cards run very hot compared to my EVGA and MSI cards. I had one die on me a few days ago after running avg temps of 62C. I don't know if it was heat-related, but I bumped up my fan speeds after that just in case).

OverEasy

sr. member

Activity: 301

Merit: 251

Ok I think I am on to something now. While on nvOC I opened the Nvidia tools and noticed that my 1070 was fully editable while the 1060 was not.

I had this card in another rig (NOT nvOC) and was able to control it with EVGA Precision so I know it CAN be done.

This is a very popular card right now, the 3gb 1060, so would be nice if we can figure out how to set clocks in nvOC

Thanks!

tempgoga

newbie

Activity: 29

Merit: 0

Quote from: bibyfok on June 28, 2017, 03:00:11 PM

Same question as before but with pictures, miner is hashing away when suddenly the whole OS slows down to a snail pace where i have to wait for 20 seconds for every action to go through and the hash rate is cut by 50% with the GPUs doing this strange hashing pattern:
https://i.imgur.com/wts4CgG.jpg

Please advise, this happens on any pool i try, in both dual mining and ETH only mode, across multiple overclocks..

This is a soft crash; if you have already tried lower OC; it is most likely being caused by too low of a powerlimit.

What GPUs / clocks / powerlimits are you using?

7 x gigabyte 1070 FE, each at 120 pl and clocked +200/+1600, turns out this also happens in ETH only mode, not just dual mining.

any suggestions?

If you want to keep that OC, you will need more power. 120 is not enough to maintain that OC (based on from my experience with my 1070s) I had to give them at least 135-145 to do +200/1600 solo mining ETH.

i see, i was going by UberDaemon's settings since i ended up getting the same parts as his build.

Right now it should be more profitable to use genoil (which unless I am mistaken; can only single mine) as you should be able to net at least +5% from Claymore single mode (with outright higher hashrate and no 2% fee).

I am not sure at all what the best way to avoid soft crashes is with genoil; if anyone can find OPT settings that are stable with high memory clocks let me know.

Currently testing it, but am noticing that it does not have the nice web API to connect too like claymore lol. I will get back with you later today with my settings.

Thanks man,
I just finished testing and for some reason the same overclock (200/1600) @ 125 pl while still soft crashes with genoil, it doesnt cripple the whole system to the point where i have to restart the rig, and for the same clocks it does hash around 10Mh/s faster.

BUT, i've noticed something else, Claymore now hashes SLOWER with CUDA 8 then with the previous version (218Mh/s vs 222Mh/s), and i was planning on dual mining, and now its slower?

Nexillus

full member

Activity: 169

Merit: 100

When running GENOIL is there a way to see card temperatures? I cant find any setting?
If there is no settings, is there any app that we can install ?
Thanks

GENOIL seems does not have a way to put it on screen like claymore however can do it manually by hitting F12 to open guake then typing "nvidia-smi" should show you all the GPUs watts, temps and loads

OverEasy

sr. member

Activity: 301

Merit: 251

You know I have that 1060 plugged directly into the MoBo. Let me get it on a riser...I'll let ya know if that's it. I just thought of that lol...

Nope. On a riser now. Same issue.

Now let me switch slots on the MoBo...brb.. Nope same issue..

HEY! Just made a change to MoBo bios. Had some alternate pcie slot setting that was checked.

Damn that wasnt it. It just skips right over GPU:1 (GPU:1 is mining btw, just cannot control anything)

Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 100.

Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 350.

ERROR: Error resolving target specification 'gpu:2' (No targets match target specification), specified in assignment
'[gpu:2]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:2' (No targets match target specification), specified in assignment
'[gpu:2]/GPUMemoryTransferRateOffset[3]=100'.

OverEasy

sr. member

Activity: 301

Merit: 251

Quote from: Nexillus on June 28, 2017, 01:09:48 PM

Quote from: OverEasy on June 28, 2017, 12:25:00 PM

Quote from: OverEasy on June 28, 2017, 09:34:02 AM

Clock speeds not working on second card.

Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 100.

Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 350.

Where is gpu:1 ?

My oneBash -

INDIVIDUAL_CLOCKS="YES" # YES NO

# Set individual clocks here if INDIVIDUAL_CLOCKS="YES"
__CORE_OVERCLOCK_0=100
MEMORY_OVERCLOCK_0=350

__CORE_OVERCLOCK_1=100
MEMORY_OVERCLOCK_1=800

Thought maybe my USB was too slow so I changed oneBash to "slow" usb.
Same thing is happening. Clocks only getting set on GPU:0

Can't set fan manually at all.

Anyone have any ideas here?

Had this once and it was a bad image on the USB. Just re-flashed and was fixed. Was kinda weird but hasn't happened since.

You are not the first member to report this happening: if you still have this image which produces this one GPU not setting its fan: please make these changes to oneBash and let me know what happens.

in the implementation section most likely line 483:

Code:

GPUS=$(nvidia-smi --query-gpu=count --format=csv,noheader,nounits | tail -1)

change this to:

Code:

GPUS=14

save, restart the mining process

If the problem is an indexing error: then the second GPU should have its fan properly set: however if you are using 2 GPUs; you should also see error messages for each cmd for 12 GPUs that you don't have.

If the second GPU does set the fans properly note its index number.

Let me know the result; and hopefully it will only take a new oneBash to fix this.

I made the change and here is my result. GPU:1 clocks still not setting

dos2unix: converting file /media/m1/1263-A96E/oneBash to Unix format ...

workername: 136

rig IP: 10.0.0.136
Power limit for GPU 0000:04:00.0 was set to 125.00 W from 125.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

All done.
Power limit for GPU 0000:22:00.0 was set to 125.00 W from 125.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

All done.
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found
No devices were found

Wed Jun 28 16:48:42 EDT 2017
Action: Installing daemon (12.0.76279) for 'systemd' ...
installing /etc/systemd/system/teamviewerd.service (/opt/teamviewer/tv_bin/script/teamviewerd.service)
Try: systemctl enable teamviewerd.service
systemctl start teamviewerd.service

Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 100.

Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 350.

ERROR: Error resolving target specification 'gpu:2' (No targets match target specification), specified in assignment
'[gpu:2]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:2' (No targets match target specification), specified in assignment
'[gpu:2]/GPUMemoryTransferRateOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:3' (No targets match target specification), specified in assignment
'[gpu:3]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:3' (No targets match target specification), specified in assignment
'[gpu:3]/GPUMemoryTransferRateOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:4' (No targets match target specification), specified in assignment
'[gpu:4]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:4' (No targets match target specification), specified in assignment
'[gpu:4]/GPUMemoryTransferRateOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:5' (No targets match target specification), specified in assignment
'[gpu:5]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:5' (No targets match target specification), specified in assignment
'[gpu:5]/GPUMemoryTransferRateOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:6' (No targets match target specification), specified in assignment
'[gpu:6]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:6' (No targets match target specification), specified in assignment
'[gpu:6]/GPUMemoryTransferRateOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:7' (No targets match target specification), specified in assignment
'[gpu:7]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:7' (No targets match target specification), specified in assignment
'[gpu:7]/GPUMemoryTransferRateOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:8' (No targets match target specification), specified in assignment
'[gpu:8]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:8' (No targets match target specification), specified in assignment
'[gpu:8]/GPUMemoryTransferRateOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:9' (No targets match target specification), specified in assignment
'[gpu:9]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:9' (No targets match target specification), specified in assignment
'[gpu:9]/GPUMemoryTransferRateOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:10' (No targets match target specification), specified in assignment
'[gpu:10]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:10' (No targets match target specification), specified in assignment
'[gpu:10]/GPUMemoryTransferRateOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:11' (No targets match target specification), specified in assignment
'[gpu:11]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:11' (No targets match target specification), specified in assignment
'[gpu:11]/GPUMemoryTransferRateOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:12' (No targets match target specification), specified in assignment
'[gpu:12]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:12' (No targets match target specification), specified in assignment
'[gpu:12]/GPUMemoryTransferRateOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:13' (No targets match target specification), specified in assignment
'[gpu:13]/GPUGraphicsClockOffset[3]=100'.

ERROR: Error resolving target specification 'gpu:13' (No targets match target specification), specified in assignment
'[gpu:13]/GPUMemoryTransferRateOffset[3]=100'.

Attribute 'GPUFanControlState' (m1-desktop:0[gpu:0]) assigned value 0.

ERROR: Error resolving target specification 'gpu:2' (No targets match target specification), specified in assignment
'[gpu:2]/GPUFanControlState=0'.

ERROR: Error resolving target specification 'gpu:3' (No targets match target specification), specified in assignment
'[gpu:3]/GPUFanControlState=0'.

ERROR: Error resolving target specification 'gpu:4' (No targets match target specification), specified in assignment
'[gpu:4]/GPUFanControlState=0'.

ERROR: Error resolving target specification 'gpu:5' (No targets match target specification), specified in assignment
'[gpu:5]/GPUFanControlState=0'.

ERROR: Error resolving target specification 'gpu:6' (No targets match target specification), specified in assignment
'[gpu:6]/GPUFanControlState=0'.

ERROR: Error resolving target specification 'gpu:7' (No targets match target specification), specified in assignment
'[gpu:7]/GPUFanControlState=0'.

ERROR: Error resolving target specification 'gpu:8' (No targets match target specification), specified in assignment
'[gpu:8]/GPUFanControlState=0'.

ERROR: Error resolving target specification 'gpu:9' (No targets match target specification), specified in assignment
'[gpu:9]/GPUFanControlState=0'.

ERROR: Error resolving target specification 'gpu:10' (No targets match target specification), specified in assignment
'[gpu:10]/GPUFanControlState=0'.

ERROR: Error resolving target specification 'gpu:11' (No targets match target specification), specified in assignment
'[gpu:11]/GPUFanControlState=0'.

ERROR: Error resolving target specification 'gpu:12' (No targets match target specification), specified in assignment
'[gpu:12]/GPUFanControlState=0'.

ERROR: Error resolving target specification 'gpu:13' (No targets match target specification), specified in assignment
'[gpu:13]/GPUFanControlState=0'.

Nexillus

full member

Activity: 169

Merit: 100

Anyone else have problems with Nanopool right now? It seems to be calculating the hash but not getting a reported hash. It is also still receiving shares and going over to genoil it is also saying accepted shares.

https://eth.nanopool.org/account/0xdc04faa92bb8fa95ed93a4a48bb72554985a97f2 to see what I'm talking about.

Nexillus

full member

Activity: 169

Merit: 100

Quote from: philipma1957 on June 28, 2017, 12:09:25 PM

Same question as before but with pictures, miner is hashing away when suddenly the whole OS slows down to a snail pace where i have to wait for 20 seconds for every action to go through and the hash rate is cut by 50% with the GPUs doing this strange hashing pattern:

Please advise, this happens on any pool i try, in both dual mining and ETH only mode, across multiple overclocks..

This is a soft crash; if you have already tried lower OC; it is most likely being caused by too low of a powerlimit.

What GPUs / clocks / powerlimits are you using?

7 x gigabyte 1070 FE, each at 120 pl and clocked +200/+1600, turns out this also happens in ETH only mode, not just dual mining.

any suggestions?

If you want to keep that OC, you will need more power. 120 is not enough to maintain that OC (based on from my experience with my 1070s) I had to give them at least 135-145 to do +200/1600 solo mining ETH.

i see, i was going by UberDaemon's settings since i ended up getting the same parts as his build.

Right now it should be more profitable to use genoil (which unless I am mistaken; can only single mine) as you should be able to net at least +5% from Claymore single mode (with outright higher hashrate and no 2% fee).

I am not sure at all what the best way to avoid soft crashes is with genoil; if anyone can find OPT settings that are stable with high memory clocks let me know.

Currently testing it, but am noticing that it does not have the nice web API to connect too like claymore lol. I will get back with you later today with my settings.

bibyfok

full member

Activity: 160

Merit: 100

When running GENOIL is there a way to see card temperatures? I cant find any setting?
If there is no settings, is there any app that we can install ?
Thanks

ATCkit

hero member

Activity: 786

Merit: 1000

Quote from: ATCkit on June 28, 2017, 11:28:07 AM

Quote from: xleejohnx on June 27, 2017, 08:42:54 PM

Quote from: ATCkit on June 27, 2017, 08:40:33 PM

Quote from: xleejohnx on June 27, 2017, 06:31:12 PM

Quote from: ATCkit on June 27, 2017, 06:24:51 PM

Quote from: xleejohnx on June 27, 2017, 01:31:06 PM

Quote from: ATCkit on June 27, 2017, 11:54:19 AM

So I've imaged my USB, set up onebash & plugged the USB into my rig. The monitor immediately showed " grub rescue".

Questions:
1. I assume this the process of converting the file from windows to linux- correct?

2. If so, this process has been running for 30 minutes. How long should it take?

This shouldn't happen.
Try flashing the USB again

Flashed 3 times. Even left fullzero's oneBash mining info intact on the 3rd attempt. Same result.

Maybe it won't work with this MoBo?:

http://www.asrock.com/mb/Intel/Z170A-X13.1/

what image are you using?

Did you forget to extract the image from the zip before imaging?

v0016. Yes I extracted it. I'll try v0017.

what usb do you have? i would get a 32gb one if you can

64 GB SANDISK ULTRA. Downloading v0017 now.

is this it?

https://www.amazon.com/SanDisk-Ultra-Transfer-Speeds-SDCZ48-064G-UAM46/dp/B00KYK2ABI/ref=sr_1_1?

this works for sure:

https://www.amazon.com/Lexar-JumpDrive-32GB-Flash-Drive/dp/B00T61JM4E/ref=sr_1_1?

https://www.amazon.com/gp/product/B012PKT4QS/ref=oh_aui_detailpage_o04_s00?

I have had no trouble with the 2 above.

I have had trouble with some sandisk loading smOS linux

Yes-that's the one I am using Philip.
Guys, thanks for your help & patience. Everything worked fine this time. The only I did different was use a newer PC.

Anyhow, I'm mining at 39 MHS on 2x 1060s and the whole rig is using only 171 watts. Before the mining began, it was 65 watts. So it looks like I am using less than 60 watts per GPU.

Nexillus

full member

Activity: 169

Merit: 100

Quote from: OverEasy on June 28, 2017, 12:25:00 PM

Quote from: OverEasy on June 28, 2017, 09:34:02 AM

Clock speeds not working on second card.

Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 100.

Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 350.

Where is gpu:1 ?

My oneBash -

INDIVIDUAL_CLOCKS="YES" # YES NO

# Set individual clocks here if INDIVIDUAL_CLOCKS="YES"
__CORE_OVERCLOCK_0=100
MEMORY_OVERCLOCK_0=350

__CORE_OVERCLOCK_1=100
MEMORY_OVERCLOCK_1=800

Thought maybe my USB was too slow so I changed oneBash to "slow" usb.
Same thing is happening. Clocks only getting set on GPU:0

Can't set fan manually at all.

Anyone have any ideas here?

Had this once and it was a bad image on the USB. Just re-flashed and was fixed. Was kinda weird but hasn't happened since.

OverEasy

sr. member

Activity: 301

Merit: 251

Quote from: OverEasy on June 28, 2017, 09:34:02 AM

Clock speeds not working on second card.

Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 100.

Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 350.

Where is gpu:1 ?

My oneBash -

INDIVIDUAL_CLOCKS="YES" # YES NO

# Set individual clocks here if INDIVIDUAL_CLOCKS="YES"
__CORE_OVERCLOCK_0=100
MEMORY_OVERCLOCK_0=350

__CORE_OVERCLOCK_1=100
MEMORY_OVERCLOCK_1=800

Thought maybe my USB was too slow so I changed oneBash to "slow" usb.
Same thing is happening. Clocks only getting set on GPU:0

Can't set fan manually at all.

Anyone have any ideas here?

Nexillus

full member

Activity: 169

Merit: 100

Also with VER0017 is a single miner unlike claymore? (wanted to clarify)

philipma1957

legendary

Activity: 4354

Merit: 9201

'The right to privacy matters'

Quote from: ATCkit on June 28, 2017, 11:28:07 AM

Quote from: xleejohnx on June 27, 2017, 08:42:54 PM

Quote from: ATCkit on June 27, 2017, 08:40:33 PM

Quote from: xleejohnx on June 27, 2017, 06:31:12 PM

Quote from: ATCkit on June 27, 2017, 06:24:51 PM

Quote from: xleejohnx on June 27, 2017, 01:31:06 PM

Quote from: ATCkit on June 27, 2017, 11:54:19 AM

So I've imaged my USB, set up onebash & plugged the USB into my rig. The monitor immediately showed " grub rescue".

Questions:
1. I assume this the process of converting the file from windows to linux- correct?

2. If so, this process has been running for 30 minutes. How long should it take?

This shouldn't happen.
Try flashing the USB again

Flashed 3 times. Even left fullzero's oneBash mining info intact on the 3rd attempt. Same result.

Maybe it won't work with this MoBo?:

http://www.asrock.com/mb/Intel/Z170A-X13.1/

what image are you using?

Did you forget to extract the image from the zip before imaging?

v0016. Yes I extracted it. I'll try v0017.

what usb do you have? i would get a 32gb one if you can

64 GB SANDISK ULTRA. Downloading v0017 now.

is this it?

https://www.amazon.com/SanDisk-Ultra-Transfer-Speeds-SDCZ48-064G-UAM46/dp/B00KYK2ABI/ref=sr_1_1?

this works for sure:

https://www.amazon.com/Lexar-JumpDrive-32GB-Flash-Drive/dp/B00T61JM4E/ref=sr_1_1?

https://www.amazon.com/gp/product/B012PKT4QS/ref=oh_aui_detailpage_o04_s00?

I have had no trouble with the 2 above.

I have had trouble with some sandisk loading smOS linux

ATCkit

hero member

Activity: 786

Merit: 1000

Quote from: xleejohnx on June 27, 2017, 08:42:54 PM

Quote from: ATCkit on June 27, 2017, 08:40:33 PM

Quote from: xleejohnx on June 27, 2017, 06:31:12 PM

Quote from: ATCkit on June 27, 2017, 06:24:51 PM

Quote from: xleejohnx on June 27, 2017, 01:31:06 PM

Quote from: ATCkit on June 27, 2017, 11:54:19 AM

So I've imaged my USB, set up onebash & plugged the USB into my rig. The monitor immediately showed " grub rescue".

Questions:
1. I assume this the process of converting the file from windows to linux- correct?

2. If so, this process has been running for 30 minutes. How long should it take?

This shouldn't happen.
Try flashing the USB again

Flashed 3 times. Even left fullzero's oneBash mining info intact on the 3rd attempt. Same result.

Maybe it won't work with this MoBo?:

http://www.asrock.com/mb/Intel/Z170A-X13.1/

what image are you using?

Did you forget to extract the image from the zip before imaging?

v0016. Yes I extracted it. I'll try v0017.

what usb do you have? i would get a 32gb one if you can

64 GB SANDISK ULTRA. Downloading v0017 now.

OverEasy

sr. member

Activity: 301

Merit: 251

Clock speeds not working on second card.

Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 100.

Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 350.

Where is gpu:1 ?

My oneBash -

INDIVIDUAL_CLOCKS="YES" # YES NO

# Set individual clocks here if INDIVIDUAL_CLOCKS="YES"
__CORE_OVERCLOCK_0=100
MEMORY_OVERCLOCK_0=350

__CORE_OVERCLOCK_1=100
MEMORY_OVERCLOCK_1=800

tempgoga

newbie

Activity: 29

Merit: 0

Same question as before but with pictures, miner is hashing away when suddenly the whole OS slows down to a snail pace where i have to wait for 20 seconds for every action to go through and the hash rate is cut by 50% with the GPUs doing this strange hashing pattern:
https://i.imgur.com/wts4CgG.jpg

Please advise, this happens on any pool i try, in both dual mining and ETH only mode, across multiple overclocks..

This is a soft crash; if you have already tried lower OC; it is most likely being caused by too low of a powerlimit.

What GPUs / clocks / powerlimits are you using?

7 x gigabyte 1070 FE, each at 120 pl and clocked +200/+1600, turns out this also happens in ETH only mode, not just dual mining.

any suggestions?

If you want to keep that OC, you will need more power. 120 is not enough to maintain that OC (based on from my experience with my 1070s) I had to give them at least 135-145 to do +200/1600 solo mining ETH.

i see, i was going by UberDaemon's settings since i ended up getting the same parts as his build.

OverEasy

sr. member

Activity: 301

Merit: 251

Ok I am up and running on new ver 17 of nvOC. THANK YOU!!!

Using Genoil and mining ETH getting this error

Attribute 'GPUFanControlState' (m1-desktop:0[gpu:0]) assigned value 1.

Attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:0]) assigned value 75.

ERROR: Error assigning value 75 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:1]) as specified in assignment
'[fan:1]/GPUTargetFanSpeed=75' (Unknown Error).

Also using Genoil how do I determine which GPU is which? I have a 1060 and a 1070 and I want to set clocks but am not sure which is which. Any command like Claymores "S" I can use?

Nexillus

full member

Activity: 169

Merit: 100