This forum is a place to discuss mining pools, features, etc. Topics can include but are not limited to PROHASHING pool.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
that happened with mine a few times and i just let it run, see if it did its own thing and it doesnt, it just continues to default to restarting in 10 seconds, the length of time before it registers the damaged DAG does flucuate though which gave me false hope , and then i just did the same as you killed it, i noticed tohugh that if i change my virtual memory paging file size for the drives from 5604 (default) to 14000 i have 16gb of ram to play with so i just threw a number in, and the damaged dag file from OC error hasnt happened since, im pulling 21.9Mh/s from a msi geforce 1650 4gb ddr5 ventus 68w at 52celcius as we speak... most people are getting 14-19.. and higher temps as well, ive also noticed that the damaged dag happens more when i try and increase the clocks just a little more each time by 5-10 that there is the slightest lag for it to register which is when the miner is suspecting the dag is damaged, but if i do 2-4 increments like 2 for clock and 4 for memory i have no issues, im scared to try and get any more out of mine cause shes offering well more then what shes bargained for ,bMeister1 wrote: ↑Thu Jan 27, 2022 8:22 pm I'm not entirely sure what happens at that point. Every time Gminer tells me the DAG is damaged while I'm testing overclock settings, I just kill it and tweak the settings until it works. My assumption is that if the DAG breaks then any shares submitted will be invalid since the data being used to process solutions is at least partially corrupted.
Total paging file size for all drives
Minimum allowed: 16mb