GKumaran
Member
 Offline
Activity: 204
Merit: 10
|
 |
November 07, 2018, 08:32:40 AM |
|
Last night noticed on the pool side gap in hash for period for more than 1 hour, then in the log file found gap that correspond to that drop in hashrate on the pool. Why this gap of more than 70 minutes? Can I setup that miner closes when gpu chrash is detected so my own script can take care of it? [2018-11-07 00:47:33] watchdog: GPU crash detected, miner will try to restart
[2018-11-07 00:47:33] Restarting miner process
[2018-11-07 00:47:34] Miner version: 1.6.8
[2018-11-07 00:47:34] Windows version: 10.0 build 15063
[2018-11-07 00:47:34] Video driver version: 24.20.11016.4
[2018-11-07 00:50:47] AMD Platform ID: 1
[2018-11-07 00:50:47] AMD platform FOUND
[2018-11-07 00:50:47] Found 5 AMD devices
[2018-11-07 00:50:47] CPU AES-NI: TRUE
[2018-11-07 00:50:47] GPU0: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 4]
[2018-11-07 00:50:47] GPU1: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 16]
[2018-11-07 00:50:47] GPU2: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 13]
[2018-11-07 00:50:47] GPU3: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 10]
[2018-11-07 00:50:47] GPU4: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 7]
[2018-11-07 00:50:47] ADL is enabled
[2018-11-07 00:50:47] Cryptonight Fast mode enabled
[2018-11-07 00:50:47] Starting init of mining threads
[2018-11-07 00:50:47] Heating up system, please wait...
[2018-11-07 00:50:47] Created OCL context
[2018-11-07 00:50:47] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-11-07 00:50:47] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-11-07 00:50:47] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-11-07 00:50:47] Loading kernel for DEVICE BUS ID 4 ...
[2018-11-07 00:50:47] Created OCL command queue for DeviceID 0 (Thread 1)
[2018-11-07 00:50:47] Created OCL input buffer for DeviceID 0 (Thread 1)
[2018-11-07 00:50:47] Created OCL output buffer for DeviceID 0 (Thread 1)
[2018-11-07 00:50:47] Loading kernel for DEVICE BUS ID 4 ...
[2018-11-07 00:50:47] Created OCL command queue for DeviceID 1 (Thread 2)
[2018-11-07 00:50:47] Created OCL input buffer for DeviceID 1 (Thread 2)
[2018-11-07 00:50:47] Created OCL output buffer for DeviceID 1 (Thread 2)
[2018-11-07 00:50:47] Loading kernel for DEVICE BUS ID 16 ...
[2018-11-07 00:50:47] Created OCL command queue for DeviceID 1 (Thread 3)
[2018-11-07 00:50:47] Created OCL input buffer for DeviceID 1 (Thread 3)
[2018-11-07 00:50:47] Created OCL output buffer for DeviceID 1 (Thread 3)
[2018-11-07 00:50:47] Loading kernel for DEVICE BUS ID 16 ...
[2018-11-07 00:50:55] Miner version: 1.6.8
[2018-11-07 00:50:55] Windows version: 10.0 build 15063
[2018-11-07 00:50:55] Video driver version: 24.20.11016.4
[2018-11-07 02:03:04] AMD Platform ID: 1
[2018-11-07 02:03:04] AMD platform FOUND
[2018-11-07 02:03:04] Found 5 AMD devices
[2018-11-07 02:03:04] CPU AES-NI: TRUE
[2018-11-07 02:03:04] GPU0: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 4]
[2018-11-07 02:03:04] GPU1: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 16]
[2018-11-07 02:03:04] GPU2: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 13]
[2018-11-07 02:03:04] GPU3: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 10]
[2018-11-07 02:03:04] GPU4: Radeon RX Vega [gfx900] [8176 MB][Intensity 112.0][W: 16][T: 2][K: 1][BUS: 7]
[2018-11-07 02:03:04] ADL is enabled
[2018-11-07 02:03:04] Cryptonight Fast mode enabled
[2018-11-07 02:03:04] Starting init of mining threads
[2018-11-07 02:03:04] Heating up system, please wait...
[2018-11-07 02:03:04] Created OCL context
[2018-11-07 02:03:04] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-11-07 02:03:04] Created OCL input buffer for DeviceID 0 (Thread 0)
Adding "--disablegpuwatchdog (disable gpu crash detection watchdog)" to start.bat allows u to control crash responses. |
|
|
|
|
nordmann666
Member
Offline
Activity: 364
Merit: 16
|
|
November 07, 2018, 10:05:24 AM |
|
SUCCESS: Specified value was saved.
Initializing OpenCL devices, please wait..
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
GPU0: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 5]
GPU1: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 8]
GPU2: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 12]
GPU3: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 4]
GPU4: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 14]
GPU5: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 9]
GPU6: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 13]
GPU7: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 2]
GPU8: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 3]
GPU9: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 11]
GPU10: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 1]
GPU11: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 10]
what does this means?!
|
|
|
|
|
|
doktor83 (OP)
|
|
November 07, 2018, 10:11:31 AM |
|
SUCCESS: Specified value was saved.
Initializing OpenCL devices, please wait..
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
GPU0: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 5]
GPU1: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 8]
GPU2: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 12]
GPU3: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 4]
GPU4: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 14]
GPU5: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 9]
GPU6: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 13]
GPU7: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 2]
GPU8: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 3]
GPU9: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 11]
GPU10: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 1]
GPU11: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 10]
what does this means?!
Ahahahaha, i was doing some debug and left this uncommented  Sorry about that, i will remove it in next version. Maybe there are a few more hidden messages, i don't know  Oh you made me laugh so hard  |
|
|
|
Luisjc69
Member
Offline
Activity: 163
Merit: 10
|
|
November 07, 2018, 12:20:54 PM |
|
Hi guys,
i have also 580RX 8Giga RedDevil,
with 1.6.7 i get like 1000hs....now with the 1.6.9 "only" 900-920hs (Hynix!)
I have 7 cards and all cards have the same hash.
1200 Core /2240 Mem....i try with lot of different settings, but the issues comes only with the new version, because with the "old" ones i get with that settings 1khs (little more)
Any ideas please?
Algo : heavy with Intensity 0 and 58 --> with 58 i get the 1khs
Thx
|
|
|
|
|
Cideg
Newbie
Offline
Activity: 24
Merit: 0
|
|
November 07, 2018, 03:13:41 PM |
|
Hello doctor83 ", we need your help for our new project. We have implemented a new ALGO: CN Heavy Fast in our new coin We just wanted to use it as friendly software. How can we adapt SRBMINER to the new Algo? Maybe you have the opportunity to take a look. Our project is here: https://github.com/BitStream-Project/BitStreamOur pool is here: http://207.180.227.127/#Yours sincerely Cideg |
|
|
|
|
golya87
Newbie
Offline
Activity: 10
Merit: 0
|
|
November 07, 2018, 10:57:02 PM |
|
Hello I would like to use SRB Miner with Wownero, but after I start the miner, I've got this error: [2018-11-07 23:27:46] ADL initialised successfully!
[2018-11-07 23:27:46] Main pool: wownero.ingest.cryptoknight.cc:50903
[2018-11-07 23:27:46] Connected to wownero.ingest.cryptoknight.cc:50903
[2018-11-07 23:27:46] User logged in
[2018-11-07 23:27:46] Pool difficulty: 380018
[2018-11-07 23:27:46] Pool sent a new job (ID: 962256876332685)
[2018-11-07 23:28:11] ERROR : A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
[2018-11-07 23:28:11] Connection to pool lost. Reconnecting in 10 seconds.
[2018-11-07 23:28:21] Connected to wownero.ingest.cryptoknight.cc:50903
[2018-11-07 23:28:21] User logged in
[2018-11-07 23:28:21] Pool difficulty: 380018
[2018-11-07 23:28:21] Pool sent a new job (ID: 672175473277457)
[2018-11-07 23:29:16] ERROR : A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
[2018-11-07 23:29:16] Connection to pool lost. Reconnecting in 10 seconds.
[2018-11-07 23:29:27] Connected to wownero.ingest.cryptoknight.cc:50903
[2018-11-07 23:29:27] User logged in
[2018-11-07 23:29:27] Pool difficulty: 380018
[2018-11-07 23:29:28] Pool sent a new job (ID: 256498567131347) Win Defender and Firewall is turned off. CNv8 algo, 18.5.1 driver. This is the case with SRB and TMR Miner on Nanopool, MiningPoolHub, SupportXMR and Cryptoknight also. Could you help to solve this problem? |
|
|
|
|
|
doktor83 (OP)
|
|
November 08, 2018, 07:57:54 AM |
|
Both SRBMiner 1.6.8 and 1.6.9 are always stop mining because of devfee connection. I'm mining XMR on nanopool.Problem started few days ago and I didn't change anything or any settings. But my miners are stop after 4-10 hours after start mining. I check the log and the reason is can't connect to srbminer servers because of devfee. I'm not using any firewall /antivirus or i didn't change any settings in windows. Please help me... Log: [2018-11-05 23:18:03] miner_result: Pool accepted result 0x0000477E
[2018-11-05 23:18:10] hashrate: GPU0: 1949 H/s [BUS:3]
[2018-11-05 23:18:10] hashrate: GPU1: 1794 H/s [BUS:6]
[2018-11-05 23:18:10] hashrate: GPU2: 1797 H/s [BUS:10]
[2018-11-05 23:18:10] hashrate: GPU3: 1787 H/s [BUS:13]
[2018-11-05 23:18:10] hashrate: GPU4: 1950 H/s [BUS:16]
[2018-11-05 23:18:10] hashrate: Total: 9277 H/s
[2018-11-05 23:18:13] DFP online load: FAIL
[2018-11-05 23:18:13] devfee: Tried to contact http://srbminer.com a few times, but couldn't! Please check you firewall/antivirus is not blocking connections!
[2018-11-05 23:18:13] GPU devices disabled!
[2018-11-05 23:18:38] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"09099ccb82df052000470b275e855f7fc0bddec6e66d85d332ef5587d123ecae79497ca82d2d8d000000007fdbf809f7f1c393372b235952fa9d5d065ef55f6b85cfe44b5d16379478aa8f11","job_id":"26959","target":"cf8b0000"}}
[2018-11-05 23:18:38] pool_have_job: Pool sent a new job (ID: 26959)
[2018-11-05 23:19:38] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909d9cb82df052000470b275e855f7fc0bddec6e66d85d332ef5587d123ecae79497ca82d2d8d000000002128e76038ebc5877de5d30ef6ce777fee1a164e92609904ae3291b08804a89013","job_id":"26960","target":"cf8b0000"}}
[2018-11-05 23:19:38] pool_have_job: Pool sent a new job (ID: 26960)
[2018-11-05 23:19:52] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909e7cb82df05adb0ec44c0fa30bd4880834613a4d1ced482636a905455a1e9dffda32d5fe0ff00000000695abbfdff3108a5545ebbfccfceb75e8c897b7c7cd5af7054ba84cbbbd3cbc50c","job_id":"26961","target":"cf8b0000"}}
[2018-11-05 23:19:52] pool_have_job: Pool sent a new job (ID: 26961)
[2018-11-05 23:20:10] hashrate: GPU0: 0 H/s [BUS:3]
[2018-11-05 23:20:10] hashrate: GPU1: 0 H/s [BUS:6]
[2018-11-05 23:20:10] hashrate: GPU2: 0 H/s [BUS:10]
[2018-11-05 23:20:10] hashrate: GPU3: 0 H/s [BUS:13]
[2018-11-05 23:20:10] hashrate: GPU4: 0 H/s [BUS:16]
[2018-11-05 23:20:10] hashrate: Total: 0 H/s
[2018-11-05 23:20:52] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909a3cc82df05adb0ec44c0fa30bd4880834613a4d1ced482636a905455a1e9dffda32d5fe0ff0000000079cfa3f7ca31dce5a65e237a3c4799ea723a48d3e7a4bdb4c67343d9e763070d0f","job_id":"26962","target":"cf8b0000"}}
[2018-11-05 23:20:52] pool_have_job: Pool sent a new job (ID: 26962)
[2018-11-05 23:21:52] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909dfcc82df05adb0ec44c0fa30bd4880834613a4d1ced482636a905455a1e9dffda32d5fe0ff00000000462277818a7213d95dd8a7a1613d1589b973545b939dffa2d08f3016b142c00312","job_id":"26963","target":"cf8b0000"}}
[2018-11-05 23:21:52] pool_have_job: Pool sent a new job (ID: 26963)
[2018-11-05 23:22:01] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909e8cc82df05add27b1f85c9f24682b3e2961a325e35424050d1e0403355f27a174b3c8a3d5f00000000a444d6ef9957489461d33bc2d04591b60714cf193204d96f184c12807b6fe1ff07","job_id":"26964","target":"cf8b0000"}}
[2018-11-05 23:22:01] pool_have_job: Pool sent a new job (ID: 26964)
[2018-11-05 23:22:10] hashrate: GPU0: 0 H/s [BUS:3]
[2018-11-05 23:22:10] hashrate: GPU1: 0 H/s [BUS:6]
[2018-11-05 23:22:10] hashrate: GPU2: 0 H/s [BUS:10]
[2018-11-05 23:22:10] hashrate: GPU3: 0 H/s [BUS:13]
[2018-11-05 23:22:10] hashrate: GPU4: 0 H/s [BUS:16]
[2018-11-05 23:22:10] hashrate: Total: 0 H/s
If it started a few days ago, and you did not have this problem before, it really looks to me that something did change there on your computer/rig. I checked the srbminer.com was not down for a looooooong time, so that wasn't the issue. Anyways, i will loosen on this check a little bit in the next version. |
|
|
|
KhorneFlake
Newbie
Offline
Activity: 27
Merit: 0
|
|
November 08, 2018, 06:52:27 PM |
|
I just wanted to report that I've solved my problem with one of my Vegas being quite spastic, like less than half hashrate of its sibling. My Windows key was deactivated for a while now, and I finally contacted the supports and they helped me reactivating my Windows copy. I got an update, and after restarting both cards are running at the same speed: https://i.imgur.com/Sxk4zwu.pngEdit: Um, it seems I started celebrating too early. My 4th miner report shows it dropped to around 1100h/s again... you need to cool those vegas, set the fan to 3000rpm. That is why the hashrate drops, hbm gets too hot Both are pretty much the same temps wise, maybe the upper one has a degree more.. Much better now since I switched to the Threadripper platform and there's more space between them, on the mainstream Ryzen mobo they were too close. Use Soft Power Play Tables to get Memory to 1100 Mhz if possible and also voltages a little down, you should get ~1900 H/s out of one Vega and temp around 50 degrees Celsius (depends of the Vega model). Keep in mind the HBM is ~10 degrees hotter than what you see on the screen. Hey, I just wanted to report that it seems I've fixed my issue. My X399 Taichi originally came with the 2.00 BIOS version, I just updated to the 2.30 Bridge BIOS and both cards are now working fully. Imagine that… Hopefully this will stop thread_stuck_in_device_driver and video_memory_management_internal BSODs, but eh. Meh, once again I celebrated too early… This time hash on the second GPU started dropping after a couple of hours, and its still around 1k or less, even if I restart my PC. WTH already. I'll see what will happen when I reinstall Windows. |
|
|
|
|
BS0D
Newbie
Offline
Activity: 29
Merit: 0
|
|
November 08, 2018, 06:58:51 PM |
|
I just wanted to report that I've solved my problem with one of my Vegas being quite spastic, like less than half hashrate of its sibling. My Windows key was deactivated for a while now, and I finally contacted the supports and they helped me reactivating my Windows copy. I got an update, and after restarting both cards are running at the same speed: https://i.imgur.com/Sxk4zwu.pngEdit: Um, it seems I started celebrating too early. My 4th miner report shows it dropped to around 1100h/s again... you need to cool those vegas, set the fan to 3000rpm. That is why the hashrate drops, hbm gets too hot Both are pretty much the same temps wise, maybe the upper one has a degree more.. Much better now since I switched to the Threadripper platform and there's more space between them, on the mainstream Ryzen mobo they were too close. Use Soft Power Play Tables to get Memory to 1100 Mhz if possible and also voltages a little down, you should get ~1900 H/s out of one Vega and temp around 50 degrees Celsius (depends of the Vega model). Keep in mind the HBM is ~10 degrees hotter than what you see on the screen. Hey, I just wanted to report that it seems I've fixed my issue. My X399 Taichi originally came with the 2.00 BIOS version, I just updated to the 2.30 Bridge BIOS and both cards are now working fully. Imagine that… Hopefully this will stop thread_stuck_in_device_driver and video_memory_management_internal BSODs, but eh. Meh, once again I celebrated too early… This time hash on the second GPU started dropping after a couple of hours, and its still around 1k or less, even if I restart my PC. WTH already. I'll see what will happen when I reinstall Windows. Maybe increasing swapfile can help. Or reducing intensity. |
|
|
|
|
|
BogdanCo
|
|
November 08, 2018, 07:15:41 PM |
|
I just wanted to report that I've solved my problem with one of my Vegas being quite spastic, like less than half hashrate of its sibling. My Windows key was deactivated for a while now, and I finally contacted the supports and they helped me reactivating my Windows copy. I got an update, and after restarting both cards are running at the same speed:  Edit: Um, it seems I started celebrating too early. My 4th miner report shows it dropped to around 1100h/s again... you need to cool those vegas, set the fan to 3000rpm. That is why the hashrate drops, hbm gets too hot Both are pretty much the same temps wise, maybe the upper one has a degree more.. Much better now since I switched to the Threadripper platform and there's more space between them, on the mainstream Ryzen mobo they were too close. Use Soft Power Play Tables to get Memory to 1100 Mhz if possible and also voltages a little down, you should get ~1900 H/s out of one Vega and temp around 50 degrees Celsius (depends of the Vega model). Keep in mind the HBM is ~10 degrees hotter than what you see on the screen. Hey, I just wanted to report that it seems I've fixed my issue. My X399 Taichi originally came with the 2.00 BIOS version, I just updated to the 2.30 Bridge BIOS and both cards are now working fully. Imagine that… Hopefully this will stop thread_stuck_in_device_driver and video_memory_management_internal BSODs, but eh. Meh, once again I celebrated too early… This time hash on the second GPU started dropping after a couple of hours, and its still around 1k or less, even if I restart my PC. WTH already. I'll see what will happen when I reinstall Windows. How much is the temperature on the cards? |
|
|
|
|
BS0D
Newbie
Offline
Activity: 29
Merit: 0
|
|
November 08, 2018, 07:23:06 PM |
|
I just wanted to report that I've solved my problem with one of my Vegas being quite spastic, like less than half hashrate of its sibling. My Windows key was deactivated for a while now, and I finally contacted the supports and they helped me reactivating my Windows copy. I got an update, and after restarting both cards are running at the same speed: https://i.imgur.com/Sxk4zwu.pngEdit: Um, it seems I started celebrating too early. My 4th miner report shows it dropped to around 1100h/s again... you need to cool those vegas, set the fan to 3000rpm. That is why the hashrate drops, hbm gets too hot Both are pretty much the same temps wise, maybe the upper one has a degree more.. Much better now since I switched to the Threadripper platform and there's more space between them, on the mainstream Ryzen mobo they were too close. Use Soft Power Play Tables to get Memory to 1100 Mhz if possible and also voltages a little down, you should get ~1900 H/s out of one Vega and temp around 50 degrees Celsius (depends of the Vega model). Keep in mind the HBM is ~10 degrees hotter than what you see on the screen. Hey, I just wanted to report that it seems I've fixed my issue. My X399 Taichi originally came with the 2.00 BIOS version, I just updated to the 2.30 Bridge BIOS and both cards are now working fully. Imagine that… Hopefully this will stop thread_stuck_in_device_driver and video_memory_management_internal BSODs, but eh. Meh, once again I celebrated too early… This time hash on the second GPU started dropping after a couple of hours, and its still around 1k or less, even if I restart my PC. WTH already. I'll see what will happen when I reinstall Windows. How much is the temperature on the cards? It's written - ~70C. HBM must be hell-hot that way. I wonder why does that vega still alive. I'm running my V64 at 40-45C GPU and about 45-50C HBM at 1478/1100 by HWinfo. |
|
|
|
|
|
|
|
BogdanCo
|
|
November 08, 2018, 08:21:48 PM |
|
Temps:  Still far better than having them at stock voltages, in that case the hottest card has its HBM2 at 95c.... Still too hot, I'm guessing this is the reason why after some time you see a decrease in hash rate. |
|
|
|
|
|
Bojcha
|
|
November 08, 2018, 08:31:52 PM |
|
When i see temps like this... i want to cry.
|
|
|
|
|
BS0D
Newbie
Offline
Activity: 29
Merit: 0
|
|
November 08, 2018, 08:33:12 PM |
|
When i see temps like this... i want to cry.
Yep. That's insanity. |
|
|
|
|
Dripac
Newbie
Offline
Activity: 71
Merit: 0
|
|
November 08, 2018, 08:36:15 PM |
|
Anyone setup for 580 8gb Sapphire Nitro Hynix memory Monero algo
|
|
|
|
|
KhorneFlake
Newbie
Offline
Activity: 27
Merit: 0
|
|
November 08, 2018, 08:45:06 PM |
|
Again, temps are pretty much identical on both cards, and were still the same when the second GPU worked at full. With Claymore Cryptonote miner both were running fully, but there's no new releases that support v8. I don't know what's the issue, it seems so random. First Windows update made it working correctly for several minutes…. Then the BIOS update for a couple of hours. After that initial window its the same story again. My last resort is reinstalling the Windows again.
|
|
|
|
|
BS0D
Newbie
Offline
Activity: 29
Merit: 0
|
|
November 08, 2018, 09:24:02 PM |
|
Again, temps are pretty much identical on both cards, and were still the same when the second GPU worked at full. With Claymore Cryptonote miner both were running fully, but there's no new releases that support v8. I don't know what's the issue, it seems so random. First Windows update made it working correctly for several minutes?. Then the BIOS update for a couple of hours. After that initial window its the same story again. My last resort is reinstalling the Windows again.
BTW what is that card vendor/model? And what is your overdriventool config. |
|
|
|
|
|
|
BS0D
Newbie
Offline
Activity: 29
Merit: 0
|
|
November 08, 2018, 09:41:46 PM |
|
I use that with OD v.0.2.6 on my Sapphire V64 nitro+: GPU_P0=852;800 GPU_P1=991;820 GPU_P2=1084;825 GPU_P3=1138;850 GPU_P4=1150;910 GPU_P5=1202;875 GPU_P6=1212;875 GPU_P7=1478;920 Mem_P0=167;800 Mem_P1=500;800 Mem_P2=800;825 Mem_P3=1100;910 Fan_Min=400 Fan_Max=2400 Fan_Target=40 Fan_Acoustic=0 Power_Temp=65 Power_Target=0 Try to set target temp to 50C to look what should happen. |
|
|
|
|
|
