cuda error out of memory nicehash что делать

Ошибка «out of memory» при алгоритме NeoScrypt

Stee1Arm

Новичок

Добрый вечер.
Подскажите пожалуйста, в чем может быть причина:
Майню на Nicehash, при переключение на алгоритм NeoScrypt вылетает ошибка «out of memory».
Майнер перезагружается и с ново выдает ту же ошибку, так по кругу пока не поменяет алгоритм.
Когда выставляю NeoScrypt только на 2 картах, все работает хорошо, больше 2-х вылетает с ошибкой.

Ферма:
8x Palit GTX 1080 Ti JetStream 11GB
1x Corsair 1000W 80+ Gold RM1000i
3x Corsair 850W 80+ Gold RM850
Asus Prime Z270-A + G4400 3.3Ghz 3MB
8GB DDR4 2400Mhz
Kingston SSD 120GB
Файл подкачки ставил 16000 и 24000 не помогает.

Бывалый

pilat200

Свой человек

Источник

Nicehash Miner 2.0.1.1 CUDA error ‘out of memory’ in func ‘cuda_eq_run’ #1294

Comments

Hitu63 commented Sep 30, 2017

Hey,
i’m using nicehash miner 2.0.1.1 with Win 10 pro 64bit.
My Rig is build with 4GB RAM and 8x GTX1080ti.

Sometimes, nicehash miner is freezing after a couple of hours mining, and showing:

CUDA error ‘out of memory’ in func ‘cuda_eq_run’ line

I already set up the virtual memory to:
Startsize: 500MB
Maximumsize: 90.000MB

Someone knows a solution or reason for this problem?

The text was updated successfully, but these errors were encountered:

Timoulis commented Oct 1, 2017 •

Really. 4GB RAM and 8X GTX 1080ti?
Only Windows need the half of it.
OS can not handle the virtual memory because there is no left of it.
Add more RAM and you will be ok.

j2inet commented Nov 1, 2017

I get the same error consistently at startup when it’s trying to test the mining algorithms.

GTX 1080 with 8 gigs video RAM
16 gigs system memory
Core-i7 6700 @ 3.4 GHz

It works fine on another system I have with a GTX1080 and a GTX1060.

ksze commented Nov 3, 2017

Pretty similar issue as @j2inet.

GTX 1080 with 8 GiB video RAM
32 GiB RAM
Core i7-6700
Windows 10 Pro 64-bit Fall Creator Update
GeForce driver version 388.13
CUDA 9.0.176

mitch619911 commented Dec 3, 2017

I am running 2 x GTX 1060 3GB cards with 4GB ram and am getting this error. still need more ram.
I have been running for almost a year without errors and now I get it?

mitch619911 commented Dec 3, 2017

I’m using 2.0.1.5 Beta.
increasing virtual memory?

mitch619911 commented Dec 3, 2017

Starting to happen hourly 🙁

mitch619911 commented Dec 3, 2017

Followed that post but it looks like its smaller now?

mitch619911 commented Dec 3, 2017

I tried this:
https://mitchs.tech/i/188623.png
Gonna run it for a few hours and see what happens.

mitch619911 commented Dec 4, 2017

Please note that we will fix this issue with the next release. Till then we suggest you disable NeoScrypt in your miner. Thank you for understanding.

Kind regards,
NiceHash Team»

Johnb21 commented Dec 23, 2017

10ktoday commented Dec 28, 2017

westy666 commented Dec 29, 2017

Same issue here as well with over the past couple of days with 2.0.1.5 beta.

Have 8gb systems ram running 2×1070’s and 1×1060 with Windows 10 and latest Nvidia drivers.

Just seen it happen in front of my eye’s. Seems to get the error then keep restarting the miner window then eventually freezes.

gofres commented Dec 30, 2017

I have identical set up to OP and getting the same issue using both the latest NH and NHML. It ran stable all over the Christmas period but has since been crashing a few times a day.

Virtual memory set to 32gb which should be plenty.

I’ve sat and watched it run for ages to catch an error. It seems like each algo switch adds more load to RAM until it crashes. Haven’t tried setting a single algo yet to test.

Don’t get any issues using other miners.

Anyone found a solution yet?

CyrptoCraig commented Jan 5, 2018

I just had this same issue and went to google for help but everyone was just on about the VM and i didn’t think it could have been that.

