Topic: Any recent ETH changes affecting 3.5MB GPU re DAG? (Read 345 times)
It's not the Dag file size, since the current ETH Dag file is nowhere near even 3GB. It's a driver or PCI-E Bios configuration issue. I would uninstall the driver in safe mode using DDU and then reinstall the drivers. I was having a similar issue after adding a GTX 1070 to a rig with AMD cards and changing the PCI-E slot speed for the Nvidia cards in the motherboard Bios to GEN 2 solved it.
Have just come back to start rig again after approx 3 weeks away.
Working fine before. Fired up, claymore gives CUDA errors, and unable re DAG file.
NVIDIA GTX 970s, sold as 4GB, but realistic have 3.5GB story.
Was working fine on Claymore 9.7. Updated to 10, same issue.
Will work it out (as painfully as we all do), but just wondered if this may be an issue encountered by many recently, or is just a matter of updating / reconfiguring etc...
Questioning where at GPU MB size and DAG size.
How, and if any, are the implications regarding recent fork affecting?
Obv, PoS soon.
Working fine before. Fired up, claymore gives CUDA errors, and unable re DAG file.
NVIDIA GTX 970s, sold as 4GB, but realistic have 3.5GB story.
Was working fine on Claymore 9.7. Updated to 10, same issue.
Will work it out (as painfully as we all do), but just wondered if this may be an issue encountered by many recently, or is just a matter of updating / reconfiguring etc...
Questioning where at GPU MB size and DAG size.
How, and if any, are the implications regarding recent fork affecting?
Obv, PoS soon.
Jump to: