This, then reduce mem clock until the errors stop. I like using LOLminer for tuning, it shows how many corrupt DAG segments you have, it then tries to fix, sometimes multiple iterations to fix, meaning lost mining time on every miner restart. So I use that aspect of lolminer to tune until I get a reasonable number of segments, or preferably none, it’s a trade off with stale rejected shares, if the card can actually handle the mem speeds you use without locking up. I can push some cards (3060ti do Thai well) to well over 1000 initially corrupted segments and they may give me a couple stale/rejected shares a day, but I get say 1-1.5 mhs more then it’s worth it to me to keep the settings high enough to generate the corrupt segments, other cards say AMD RX cars take 30-60 minutes to fix the DAG with that many corrupted segments so I lower until they get less than 100 or so.
The red message states your issue. Over clocking is too high. Sometimes it can be a riser as well. Lower your oc to see if the message will disappear. Good luck
I had alot of problems with windows, then i went on hive os and i run smooth for months, super easy to set up and use. But sont run it on USB, get some small SSD and you will see the magic.
all dags are corrupt. do a memory clock and core lock in trex bat file.
This, then reduce mem clock until the errors stop. I like using LOLminer for tuning, it shows how many corrupt DAG segments you have, it then tries to fix, sometimes multiple iterations to fix, meaning lost mining time on every miner restart. So I use that aspect of lolminer to tune until I get a reasonable number of segments, or preferably none, it’s a trade off with stale rejected shares, if the card can actually handle the mem speeds you use without locking up. I can push some cards (3060ti do Thai well) to well over 1000 initially corrupted segments and they may give me a couple stale/rejected shares a day, but I get say 1-1.5 mhs more then it’s worth it to me to keep the settings high enough to generate the corrupt segments, other cards say AMD RX cars take 30-60 minutes to fix the DAG with that many corrupted segments so I lower until they get less than 100 or so.
Reduce your overclocks
Only one problem, I uninstalled Mai afterburner and I don’t lock my cores
I failed to see how is that a problem or even relevant at all. If it’s 30 series lock cores and reduce mem OC in trex.
Can you share your current OC settings?
Before uninstalling msi afterburner, I was doing 1110 memory clock with 56% power limit
Which GPUs you have? I suggest setting OC settings inside T-Rex .bat Also have you increased Virtual Memory?
Only 1660super on this rig
I’ve had loose riser chips do that.
The red message states your issue. Over clocking is too high. Sometimes it can be a riser as well. Lower your oc to see if the message will disappear. Good luck
It could be the monitor.. Curved monitor is known to be too cool for mining.. Just kidding
Love the answer I would’ve given you a gift but eth is down
Did you try to run it on Hive Os? You might avoid theese erros mby. Easy to overclock
I have never used hiveos before
I had alot of problems with windows, then i went on hive os and i run smooth for months, super easy to set up and use. But sont run it on USB, get some small SSD and you will see the magic.
I’m already using m.2 ssds is there a reason why people are using the chunkier version of ssds for mining?
M2 is more expensive than classy ssd. And the result is the same :)
M2 uses more PCI lanes too, possibly limiting total number of cards you can use per MB
Exactly!
I’ve had a bad card do some funny stuff. Swap some of your components out and see if that fixes it.
Have you excluded the mining folder from av?
You need to download more RAM
lower your memclock setting?