Claymore-Dual-Miner icon indicating copy to clipboard operation
Claymore-Dual-Miner copied to clipboard

low memory detected: 3GB instead of 4GB

Open koenvandenberge opened this issue 6 years ago • 27 comments

When I initialise the mining with one AMD Radeon RX550 4GB card, the miner successfully detects a card, saying:

gpu #0: gfx804, 3072 mb available, 8 compute units

However, it finds only 3 available GB instead of 4. The peculiar thing is that yesterday I had it set up and running, but the desktop shut down due to Windows updates over night, and since then I have had this problem, not allowing me to mine Ethereum.

  • I have 16GB RAM specified
  • I have tried reinstalling the drivers (Radeon Crinson 17.9.1)
  • I have Claymore dual miner v9.8 on Windows 10

koenvandenberge avatar Sep 15 '17 18:09 koenvandenberge

I have now seen that this always occurs after a first initialization of the mining. After completely re-installing my operating system, formatting the hard drive and reinstalling drivers and miner software, Claymore again says the card has 4GB and continues mining. However, canceling such a job and restarting the mining then results again in only 3GB being detected.

koenvandenberge avatar Sep 19 '17 20:09 koenvandenberge

I'm experiencing the exact same issue, fresh install of windows and it works properly, as soon as the system is rebooted then only 3gig detected and Claymore crashes. This is on an RX570 card.

There is only one card on this computer as I had a spare, I will swap it over with a RX580 and see what happens.

chimplicker avatar Sep 22 '17 07:09 chimplicker

I also have only one card. Switched cards aswell to another RX550, which did not solve the issue.

koenvandenberge avatar Sep 22 '17 08:09 koenvandenberge

I might try another fresh install and before running claymore set a restore point that I can hopefully go back to.

I'm also wondering is it due to only having one card, I might try putting two RX570s in this build.

I will update you later on anything I try.

chimplicker avatar Sep 22 '17 08:09 chimplicker

Hm... I can't be sure since I never test it, however in Readme it says: For AMD cards, set the following environment variables, especially if you have 2GB cards:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

EthDcrMiner64.exe

This has to be located inside start.bat file. For Windows you will have to use setx in front of each command (and to prepare the virtual memory for the cards if you don't have enough RAM - at least 16 GB)

This wont help you to find the missing memory but it might make it work...

lutsifer avatar Sep 22 '17 08:09 lutsifer

I was always curious about this less then 2G description in Claymore. @chimplicker Please let me know does it work.

lutsifer avatar Sep 22 '17 08:09 lutsifer

I'll give it a go when I get home later and post my results.

chimplicker avatar Sep 22 '17 08:09 chimplicker

Same here.

koenvandenberge avatar Sep 22 '17 08:09 koenvandenberge

I tried the 2 gig settings suggested above, Claymore just dumps out to desktop without any errors or messages.

I have created a restore point with everything setup on the PC but before claymore was ran for the first time, I can restore to this then mine. If Claymore is closed or the PC shut down, then I need to restore to this.

For now I will use this method as the system rarely gets turned off.

chimplicker avatar Sep 22 '17 19:09 chimplicker

Thans for the suggestion, @chimplicker

koenvandenberge avatar Sep 22 '17 20:09 koenvandenberge

My idea is to look what files are created by the claymore miner on startup & try to delete them maybee it will work then

htinc avatar Sep 22 '17 21:09 htinc

So I finally got round to trying an RX580 8gig card in this machine. Exact same thing occurs, it will run once on its very first claymore startup then anytime after that it only detects 3 gig and crashes to the desktop.

Very very strange.

chimplicker avatar Sep 30 '17 13:09 chimplicker

Same issue here on cloned Windows 10. At first Claymore recognized memory size correctly but then suddenly stopped working. it shows 6 Gpus are detected but each with only 3gb memory size. After that Claymore crashes. Strange thing is my other Rig is working properly, cloned Version not. Indeed very very strange.

DoktorWhat avatar Nov 20 '17 13:11 DoktorWhat

I've had a small but confusing break through, I started XMR mining using Claymore 10.2beta on the same rig, it detects the memory everytime correctly, ever since then, when I go back to mine Eth on Claymore it detects the memory properly everytime.

No idea how or why it is now working properly.

chimplicker avatar Nov 20 '17 14:11 chimplicker

So i had some little success by not cloning my OS

But this Problem still keeps appearing randomly, sometimes even on a freshly installed OS

Only once i got claymore to recognize them correctly after opening the start.bat file with admin rights but i don't think that this is the solution for that problem since i couldn't reproduce this fix a second time. randomly it appeared and as randomly it was gone again. @chimplicker I also don't think starting another Claymore version is helping anything, at least for me it didn't.

Any other solutions?

EDIT: i found a workaround by adding 4gb additional RAM. calling it a workaround because 1 rig is running properly with only 4gb RAM built in. Still a strange problem.

DoktorWhat avatar Nov 28 '17 15:11 DoktorWhat

I have same issue and finally i got it Remove from start.bat any environment variable (by default you should have like setx GPU_FORCE_64BIT_PTR 0 setx GPU_MAX_HEAP_SIZE 100 setx GPU_USE_SYNC_OBJECTS 1 setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_SINGLE_ALLOC_PERCENT 100)

And go to environment vars of windows and delete this vars and claymore runs again...

skymota avatar Dec 07 '17 17:12 skymota

I did what @skymota did, and it worked for me. Claymore was initially only recognizing 5192 out of 8192 MB on my RX580, and clearing environment variables worked. I also restarted at the same time, but not sure if that was connected.

harterj avatar Dec 20 '17 03:12 harterj

i also have same problem... Clearing environment variable helps in starting miner. ...but then device menager and many things gets disabled with some strange error code.... anyone fixed this problem?

krazyket4 avatar Jan 03 '18 17:01 krazyket4

Has anyone found a solution to this? I get "GPU #0: Hainan, 3072 MB available, 5 compute units" for my amd radeon r5 m335 I tried deleting the

setx GPU_FORCE_64BIT_PTR 0 setx GPU_MAX_HEAP_SIZE 100 setx GPU_USE_SYNC_OBJECTS 1 setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_SINGLE_ALLOC_PERCENT 100)

from my start.bat. I don't know what is meant by "And go to environment vars of windows and delete this vars", so I just rebooted.

I am trying to mine with Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal AMD+NVIDIA GPU Miner v9.8.

raz2000 avatar Jan 05 '18 07:01 raz2000

raj...its simple ... just delete setx GPU_FORCE_64BIT_PTR 0 setx GPU_MAX_HEAP_SIZE 100 setx GPU_USE_SYNC_OBJECTS 1 setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_SINGLE_ALLOC_PERCENT 100 from mining start .bat file and go to

right click on my computer (dont right click on my computershort cut....its better to open start menu..find my computer ....and right click) click on properties click on advance setting click on environment variable delet from user variable only these lines setx GPU_FORCE_64BIT_PTR 0 setx GPU_MAX_HEAP_SIZE 100 setx GPU_USE_SYNC_OBJECTS 1 setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_SINGLE_ALLOC_PERCENT 100

save restart now startminerand enjoy!!!!!

krazyket4 avatar Jan 05 '18 09:01 krazyket4

Thanks krazyket, I've done that now. Restarted, and went in to env vars to make sure they were still gone, checked my start.bat to make sure I had deleted them there, and started up caymore.

It still only finds 3072 MB available.

On a side note, I'm using nanopool, which has a minimum payout of 0.05 ethereum. With my setup, that should take me about a month of mining. I'm not doing this in the hope of making any real money, people will be ice skating in hell sooner. I just want some small amount in a wallet somewhere, just to try this. Any suggestions?

raz2000 avatar Jan 05 '18 09:01 raz2000

i think might you have driver problem ...which os r u using? ......have you tried any other driver?

krazyket4 avatar Jan 05 '18 10:01 krazyket4

I'm using windows 10. I've downloaded the latest amd driver, win10-64bit-radeon-software-adrenalin-edition-17.12.2-dec19.exe. I haven't tried any other drivers. I have tried using msi afterburner, but that won't let me change clock speeds.

raz2000 avatar Jan 05 '18 11:01 raz2000

I found this "OpenCL reduced available memory for OpenCL applications on your system, usually it is related to environment variables and size of RAM installed. But detecting 3GB instead of 4GB will not change your mining speed. So what's the problem?"

Here https://bitcointalk.org/index.php?topic=1433925.6220

Also "That's it. BINGO! Machine had only 2GB of RAM. Replacing a 1GB memory card for a 2GB one (3GB total) solved. Thank you very much to everyone to replied." on the same page.

As far as I can tell, I have 8 GB ram, so that shouldn't be a problem. Unless I've got my settings wrong. Not at all into the hardware part of computers. Here's a shot of my task manager image Is there something I should change here? Pagefile or something?

raz2000 avatar Jan 06 '18 10:01 raz2000

Also having the same issue on my 4gb R7 370, only detecting as 3gb. Runs fine without crashing etc. But would be keen to know if there's a fix.

jeremyisme avatar Jan 16 '18 06:01 jeremyisme

Got the same problem with Ubuntu 18.04 and any eth miners. Removing export GPU_FORCE_64BIT_PTR=0 export GPU_MAX_HEAP_SIZE=100 export GPU_USE_SYNC_OBJECTS=1 export GPU_MAX_ALLOC_PERCENT=100 export GPU_SINGLE_ALLOC_PERCENT=100 solve the problem antil I close terminal and try to start miner again. Then a got DAG error like not enough VRAM Без имени rebooting helps

foraEV avatar Jan 16 '20 06:01 foraEV

I have same issue and finally i got it Remove from start.bat any environment variable (by default you should have like setx GPU_FORCE_64BIT_PTR 0 setx GPU_MAX_HEAP_SIZE 100 setx GPU_USE_SYNC_OBJECTS 1 setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_SINGLE_ALLOC_PERCENT 100)

And go to environment vars of windows and delete this vars and claymore runs again...

that's really tricky, and it works! thanks.

botemple avatar Oct 13 '20 17:10 botemple