Главная » Криптовалюты

Illegal memory access was encountered майнинг

Содержание
  1. GTX 1000 GpuMiner cu_kd failed 77 (0), an illegal memory access was encountered
  2. hshan
  3. Помогите расшифровать ошибку nbminer
  4. Vadim56
  5. Андрей_ua
  6. Lexterman
  7. multik555
  8. Roman Banzay
  9. svetik116
  10. Андрей_ua
  11. svetik116
  12. Endruscott
  13. illegal memory access was encountered. #285
  14. Comments
  15. roachadam commented Sep 4, 2017 •
  16. aliceaia commented Sep 4, 2017
  17. roachadam commented Sep 4, 2017
  18. dafyk commented Sep 4, 2017
  19. yamid-ny commented Nov 19, 2017
  20. derubm commented Nov 23, 2017 •
  21. DeadManWalkingTO commented Feb 19, 2018
  22. DeadManWalkingTO commented Feb 27, 2018
  23. ccminer — GPU #0: an illegal memory access was encountered #526
  24. Comments
  25. lukiifaz commented Nov 22, 2017
  26. aaronsace commented Nov 22, 2017 •
  27. lukiifaz commented Nov 23, 2017
  28. aaronsace commented Nov 23, 2017
  29. lukiifaz commented Nov 23, 2017 •
  30. aaronsace commented Nov 23, 2017 •
  31. aaronsace commented Nov 23, 2017
  32. lukiifaz commented Nov 23, 2017 •
  33. aaronsace commented Nov 23, 2017
  34. lukiifaz commented Nov 23, 2017
  35. aaronsace commented Nov 23, 2017
  36. lukiifaz commented Nov 23, 2017 •
  37. chabgood commented Nov 23, 2017
  38. lukiifaz commented Nov 23, 2017 •
  39. chabgood commented Nov 23, 2017
  40. aaronsace commented Nov 23, 2017
  41. UselessGuru commented Nov 23, 2017 •
  42. lukiifaz commented Nov 23, 2017
  43. UselessGuru commented Nov 23, 2017
  44. fonyo commented Nov 23, 2017 •
  45. lukiifaz commented Nov 23, 2017
  46. fonyo commented Nov 23, 2017
  47. aaronsace commented Nov 24, 2017

GTX 1000 GpuMiner cu_kd failed 77 (0), an illegal memory access was encountered

hshan

Пляшущий с бубном

Риг из 1060 отработал несколько дней и начал сыпаться ошибкой как в заголовке. Ниже написан большой кусок из лога.

Сброс настроек к заводским, ребуты и прочие простые прием ничего не дали. Так как ошибка сразу по всем картам дело не мот быть в райзере или смерти какой-то карты.

Кто знает как решить проблему — отпишитесь!

07:18:02:681 bc0 parse packet: 247
07:18:02:681 bc0 ETH: job changed
07:18:02:681 bc0 new buf size: 0
07:18:02:682 bc0 ETH: 06/25/17-07:18:02 — New job from eu2.ethermine.org:4444
07:18:02:682 bc0 target: 0x0000000112e0be82 (diff: 4000MH), epoch #130
07:18:02:686 bc0 ETH — Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
07:18:02:687 bc0 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s
07:18:02:688 bc0 DCR — Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0
07:18:02:689 bc0 DCR: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s
07:18:03:024 12e0 Setting DAG epoch #130 for GPU1
07:18:03:026 c74 Setting DAG epoch #130 for GPU0
07:18:03:027 1350 Setting DAG epoch #130 for GPU3
07:18:03:028 12e0 Create GPU buffer for GPU1
07:18:03:028 ac4 Setting DAG epoch #130 for GPU2
07:18:03:030 1350 Create GPU buffer for GPU3
07:18:03:031 ac4 Create GPU buffer for GPU2
07:18:03:029 c74 Create GPU buffer for GPU0
07:18:03:427 12e0 GPU 1, GpuMiner cu_kd failed 77 (0), an illegal memory access was encountered
07:18:03:430 12e0 GPU 1, Calc DAG failed!
07:18:03:471 1350 GPU 3, GpuMiner cu_kd failed 77 (0), an illegal memory access was encountered
07:18:03:534 1350 GPU 3, Calc DAG failed!
07:18:03:535 ac4 GPU 2, GpuMiner cu_kd failed 77 (0), an illegal memory access was encountered
07:18:03:536 ac4 GPU 2, Calc DAG failed!
07:18:03:537 c74 GPU 0, GpuMiner cu_kd failed 77 (0), an illegal memory access was encountered
07:18:03:538 c74 GPU 0, Calc DAG failed!
07:18:06:234 bc0 got 248 bytes
07:18:06:234 bc0 buf:

07:18:06:234 bc0 parse packet: 247
07:18:06:234 bc0 ETH: job changed
07:18:06:234 bc0 new buf size: 0
07:18:06:235 bc0 ETH: 06/25/17-07:18:06 — New job from eu2.ethermine.org:4444
07:18:06:236 bc0 target: 0x0000000112e0be82 (diff: 4000MH), epoch #130
07:18:06:238 bc0 ETH — Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
07:18:06:239 bc0 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s
07:18:06:240 bc0 DCR — Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0
07:18:06:241 bc0 DCR: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s
07:18:06:932 12e0 GPU 1 failed
07:18:06:936 ecc Setting DAG epoch #130 for GPU1
07:18:06:937 ecc GPU 1, CUDA error 77 — cannot write buffer for DAG

Читайте также:  С повышением реальной процентной ставки объем инвестиций

07:18:07:036 1350 GPU 3 failed
07:18:07:041 ac4 GPU 2 failed
07:18:07:040 b70 Setting DAG epoch #130 for GPU3
07:18:07:043 b70 GPU 3, CUDA error 77 — cannot write buffer for DAG

07:18:07:041 c64 Setting DAG epoch #130 for GPU2
07:18:07:045 c74 GPU 0 failed
07:18:07:044 4c0 Setting DAG epoch #130 for GPU0
07:18:07:046 4c0 GPU 0, CUDA error 77 — cannot write buffer for DAG

07:18:07:047 c64 GPU 2, CUDA error 77 — cannot write buffer for DAG

07:18:09:938 ecc GPU 1 failed
07:18:10:044 b70 GPU 3 failed
07:18:10:048 4c0 GPU 0 failed
07:18:10:080 c64 GPU 2 failed
07:18:10:133 bc0 ETH: checking pool connection.
07:18:10:133 bc0 send:

07:18:10:193 bc0 got 248 bytes
07:18:10:193 bc0 buf:

07:18:10:193 bc0 parse packet: 247
07:18:10:193 bc0 ETH: job is the same
07:18:10:193 bc0 new buf size: 0
07:18:11:690 bc0 got 248 bytes
07:18:11:690 bc0 buf:

07:18:11:691 bc0 parse packet: 247
07:18:11:691 bc0 ETH: job changed
07:18:11:691 bc0 new buf size: 0
07:18:11:691 bc0 ETH: 06/25/17-07:18:11 — New job from eu2.ethermine.org:4444
07:18:11:692 bc0 target: 0x0000000112e0be82 (diff: 4000MH), epoch #130
07:18:11:692 bc0 ETH — Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
07:18:11:693 bc0 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s
07:18:11:694 bc0 DCR — Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0
07:18:11:695 bc0 DCR: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s
07:18:20:131 bc0 send:

07:18:20:147 bc0 ETH: checking pool connection.
07:18:20:147 bc0 send:

07:18:20:193 bc0 got 39 bytes
07:18:20:193 bc0 buf:

07:18:20:194 bc0 parse packet: 38
07:18:20:194 bc0 new buf size: 0
07:18:20:250 bc0 got 248 bytes
07:18:20:250 bc0 buf:

07:18:20:250 bc0 parse packet: 247
07:18:20:251 bc0 ETH: job is the same
07:18:20:251 bc0 new buf size: 0
07:18:26:833 308 got 402 bytes
07:18:26:833 308 buf:

Источник

Помогите расшифровать ошибку nbminer

Vadim56

Свой человек

Помогите расшифровать ошибку hiveos nbminer,риг перезагружается каждые 3 часа.Есть карта GPU3 под ней написано 05:00.0, или же это GPU5 отваливается?

[Fri Apr 9 10:52:19 2021] NVRM: Xid (PCI:0000:05:00): 62, pid=1084, 0a97(2c24) 00000000 00000000

Андрей_ua

Великий мудрец

Помогите расшифровать ошибку hiveos nbminer,риг перезагружается каждые 3 часа.Есть карта GPU3 под ней написано 05:00.0, или же это GPU5 отваливается?

[Fri Apr 9 10:52:19 2021] NVRM: Xid (PCI:0000:05:00): 62, pid=1084, 0a97(2c24) 00000000 00000000

Lexterman

Бывалый

multik555

Местный житель

Помогите расшифровать ошибку hiveos nbminer,риг перезагружается каждые 3 часа.Есть карта GPU3 под ней написано 05:00.0, или же это GPU5 отваливается?

[Fri Apr 9 10:52:19 2021] NVRM: Xid (PCI:0000:05:00): 62, pid=1084, 0a97(2c24) 00000000 00000000

Roman Banzay

Бывалый

Помогите расшифровать ошибку hiveos nbminer,риг перезагружается каждые 3 часа.Есть карта GPU3 под ней написано 05:00.0, или же это GPU5 отваливается?

[Fri Apr 9 10:52:19 2021] NVRM: Xid (PCI:0000:05:00): 62, pid=1084, 0a97(2c24) 00000000 00000000

svetik116

Новичок

Добрый день. Может кто подскажет, что за ошибка вылетает?

[2021-04-19 13:52:11,871] ERROR — CUDA Error: an illegal memory access was encountered (err_no=77)
[2021-04-19 13:52:11,878] ERROR — Device 2 exception, exit .
[2021-04-19 13:52:11,886] ERROR — CUDA Error: an illegal memory access was encountered (err_no=77)
[2021-04-19 13:52:11,886] ERROR — CUDA Error: an illegal memory access was encountered (err_no=77)
ERROR — Device 1 exception, exit .
ERROR — Logger lock failed.[2021-04-19 13:52:11,898] ERROR — Device 3 exception, exit .
[2021-04-19 13:52:11,898] ERROR — Logger lock failed.[2021-04-19 13:52:11,895] ERROR — CUDA Error: an illegal memory access was encountered (err_no=77)
[2021-04-19 13:52:11,895] ERROR — Logger lock failed.ERROR — Device 0 exception, exit .
ERROR — Logger lock failed.

После чего комп зависает и просто черный экран. Приходится перезагружать и через некоторое время все повторяется.

Андрей_ua

Великий мудрец

Добрый день. Может кто подскажет, что за ошибка вылетает?

[2021-04-19 13:52:11,871] ERROR — CUDA Error: an illegal memory access was encountered (err_no=77)
[2021-04-19 13:52:11,878] ERROR — Device 2 exception, exit .
[2021-04-19 13:52:11,886] ERROR — CUDA Error: an illegal memory access was encountered (err_no=77)
[2021-04-19 13:52:11,886] ERROR — CUDA Error: an illegal memory access was encountered (err_no=77)
ERROR — Device 1 exception, exit .
ERROR — Logger lock failed.[2021-04-19 13:52:11,898] ERROR — Device 3 exception, exit .
[2021-04-19 13:52:11,898] ERROR — Logger lock failed.[2021-04-19 13:52:11,895] ERROR — CUDA Error: an illegal memory access was encountered (err_no=77)
[2021-04-19 13:52:11,895] ERROR — Logger lock failed.ERROR — Device 0 exception, exit .
ERROR — Logger lock failed.

Читайте также:  Инвестиции текущие финансовые обязательства

После чего комп зависает и просто черный экран. Приходится перезагружать и через некоторое время все повторяется.

svetik116

Новичок

Endruscott

Пляшущий с бубном

Добрый день. Может кто подскажет, что за ошибка вылетает?

[2021-04-19 13:52:11,871] ERROR — CUDA Error: an illegal memory access was encountered (err_no=77)
[2021-04-19 13:52:11,878] ERROR — Device 2 exception, exit .
[2021-04-19 13:52:11,886] ERROR — CUDA Error: an illegal memory access was encountered (err_no=77)
[2021-04-19 13:52:11,886] ERROR — CUDA Error: an illegal memory access was encountered (err_no=77)
ERROR — Device 1 exception, exit .
ERROR — Logger lock failed.[2021-04-19 13:52:11,898] ERROR — Device 3 exception, exit .
[2021-04-19 13:52:11,898] ERROR — Logger lock failed.[2021-04-19 13:52:11,895] ERROR — CUDA Error: an illegal memory access was encountered (err_no=77)
[2021-04-19 13:52:11,895] ERROR — Logger lock failed.ERROR — Device 0 exception, exit .
ERROR — Logger lock failed.

После чего комп зависает и просто черный экран. Приходится перезагружать и через некоторое время все повторяется.

Источник

illegal memory access was encountered. #285

Comments

roachadam commented Sep 4, 2017 •

Specs:
Windows 10 64-bit home
4gb ram
6×1070 Nvidia FE
ethminer v0.11.0

I know this issue has been posted before, but I did not find a solution to this issue. I’ve messed with my OC’s, lowering them, as well as increasing pagefile size in windows with the same results. After a few hours I get this error.

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

aliceaia commented Sep 4, 2017

Often this error due to wrong overclock.

roachadam commented Sep 4, 2017

@aliceaia I figured that was the issue, but it ran stable for 2 months on the same OCs, so I’m not sure what happened. I lowed it and still got the same result.

For now I’m testing Claymore’s to see if it encounters a similar error with the same OC.

dafyk commented Sep 4, 2017

Different miner is not a good test (theres high chance calymore will work fine), but try to replicate your problem with single GPU. My expectations are that ethminer wont crash with single card and @aliceaia is right (i also believe its problem with OC or power issues)

yamid-ny commented Nov 19, 2017

I have the same problem with 1060 3gb, it was run 1 month without problem but now only a card (from 5 1060s) restart complete rig, I only use 4 1060s and the rig works very well but when I put the «rare» GPU the rig shows the problem.
.
Thanks for the help and the best energy for all.

Rig: Asus B250 mining expert, 8gb RAM, Celeron 3930, EVGA 750 GQ, SMOS (simple mining os) Claymore 10.0, 1060 3GB Gibabyte

derubm commented Nov 23, 2017 •

#72 (comment)
#72
Happens due to P2 state switching into P0 state on Nvidia cards,
Solution: set your cards to P0 state from start on.
(windows: nvidia inspector, linux: nvidia-smi)

DeadManWalkingTO commented Feb 19, 2018

  • At section «5 — Common»
    ** Change «CUDA — Force P2 State» to «Off»
    ** Change «Power management mode» to «Prefer maximum performance»
  • Click «Apply Changes»
  • Reboot and start mining!

DeadManWalkingTO commented Feb 27, 2018

GTX1060 +150/+500/65%TDP @ 23-24MHs

Try Update Drivers.
Download and install the latests.

Try Update Ethminer.
Download (or beter build) the latest.

Try use -U for CUDA devices.
Test launch command:
ethminer -RH -U -S eu1.ethermine.org:4444 -FS us1.ethermine.org:4444 -O 0x7013275311fc37ccc1e40193D75086293eCb43A4.test

Try to change P2 State and Power managment mode.
You can use NVidiaProfileInspectorDmW.
For the best mining hashrate choose from sector «5 — Common»:

  • CUDA — Force P2 State (Set to «Off»)
  • Power managment mode (Set to «Prefer maximum performance»)

Try Optimize/Overclock GPUs.
You can use MSI Afterburner for GPU OverClock/Optimize.

Источник

ccminer — GPU #0: an illegal memory access was encountered #526

Comments

lukiifaz commented Nov 22, 2017

Bin\Lyra2z-NVIDIA\ccminer_cuda9.exe -a lyra2z -o stratum+tcp://europe.lyra2z-hub.miningpoolhub.com:17025 -u xxxx.xxxx -p x
Sys: Win 10
CPU: i7-7700
GPU: GTX 1060
Drivers: v388.31 15-11-2017

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

aaronsace commented Nov 22, 2017 •

Not sure what could be causing that. MultiPoolMiner will skip past the issue.

Читайте также:  Русские пулы для майнинга биткоина

lukiifaz commented Nov 23, 2017

Miner did not restart himself. It would be helpful to detect this type of error and to automatically restart the miner. During the problem, the value of 12GH / s, normally 1142.52 kH / s. Multipoolminer did not detect the problem.

aaronsace commented Nov 23, 2017

Please can you post the log?

lukiifaz commented Nov 23, 2017 •

CcminerPalgin MyriadGroestl 38,00 MH/s 13,86794 364,99247 Hashrefinery
CcminerKlaust MyriadGroestl 35,19 MH/s 12,84529 364,99247 Hashrefinery

Miner : MultiPoolMiner
PLN : 1 330,89047 ±11 415% (11,55789-153 252,03091)
USD : 373,26901 ±11 415% (3,24159-42 981,92475)
BCH : 0,00000 ±11 415% (0,00000-0,00000)
BCT : 0,00000 ±11 415% (0,00000-0,00000)

Miner :
PLN : 420 195,84027 ±0% (420 195,73327-420 195,94727)
USD : 117 850,48381 ±0% (117 850,45380-117 850,51383)
BCH : 0,00000 ±0% (0,00000-0,00000)
BCT : 0,00000 ±0% (0,00000-0,00000)

aaronsace commented Nov 23, 2017 •

The speed is 1140KH/s all over your log; where does it say 12000KH/s?
Is the speed wrong or not?

aaronsace commented Nov 23, 2017

The figures you pasted at the end are because of this: #525

lukiifaz commented Nov 23, 2017 •

Yes in log is ok but when i have error «GPU #0: an illegal memory access was encountered» miner show 12GH /s.

It looked like that:

aaronsace commented Nov 23, 2017

So what happens in MultiPoolMiner?
I can’t see 10GH/s.

lukiifaz commented Nov 23, 2017

MultiPoolMiner not detect error and i have to restart miner.

aaronsace commented Nov 23, 2017

What does it say under «Status: Running»?

lukiifaz commented Nov 23, 2017 •

In miner window :
GPU #0: result for 05b4b533 does not validate on CPU!

chabgood commented Nov 23, 2017

Are you overclocking?

lukiifaz commented Nov 23, 2017 •

chabgood
«Are you overclocking?»
Oc Gpu+200 Mem + 950
Yes, but for test i’m back to default settings.

chabgood commented Nov 23, 2017

Sure, I have gotten the same error when you overclock too much for your card.

aaronsace commented Nov 23, 2017

Ok, so the reading is too high, correct? «452MH/s»
That wasn’t in your log.

Does MultiPoolMiner say this?
«WARNING: Stat file was not updated because the value is outside fault tolerance.»

Can you send the stat files?

UselessGuru commented Nov 23, 2017 •

seems way to high.
My 1060 (Samsung memory) can do Gpu +185-160 (curve) and Mem + 650 with PL 85%
High mem OC causes all sorts of weird problems

lukiifaz commented Nov 23, 2017

Lenovo legion y720 Im use Oc Gpu+200 Mem + 950 and dont have problem with other miners and games, temperature is stable 69C. But i’m change thermal paste and thermopads.
UselessGuru what is yours brand 1060 ?

UselessGuru commented Nov 23, 2017

UselessGuru what is yours brand 1060 ?

Gigabyte GeForce GTX 1060 WindForce OC 3G
Too high an overclock actually reduces performance. You may not notice over-overclocking by just checking for artifacts. The gpu will spend lots of cycles fixing memory errors, so that they go unnoticed but eat performance.
Some algorithms are more prone to crashes when overclocked than others. E.g cryptonight or Lyr22z crash sooner.

fonyo commented Nov 23, 2017 •

Clock +200 is not necessary for most algos, a bit of a bump is all you need and mem +950 is way too high, I am surprised you are not experiencing screen tearing and artifacts or a complete blackout every now and then!
+950 mem also confirms the reason for illegal mem access.

lukiifaz commented Nov 23, 2017

fonyo but i have this problem without OC. Tomorow i try difrend drivers.

fonyo commented Nov 23, 2017

Try the cuda 8 version, cuda 9 compiled ccminers only work with driver version 384.xx or later so please bear that in mind when switching to another driver.

aaronsace commented Nov 24, 2017

Ccminer seems to throw masses of errors and a huge haserate when there are other issues also.
Note to self: check the stat value error checking is working correctly.

Источник

Оцените статью
© 2024 Идеи для бизнеса