Download
DownloadThere are several most common stability issues that RandomX miners experience and ask repeatedly on reddit/github/elsewhere. Here's a little summary of what is known about them and how to fix them.
You either experience blue screens, the whole PC hangs or XMRig just randomly closes. The most common reason for this is unstable overclock or bad power supply. Try running stability tests such as:
If these tests don't pass, reduce overclock or try running your CPU and RAM at stock settings.
Note for AMD Ryzen owners: RandomX is very sensitive to FCLK instability and may crash even when everything else works, so try reducing FCLK to 1600 or less (corresponds to DDR4 speed 3200 or less) if it's unstable.
Some first gen Ryzen/EPYC CPUs have a hardware bug which prevents them from running RandomX at all. XMRig has built-in workaround for this, but it doesn't always work.
If XMRig closes immediately after startup and you have such CPU, you can try disabling Opcache in your BIOS. If there's no such option in BIOS, you can try using the following MSR mod setting in config.json:
"wrmsr": ["0xc0011020:0x0", "0xc0011021:0x60", "0xc0011022:0x510000", "0xc001102b:0x1808cc16"],Sometimes hashrate drops to almost 0 and then restores again. This is a known bug with Windows 10 scheduler, starting with Windows 10 v1903 and newer. The only known workaround for this is to unpin threads from cores like this (example for Ryzen 5 3600):
"rx": [-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1],In general, just edit your config.json and replace each core number with -1 in the "rx" array in config.json.
Other causes of low hashrate can be Windows background tasks running, especially memory compression and RunFullMemoryDiagnostic task. You can check Windows 10 tuning guide to find out how to turn them off.
More discussions about this issue: