Mining

Failed to Apply MSR mod Nicehash Fix CPU Mining

Failed to Apply MSR mod Nicehash Fix CPU Mining

#Failed #Apply #MSR #mod #Nicehash #Fix #CPU #Mining

“brandon coin”

BC PC Store link

Facebook Page

shop email
brandoncoincomputers@gmail.com

PC Shop Launch Shirts

Ebay…

source

 

To see the full content, share this page by clicking one of the buttons below

Related Articles

26 Comments

  1. Update to the latest XMRig 6.21.0 and the errors should go away, I was still getting the errors even running as administrator with the NH version. Ryzen 7000 appears to throw up an additional error as well. You may also get a slight bump in hash rate.

  2. Worked for me only when I followed the steps you outlined AND after I started mining (no fixes appeared) I paused the mining and went back into settings and enabled device monitoring. When I unpaused the miner, it loads properly. So I have to start with device monitoring disabled, pause the mining, enable device monitoring, then unpause the miner. I'll take it!😁😁

  3. Did the admin changes and restarted. Still get 1-failed to start winRing0, driver error 183, then failed to apply msr mod?
    I’ll look through ur comments. Some having fixed this. Thanks Brandon for ur help.

  4. It's funny to see everyone jumping on the CPU mining tchoo-tchoo-train now 😂
    Please keep in mind people, the more hashrate is coming on the network, the more difficulty will rise and the less yield you will get. Which means only one thing, the price of the coin will have to increase in order to remain profitable. So far, the market does not seem to go in that direction 😅
    Happy mining jellyfish nation 🔥🚀

  5. Thank you sir. My problem was I was using a non administrator login. When I logged onto an admin and did these steps it worked fine. went from 10k to 14k. Then I hit all my other machines, worked on all. Thank you again. Happy Holidays!

  6. Run xmrig as admin once reboot then hugepages are enabled on Windows. In Linux or hiveos you can get more hashrate 1-2% by editing or adding "randomx": { "1gb-pages": true }

  7. Thank you for this! It fixed it for me. Other guides did not mention changing the compatibility setting of XMRig as well; I believe that is what made the difference in my case.

Leave a Reply