Bitcoin Forum
April 16, 2024, 07:30:39 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Problems with Claymore v9.8 getting error messages like cu_k1 failed 30  (Read 477 times)
BitMan94 (OP)
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
August 27, 2017, 09:35:10 AM
 #1

so im getting these errors cu_k1 failed 30, NVML: Cannot get current temperature, error 15 when trying to run claymore v9.8  On almost all my graphic cards (5 Gtx 1060s & 1 1070) for some reason about 2 out of 6 will shutdown and stop working but the other 4 will keep running and its weird becuase when i go check MSI after burner or nvidia inspector they show like they completely turned off from the computer and the only way to get the to show as active and working again is to shutdown and restart the whole computer any ideas on how to fix this problem? Please help ):!!!
The grue lurks in the darkest places of the earth. Its favorite diet is adventurers, but its insatiable appetite is tempered by its fear of light. No grue has ever been seen by the light of day, and few have survived its fearsome jaws to tell the tale.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1713252639
Hero Member
*
Offline Offline

Posts: 1713252639

View Profile Personal Message (Offline)

Ignore
1713252639
Reply with quote  #2

1713252639
Report to moderator
1713252639
Hero Member
*
Offline Offline

Posts: 1713252639

View Profile Personal Message (Offline)

Ignore
1713252639
Reply with quote  #2

1713252639
Report to moderator
1713252639
Hero Member
*
Offline Offline

Posts: 1713252639

View Profile Personal Message (Offline)

Ignore
1713252639
Reply with quote  #2

1713252639
Report to moderator
Bothebu
Member
**
Offline Offline

Activity: 81
Merit: 15


View Profile
August 27, 2017, 12:59:03 PM
 #2

you are clocking too high....memory instability
gt_addict
Hero Member
*****
Offline Offline

Activity: 2478
Merit: 621


View Profile
August 27, 2017, 02:42:51 PM
 #3

Yep clock to high. Reduce the clock and it will find its groove and be stable. Its an experimentation process to find the right balance. Start low and edge up higher and higher until you get the error and then reduce it a couple of steps.

**SUPPORT SIDEHACK** Miner Development Donations to:  1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr

Donations/Tips to:-   1GTADDicTXD1uachKKgW24DZDxDGhSMdRa

Join Bitconnect: https://bitconnect.co/?ref=gtaddict
BitMan94 (OP)
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
August 28, 2017, 01:28:06 AM
 #4

i have all my GPUS set to stock, i had them over clocked but put them back to stock and still getting this error
gt_addict
Hero Member
*****
Offline Offline

Activity: 2478
Merit: 621


View Profile
August 28, 2017, 08:34:27 AM
 #5

Ive found running the latest nvidia driver doesnt help eother. Best driver for me is 372.70. Gives the best stability and hashrate.

**SUPPORT SIDEHACK** Miner Development Donations to:  1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr

Donations/Tips to:-   1GTADDicTXD1uachKKgW24DZDxDGhSMdRa

Join Bitconnect: https://bitconnect.co/?ref=gtaddict
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!