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

I just got around to test v16.

Same error messages like below.

Getting infinite loop.

LCD connected to mobo graphics (like always in v15 and BIOS set to on board graphics not PCI)

Will test on PCI graphics later thi PM - hopefully no more infinite loops - will post results later.

Much better boot-up speed, this time can use USB3 port fully compatible with build?

I just added 5 more 20A circuits in my warehouse - fun times begins!

Hi there,
I just built my first mining rig, well, trying to, still awaiting for the risers, so I installed v16 and it's not mounting the oneBash partition automatically, also I set up an account with suprnova and updated my LBC details in the oneBash file I keep getting a Stratum Authentication Error, my worker is name.BLA and I set the password as 'x' as seen below in the oneBash source, nothing at all. Anyone have the same problem?

Yeah so, I have the HDMI connected to the first PCI-E x16 slot, unfortunately it seems like it is still only registering GPU (0-4) so only 5.

To clarify, its the "Second" PCI-E x16 slot that seems like it's not working, have tested it solo, it works, its just that slot that's not showing any of the GPU's during the mining process. Perhaps its a power to that pci-e x16 slot issue? 

So I tried the xorg="OK" and it doesn't seem to be working either, still showing me 5 of the 6 GPU.

MSI Z270-A Pro & 6 ASUS Dual OC 1070.

I have HDMI cable connected to primary x16 PCIE port. But thanks for your prompt answers, fullzero!

Sorry for the delay!

Alright so something maybe worth mentioning, the boots seem to be taking significantly more time then before. (It's a problem I should be able to figure out once the GPU's are all running,

So the initial test returned:

1:00.0 VGA compatible controller: Nvidia Corporation Device 1b81 (rev a1)
3:00.0 VGA compatible controller: Nvidia Corporation Device 1b81 (rev a1)
6:00.0 VGA compatible controller: Nvidia Corporation Device 1b81 (rev a1)
7:00.0 VGA compatible controller: Nvidia Corporation Device 1b81 (rev a1)
8:00.0 VGA compatible controller: Nvidia Corporation Device 1b81 (rev a1)
9:00.0 VGA compatible controller: Nvidia Corporation Device 1b81 (rev a1)

I was waiting for a solid 15 minutes for it to boot, and it wasn't so I used a different USB to boot since I believe the first USB might have been corrupted from all the restarts.

After here is what I got:
1:00.0 VGA compatible controller: Nvidia Corporation Device 1b81 (rev a1)
3:00.0 VGA compatible controller: Nvidia Corporation Device 1b81 (rev a1)
6:00.0 VGA compatible controller: Nvidia Corporation Device 1b81 (rev a1)
7:00.0 VGA compatible controller: Nvidia Corporation Device 1b81 (rev a1)
8:00.0 VGA compatible controller: Nvidia Corporation Device 1b81 (rev a1)
9:00.0 VGA compatible controller: Nvidia Corporation Device 1b81 (rev a1)

reserved

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.

Version 006 risers, with 2 risers plugged per port on my PSU using 6 pin to sata to molex, thanks for the help!

Thank you, UberDaemon. I've already done that but to no avail. Out of curiousity, are you usng the same asus mobo? if so, which nvOC are you using? Thanks

I don't know if this is your issue or not, but worth giving it a shot:

Thank you sir! Etcher worked perfectly.

So I imaged the USB properly and replaced oneBash with my own configured one. Trying to boot however seems to suffer from repeated reboots (5+ so far).

Here are my specs:

- Asus Prime Z270-p. It's not listed under fully supported boards. I still used the "all mobo nvOC" for it. Please let me know if I should use another specific image.
- 6 *  MSI GTX 1060
- Intel pentium 1151 processor

BIOS changes
- Above 4G: enabled
- Primary display: PCIE
- Audio controller: disabled

Please let me know if I missed something.

I am mining ETH and am overclocked (~30.9 MH/sec on 1070 Founders Ed cards and ~29.5 MH/sec on a frankenstein rig with 3 different kinds of 1070 cards).

I've tried three different versions of nvOC now and I still just CAN'T GET THE OVERCLOCKS TO WORK!

I've tried individual and whole system and I even see the overclocks apply when onebash starts - but they aren't sticking.

I'm mining eth and in Windows with Afterburner I set all 5 cards (2 1070s and 3 1060s) to core +75 and mem +800 and I get 132mh/s

Using nvOC and trying to set the same overclocks, I get 120mh/s.

It's really frustrating. I just don't understand. Does Claymore set everything to factory clocks when it starts or something?

Anyone else mining ETH and managing to ue overclocking?

Ok, just checking. 

I'm having a problem with one of my 1070s (Gigabyte Founders Ed.) that was running at 62C.  It lights up at POST, but then after about 30 seconds the light goes out (though the fan stays on) and it's not recognized by claymore.  I pulled it for further testing.  Pretty sure it's failed based on first attempt to get it to start in another machine on my test bench (same behavior; it lights up and then after 30 secs the light goes out and I don't get video).  I'm thinking maybe it was heat, but even 62C isn't outrageous.

Anyone else managed to kill a 1070? 

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.

Hello! I ran into a problem with my Msi Z270-A motherboard, so I am using 6 Asus dual 1070 OC graphics cards, and only 5 of them are being picked up. The second pci-e riser doesn't seem to be working. I tested the port, it does work and I have tested the riser cables, they all seem to be working. I am a little bit of a loss for words on what I should do to fix this problem.

Average temp of them are 50C and one in the center hottest it gets to is 58C.

What are your temps like on those 1070s?

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...

This is quite odd, but after about 20 hours I received this error on the new ver16. Thinking it maybe a bad OC, I lowered it slightly however after 14 more hours it crashed again.

When it happens, I have to hard reset the miner to come back online.

To me this makes no sense since buffer for DAG errors should only be for 2GB cards and I have 6x 1070 on this rig :/

GPU 0, CUDA error 6- cannot write buffer for DAG
GPU 5, CUDA error 6- cannot write buffer for DAG
GPU 1, CUDA error 6- cannot write buffer for DAG
GPU 3, CUDA error 6- cannot write buffer for DAG
GPU 2, CUDA error 6- cannot write buffer for DAG
GPU 4, CUDA error 6- cannot write buffer for DAG

GPUmienr cu_k01 failed 6 the launch timed out and was terminted

I also get the failed message for all 6 GPUs on this rig.

For the time being I have rolled this rig back to ver15.