This forum thread needs a solution.
Kudos0

hashing at 25MH/s but balance not changing

So my system as been mining without issue for about 10 days. I run an RTX 3060 on Windows 10 latest build and my hash rate is about 25MH/s +/- 5Mh/s. All was good until a few days ago. Norton would show "Calculating" for ages and would not start mining, or it would show "waiting for idle" for like half an hour or more when there were no apps utilizing GPU (checked in task manager).

I uninstalled Norton and clean installed and it seemed to resolve the issue of "waiting for idle" but shortly after, a new issue has come up. Now I see 100% usage, I see 25Mh/s, and hours sitting at this number but there is no change in accumulated Ethereum. I track it daily and I have seen a change of 0.000001 Ethereum after mining for half a day or more. I usually mine about 0.000300 over the course of a day so that yield is 99.3% less than I should be getting.

The strange thing is that I know the GPU is working as I can see the memory being utilized and core temp rising but there is no change in Ethereum. So if my card is mining, where is the mined Ethereum going?

Sometimes it shows it is mining, but I can see that it is not. The figures on the online wallet tool and the Crypto client screens never match either. Local client often shows mining and online shows idle.

What has changed recently so my card is mining at 0.3% of what is was before, and how do I fix it?

I've uninstalled Norton and reinstalled, done the latest live update, and updated to the latest GPU drivers. I have the PC on 24/7 for the purpose of mining when I'm not on it. If it is just wasted electricity and adding wear to my PC and components, I have better things to do with my time and energy than search forums and constantly stop and start the service hoping that it will start hashing and not just sit on "Calculating" endlessly. I'm not expecting to get rich over night off this casual mining, but I don't want it to be a waste of time and money leaving the pc on 24/7 if it will not be mining or if I am note getting credited for the mined Ethereum. I think this is an early release of the product however I expect it to work more reliably especially if there is a financial cost to me when it does not work as expected and potential financial gain for the vendor at my expense.

Please advise on how to resolve this issue. Thanks.

Replies

Kudos0

Re: hashing at 25MH/s but balance not changing

can you narrow the timing down so we can take a look, sounds like on dec 2nd it started working differently, and the 10 days prior it was fine

Kudos0

Re: hashing at 25MH/s but balance not changing

It has been flaky for some time... taking forever to stop showing "Calculating", and needing to manually stop then start mining again in the hopes that it would catch and start mining. I would say for the past 5 days it's been flaky. All day Dec 4 .000136 was mined and all day Dec 5 .00004 was mined. Today has been .000089. I typically see about .000300 on a good day and .000200 on a day with less idle time (more computer usage). It has been more reliable today but as an example, it's been mining for about 1 hour and it hasn't changed at all.... GPU is drawing 132Watts so it's working, but the Ethereum totals haven't changed in at least 1hr. I can usually see it change incrementally every 5-10 minutes or so. It's hashing at 25MH/s.

Another oddity is that the online tool shows it's hashing at 4.01 MH/s and the desktop client shows 24.6 MH/s +/- 5MH/s

Kudos0

Re: hashing at 25MH/s but balance not changing

Reporting that I see dead mining time again the last couple of hrs.  I started my miner up at about 1249 pm, ran for about 6.4 hrs.  It was decent until the last couple of hrs where it was mining but ZERO balance increase.  Looks like the old problem from back in Oct.  My rate of increase today was about 55% of my low par.  I shut it down.

Kudos0

Re: hashing at 25MH/s but balance not changing

I'm having the same issues with dead mining time. Hashing at 26 MH/s but no change in balance, it started happening a few hours ago. This  is a issue on Norton's end. When can we expect for this to be resolved?

This thread is closed from further comment. Please visit the forum to start a new thread.