I then looked at all my cards and thought i’ll get rid of any OC settings on afterburner and it worked fine.

I have 1 1060 and when i turned down the memory clock on afterburner it worked fine so might be worth checking overclocking settings.

Hope that helps others.

ThePhoneGuy65 commented Jan 10, 2018

just tried to open Google chrome, while mining w/ 3 cards. got an error. » not enough memory to open »
tried again. display was flashing until I stopped the miner. Immediately opened.
so. virtual memory.

morphk3t commented Jan 11, 2018

I have found myself in the similar situation that people have above. I currently have a 6x 1070 Asus Turbo that was setup with Nicehash and made a few changes by changing the VM to 16GB and also adding the following environmental variables:

Name: GPU_FORCE_64BIT_PTR
Value: 1
Name: GPU_MAX_ALLOC_PERCENT
Value: 100
Name: GPU_SINGLE_ALLOC_PERCENT
Value: 100
Name: GPU_MAX_HEAP_SIZE
Value: 100
Name: GPU_USE_SYNC_OBJECTS
Value: 1

After doing so it seems to have fixed the issue, or so I thought. Seems that when it runs neoscrypt is where it crashes and restarts the miner. Have not seeing it do it on any other algo. If I recall correctly, one can disable certain algos from mining, no?

morphk3t commented Jan 11, 2018 •

NVM, seems I found the issue listed here, if issue is related with neoscrypt: https://github.com/nicehash/excavator/issues/78

duracoin commented Jan 11, 2018

i had the same issue with a 6 card rig. Solution is to set pci slots to gen1 in bios and also set virtual memery in windows performance settings to the following: min:4000 max:45000

after this it works fine. if you have more cards keep increasing virtual memory untill it is stable. i had mine at 35000 before i made the changes now its fine.

ThePhoneGuy65 commented Jan 12, 2018

I do have my GTX cards set to Gen2. so I will try that for sure. I adjusted the virtual Memory already.. but will double check & report back. Thank you » Duracoin «.

mitch619911 commented Jan 18, 2018

Seems to be Nicehash this time.
DIsable Neo, https://mitchs.tech/i/2073cd.gif

ellensp commented Jun 13, 2018

I just struck this error. I upgraded from 5 * 1060 6gb rig to a 6 *1060 6gb ie added 1 more GPU.
PhoenixMiner and Claymore’s Dual Ethereum also reported memory allocation issues in cuda.
The issue for me was the swap size. I had it set to 16000mb but it needed more. Is now working with 24000MB swap. Why? I dont know but I suspect the cuda drivers generate the DAG in real memory for all cards then move it into the GPU’s memory. Since the dag at present is

slonuh commented Jul 4, 2018

Elensp, brilliant solution! It helps me.
So everybody, you should set minimum Windows Virtual memory swap according summ memory of your GPU’s.

Источник

Исправляем ошибку при майнинге Ethereum на GeForce 1050

Все кто занимается добычей криптовалюты, рано или поздно сталкиваются с определенными проблемами в работе оборудования. Часто, решаются они быстро, а в большинстве случаев, вовсе проходят сами, после автоматического обновления ПО.

Сегодня же, поговорим о ошибке «CUDA error», а если быть точнее, то о том, как её победить. Я лично столкнулся с подобной проблемой, по-этому знаю о чем говорю. Не буду мучить вас предысториями о том, как у меня все начиналось и как я от этого страдал — это лишнее. Давайте сразу приступим к сути вопроса и его решению.

Если вы занимаетесь добычей Ethereum (эфириума), и у вас возникает такая ошибка (ниже выложу скрин), значит мой метод решения именно для вас:

Решение ошибки CUDA error

Шаг 1. На рабочем столе находим «Мой компьютер» нажимаем на него правой кнопкой, и выбираем последний пункт «Свойства»

Шаг 2. Идем по пути: «Дополнительные параметры системы» — «Дополнительно» — «Параметры» — опять «Дополнительно»

Шаг 3. Нажимаем кнопку «Изменить» возле надписи «Виртуальная память»

Шаг 4. Вводим нужную цифру (напомним, что она не должна быть ниже 16 000 Мб)

