Topic: Litecoin Mining - Crashing; Bitcoin Works (Read 2595 times)
Does it matter? Bitcoin is more profitable than litecoin now.
A lot of shit advice in this thread. This could have been solved in post #2 (if poster #2 hadn't been a moron).
I haven't tested drivers above 13.1, and you should use the current cgminer (3.1.1).
In Windows, cmd.exe, run this:
Your cgminer.conf needs nothing more than to be very basic:
After your .bin file is created, you can add the thread-concurrency and worksize from the filename "xxxxxxxxxxxtcxxxxxwxxx".
Of course, after you're done setting up, set the fan speeds and overclocks to what you need.
I haven't tested drivers above 13.1, and you should use the current cgminer (3.1.1).
In Windows, cmd.exe, run this:
Code:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_USE_SYNC_OBJECTS 1
Your cgminer.conf needs nothing more than to be very basic:
Code:
{
"pools" : [
{
"url" : "",
"user" : "",
"pass" : ""
}
],
"gpu-fan" : "100",
"intensity" : "20",
"queue" : "0",
"scrypt" : true,
"kernel-path" : "/usr/local/bin"
}
"pools" : [
{
"url" : "",
"user" : "",
"pass" : ""
}
],
"gpu-fan" : "100",
"intensity" : "20",
"queue" : "0",
"scrypt" : true,
"kernel-path" : "/usr/local/bin"
}
After your .bin file is created, you can add the thread-concurrency and worksize from the filename "xxxxxxxxxxxtcxxxxxwxxx".
Of course, after you're done setting up, set the fan speeds and overclocks to what you need.
Thanks! I have it working now.
Also, I think that thread-concurrency was an issue as well. Anything above 6144 will cause it to crash.
Lastly, although it is now mining, I am getting a very high stale rate with CGMiner (2 accepted, like 10 rejected). GUIMiner is doing better, but perhaps this is a pool issue at the moment though because GUIMiner is at 14 accepted, 4 rejected atm. - Burnsides Pool
Edit: I tried running on the coinotron pool. CGMiner will throw an error about "hashrate above target" when I run with coinotron using stratum, but guiminer has given me 100% acceptance rate using coinotron.
I'm sure guiminer uses some non-standard settings. There could still be an issue with your thread-concurrency. Did you try values above 10000? 6970 runs great with 14208 (my 6950 is flashed to 6970).
I tried higher values and no go. In GUIMiner the highest I can run at is 6400
A lot of shit advice in this thread. This could have been solved in post #2 (if poster #2 hadn't been a moron).
I haven't tested drivers above 13.1, and you should use the current cgminer (3.1.1).
In Windows, cmd.exe, run this:
Your cgminer.conf needs nothing more than to be very basic:
After your .bin file is created, you can add the thread-concurrency and worksize from the filename "xxxxxxxxxxxtcxxxxxwxxx".
Of course, after you're done setting up, set the fan speeds and overclocks to what you need.
I haven't tested drivers above 13.1, and you should use the current cgminer (3.1.1).
In Windows, cmd.exe, run this:
Code:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_USE_SYNC_OBJECTS 1
Your cgminer.conf needs nothing more than to be very basic:
Code:
{
"pools" : [
{
"url" : "",
"user" : "",
"pass" : ""
}
],
"gpu-fan" : "100",
"intensity" : "20",
"queue" : "0",
"scrypt" : true,
"kernel-path" : "/usr/local/bin"
}
"pools" : [
{
"url" : "",
"user" : "",
"pass" : ""
}
],
"gpu-fan" : "100",
"intensity" : "20",
"queue" : "0",
"scrypt" : true,
"kernel-path" : "/usr/local/bin"
}
After your .bin file is created, you can add the thread-concurrency and worksize from the filename "xxxxxxxxxxxtcxxxxxwxxx".
Of course, after you're done setting up, set the fan speeds and overclocks to what you need.
Thanks! I have it working now.
Also, I think that thread-concurrency was an issue as well. Anything above 6144 will cause it to crash.
Lastly, although it is now mining, I am getting a very high stale rate with CGMiner (2 accepted, like 10 rejected). GUIMiner is doing better, but perhaps this is a pool issue at the moment though because GUIMiner is at 14 accepted, 4 rejected atm. - Burnsides Pool
Edit: I tried running on the coinotron pool. CGMiner will throw an error about "hashrate above target" when I run with coinotron using stratum, but guiminer has given me 100% acceptance rate using coinotron.
I'm sure guiminer uses some non-standard settings. There could still be an issue with your thread-concurrency. Did you try values above 10000? 6970 runs great with 14208 (my 6950 is flashed to 6970).
A lot of shit advice in this thread. This could have been solved in post #2 (if poster #2 hadn't been a moron).
I haven't tested drivers above 13.1, and you should use the current cgminer (3.1.1).
In Windows, cmd.exe, run this:
Your cgminer.conf needs nothing more than to be very basic:
After your .bin file is created, you can add the thread-concurrency and worksize from the filename "xxxxxxxxxxxtcxxxxxwxxx".
Of course, after you're done setting up, set the fan speeds and overclocks to what you need.
I haven't tested drivers above 13.1, and you should use the current cgminer (3.1.1).
In Windows, cmd.exe, run this:
Code:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_USE_SYNC_OBJECTS 1
Your cgminer.conf needs nothing more than to be very basic:
Code:
{
"pools" : [
{
"url" : "",
"user" : "",
"pass" : ""
}
],
"gpu-fan" : "100",
"intensity" : "20",
"queue" : "0",
"scrypt" : true,
"kernel-path" : "/usr/local/bin"
}
"pools" : [
{
"url" : "",
"user" : "",
"pass" : ""
}
],
"gpu-fan" : "100",
"intensity" : "20",
"queue" : "0",
"scrypt" : true,
"kernel-path" : "/usr/local/bin"
}
After your .bin file is created, you can add the thread-concurrency and worksize from the filename "xxxxxxxxxxxtcxxxxxwxxx".
Of course, after you're done setting up, set the fan speeds and overclocks to what you need.
Thanks! I have it working now.
Also, I think that thread-concurrency was an issue as well. Anything above 6144 will cause it to crash.
Lastly, although it is now mining, I am getting a very high stale rate with CGMiner (2 accepted, like 10 rejected). GUIMiner is doing better, but perhaps this is a pool issue at the moment though because GUIMiner is at 14 accepted, 4 rejected atm. - Burnsides Pool
Edit: I tried running on the coinotron pool. CGMiner will throw an error about "hashrate above target" when I run with coinotron using stratum, but guiminer has given me 100% acceptance rate using coinotron.
^ Really unnecessary.
Indeed, not sure who the hell these people are running around giving 'advice'. It's damned annoying. Throw in a few linux noobs who think they are special for using terminal and the odd idiot who just likes to cause problems = 99% of the new bitcointalk alt section 'advisers'.
Anyways, as for driver version, I've tested basically every driver since 12.6 with scrypt mining....They *all* work with seemingly minor variation at most.
A lot of shit advice in this thread. This could have been solved in post #2 (if poster #2 hadn't been a moron).
I haven't tested drivers above 13.1, and you should use the current cgminer (3.1.1).
In Windows, cmd.exe, run this:
Your cgminer.conf needs nothing more than to be very basic:
After your .bin file is created, you can add the thread-concurrency and worksize from the filename "xxxxxxxxxxxtcxxxxxwxxx".
Of course, after you're done setting up, set the fan speeds and overclocks to what you need.
I haven't tested drivers above 13.1, and you should use the current cgminer (3.1.1).
In Windows, cmd.exe, run this:
Code:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_USE_SYNC_OBJECTS 1
Your cgminer.conf needs nothing more than to be very basic:
Code:
{
"pools" : [
{
"url" : "",
"user" : "",
"pass" : ""
}
],
"gpu-fan" : "100",
"intensity" : "20",
"queue" : "0",
"scrypt" : true,
"kernel-path" : "/usr/local/bin"
}
"pools" : [
{
"url" : "",
"user" : "",
"pass" : ""
}
],
"gpu-fan" : "100",
"intensity" : "20",
"queue" : "0",
"scrypt" : true,
"kernel-path" : "/usr/local/bin"
}
After your .bin file is created, you can add the thread-concurrency and worksize from the filename "xxxxxxxxxxxtcxxxxxwxxx".
Of course, after you're done setting up, set the fan speeds and overclocks to what you need.
Indeed, not sure who the hell these people are running around giving 'advice'. It's damned annoying. Throw in a few linux noobs who think they are special for using terminal and the odd idiot who just likes to cause problems = 99% of the new bitcointalk alt section 'advisers'.
Anyways, as for driver version, I've tested basically every driver since 12.6 with scrypt mining....They *all* work with seemingly minor variation at most.
I was having the same problem, in my case, in error description it said that the problem was caused by amdocl64.dll crashing whenever I run the miner, didn't allowing me to even change the conf file, my solution was download the original dll from here: http://es.originaldll.com/file/amdocl64.dll/8872.html and now is working fine
hope this help you
hope this help you
A lot of shit advice in this thread. This could have been solved in post #2 (if poster #2 hadn't been a moron).
I haven't tested drivers above 13.1, and you should use the current cgminer (3.1.1).
In Windows, cmd.exe, run this:
Your cgminer.conf needs nothing more than to be very basic:
After your .bin file is created, you can add the thread-concurrency and worksize from the filename "xxxxxxxxxxxtcxxxxxwxxx".
Of course, after you're done setting up, set the fan speeds and overclocks to what you need.
I haven't tested drivers above 13.1, and you should use the current cgminer (3.1.1).
In Windows, cmd.exe, run this:
Code:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_USE_SYNC_OBJECTS 1
Your cgminer.conf needs nothing more than to be very basic:
Code:
{
"pools" : [
{
"url" : "",
"user" : "",
"pass" : ""
}
],
"gpu-fan" : "100",
"intensity" : "20",
"queue" : "0",
"scrypt" : true,
"kernel-path" : "/usr/local/bin"
}
"pools" : [
{
"url" : "",
"user" : "",
"pass" : ""
}
],
"gpu-fan" : "100",
"intensity" : "20",
"queue" : "0",
"scrypt" : true,
"kernel-path" : "/usr/local/bin"
}
After your .bin file is created, you can add the thread-concurrency and worksize from the filename "xxxxxxxxxxxtcxxxxxwxxx".
Of course, after you're done setting up, set the fan speeds and overclocks to what you need.
I would say you are down to a 100% driver problem at this point. Uninstall, clean up with drivercleaner, make sure OpenCL dll's are deleted from system32 and syswow64, reinstall 13.1 driver.
Thanks - Progress has been made! The miners would start, but GUIMiner would only pull stales and CGMiner would give me a "nonce - hw error". At least the programs run. I'm going to try rolling back to 12.8 drivers as that was a suggestion for the cgminer issue in another thread (incidentally, a 6950 as well). I will post back when I have more info.
I would say you are down to a 100% driver problem at this point. Uninstall, clean up with drivercleaner, make sure OpenCL dll's are deleted from system32 and syswow64, reinstall 13.1 driver.
An old trick I learned a long time ago was to set the minimum fan speed to 50%. Sometimes your clockspeeds can be so aggressive, and the ambient temp high enough, that the card will immediately lock upon the first few seconds of mining.
As it so happens, I actually had the fan up to 65-70%. Idle was 40*C and Load (under bitcoin) was 70*C. I greatly appreciate the suggestion, but with my temps I don't think it is the cause of the issue.
On a side-note, I tried the card that was in the computer (4870x2) and that produced the same crash, so I can be confident that the issue is not related to the card and the odds of it being hardware related would be slim.
To add onto the thought that it is not the hardware, it would seem that a q6600 can support a litecoin miner:
https://bitcointalksearch.org/topic/poor-radeon-hd6950-litecoin-mining-performance-need-help-solved-131083
^^Incidentally, this is a fairly similar setup (same cpu, same ram), yet he appears to have not had any trouble with crashing...though he is on way older drivers.
An old trick I learned a long time ago was to set the minimum fan speed to 50%. Sometimes your clockspeeds can be so aggressive, and the ambient temp high enough, that the card will immediately lock upon the first few seconds of mining.
Reinstall Windows and use the 13.1 drivers. The 13.4 drivers tend to crash.
Well, Linux didn't go over well either. It took me all day to get cgminer properly installed along with the AMD APP drivers and alas, I could not mine. I did some reading and perhaps it is because the CPU is a Q6600 (no SSE4.1, so perhaps an issue with OpenCL)?
I popped the card out and put it into another (Phenom II X4 955, M4A79 Deluxe mobo) computer that had an ATI card already in it. Same issue more or less - the miners crash.
And, likewise, bitcoin mining works fine. Clearly I am doing something wrong if both computers are unable to mine litecoins...but what? Latest ATI Catalyst Control Center drivers, latest AMD APP SDK, and this time I am on a system that certainly has full support of OpenCL.
Now I remember why I hate ATI
[love the cards, hate the drivers]
I popped the card out and put it into another (Phenom II X4 955, M4A79 Deluxe mobo) computer that had an ATI card already in it. Same issue more or less - the miners crash.
And, likewise, bitcoin mining works fine. Clearly I am doing something wrong if both computers are unable to mine litecoins...but what? Latest ATI Catalyst Control Center drivers, latest AMD APP SDK, and this time I am on a system that certainly has full support of OpenCL.
Now I remember why I hate ATI
[love the cards, hate the drivers] I just reinstalled Win7 today in hopes to fix this issue, so there is no antivirus installed at the moment but the problem is still present.
I've considered running Ubuntu haha, but the ability to mildly overclock with Afterburner is alluring, so I just want to make sure Windows is hopeless.
I've considered running Ubuntu haha, but the ability to mildly overclock with Afterburner is alluring, so I just want to make sure Windows is hopeless.
Don't listen to RichG, you can mine just fine on windows.
I know mining with Windows works (like I said, I was doing it with my other computer), but for some reason this computer isn't wanting to work properly. If I can't get it working, I will need to switch to a linux distro.
@r3animation
I had to have my account manually activated. I never received any account activation email and I could not post on any board nor could I send PMs to mods.
Started mining LTC with Win7 Home Premier on 2r rigs 3 weeks ago.
Learned a lot from the Newbie section. Would not have made it without them.
Jus sayin......
Learned a lot from the Newbie section. Would not have made it without them.
Jus sayin......
I just reinstalled Win7 today in hopes to fix this issue, so there is no antivirus installed at the moment but the problem is still present.
I've considered running Ubuntu haha, but the ability to mildly overclock with Afterburner is alluring, so I just want to make sure Windows is hopeless.
I've considered running Ubuntu haha, but the ability to mildly overclock with Afterburner is alluring, so I just want to make sure Windows is hopeless.
Don't listen to RichG, you can mine just fine on windows.
I just reinstalled Win7 today in hopes to fix this issue, so there is no antivirus installed at the moment but the problem is still present.
I've considered running Ubuntu haha, but the ability to mildly overclock with Afterburner is alluring, so I just want to make sure Windows is hopeless.
I've considered running Ubuntu haha, but the ability to mildly overclock with Afterburner is alluring, so I just want to make sure Windows is hopeless.
Just curious how a 1 time poster is allowed to post here?
To the OP, check your firewall, AV settings.
To the OP, check your firewall, AV settings.
You're running Windows?
That's your problem!
That's your problem!
Jump to: