Topic: Need Some Help With my ETH Claymore Rig Crashing (Read 318 times)

correct brother, don't ever update to newer version of windows 10. Because some updates will block the mining activity and the DAG created. I don't know what exactly microsoft want with the miner or crypto-world, maybe they want to more safe and stable to their system

I found the problem. You are running the wrong OS for mining.

I had nearly the exact same error after running the August Windows update. Like many of you I spent quite a bit of time going down the Intel HD Graphics route due to the "Faulting module name: igdrcl64.dll" bread crumb. It turns out that, for me, the ***FIX*** for this issue was to increase my virtual memory from 16GB to 32GB (the same as the total memory of all 8 8GB AMD RX 570 cards divided 2). I cannot say whether it was an DAG/epoch 200 related change, Windows Update, Windows Defender, or Mercury being retrograde that caused it - but I am back up and running!

Initial errors:

1.)  Windows event viewer:

Faulting application name: EthDcrMiner64.exe, version: 0.0.0.0, time stamp: 0x5b114486
Faulting module name: igdrcl64.dll, version: 20.19.15.4463, time stamp: 0x57462743
Exception code: 0xc0000005
Fault offset: 0x000000000007a74a
Faulting process id: 0x7c0
Faulting application start time: 0x01d42f4e4dbceb27
Faulting application path: C:\Install\Claymore\Claymore Dual Ethereum Miner v11.8\EthDcrMiner64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\igdrcl64.dll

2.) Claymore logs: (randomly rotated through cards for each start attempt)

15:29:44:986   11d4   GPU1, OpenCL error -4 (0) - cannot create DAG on GPU
15:29:44:986   1fcc   GPU7, OpenCL error -4 (0) - cannot create DAG on GPU
15:29:45:017   670   GPU4, OpenCL error -4 (0) - cannot create DAG on GPU
15:29:45:263   17fc   GPU0, OpenCL error -4 (0) - cannot create DAG on GPU

Miner version: Claymore's Dual GPU Miner - v11.8
Radeon driver: 17.30.1029-170808a2-317304E-CrimsonReLive (Blockchain Beta)
OS Name   Microsoft Windows 10 Pro N
Version   10.0.17134 Build 17134
MB: Asus Prime Z270-A

Thanks I turned off windows update as you know windows doesn't like that, but we will see how it works. I looked into ethOS and it says right on the website they do not support different drivers/cards so I didn't put much effort into looking more into it considering the OS dedicated to mining doesn't even support mining.

My advice to you. In the future install on a computer the utility which blocks automatic updating of Windows. Even these utilities do not always help but most of time they do not provide updated Windows. In 90% you will be protected from problems with Windows. Each reinstallation of Windows is a loss of time and money. Consider switching to Linux.

Hello Guys,

I ended up figuring it out on my own, but the last guy is most likely right. I ended reinstalling windows 4 times on the 4th try I didn't run any updates. Everything worked fine. So it's definitely something wrong in one of windows updates.

OMG send me your addy in PM and I will still send the ZRX since you answer was the correct answer. Thanks for everyones help. Also I apologize for my slow response I thought I had notifications set up on this thread and I thought no one had replied.

There is a problem with windows upgrade to 180x. under settings and update you can uninstall any update within 7 days. and by all means you should absolutely disable any updates für both windows Nd gryphics drivers until you know for sure that the update does not kill your system. stay with windows 10 release 1709 and your system will be fine...

it seems ridiculous but it did work, with 36 gb virtual memory all 9 cards worked again, what I don't get is WTF is doing windows to the resources as it was working perfectly with 24, and even if I add 4 gb of ram it wont work, with 8gb ram 24 virtual it wont work, but with 4 an 36 virtual its working fine right now, thanks for the help

I had a similar issue before, did all the "known" solutions (new drivers, check risers, check power, check overclocking profiles and even tried stock); my rig would always crash after installing the 6th card.

Anyways, It seemed to work fine after changing my PCIs to GEN 2 instead of GEN 1, and disabling CSM Support from the boot settings in bios.

Whats still bothering me is that I dont understand how this solved my issue, it just does not make sense; but it worked on multiple rigs.

In your case it could be worth a try.

Good luck

Hi guys, i think i have the same problem here, mi rig is asrock h110 btc pro MB with 9 EVGA 1060 6gb cards, working without problems for months and suddenly a few days ago after a windows update it doesnt work any more, i have the same error about dag file (cannot allocate big buffer for dag) it only works if i set -di 012345 but if i activate the rest of the cards (678) it will crash, ive tried different cards and orders or tried running 5-6-7-8-9 cards and once and it will allways crash at card 7

i also tried adding RAM (i have 4 gb and installed 4 more) it didnt work, page file size was 20,000 increased to 28,000 same problem. im running out of ideas, has anyone else having the same problem??

looking at what you have already tried, I can only offer you to test different frequencies in overclocking + downvolt. even in this motherboard there may be problems with connecting different video cards, try to connect to different connectors PCI-E, with different connection order

there's a bit confusion on the other errors posted with this


And this


5 cards detected but only 1 GPU registered, did you use -di command

if yes, Seems a single GPU also has a problem

is this the 7th GPU?

if yes, did you check or try to replace the riser?

I was also thinking on the driver changes upon win10 possible updates

sometimes mixing up AMD and NVIDIA GPU cards are too challenging to make it work with

As above comment said, it may relate to pagefile (Virtual Memory) Have you tried to disable Windows Defender?

as shown on your Errors Log "MsMpEng.exe (5516) consumed 109989888 bytes"

MsMpEng.exe is related Windows Defender 

Which version of Widows are you using? Windows 10 1709 or some other?
Have you been using 7 GPU's before or did you connect 7th GPU now and it's not working anymore?
Are all GPU's connected to one PSU or have you distributed it equally on both PSU's?
By the error you are getting, it seems that somethings wrong with Nvidia drivers, but you wrote that you've reinstalled everything and it didn't help.
Try set virtual memory Initial size: 16000 MB, and Maximum size: 32000 MB since error says that Low virtual memory condition.

bounty for solving my issue 30 ZRX

Hello I am trying to figure out why my mining rig is not stable anymore. I have had it about 4 months and it has been running very stable. I am not sure what caused the instability now the only thing I can think of is a power outgage or windows update. Other than that I dont have an idea. I didn't do anything new to cause this error I didnt even catch it for a while that the PC was in a boot loop. Any help would be appreciated.

things I have done.

1.Tested each video card in claymore 1 by 1 none give any errors
2 Tests lots of cards together randomly it seems to only have an issue with the 7th card. Every time I use 7 the rig crashes.
3 Tried running different instances of claymore separating amd and nvidia still crashes at 7GPU threshold
4 reformatted PC
5. change pci slots around
6 tried different drivers
7. all this testing was done without OC on nvidia cards other than the custom bios on the AMD cards
8.changed between 16 and 20GB virtual memory
9.Tried using -gser 2

Hardware-All I got Brand new
MSI GTX 1070TI X3
EVGA GTX 1070
RED DEVIL RX580
XFX RX580
SAPPHIRE RX580
2X EVGA 1000P2 PSU
SAMSUNG EVO 850 256GB
WINDOWS 10
I3-7100
8GB HYPERX RAM
H110 PRO BTC MOBO






errors that I am getting

BSOD VIDEO_SCHEDULER_INTERNAL_ERROR

-----Windows Log Errors
Display driver nvlddmkm stopped responding and has successfully recovered.

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: EthDcrMiner64.exe (7912) consumed 17870532608 bytes, MsMpEng.exe (5516) consumed 109989888 bytes, and explorer.exe (3856) consumed 42541056 bytes.

The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video22
ffffffff(ffffffff) ffffffff ffffffff
The message resource is present but the message was not found in the message table

Display driver nvlddmkm stopped responding and has successfully recovered.
---

claymore error
--
10:27:26:350   1fbc   Setting DAG epoch #196...
10:27:28:271   1fbc   Setting DAG epoch #196 for GPU1
10:27:28:271   1fcc   Setting DAG epoch #196 for GPU3
10:27:28:271   1fc0   Setting DAG epoch #196 for GPU2
10:27:28:271   1fd4   Setting DAG epoch #196 for GPU4
10:27:28:271   1fb4   Setting DAG epoch #196 for GPU0
10:27:28:271   1fe0   Setting DAG epoch #196 for GPU6
10:27:28:271   1fdc   Setting DAG epoch #196 for GPU5
10:27:28:271   1fbc   Create GPU buffer for GPU1
10:27:28:271   1fcc   Create GPU buffer for GPU3
10:27:28:271   1fc0   Create GPU buffer for GPU2
10:27:28:271   1fd4   Create GPU buffer for GPU4
10:27:28:271   1fb4   Create GPU buffer for GPU0
10:27:28:271   1fe0   Create GPU buffer for GPU6
10:27:28:271   1fdc   Create GPU buffer for GPU5
10:27:28:553   1fb4   GPU0, OpenCL error -4 (0) - cannot create DAG on GPU

10:27:32:583   1eec   Quit, please wait...
10:27:31:568   1fb4   Set global fail flag, failed GPU0
10:27:32:614   1fb4   GPU 0 failed
10:27:32:614   1fe0   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

10:27:32:614   1fd4   GPU 4, GpuMiner cu_kd failed 30 (16), unknown error
10:27:32:614   1fd4   GPU 4, Calc DAG failed!
10:27:32:739   1fc0   GPU 2, GpuMiner cu_kd failed 30 (17), unknown error
10:27:32:739   1fcc   GPU 3, GpuMiner cu_kd failed 30 (16), unknown error
10:27:32:739   1fc0   GPU 2, Calc DAG failed!
10:27:32:739   1fcc   GPU 3, Calc DAG failed!
10:27:33:098   1904   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:27:33:098   1904   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:27:33:192   1904   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:27:33:192   1904   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:27:33:286   1904   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:27:33:286   1904   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:27:33:364   1904   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:27:33:364   1904   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:27:33:442   1904   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:27:33:442   1904   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:27:33:770   1fbc   GPU1 DAG creation time - 5319 ms
10:27:33:786   1fbc   Setting DAG epoch #196 for GPU1 done
10:27:35:618   1fe0   Set global fail flag, failed GPU6


------


other error

9:57:12:488   1418   ETH: 1 pool is specified
09:57:12:503   1418   Main Ethereum pool is us2.ethermine.org:4444
09:57:14:003   1418   OpenCL platform: Intel(R) OpenCL
09:57:14:003   1418   OpenCL platform: NVIDIA CUDA
09:57:14:018   1418   OpenCL platform: AMD Accelerated Parallel Processing
09:57:14:018   1418   No AMD cards in the list.
09:57:14:706   1418   CUDA initializing...

09:57:14:721   1418   NVIDIA Cards available: 5
09:57:14:721   1418   CUDA Driver Version/Runtime Version: 9.2/8.0
09:57:14:831   1418   GPU #0: GeForce GTX 1070 Ti, 8192 MB available, 19 compute units, capability: 6.1  (pci bus 10:0:0)
09:57:14:846   1418   Total cards: 1
09:57:17:690   1418   
You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.

09:57:18:721   1418   NVML version: 9.398.36
09:57:19:580   1418   SSL: Imported 28 certificates from local storage
09:57:19:595   1930   ETH: Stratum - connecting to 'us2.ethermine.org' <54.71.50.231> port 4444 (unsecure)
09:57:19:642   1930   sent: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["44dE6758adb294E113712.power", "x"], "id": 2, "method": "eth_submitLogin"}

09:57:19:673   1930   ETH: Stratum - Connected (us2.ethermine.org:4444) (unsecure)
09:57:19:689   1930   buf: {"id":2,"jsonrpc":"2.0","result":true}

09:57:19:689   1930   ETH: Authorized
09:57:19:705   1418   ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)

09:57:19:705   1930   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

09:57:19:736   1418   ETH: eth-proxy stratum mode
09:57:19:752   1418   "-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
09:57:19:752   1418   Watchdog enabled
09:57:19:752   1418   

09:57:19:767   1930   buf: {"id":3,"jsonrpc":"2.0","result":["0xd27234a1446bd15500c13cbf4045b23a0dc111619c35cb89b852cb22884d04f8","0x9d3fef9bc522aee668ac0c6f6b22cf92cd30916e8da6cc5ac3ebe0a64234d5ce","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5a1b2a"]}

09:57:19:908   1bcc   Setting DAG epoch #196...
09:57:20:814   1930   buf: {"id":0,"jsonrpc":"2.0","result":["0xbaebb1073f4ad7a2c3f8ffb25a163ca74121621ce85c1460d11ac5b1b4bad5f6","0x9d3fef9bc522aee668ac0c6f6b22cf92cd30916e8da6cc5ac3ebe0a64234d5ce","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5a1b2b"]}

09:57:20:814   1930   ETH: 07/04/18-09:57:20 - New job from us2.ethermine.org:4444
09:57:20:814   1930   target: 0x0000000112e0be82 (diff: 4000MH), epoch 196(2.53GB)
09:57:20:814   1930   ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:57:20:814   1930   ETH: GPU0 0.000 Mh/s
09:57:22:267   1bcc   Setting DAG epoch #196 for GPU0
09:57:22:267   1bcc   Create GPU buffer for GPU0
09:57:22:282   1bcc   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

09:57:25:297   1bcc   Set global fail flag, failed GPU0
09:57:25:297   1bcc   GPU 0 failed
09:57:25:297   d40   Setting DAG epoch #196 for GPU0
09:57:25:313   d40   GPU 0, CUDA error 11 - cannot write buffer for DAG

09:57:25:328   1930   buf: {"id":0,"jsonrpc":"2.0","result":["0xbe640508867d1dc920830c67a0aa87e2cf9436557dceccc36d5f754ff58ce135","0x9d3fef9bc522aee668ac0c6f6b22cf92cd30916e8da6cc5ac3ebe0a64234d5ce","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5a1b2c"]}

09:57:25:328   1930   ETH: 07/04/18-09:57:25 - New job from us2.ethermine.org:4444
09:57:25:328   1930   target: 0x0000000112e0be82 (diff: 4000MH), epoch 196(2.53GB)
09:57:25:344   1930   ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:57:25:344   1930   ETH: GPU0 0.000 Mh/s
09:57:28:328   d40   Set global fail flag, failed GPU0
09:57:28:328   d40   GPU 0 failed
09:57:29:796   1930   ETH: checking pool connection...
09:57:29:796   1930   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

09:57:29:843   1930   buf: {"id":3,"jsonrpc":"2.0","result":["0xbe640508867d1dc920830c67a0aa87e2cf9436557dceccc36d5f754ff58ce135","0x9d3fef9bc522aee668ac0c6f6b22cf92cd30916e8da6cc5ac3ebe0a64234d5ce","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5a1b2c"]}

09:57:39:794   1930   sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x000000000000000000000000000000000000000000000000000000003f9c149a"]}

09:57:39:825   1930   ETH: checking pool connection...
09:57:39:825   1930   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

09:57:39:856   1930   buf: {"id":6,"jsonrpc":"2.0","result":true}

09:57:39:872   1930   buf: {"id":3,"jsonrpc":"2.0","result":["0xbe640508867d1dc920830c67a0aa87e2cf9436557dceccc36d5f754ff58ce135","0x9d3fef9bc522aee668ac0c6f6b22cf92cd30916e8da6cc5ac3ebe0a64234d5ce","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5a1b2c"]}

09:57:42:668   c78   GPU0 t=46C fan=0%
09:57:43:246   c94   em hbt: 16, fm hbt: 78,
09:57:43:246   c94   watchdog - thread 0 (gpu0), hb time 17938
09:57:43:246   c94   watchdog - thread 1 (gpu0), hb time 17938
09:57:43:246   c94   WATCHDOG: GPU error, you need to restart miner