-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
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
MEMORY ALLOC FAILED: VirtualAlloc failed #2582
Comments
I have the same error, but only on machine with AMD CPU. Intel CPU does not have this error. |
Few more observations: |
I am getting this (MEMORY ALLOC FAILED: VirtualAlloc failed) on GPU (RX560) on an AMD CPU host (FX-8350). |
how do you enabled large page support. Try to run |
I am using Win OS, so through the Local Security Policy. I didn't find any option to set large pages count there ... |
Same problem here, but I noticed that occurs only if I use --noTest parameter. |
can you please post the output with and without --noTest
|
Sure... WITH --noTest xmr-stak-rx.exe --noTestxmr-stak-rx 1.0.1-rx 7a9361b Brought to you by fireice_uk and psychocrypt under GPLv3.
|
I can confirm that --noTest causes the issue, without this option, memory is allocated fine and hashrate jumps to almost double. --noTest/test outputs attached, but only extra information there is the MEMORY ALLOC error line. I am running pre-compiled binaries. |
same issue on windows 10 , i do not use noTest switch. |
btw there is a new version 1.0.2 available. I think your issue is not fixed
but an issue with memory pinning is fixed.
|
@psychocrypt I can confirm that even in 1.0.2 issue is not fixed. |
thanks for the report, fixed by #2624 |
It still fails for me on Windows 8.1. (Even without the flag). And that with the latest version. |
Why is it mining based on CPU only? |
Since switch to randomx, I see the MEMORY ALLOC FAILED: VirtualAlloc failed for each working cpu thread. HW is the same (was working fine - without the error - before the switch), cpu config auto-generated. I googled a bit and done following:
-run miner as admin
-checked that locking pages in Local Security Policy is allowed for the account
-restarted the system, run the mining as a very first thing
-increased Virtual RAM Size (I did not find any tips how much to increase it, so tried to set it to 40GB virtual RAM on machine with 8GB physical RAM, 5 mining threads)
None of the above helped. Any tips? Or logs where can I find closer info about the issue? Thx in advance.
The text was updated successfully, but these errors were encountered: