You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Safe DAG generation is not working. Whenever the dag file gets corrupted, the excavator gets stuck in a loop of corrupted dag files, giving only rejected shares. Also, the excavator shows "Safe DAG generation: disabled" at the beggining, even though I never disabled it. I even uninstalled everything, and reinstalled and it keeps starting like that.
To Reproduce
Steps to reproduce the behavior:
Just start mining
Expected behavior
Screenshots
Version affected (please complete the following information):
Version number v1.8.6.2
STABLE
NVIDIA driver version
546.17
Hardware
2 evga 3080 and one 3060ti. 3060ti connected directly to motherboard, 3080s connected through riser.
CPU: ryzen 5950x
Logs
Activate logging first, then record event - bug - then export logs into a .zip file and attach it when submitting this issue. log.zip
Additional context
On windows 11
The text was updated successfully, but these errors were encountered:
Describe the bug
Safe DAG generation is not working. Whenever the dag file gets corrupted, the excavator gets stuck in a loop of corrupted dag files, giving only rejected shares. Also, the excavator shows "Safe DAG generation: disabled" at the beggining, even though I never disabled it. I even uninstalled everything, and reinstalled and it keeps starting like that.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
Version affected (please complete the following information):
NVIDIA driver version
546.17
Hardware
2 evga 3080 and one 3060ti. 3060ti connected directly to motherboard, 3080s connected through riser.
CPU: ryzen 5950x
Logs
Activate logging first, then record event - bug - then export logs into a .zip file and attach it when submitting this issue.
log.zip
Additional context
On windows 11
The text was updated successfully, but these errors were encountered: