![]() Intensities start writing over the same ram and it is highly dependent The reason this is crucial is that too high an intensity can actuallyīe disastrous with scrypt because it CAN run out of ram. As the SCRYPT-README file of cgminer states: ![]() In my experience scrypt mining on GPUs is quite susceptible to cause HW errors and wrong nonces if the parameters are not chosen to match the GPUs the algorithm is run on. Got work from get queue to get work for thread 0 API not running - API will not be available Initialising kernel scrypt130511.cl with bitalign, 1 vectors and worksize 256 Loaded binary image scrypt130511Tahitiglg2tc22400w256l4.bin GPU 0: selecting thread concurrency of 22400 CL Platform version: OpenCL 1.2 AMD-APP (1124.2) CL Platform name: AMD Accelerated Parallel Processing CL Platform vendor: Advanced Micro Devices, Inc. GPU 0 AMD Radeon HD 7900 Series hardware monitoring enabled GPU 0 iAdapterIndex 0 strUDID PCI_VEN_1002&DEV_6798&SUBSYS_254D1458&REV_00_4&176F368&0&0018A iBusNumber 2 iDeviceNumber 0 iFunctionNumber 0 iVendorID 1002 strAdapterName AMD Radeon HD 7900 Series CL Platform 0 version: OpenCL 1.2 AMD-APP (1124.2) CL Platform 0 name: AMD Accelerated Parallel Processing CL Platform 0 vendor: Advanced Micro Devices, Inc. Here's the output from command line:Ĭgminer -benchmark -scrypt -debug -verbose Started cgminer 3.2.0 So far I've tried much and always the same problem. Some seem to be able to resolve the problem by experimenting with different versions and combinations of drivers and AMD SDK. It seems that litecoin/scrypt support in cgminer is unstable as I've found a lot of mentions of this error in various forums and no real solutions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |