search

nicehash / NiceHashMiner

NiceHash Miner
Other
483 stars 217 forks source link

XMRig - failed to start WinRing0 driver, error 183 since NiceHashMiner version 3.0.6.6 #2537

Closed spajdrEX closed 2 years ago

spajdrEX commented 3 years ago

When running NiceHashMiner as admin + XMRig miner then starting from version 3.0.6.6 following issue is being reported.: [2021-10-25 14:52:59.819] msr failed to start WinRing0 driver, error 183 [2021-10-25 14:52:59.834] msr FAILED TO APPLY MSR MOD, HASHRATE WILL BE LOW

This result in 5-7% performance loss

When ENABLED under Advanced -> Disable Device Status Monitoring and restarting NiceHashMiner fixes it (running as admin) but of course no temperatures are shown.

I'm running AMD 5600X under Windows 11 Pro , 22000.282 (21H2)

BobbyMcPrescott commented 3 years ago

I wish this was the only issue, as I'm sure it would be much easier to fix. Good to know it isn't some Windows 11 update that broke 10 though, as I'm still stuck with one of the first gen Ryzens that don't work with 11.

I actually tried to reinstall it once just because it did actually start showing temps not only for my CPU, but also my 5700XT which previously showed no readings. Same issues. In addition to the topic of this post, there were errors everywhere. Miners would start with default settings mining to god knows where, massive lag, plugins fail to install and just hang there if you reboot and try to start over, etc. The whole program seems to have been thrown off a decimal point.

Oh, I guess it's worth asking, but I doubt it applies if you have 11 as I believe the issue with first gens and 11 is the same core issue, but does MSR mode work for you without it resetting randomly? I can only do Monero mining if I use that custom code that doesn't work in NH, or using NH and hiding the windows so it doesn't constantly reboot on top of what I'm doing.

spajdrEX commented 3 years ago

Issue still not fixed in NiceHashMiner version 3.0.6.8

sumwatt commented 3 years ago

I get the same issue in 3.0.68. The previous version worked as long as I ran it in Admin mode. I tried using the workaround (Disabling Device monitoring) and while I no longer see the error message, the hash rate is consistent with the degraded performance.

Win 11 Home AMD 3600 Radeon 5600XT

jh0bc commented 3 years ago

Same issue here with an i5 7600 + Win 10 with NiceHashMiner 3.0.6.8

This "When ENABLED under Advanced -> Disable Device Status Monitoring and restarting NiceHashMiner fixes it (running as admin)" worked to temp solve the problem.

VaelVictus commented 3 years ago

Three separate CPUs on three separate computers, running with Administrator, had this problem and the solution listed fixed it. I saw anywhere from a 10% to 50% performance boost across all three computers. Note I'm also running the latest xmrig on each of them, simply by placing the new xmrig files over the installation nicehash is using.

spajdrEX commented 2 years ago

Can't check now, but did latest update 3.0.6.9 fixed the issue?

jh0bc commented 2 years ago

Unfortunately no

tmiland commented 2 years ago

Made it work by:

  1. Delete/uninstall Nicehash Miner (remover folders and registry references)
  2. Delete WinRing0_1_2_0 reference in registry
  3. reboot
  4. Install with the installer (As user, not Admin) (Remember exceptions in antivirus for the install folder)

  5. Run Nicehash as Admin

    Version 3.0.6.9.

Stealrull commented 2 years ago

Still having the issue, tried what tmiland posted and no dice. Uninstalled, couldn't even find any mentions of WinRing in registry, deleted all entries of nicehash, rebooted, reinstalled, rebooted, ran as admin same issue still.

5950x running Version 3.0.6.9

Very weird bug I hope can get fixed soon.

satanforaday commented 2 years ago

I am still getting this error after upgrading to the last .9 build. Just wanted to let people know.

UltimateByte commented 2 years ago

Exact same issue as @satanforaday with 5950X. There is no occurrence of "WinRing0" in windows Registry, so I guess it's not worth reinstalling.

tmiland commented 2 years ago

The issue came back.

Temporary solution is to run XMRig with Awesome Miner (enable run mining process with Admin privs)

Start the miner and make sure it's working, then start XMRig with NH.

[2021-11-14 14:22:56.083]  msr      service WinRing0_1_2_0 already exists
[2021-11-14 14:22:56.083]  msr      service path: "\??\****\AwesomeMiner\LibreHardwareMonitorLib.sys"
[2021-11-14 14:22:56.577]  msr      register values for "ryzen_19h" preset have been set successfully (493 ms)
UltimateByte commented 2 years ago

@tmiland Thanks for sharing. Any procedure on how to run "Awesome Miner", more specifically, concurring with XMRig?

tmiland commented 2 years ago

@tmiland Thanks for sharing. Any procedure on how to run "Awesome Miner", more specifically, concurring with XMRig?

No problem.

Set up a new "managed profit miner", add nicehash pool and wallet, choose the CPU profile.

Go to options -> Managed miners -> Edit (miner) -> Environment, tick the checkbox (enable run mining process with Admin privs)

See: Getting started with CPU mining (Monero)

tmiland commented 2 years ago

If anyone needs to add the registry entry manually, you can use this: 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\WinRing0_1_2_0]
"Type"=dword:00000001
"Start"=dword:00000003
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):5c,00,3f,00,3f,00,5c,00,50,00,41,00,54,00,48,00,5f,00,54,00,\
  4f,00,5f,00,4d,00,49,00,4e,00,45,00,52,00,5c,00,57,00,69,00,6e,00,52,00,69,\
  00,6e,00,67,00,30,00,78,00,36,00,34,00,2e,00,73,00,79,00,73,00,00,00
"DisplayName"="WinRing0_1_2_0"

Save as WinRing0_1_2_0.reg

Open regedit (as admin), go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\WinRing0_1_2_0 and change ImagePath to the correct path.

E.g: C:\Users\User\AppData\Local\Programs\NiceHash Miner\miner_plugins\0e0a7320-94ec-11ea-a64d-17be303ea466\bins\16.0\xmrig-6.8.1\WinRing0x64.sys

Adding the entry fixed the issue at one time for me, so it might work for others as well.

bstrakt commented 2 years ago

This is not a fix, but is what I found: it seems that it conflicts with LibreHardwareMonitorLib.dll from app_3.0.6.9 folder of NiceHash. If monitoring is enabled, it loads that library and the service WinRing0 cannot be created.

UltimateByte commented 2 years ago

Now using Arch Linux as a daily driver. No more problem with this kind of Windowsy nonsense, hashrate is now a bit better. If you're an advanced PC user and are tired of Microsoft, might be worth learning Linux (not necessarily Arch, which is targetting advanced Linux users). OFC, I know this won't suit everyone, but I just wanted to remember that Windows isn't an absolute necessity.

roboyeti commented 2 years ago

This is not a fix, but is what I found: it seems that it conflicts with LibreHardwareMonitorLib.dll from app_3.0.6.9 folder of NiceHash. If monitoring is enabled, it loads that library and the service WinRing0 cannot be created.

Aha! You solved my issue. If I run LibreHardwareMonitor (the app) after xmrig runs, it works fine.

muratia commented 2 years ago

I have fixed the issue by downloading latest XMRig from the github and i replaced the old xmrig and it worked flawlessly

MrOrister commented 2 years ago

I have fixed the issue by downloading latest XMRig from the github and i replaced the old xmrig and it worked flawlessly

This worked for me also! and even service monitoring can be enabled.

Dohtar1337 commented 2 years ago

XMRig will be updated in the future

scorsy63 commented 9 months ago

I have fixed the issue by downloading latest XMRig from the github and i replaced the old xmrig and it worked flawlessly

This fixed it for me. I was running both NiceHashMiner and xmrig as admin and was still receiving the error message.

Vyeche commented 8 months ago

I have fixed the issue by downloading latest XMRig from the github and i replaced the old xmrig and it worked flawlessly

This worked for me also! and even service monitoring can be enabled.

Woo Wee worked for me, too.

image image