I'm wondering if it is a heat issue. Can you run a temp monitoring program and observe the temperatures up to and during a crash? Try also not using miner control and just mine one select coin and see if you can make 12 hours. One card at a time, repeat process. If you're using a scrypt like JK's, then you aren't the only one getting crashes every 6 hours(mine does as well on 1.03). My theory on the scrypt switching is it fails to close the non profitable miner before opening up the other, and with high intensities(which is another issue you might be running into(if you're mining with -i intensity try removing that altogether))it causes a memory overlap and crash.
I'm running lyra2v2 right now without the 970 gtx in the bat file. Running great. Take a look on the OP. The 970 gtx is at 1413 core clock.. should be 1178..I think that is one of the problems. I'm just running the 2 980ti and 1 750ti test run.  If the 970 is not mining, why is it so hot? It's in a room.. temp 95 f 35 c and next to the other cards.. At room temp that card mines very cool about 68c on some algo's. If I run the other 970 gtx I have all by itself all cards removed .. it will crash immediately. I think I have a bad batch of 970 gtx cards. Which temp is for which card? It looks like the third card is at 79, isn't that ccminer GPU #2? Anyway if the cards crash at stock settings and reasonable temps they are defective. Double faults can easilly get you going in circles trying to troubleshoot. |
|
|
|
I'm wondering if it is a heat issue. Can you run a temp monitoring program and observe the temperatures up to and during a crash? Try also not using miner control and just mine one select coin and see if you can make 12 hours. One card at a time, repeat process. If you're using a scrypt like JK's, then you aren't the only one getting crashes every 6 hours(mine does as well on 1.03). My theory on the scrypt switching is it fails to close the non profitable miner before opening up the other, and with high intensities(which is another issue you might be running into(if you're mining with -i intensity try removing that altogether))it causes a memory overlap and crash.
I'm running lyra2v2 right now without the 970 gtx in the bat file. Running great. Take a look on the OP. The 970 gtx is at 1413 core clock.. should be 1178..I think that is one of the problems. I'm just running the 2 980ti and 1 750ti test run. If the 970 is not mining, why is it so hot? |
|
|
|
Yes exactly.... it crashed... card #2 again 970 gtx now going to mine without it in the bat file on lyra2v2 only no switching. But the crash .....it was mining with only the 970 and scrolling fast but mining. I have a lot of things that must get done... so I will be on and off the thread for the next day or 2.  If it still crashes I will remove the card and try that next.  Thx  This is not good hashing, that card is sick. |
|
|
|
You're juggling too many things at once, start isolating cards. If you have multiple faults you have to seperate them.
You seem to have an issue triggerred by heat, you need to find out which card it is and you need to monitor
the GPU temperatures to confirm it's temp related.
That's what I was doing... now im mining one algo only and so far no crashes. Room temp 86 f. I'm also posting extra info for my own notes. OK, so your following the algo switching lead. Following up with that, has it failed imediately after a reboot, ie the first algo starts up but crashes after a few minutes? Or does it run fine for a while algo switching and not crashing until suddenly it crashes? Monitor the GPU temperatures, not the room remperatures, to see if there is a correlation. You will also need to identify which card is crashing. If you don't want to test one card at a time you can test minus 1 card at a time, remove one card, test, resinstall, remove a different card, repeat. |
|
|
|
Despite the lower model number the 750ti uses a newer architecture, faster and more efficient. |
|
|
|
|
You're juggling too many things at once, start isolating cards. If you have multiple faults you have to seperate them.
You seem to have an issue triggerred by heat, you need to find out which card it is and you need to monitor
the GPU temperatures to confirm it's temp related.
|
|
|
|
Ok first crash 5 hours later at 78f.
Just to be clear, does it always start mining then crash due to access blocked or does it ever crash on ccminer startup? Does it crash if you run a single algo without ever swicthing? Have you been monitoring GPU temps? |
|
|
|
Right now it is room temperature. It seems to be so much more stable. Today it will go up to and beyond 32c. At that point it won't mine for more then a few minutes but it should and was 4 days straight without a crash one time about a week ago.
I'm mining muti algo switching with Minercontrol.
And right now everything is fine but as the temperature rises it should start crashing.
I will be doing things as suggested as soon as possible.
Keep notes of what algos fail to start to see if it's algo specific. Also try to characterize the failures in more detail. Does it ever fail on the first algo or does it switch a few times before it fails? Once you have a failure does it then fail consistently. How does it recover, do you reboot? |
|
|
|
My apologies to everyone helping me especially crackfoo for messing up his thread.
I have so many other personal problems hitting me at the same time.
I started this thread on this extremely annoying problem I have been have for some time with my one rig.
Thank you all for your understanding.
When you're ready to dig into this post your rig configs for reference. You'll need to follow a precise process to avoid confusion. Make sure you can identify each component if they look too similar. Keep good notes. Limit the number of variables that need to be controlled. Avoid assumptions and prove conclusions. The first step is to test all your HW. Minimal configs are best for this, one GPU, one riser. Test them one at a time to ensure they are all ok. If you have 2 rigs test all cards in both rigs to increase your confidence. Once you've tried them all focus on any failures. Look for pattenrs, if there is a persistent fault the faulty component should become obvious as it moves and the problem follows it. If it's intermittent it gets trickier. That's enough to start. |
|
|
|
Finally I see the error massage .. ccminer has been blocked from accessing the graphics driver.
Any help plz
Sorry Crackfoo for messing up your thread.
Are you running it as administrator? No.... giving that a try. EDIT:Same thing. an app....blocked ... ccminer has been blocked from accessing the graphics driver. How do I find out what app. anyone plz. At lest I found why its crashing. Sorry Crackfoo for messing up your thread. Reinstalling drivers. How do I find out what app. anyone plz. I had to shut that rig down for now. It has nothing to do with the pool, I suggest a seperate thread. It's a problem between ccminer and the GPU, which includes the OS and the drivers. Have you googled the error message for clues as to its meaning? Beyond that have you done any HW troubleshooting? Have you been messing with the clocks or voltage? Can you identify a trigger? Part of the time it was the pool read back me talking to Crackfoo I'm giving.. up the only solution I have is to take out the gigabyte 970. I'm done. 5 months of this problem ..it worked great for 4 days when crackfoo made an adjustment but it is a multiple problem. Putting 2x 970 gigabyte gtx g1 on the shelf. Garbage cards. My apologies for offering to help. Sorry joblo my sincere apologies. I have so many other things hitting me at once..legal matters that I don't know which why is up. I hope you understand. Thank you. As I said 4 days of mining without a problem after crackfoo did a pool adjustment no messing with anything. No problem. I can help when you're ready. I did this for a living and was pretty good at it, but it was a completely different system. |
|
|
|
Finally I see the error massage .. ccminer has been blocked from accessing the graphics driver.
Any help plz
Sorry Crackfoo for messing up your thread.
Are you running it as administrator? No.... giving that a try. EDIT:Same thing. an app....blocked ... ccminer has been blocked from accessing the graphics driver. How do I find out what app. anyone plz. At lest I found why its crashing. Sorry Crackfoo for messing up your thread. Reinstalling drivers. How do I find out what app. anyone plz. I had to shut that rig down for now. It has nothing to do with the pool, I suggest a seperate thread. It's a problem between ccminer and the GPU, which includes the OS and the drivers. Have you googled the error message for clues as to its meaning? Beyond that have you done any HW troubleshooting? Have you been messing with the clocks or voltage? Can you identify a trigger? Part of the time it was the pool read back me talking to Crackfoo I'm giving.. up the only solution I have is to take out the gigabyte 970. I'm done. 5 months of this problem ..it worked great for 4 days when crackfoo made an adjustment but it is a multiple problem. Putting 2x 970 gigabyte gtx g1 on the shelf. Garbage cards. My apologies for offering to help. |
|
|
|
Don't know about SIA but it looks like yiimp already supports LBRY. |
|
|
|
Finally I see the error massage .. ccminer has been blocked from accessing the graphics driver.
Any help plz
Sorry Crackfoo for messing up your thread.
Are you running it as administrator? No.... giving that a try. EDIT:Same thing. an app....blocked ... ccminer has been blocked from accessing the graphics driver. How do I find out what app. anyone plz. At lest I found why its crashing. Sorry Crackfoo for messing up your thread. Reinstalling drivers. How do I find out what app. anyone plz. I had to shut that rig down for now. It has nothing to do with the pool, I suggest a seperate thread. It's a problem between ccminer and the GPU, which includes the OS and the drivers. Have you googled the error message for clues as to its meaning? Beyond that have you done any HW troubleshooting? Have you been messing with the clocks or voltage? Can you identify a trigger? |
|
|
|
|
If you can afford the GPUs to fill the Seasonic you can afford a third PSU. You're just asking for trouble trying
to power 2 mobos with one PSU.
|
|
|
|
Small request to developers, please show the intensity on GPUs when your miner is running somewhere. You shouldn't need to request the intensity for a GPU so you can tweak it. Saves both parties a extra step.
That would be nice, unfortunately the default intensity of an algo is set inside that algo-specific file and is not store anywhere, so there is no nice way of doing it. To do it the right way, there should be an algo structure holding default intensities for the various cards, so that it is initialised with either the user supplied one or the default, and printed at the beginning. To be fair, sgminer doesn't even have algo-specific (let alone device-specific) default intensities, AFAIK. Anyways it's pretty easy to spot them, just look at the file named as the algo plus ".cu", near the beginning you will see the code which sets intensities (throughput). It's already implemented in SP_MOD v80. |
|
|
|
Since the hard fork was announced the locked up supply has shrunk from 65% of total to 56%.
Mining has ceased to be a factor in avalable supply and maturing TDs have not yet started to ramp up.
After a brief pre-fork price and volume surge trading has almost dried up completely.
Yet the available supply is growing faster that pre-fork.
It seems a lot of us evil miners were actually hodlers after all. Who would have thought?
I'd guess that is to do with Yobit suspending deposits until they have updated. The fact is there is more hodl coming out of TDs than going in, in spite of miners being forced to lock up. Maturing TDs aren't being renewed regardless of Yobit's issues. Prior to the fork the percentage locked up was dropping slowly but the absolute hodl was still rising due to the the increasing supply. Now the absolute hodl has dropped 100k since the fork. |
|
|
|
|
Since the hard fork was announced the locked up supply has shrunk from 65% of total to 56%.
Mining has ceased to be a factor in avalable supply and maturing TDs have not yet started to ramp up.
After a brief pre-fork price and volume surge trading has almost dried up completely.
Yet the available supply is growing faster that pre-fork.
It seems a lot of us evil miners were actually hodlers after all. Who would have thought?
|
|
|
|
No blocksource available.
With v1 the wallet worked ok after the fork (no mining). Today when I start up I get no block source available.
Updated to v2, same problem.
I had no hodlcoin.conf before so I created one in datadir. Same problem.
Started with -conf=hodlcoin.conf, same problem.
started with -addnode=104.154.55.111, same problem.
I never mined from the wallet so I shouldn't be banned.
The debug window shows zero connections, current block number 86003,
& current block time Mon Jul 11 15:52:53 20016.
debug.log...
2016-07-12 15:09:55 Loading addresses from DNS seeds (could take a while)
2016-07-12 15:09:55 7 addresses found from DNS seeds
2016-07-12 15:09:55 dnsseed thread exit
2016-07-12 15:10:01 socket recv error Connection reset by peer (104)
2016-07-12 15:10:03 socket recv error Connection reset by peer (104)
2016-07-12 15:10:15 socket recv error Connection reset by peer (104)
2016-07-12 15:13:23 socket recv error Connection reset by peer (104)
Maybe banned for 24hrs for relaying invalid blocks - 86003 sounds a bit iffy too - i would try a -reindex and reconnect in 24hrs. I didn't do anything to get banned. I had the v1 wallet open at the time of the fork, just to see if it would stay connected. When I saw the block number over 86000 I closed the wallet. I have made no transactions from the wallet since before the fork and the only transaction since was a payout from suprnova, with the wallet client closed. I'll reindex and try again in a few hours, 24 hours from the last block time. Edit: Working, needed to reindex to fix. |
|
|
|
|
No blocksource available.
With v1 the wallet worked ok after the fork (no mining). Today when I start up I get no block source available.
Updated to v2, same problem.
I had no hodlcoin.conf before so I created one in datadir. Same problem.
Started with -conf=hodlcoin.conf, same problem.
started with -addnode=104.154.55.111, same problem.
I never mined from the wallet so I shouldn't be banned.
The debug window shows zero connections, current block number 86003,
& current block time Mon Jul 11 15:52:53 20016.
debug.log...
2016-07-12 15:09:55 Loading addresses from DNS seeds (could take a while)
2016-07-12 15:09:55 7 addresses found from DNS seeds
2016-07-12 15:09:55 dnsseed thread exit
2016-07-12 15:10:01 socket recv error Connection reset by peer (104)
2016-07-12 15:10:03 socket recv error Connection reset by peer (104)
2016-07-12 15:10:15 socket recv error Connection reset by peer (104)
2016-07-12 15:13:23 socket recv error Connection reset by peer (104)
|
|
|
|
|
Show Posts