Собственно все. После таких манипуляций, мой риг сново ожил, а майнинг вернулся на прежний уровень дохода. Для тех кто не понял, что нужно делать, ниже оставлю видео, как это выглядит у меня, а там уже разберетесь. Собственно вот, как и обещал!

[creativ_media type=»youtube» url=»www.youtube.com/watch?v=Y-F-VcsUUpI»]

Не знаю, поможет ли вам этот способ, но мне помог. На самом деле, ошибки связанные с файлом подкачки, довольно таки частые, а данный метод поможет их решить. Всем хорошего майнинга и меньше ошибок при добыче крипты!

Источник

CUDA error ‘out of memory’ in func ‘cuda_neoscrypt::init’ line 1258 #1393

Comments

mkabatek commented Dec 28, 2017

Nicehash v2.0.1.5 Beta, Windows 10

wrkr0-6 | CUDA error ‘out of memory’ in func ‘cuda_neoscrypt::init’ line 1258

wrkr1-7 | CUDA error DRIVER: ‘2’ in func ‘cudahelp::device_thread_init’ line 168

The text was updated successfully, but these errors were encountered:

Tottom commented Dec 30, 2017 •

Hi,
Same issue for me on GeForce GTX 6x 1070 and 2x 1070Ti, CUDA 9.1.85, Nvidia 388.71
CUDA error ‘out of memory’ in func ‘cuda_neoscrypt::init’ line 1258

mkabatek commented Dec 30, 2017

I think it has to do with the amount of RAM in the machine. I only have 4Gb and I read somewhere else that someone added 8GB ram to their system and it fixed the issue.

Should be fixable in software though.

Tottom commented Dec 30, 2017

I do have 8GB memory on the system already. and 32GB swap. maybe i should do less on swap?

mkabatek commented Dec 30, 2017

They ADDED 8Gb of memory, meaning they have 16Gb now. Here is the original thread.

Tottom commented Dec 30, 2017

ic. Another poster says he can run 3x gtx 1070 on 8GB memory, anymore than that then he gets out of memory. so if i run 12x gtx 1070 i need 32GB RAM?

I will get 2x 8GB dimms in the new year only 🙁 and confirm the results on my current 8 card rig.
thanks!

Tottom commented Dec 30, 2017

I have changed my vmem to 96GB. Neoscrypt ran for awhile without failing. still monitoring.

Tottom commented Dec 31, 2017

So i tried 16GB vMem and got the errors more frequently. And on 64GB vMem and had the errors maybe about 20 hours later.

I have now upped my vMem to 98GB and i have not had any further errors in the last 24 hours. I have 6x 1070 and 2x 1070ti cards. OC 150mhz on CPU and 500mhz on memory and 65% TDP.

I have only 8GB physical memory.

remotetech commented Jan 10, 2018

Nicehash v2.0.1.5 Beta, Windows 10
Algorithm neoscrypt
cuda error out of memory in func cuda_neoscrypt::init line 1258
cuda error driver: 2 in func cudahelp::device_thread_init line 168

Same issue here. just upgraded to Nicehash v2.0.1.6 will monitor to see if fixed running precise bench again now. I’m running 1070 ti’s with 4 G Ram
I’m sure my Virtual Memory is auto. are you guys having any luck increasing it?

Tottom commented Jan 10, 2018

Are you able to change your Virtual Memory at all? how many 1070ti’s 4gb are you running?

remotetech commented Jan 10, 2018 •

Hi Tottom, I’m running:

2 ZOTAC 1070 Ti 8GB
1 Gigabyte 1060 6GB

for a total of 3 GPU cards. my Motherboard is using 4G RAM stick and I have a 60G SSD with Windows 10.

Yes I can set the Virtual Memory manually but there is not much memory left to play with.

For now I have just disabled the Neoscrypt Algorithm on all 3 GPU’s as I still have 13 other active Algorithms that are working just fine.

Please let me know exactly what has worked to fix this Neoscrypt error for you guys? so I can make the adjustments and turn back on the Neoscrypt Algorithm at some point.

remotetech commented Jan 11, 2018

Tottom, so your change to Vmem to 98GB is still working with neoscrypt with no errors?

Please advise as I will need to upgrade my ssd 🙂

Tottom commented Jan 11, 2018

remotetech, i was running 6x 1070 and 2x 1070ti at the time when the fix for vMem helped stabilize neoscrypt. apparently a 1070 8gb card is recommended to have 10 to 15gb of vMem per card. Other guys did not seem to experience this issue and when adding more physical memory on the motherboard, 16gb instead of 8gb their issue was also then resolved. if you have 40gb vMem it might work out for you if you have enough space? Another thought, start on the vMem of 16gb then see how long it takes to give the memory error or restart excavator. then add another 8gb and see till you have a stable miner. before spending too much on another drive? I have a 180gb and can only set 128gb at this time and it also seems to just not be enough for 8x 1070 and 2x 1070ti. the excavator runs for a few minutes then restarts. I added a second disk and put the vMem on it this did not fix the issue. So i think the excavator does not like vMem on another disk or shared between disks? I am no expert on the application but anything is possible.

Tottom commented Jan 11, 2018

just saw this comment from a fellow miner about Neoscrypt. Maybe it is more harsh to attempt?
from: Alex Thomas

solved
CUDA error ‘out of memory’ in func ‘cuda_neoscrypt::init’ line 1258″

raduvultur commented Jan 12, 2018

4x GTX 1070 (3 ASUS, 1 MSI) on WIN10 with 4GB RAM. After I got the error above I increased the vRAM amount to 64000 MB and running now with no errors since two hours ago.

remotetech commented Jan 16, 2018

Installed new drive and went with 125GB Vmem and turned back on neoscrypt and it’s mining neoscrypt now with no errors for about the last 10 minutes. Never got this far before. Thanks for all your help!

HoverDrive commented Feb 16, 2018

I’ve noticed a pattern here: everyone who has posted seems to have a mixture of GPUs in their mining rig. And so do I. One GTX 1080, one GTX 1070 ti, three GTX 1070s, and one GTX 1060.

I found my issue to be optimization confusion. I’m using the NIceHash miner, and when I ran the original benchmark against my GPUs, the optimizer assumed that my three GTX 1070s were created equal. But I have 2 that overclocked higher from the factory, and one that is lower-end and therefore has a slower GPU clock.

The optimizer picked one of the higher-end 1070s to run it’s optimization against, and simply assumed that the other two were identical cards. I eventually figured out that the error was occurring when the slower GTX 1070 was hit as hard as the higher-end GTX 1070s. Which was happening within seconds of starting the miner. Sometimes it took minutes.

A possible solution, would have been to overclock all three GTX 1070 at the same speed and re-run the optimizer. But what I ended up doing is replace the the slower 1070 with a GTX 1050 Ti from a different miner. The optimizer re-ran and now all seems to be working fine.

samywee commented Feb 17, 2018

I have very similar problem. I somewhat agree with HoverDrive.

I too have mix of GPUs (1070, 1060, 1050ti, 1050 and some are factory OC’d).

I have 10 GPU rig with 8GB memory. Quick look at task manager show memory is not a problem.

Is this a bug? Should I file a bug report? When I turn off neoscrypt or remove someof my cards, this rig seems to work. Is there a gpu limit to what NiceHash can handle. Windows 10 that I use, seems to recognize all cards and use the latest drivers from NVIDIA.

MitraTj commented Feb 19, 2018

I use Lab server, 8 GPUs. For running faster RCNN I have this problem.
In this case, what can I do.

samywee commented Feb 19, 2018 •

Other things to try is

MitraTj commented Feb 20, 2018

samywee: Thank you for your help. Sorry I am new in DL and using GPU. So, I should ask admin to allocate me more space of GPU, correct? Since each GPU has 12 GB of space.
Moreover, for other things you mentioned, how can I access to configuration on the server?

remotetech commented Feb 20, 2018 •

Again, I increased my onboard RAM from 4G to 8G and upgraded SSD from 60G to 250G so I could set my VM (Virtual Memory) higher to 125G. Haven’t had any issues with Neoscrypt for over a month now. I’m sure you don’t need that much virtual memory allocated but I went a little overboard just to get rid of the issue. I probably didn’t need the extra stick of RAM either. It was definetly the higher VM that finally fixed the issue.

Thanks again to Tottom for helping me finally fix this issue. 🙂

affian commented Jun 9, 2018

I had this issue, I changed the batch size and subdivisions from 64 & 8 to 128 & 64. Works fine but I am not sure if my model is training properly, hope this helps.

Источник