Hello
My Ryzen 1700 could mine wow/r with 550H/s, at 3,8GHz boost. Same result for Monero, and it working now, too.
But, when I tried to mine this new WOW, the comp crashed after few minutes. The hash till crash was about 3800H/s.
Its good number I think, but why this constantly crash? What should I set up different, to work?
PS I see now, that somebody wrote, the Hashrate jump from 300-400 H/s to 3kH/s. Then, maybe my 3800 isnt so good instead of 550 stable. It should be 4500-5000.
My Ryzen 1700 could mine wow/r with 550H/s, at 3,8GHz boost. Same result for Monero, and it working now, too.
But, when I tried to mine this new WOW, the comp crashed after few minutes. The hash till crash was about 3800H/s.
Its good number I think, but why this constantly crash? What should I set up different, to work?
PS I see now, that somebody wrote, the Hashrate jump from 300-400 H/s to 3kH/s. Then, maybe my 3800 isnt so good instead of 550 stable. It should be 4500-5000.
Try to mine without overclock.
I will, but momentarily, Im not near the comp. I use TV, and the overclock is set up in Bios. I tried to lowered the clockspeed with F-Stream Tuning, but this also crashad the comp. I mean, an automatic looff (what I never seen before), and after login no matter what I do, the logoff happened again and again after few seconds.
Win10/64
Well, I think first try turning off overclock, but if it still crashes then it would be good if you can run at higher log level, 2 or 3, and then crash it again and share the logs.
Ok, Im stupid. I realized, that I had this problem, when I started the xmrig_2.15, with my previously config.json from 2.13 version. If I started 2.15, where I set up only "url" and "user" in config.json and changed nothing else, I got n/a H/s. I tried then with added 7 more thread (first used only this 1, what is in original config file), but same situation.
I downloaded then the RandomX-benchmark. When I started this program, I got error message: "Dataset allocation failed".
What should I do? Definitely, I must set up something in config.json, but I dont know what.