Topic: NiceHash Memory Alloc and black/blue screen issues (Read 4300 times)
@JoxNiceHash you or any of the NiceHash crew on here might have any input on this?
I have tried running NiceHash 2.0.0.6 as two instances with different permissions in all variations, like I am with the 1.xxx version but can't get it to run more than 10 minutes without crashing.
All I am thinking at this point is maybe my PSU can't keep up or my RAM speeds on Ryzen are somehow a problem.
I am using this GPU:
https://www.newegg.com/Product/Product.aspx?Item=N82E16817139027
CORSAIR CX series CX500 500W 80 PLUS BRONZE Active PFC ATX12V & EPS12V Power Supply
The thing I am thinking about the RAM is that my 3200Mhz Kit is just running at 2133Mhz. Not sure if that would have any thing to do it?
All I am thinking at this point is maybe my PSU can't keep up or my RAM speeds on Ryzen are somehow a problem.
I am using this GPU:
https://www.newegg.com/Product/Product.aspx?Item=N82E16817139027
CORSAIR CX series CX500 500W 80 PLUS BRONZE Active PFC ATX12V & EPS12V Power Supply
The thing I am thinking about the RAM is that my 3200Mhz Kit is just running at 2133Mhz. Not sure if that would have any thing to do it?
First off, the XMR_stak_cpu application is a CPU miner, so i don't think that doing anything with the GPU Drivers will affect it.
If it is the 3rd party miners that are crashing, and they only crash when elevated privileges are enabled, then maybe you could try two instances of the NiceHash application, like the following:
1) In NiceHash settings, enabled "allow multiple instances"
2) Launch two instances of NiceHash; launch 1 instance with elevated privileges and launch the other instance without elevated privileges
3) In the NiceHash instance with elevated privileges untick the GPU so that instance only controls the CPU mining
4) In the NiceHash instance with regular privileges untick the CPU so that instance only controls the GPU mining
In this way, you will have an elevated instance controlling the XMR_Stak_CPU miner, and a regular non-elevated instance controlling the GPU miners including the 3rd party ones.
If it is the 3rd party miners that are crashing, and they only crash when elevated privileges are enabled, then maybe you could try two instances of the NiceHash application, like the following:
1) In NiceHash settings, enabled "allow multiple instances"
2) Launch two instances of NiceHash; launch 1 instance with elevated privileges and launch the other instance without elevated privileges
3) In the NiceHash instance with elevated privileges untick the GPU so that instance only controls the CPU mining
4) In the NiceHash instance with regular privileges untick the CPU so that instance only controls the GPU mining
In this way, you will have an elevated instance controlling the XMR_Stak_CPU miner, and a regular non-elevated instance controlling the GPU miners including the 3rd party ones.
Thank you! This worked for stopping the Memory Alloc errors, still trying to figure out the 3rd party miner issue tho.
Uninstall AMD drivers, then download and run DDU in Safe Mode --- reboot and install AMD 16.12.2 drivers. Check back here if it works or not for ya.
No joy! Using /dev/urandom's idea of two instances I got the Memory Alloc errors to go away by using the CPU on the elevated instance and miners on normal permissions. After using DDU and installing the 16,12,2 drivers I tried running both CPU/GPU as one elevated instance, running both as a regular instance, running an instance for each with both instances elevated, and running the CPU elevated with GPU normal. Every option with 3rd party workers crashes within 15 minutes.
Any other thoughts or ideas?
First off, the XMR_stak_cpu application is a CPU miner, so i don't think that doing anything with the GPU Drivers will affect it.
If it is the 3rd party miners that are crashing, and they only crash when elevated privileges are enabled, then maybe you could try two instances of the NiceHash application, like the following:
1) In NiceHash settings, enabled "allow multiple instances"
2) Launch two instances of NiceHash; launch 1 instance with elevated privileges and launch the other instance without elevated privileges
3) In the NiceHash instance with elevated privileges untick the GPU so that instance only controls the CPU mining
4) In the NiceHash instance with regular privileges untick the CPU so that instance only controls the GPU mining
In this way, you will have an elevated instance controlling the XMR_Stak_CPU miner, and a regular non-elevated instance controlling the GPU miners including the 3rd party ones.
If it is the 3rd party miners that are crashing, and they only crash when elevated privileges are enabled, then maybe you could try two instances of the NiceHash application, like the following:
1) In NiceHash settings, enabled "allow multiple instances"
2) Launch two instances of NiceHash; launch 1 instance with elevated privileges and launch the other instance without elevated privileges
3) In the NiceHash instance with elevated privileges untick the GPU so that instance only controls the CPU mining
4) In the NiceHash instance with regular privileges untick the CPU so that instance only controls the GPU mining
In this way, you will have an elevated instance controlling the XMR_Stak_CPU miner, and a regular non-elevated instance controlling the GPU miners including the 3rd party ones.
I get a crash with admin privileges even with 3rd party miners disabled. The only way it don't crash is regular privileges and no 3rd party miners.
I will try the second instance method to see what happens.
First off, the XMR_stak_cpu application is a CPU miner, so i don't think that doing anything with the GPU Drivers will affect it.
If it is the 3rd party miners that are crashing, and they only crash when elevated privileges are enabled, then maybe you could try two instances of the NiceHash application, like the following:
1) In NiceHash settings, enabled "allow multiple instances"
2) Launch two instances of NiceHash; launch 1 instance with elevated privileges and launch the other instance without elevated privileges
3) In the NiceHash instance with elevated privileges untick the GPU so that instance only controls the CPU mining
4) In the NiceHash instance with regular privileges untick the CPU so that instance only controls the GPU mining
In this way, you will have an elevated instance controlling the XMR_Stak_CPU miner, and a regular non-elevated instance controlling the GPU miners including the 3rd party ones.
If it is the 3rd party miners that are crashing, and they only crash when elevated privileges are enabled, then maybe you could try two instances of the NiceHash application, like the following:
1) In NiceHash settings, enabled "allow multiple instances"
2) Launch two instances of NiceHash; launch 1 instance with elevated privileges and launch the other instance without elevated privileges
3) In the NiceHash instance with elevated privileges untick the GPU so that instance only controls the CPU mining
4) In the NiceHash instance with regular privileges untick the CPU so that instance only controls the GPU mining
In this way, you will have an elevated instance controlling the XMR_Stak_CPU miner, and a regular non-elevated instance controlling the GPU miners including the 3rd party ones.
Regarding this error:
[2017-06-09 16:43:51] : MEMORY INIT ERROR: Obtaning SeLockMemoryPrivilege failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
In order to obtain SetLockMemoryPrivilege you must do the following:
1) Be running with elevated (Administrator) privileges
2) The user running the application must have the "Lock pages in memory" permission in GPEDIT.MSC under
/Local Computer Policy/Computer Configuration/Windows Settings/Security Settings/Local Policies/User Rights Assignment/
http://imgur.com/a/mY3Dl
If you haven't done those two things, then you will get that error.
Not sure what to say about the 3rd party miners crashing... Sorry.
[2017-06-09 16:43:51] : MEMORY INIT ERROR: Obtaning SeLockMemoryPrivilege failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
In order to obtain SetLockMemoryPrivilege you must do the following:
1) Be running with elevated (Administrator) privileges
2) The user running the application must have the "Lock pages in memory" permission in GPEDIT.MSC under
/Local Computer Policy/Computer Configuration/Windows Settings/Security Settings/Local Policies/User Rights Assignment/
http://imgur.com/a/mY3Dl
If you haven't done those two things, then you will get that error.
Not sure what to say about the 3rd party miners crashing... Sorry.
Thanks for the info, that at least explains why the Admin privilege works. I do have the permissions set in gpedit.
Any idea why the elevated command would cause the crashes even with out the 3rd party miners running?
Uninstall AMD drivers, then download and run DDU in Safe Mode --- reboot and install AMD 16.12.2 drivers. Check back here if it works or not for ya.
Thanks, I'll try this and see what happens
Regarding this error:
[2017-06-09 16:43:51] : MEMORY INIT ERROR: Obtaning SeLockMemoryPrivilege failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
In order to obtain SetLockMemoryPrivilege you must do the following:
1) Be running with elevated (Administrator) privileges
2) The user running the application must have the "Lock pages in memory" permission in GPEDIT.MSC under
/Local Computer Policy/Computer Configuration/Windows Settings/Security Settings/Local Policies/User Rights Assignment/
http://imgur.com/a/mY3Dl
If you haven't done those two things, then you will get that error.
Not sure what to say about the 3rd party miners crashing... Sorry.
[2017-06-09 16:43:51] : MEMORY INIT ERROR: Obtaning SeLockMemoryPrivilege failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
In order to obtain SetLockMemoryPrivilege you must do the following:
1) Be running with elevated (Administrator) privileges
2) The user running the application must have the "Lock pages in memory" permission in GPEDIT.MSC under
/Local Computer Policy/Computer Configuration/Windows Settings/Security Settings/Local Policies/User Rights Assignment/
http://imgur.com/a/mY3Dl
If you haven't done those two things, then you will get that error.
Not sure what to say about the 3rd party miners crashing... Sorry.
Uninstall AMD drivers, then download and run DDU in Safe Mode --- reboot and install AMD 16.12.2 drivers. Check back here if it works or not for ya.
BUMP for exposure
My System:
Ryzen 7 1800x
Gigabyte AB350 Gaming 3 Motherboard
32GB Gskill Trident Z RAM at 2133Mhz
Sapphire Nitro+ OC RX480 8GB
all settings are out of the box with no OC'ing done by me.
First problem is I get this error set every time I start xmr stak cpu miner:
[2017-06-09 16:43:51] : MEMORY INIT ERROR: Obtaning SeLockMemoryPrivilege failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
XMR-Stak-CPU mining software, CPU Version.
Based on CPU mining code by wolf9466 (heavily optimized by myself).
Brought to you by fireice_uk under GPLv3.
Configurable dev donation level is set to 0.0 %
You can use following keys to display reports:
'h' - hashrate
'r' - results
'c' - connection
[2017-06-09 16:43:51] : Starting single thread, no affinity.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : Starting single thread, no affinity.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : Starting single thread, no affinity.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : Starting single thread, no affinity.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : Starting single thread, no affinity.
[2017-06-09 16:43:51] : Starting single thread, no affinity.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
The second issue I have is that 3rd Party miners black screen crash within a couple of hours but the regular miners run fine with no problems, just less profit.
What I have tried so far:
My paging file is set manually to 32GB max which is my RAM size.
All optimizations and setting I could find here, on github and various mining sites.
Verified that my System is not crashing due to heat.
If I run NiceHash as administrator I do not get the Memory Allocation Errors but it black screen crashes in less than an hour.
The few Blue Screens I have got are irql not equal or less than caused by atikmdag.sys
My memory passes a full run of Memtest 86.
I have tried AMD Drivers 17.6.1, 17.4.4, 16.11.5 and 15.11.
I have tried running NiceHash as admin with and without 3rd party miners and it always crashes within the hour. As stated above if I start NiceHash with normal permissions and no 3rd party miners it runs fine just at half the profit margin (~$4 a day instead of ~$7).
Anyone have an idea on what to try next?
Ryzen 7 1800x
Gigabyte AB350 Gaming 3 Motherboard
32GB Gskill Trident Z RAM at 2133Mhz
Sapphire Nitro+ OC RX480 8GB
all settings are out of the box with no OC'ing done by me.
First problem is I get this error set every time I start xmr stak cpu miner:
[2017-06-09 16:43:51] : MEMORY INIT ERROR: Obtaning SeLockMemoryPrivilege failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
XMR-Stak-CPU mining software, CPU Version.
Based on CPU mining code by wolf9466 (heavily optimized by myself).
Brought to you by fireice_uk under GPLv3.
Configurable dev donation level is set to 0.0 %
You can use following keys to display reports:
'h' - hashrate
'r' - results
'c' - connection
[2017-06-09 16:43:51] : Starting single thread, no affinity.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : Starting single thread, no affinity.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : Starting single thread, no affinity.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : Starting single thread, no affinity.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : Starting single thread, no affinity.
[2017-06-09 16:43:51] : Starting single thread, no affinity.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
The second issue I have is that 3rd Party miners black screen crash within a couple of hours but the regular miners run fine with no problems, just less profit.
What I have tried so far:
My paging file is set manually to 32GB max which is my RAM size.
All optimizations and setting I could find here, on github and various mining sites.
Verified that my System is not crashing due to heat.
If I run NiceHash as administrator I do not get the Memory Allocation Errors but it black screen crashes in less than an hour.
The few Blue Screens I have got are irql not equal or less than caused by atikmdag.sys
My memory passes a full run of Memtest 86.
I have tried AMD Drivers 17.6.1, 17.4.4, 16.11.5 and 15.11.
I have tried running NiceHash as admin with and without 3rd party miners and it always crashes within the hour. As stated above if I start NiceHash with normal permissions and no 3rd party miners it runs fine just at half the profit margin (~$4 a day instead of ~$7).
Anyone have an idea on what to try next?
Jump to: