HW error logged, Detected invalid DAG, recreating в NiceHash Quick Miner — что за ошибка, как исправить?
На текущий момент исправить проблему не удалось. Но решил иначе!
Поставил стандартный найсхеш, сделал ручной разгон. Включать приходится вручную с права администратора! Т.е. правой кнопкой жмете по найсхешу и выбираете пункт запуск от Администратора. Проблема в том, что если ферма перезагрузится, то работать потом не будет нормально, надо выключать майнер и вновь запускать как админ. Квикмайнер больше не работал на этом риге. О причинах бага никто не знает. Спрашивал в майнерских чатах — встретил пару человек с этой же проблемой, но никто не знает почему на рабочем риге оно появляется и не исправляется никак.
Кто решит проблему с запуска квикмайнера — напишите в комментах, пожалуйста.
How bad are these? : [warning] dev | Device #3 HW error logged
So I've just started seriously mining with NH. Been doing it casual for years but recently started building 2 rigs with a mixture of 6x 3060tis and 6x 3070s in each.
I'm trying to tune my OC settings and I've got them all steady on 59-61MH/s 24/7 with 60-70% power settings.
However I've started noticing these error messages every few minuets. So far I've got about 150 of them in the past 5 hours of mining.
Are these something that I should be worried about?
I have a 2080 running in my main machine and I never see these errors ever and its OC'd as well.
NH Dashboard reports solid hashrates but is this going to affect my actual payout rate at all?
Do I need to increase my power or decrease my memory OC?
To put things perspective from that time range I have about 10,000 lines of activity in my Excavactor but only 153 of them are errors.
MiningFamily.org — Форум для Майнеров
Вылетают непонятные ошибки в майнере на 1070
Вылетают непонятные ошибки в майнере на 1070
Сообщение Nidre » Ср июл 07, 2021 12:16 pm
Пользуюсь NiceHash miner.
В общем повысил частоты 1070 по ядру +150, а по памяти +600. И зачастую майнит майнит и вылезает ошибка «Quick-swap DAG to: 000000000. «, после чего хеш с 27,30 +- увеличивается до 30+ на минуту. Это нормально? Ну и температуры карты тоже на пару градусов скачут.
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] HW err only during dag-generator #490
[BUG] HW err only during dag-generator #490
Comments
During cyclical dag-generator operations sometimes there are produces HW errors, and only during this phase. DAG generation during startup of excavator, quick-swap DAG and normal jobs don’t generate HW errors. Because cyclical dag-generator doesn’t happen that often and not every card on every dag-generator operation generate this error, it’s not so easy to reproduce and observe. On average there is one HW err for about 1000-2000 HW ok.
To Reproduce
Just wait for cyclical dag-generator and hope it will occur.
Expected behavior
Just no error during this phase.
Screenshots
Version affected:
Observed at current RC v0.5.1.4 RC with Excavator v1.7.1d, but probably the same was on v0.5.1.3. No such problem with older versions v0.4.x.x, but since v0.5.0.0 new RC versions were so often and I updated to every new RC version, it’s hard to tell when exactly it was introduced.
NVIDIA driver version
466.11 standard
Hardware
Observed on my and my friend’s 4 different rigs, 3 of them are just PC with one GPU (2x 3080, 1x 3090), the one from which the screenshot is rIg with 6 GPUs, running manual tuned MHz speed configuration for more than 2 months without earlier HW errors. Almost every GPU with this problem observed is different model and vendor, and waiting enough (2-3 days) HW errors are observed on every GPU this way.
Logs
Because of rare occurrence didn’t started logging during this problem.
Additional context
Introduced in one of the last version, rigs where tuned this way that there were no HW errors at all even after 24h operation for weeks.