Overclocking and Power Management

• 

  AMD BIOS Mods Without Desktop, RDP, or VNC Access
  • docdrydenn  

  3
  2
  Votes
  3
  Posts
  4744
  Views

  

  Windows is never needed when you have pimp - Polaris and atiflash are included. Here is the quick version: atiflash -s to save the existing rom, example: atiflash -s 0 gpu0-stock.rom to save the rom from gpu 0. RDP in and click Polaris load the file you just saved click one click strap mod save as another file atiflash -p to flash it, example: atiflash -p 0 gpu0-modified.rom to write the rom to the gpu0 from the file.. Also, we will be releasing an even easier way, PBE CONSOLE edition - in the next pimp image. Thanks!
• 

  DaX AMD Overclocking guide (including RX 470/480/570/580 and others)
  • DaX  

  12
  3
  Votes
  12
  Posts
  7190
  Views

  G

  @dax said in DaX AMD Overclocking guide (including RX 470/480/570/580 and others): Sapphire_HynixGDDR5_RX580_8GB_Modify_Bios.rom What ROM/config for MSI RX480s? I know I can use the 580 BIOS, but not sure what values should be. . .I think ; ) I have 4X (MSI RX480): Part num: K4G80325FB VendorID: Samsung Size (MB): 8192 Density: 4M x 32 Type: GDDR5 And 1X (again, MSI RX480): Part num: H5GC4H24AJ VendorID: Hynix Size (MB): 4096 Density: 4M x 32 Type: GDDR5 Thanks for any head's up!! G
• S

  BIOS Modding with PolarisBiosEditor. "One Click Timing Patch" on Windows.
  • Sobeit  

  1
  1
  Votes
  1
  Posts
  11255
  Views

  S

  This a basic guide on how to flash your GPU with a BIOS created in PolarisBiosEditor. Please make sure you understand all the risks that comes with playing with the BIOS before you try this. I dont take any responsibility of damages. (I dont claim my way is the only way nor the best way, but this is how I do it and it might be useful to someone) You will need a computer with Windows. Download this two programs and install them: PolarisBiosEditor: https://github.com/jaschaknack/PolarisBiosEditor ATIWinFlash: https://www.techpowerup.com/download/ati-winflash/ Turn off PC and insert the GPU you want to flash into a free 16x PCI slot. Turn on PC. When in Windows start ATIWinFlash as admin (right click-run as admin). Make sure you have selected correct card in the top corner where it says "System Video Device". (Pls note that only AMD cards will be shown here and if there is no AMD card connected ATIWinFlash will not start) Click on "Save" and save the bios on your computer. Make sure you save it somewhere safe, in case you might need it in the future. Since this is the original BIOS. You can then close ATIWinFlash. Now open PolarisBiosEditor. And click "OPEN BIOS" and find the BIOS you created earlier. (Make sure you are showing all files . if you cant find it) After you have opened your BIOS click on "ONE CLICK TIMING PATCH". You should then get a windows that confirms that it have applied new straps. Save this new modded BIOS. Make sure you dont overwrite the original BIOS. Then you can close PolarisBiosEditor. Now open ATIWinFlash as admin again. Once again make sure you have selected the right GPU under "System Video Devices" Click on "Load Image" and load the modded BIOS. Click on "Program" and that should flash your modded BIOS onto your GPU. Turn off computer, take out GPU put it into minning rig. Profit.
• 

  gputool: How to Overclock NVIDIA and AMD GPUs
  • CryptoNews  

  73
  0
  Votes
  73
  Posts
  65894
  Views

  

  ohgodatool has been modified to use PCI BUS ID as the -i parameter instead of AMD's idea of the number. Here is example how to use: [Agent: m204-2.15-mix (Running) Total HR: [0.00Kh/s] Miners running [0] GPUs [none active]] [09:21 AM][Uptime: 0d 0:29][root@pimp3(10.0.0.204)] [/root]:# gputool --list PIMP GPU Tool v20191007 GPUs type: Mixed --- 4 GPUs seen in hardware ('lspci' output): 01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) (prog-if 00 [VGA controller]) 03:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) (prog-if 00 [VGA controller]) 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev c7) (prog-if 00 [VGA controller]) 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev e7) (prog-if 00 [VGA controller]) --- GPUs reported by AMD driver ('amdmeminfo' output): 04.00.0: Radeon RX 480: xxx-xxx-xxx: SK Hynix H5GC4H24AJR: GDDR5: Polaris10 05.00.0: Radeon RX 580: MS-V34114-F1: Samsung K4G80325FB: GDDR5: Polaris10 --- GPUs reported by NVidia driver ('nvidia-smi' output): 01:00.0: GeForce GTX 1070: 8119 MiB: 86.04.50.00.46: GPU-01a09b6d-e738-2eb6-77ea-2d813faec5c4 03:00.0: GeForce GTX 1070: 8119 MiB: 86.04.50.00.46: GPU-60e2ce38-54a1-ceb8-e987-89fc36778f9d [Agent: m204-2.15-mix (Running) Total HR: [0.00Kh/s] Miners running [0] GPUs [none active]] [09:22 AM][Uptime: 0d 0:30][root@pimp3(10.0.0.204)] [/root]:# ohgodatool -i 04.00.0 --show-core DPM state 0: VDDC: 800 (voltage table entry 0) VDDC offset: 0 Core clock: 300 DPM state 1: VDDC: 65282 (voltage table entry 1) VDDC offset: -26 Core clock: 608 DPM state 2: VDDC: 65283 (voltage table entry 2) VDDC offset: -26 Core clock: 910 DPM state 3: VDDC: 65284 (voltage table entry 3) VDDC offset: -26 Core clock: 1077 DPM state 4: VDDC: 65285 (voltage table entry 4) VDDC offset: -26 Core clock: 1145 DPM state 5: VDDC: 65286 (voltage table entry 5) VDDC offset: -26 Core clock: 1191 DPM state 6: VDDC: 65287 (voltage table entry 6) VDDC offset: -26 Core clock: 1236 DPM state 7: VDDC: 65288 (voltage table entry 7) VDDC offset: 0 Core clock: 1200 [Agent: m204-2.15-mix (Running) Total HR: [0.00Kh/s] Miners running [0] GPUs [none active]] [09:22 AM][Uptime: 0d 0:31][root@pimp3(10.0.0.204)] [/root]:# ohgodatool -i 05.00.0 --show-core DPM state 0: VDDC: 750 (voltage table entry 0) VDDC offset: 0 Core clock: 300 DPM state 1: VDDC: 65282 (voltage table entry 1) VDDC offset: -26 Core clock: 600 DPM state 2: VDDC: 65283 (voltage table entry 2) VDDC offset: -26 Core clock: 918 DPM state 3: VDDC: 65284 (voltage table entry 3) VDDC offset: -26 Core clock: 1167 DPM state 4: VDDC: 65285 (voltage table entry 4) VDDC offset: -26 Core clock: 1239 DPM state 5: VDDC: 65286 (voltage table entry 5) VDDC offset: -26 Core clock: 1282 DPM state 6: VDDC: 65287 (voltage table entry 6) VDDC offset: -26 Core clock: 1326 DPM state 7: VDDC: 65288 (voltage table entry 7) VDDC offset: 0 Core clock: 1200 [Agent: m204-2.15-mix (Running) Total HR: [0.00Kh/s] Miners running [0] GPUs [none active]] [09:23 AM][Uptime: 0d 0:31][root@pimp3(10.0.0.204)] [/root]:#
• 

  setting clocks in pimp OS 1.9 fglrx
  • dbct  

  1
  0
  Votes
  1
  Posts
  2735
  Views

  

  As​ ​we​ ​have​ ​learned​ ​gputool​ ​will​ ​not​ ​run​ ​with​ ​the​ ​old​ ​cards​ ​that​ ​use​ ​the​ ​fglrx​ ​drivers. But​ ​this​ ​does​ ​not​ ​mean​ ​that​ ​you​ ​can't​ ​adjust​ ​the​ ​setting. BEFORE​ ​UNDERTAKING​ ​THERE​ ​ARE​ ​NO​ ​SAFEGUARDS​ ​IN​ ​PLACE PLEASE​ ​READ​ ​THE​ ​BELOW​ ​BEFORE​ ​STARTING​ ​OVERCLOCKING!!!!!! AS​ ​WITH​ ​ALL​ ​OVERCLOCKING​ ​TOOLS​ ​YOU​ ​ARE​ ​ENTIRELY​ ​RESPONSIBLE​ ​FOR​ ​ANY HARM​ ​YOU​ ​MAY​ ​CAUSE​ ​TO​ ​YOUR​ ​HARDWARE.​ ​OVERCLOCKING​ ​CAN​ ​INVALIDATE WARRANTIES,​ ​DAMAGE​ ​HARDWARE​ ​AND​ ​EVEN​ ​CAUSE​ ​FIRES.​ ​THE​ ​AUTHOR​ ​AND PIMP​ ​LLC.​ ​ASSUMES​ ​NO​ ​RESPONSIBILITY​ ​FOR​ ​ANY​ ​DAMAGE​ ​YOU​ ​MAY​ ​CAUSE lets​ ​start​ ​simple​ ​just​ ​adjust​ ​the​ ​intensity,​ ​shaders​ ​and​ ​​ ​thread-concurrency. intensity​ ​: how​ ​hard​ ​can​ ​your​ ​card​ ​work​ ​setting​ ​this​ ​setting​ ​goes​ ​from​ ​0​ ​to​ ​31​ ​and​ ​when​ ​it​ ​is​ ​set​ ​to​ ​high it​ ​will​ ​cause​ ​more​ ​Hardware-errors​ ​and​ ​actually​ ​causes​ ​you​ ​to​ ​mine​ ​slower shaders​ ​: here​ ​you​ ​can​ ​tell​ ​the​ ​miners​ ​how​ ​many​ ​shaders​ ​are​ ​on​ ​your​ ​card​ ​and​ ​how​ ​many​ ​can​ ​be​ ​used this​ ​​ ​is​ ​card​ ​specific thread-concurrency. Setting​ ​thread​ ​concurrency​ ​overrides​ ​anything​ ​you​ ​put​ ​into​ ​--shaders​ ​and​ ​is​ ​ultimately​ ​a BETTER​ ​way​ ​to​ ​tune​ ​performance. When​ ​changing​ ​these​ ​settings​ ​please​ ​just​ ​increase​ ​them​ ​step​ ​by​ ​step​ ​and​ ​run​ ​the​ ​miner every​ ​time​ ​​ ​you​ ​make​ ​a​ ​change. This​ ​should​ ​increase​ ​the​ ​speed. For​ ​the​ ​peeps​ ​who​ ​need​ ​more​ ​out​ ​of​ ​there​ ​cards​ ​​ ​there​ ​are​ ​2​ ​other​ ​settings​ ​to​ ​tune gpu-engine​ ​and​ ​gpu-memclock​ ​but​ ​before​ ​adjusting​ ​these​ ​please​ ​read​ ​the​ ​fat​ ​warning​ ​above again. ​ ​LOOK​ ​AT​ ​MANUFACTURER​ ​SITE​ ​FOR​ ​DEFAULT​ ​CLOCKS​ ​AND​ ​START​ ​WITH THOSE In​ ​your​ ​conf​ ​of​ ​in​ ​this​ ​case​ ​the​ ​sgminer-gm​ ​you​ ​need​ ​to​ ​add​ ​these​ ​values​ ​because​ ​they​ ​are not​ ​there​ ​by​ ​default. 1.“gpu-engine”​ ​:​ ​“engineclock”, (engine​ ​clock​ ​is​ ​the​ ​clockspeed​ ​the​ ​core​ ​will take) 2.“gpu-memclock”​ ​:​ ​“memoryclock”,(memory​ ​clock​ ​is​ ​the​ ​clockspeed​ ​the​ ​memory has​ ​on​ ​the​ ​card) EXAMPLE first​ ​a​ ​basic​ ​run​ ​random​ ​card​ ​with​ ​added​ ​values​ ​of​ ​clocks​ ​and​ ​a​ ​screenshot​ ​of​ ​the​ ​hash speed. seccond​ ​the​ ​same​ ​basic​ ​run​ ​random​ ​card​ ​with​ ​higher​ ​clock​ ​speeds​ ​and​ ​a​ ​screenshot​ ​of​ ​the hashspeed. Final words start with default changes before changing clocks. find clock speeds for your card(s) and put them in. (separate with , if you have multiple cards and clocks ) final don't go quick and check every time and TAKE TIME FOR THIS!!
• B

  Interesting article to read
  • Broomey  

  1
  1
  Votes
  1
  Posts
  364
  Views

  B

  https://videocardz.com/newz/asus-asrock-and-msi-bring-overclocking-to-h470-b460-and-non-k-intel-core-cpus
• P

  Has anyone played around with radeon-profile?
  • ParaplegicRacehorse  

  3
  1
  Votes
  3
  Posts
  334
  Views

  P

  I have not worked with rocm-smi. I thought rocm was mostly just a kernel module set and stack of conf files. I'll look more closely at it. I'm not ready to fool with radeon-profile on my mining rig. I need more knowledge before I fool with some of what it offers. That said, if there were an ncurses interface for use by ssh, it would make it more useful to PiMPs, and other GPU-compute people as well. Maybe I'll add that to their issues list at github.
• T

  SOLVED Nvidia 980 TI won't accept the offset.
  • The_Godchild  

  6
  0
  Votes
  6
  Posts
  2645
  Views

  L

  It appears 980s have limited driver support.
• P

  How did you guys do your bios flashing for RX580 Gpu's????
  • peter1  

  2
  0
  Votes
  2
  Posts
  1475
  Views

  

  Here's how I did mine, but I only did the "ONE CLICK TIMING PATCH". AMD BIOS Mods Without Desktop, RDP, or VNC Access
• H

  SOLVED gputool ( gpu-config.json )
  • hzumbach  

  6
  0
  Votes
  6
  Posts
  2492
  Views

  

  Please post what flags are set in your Claymore config file?
• A

  SOLVED We really need amd gpu undervolt feature
  • afedukov  

  13
  1
  Votes
  13
  Posts
  5725
  Views

  

  You can reflash AMD BIOS using atiflash. We have also provided multiple tools for inspection and modification, such as OhGodATool, atitool, and PolarisBiosEditor. Normally, I would use gputool to experiment and tune, and if I wanted to say move that GPU around to other rigs, I would use the information I learned with gputool to create a new BIOS, starting with the cards BIOS as a source, and reflash the card. Putting the lessons learned into a new BIOS, lets me make whats best for a card, into the card, so I do not need to track its cpu-config.json settings. In practice though, I must admit, I have been just jotting down what a card can do and slapping it on a sticker :)
• S

  SOLVED Claymore 11.0 ETH only vs EthOS Claymore 11.0 ETH only
  • slvorster  

  3
  0
  Votes
  3
  Posts
  2007
  Views

  S

  @Anjin, I am only setting the clock, core and power in the gputool config file. I used the same settings as I did in Ethos. I will need to put the SSD back in and do the "helpme", but the same SSD in an Nvidia only rig works fine, except I noticed that the hashrate per card using ethminer is also approx. 1MH/s per card lower than in ethos with the same overclock settings. So...clearly I must be doing something wrong.
• S

  Share your RX580 settings and power use!
  • Sobeit  

  5
  0
  Votes
  5
  Posts
  2734
  Views

  G

  @sobeit Did you flash the BIOS with a modded BIOS or just use the stock BOIS for each card and then play with the frequency limits within GPUTool? Your hash rates are great and the power used is average as if not modded. Can you give us a detailed explanation of exactly what you did to accomplish your numbers? And provide a sample of your "gpu-config.json" file?
• L

  SOLVED Cannot Overclock: gpu-config values are not being used
  • lsaraiva17  

  2
  0
  Votes
  2
  Posts
  1363
  Views

  

  Double check your miner profile using pimp --edit. Read the comments close, and check the FLAGS.
• G

  SOLVED /opt/pimp/gputool --config says "ERROR: Detected GPUs = 7, Defined GPUs = 1!"
  • gerry.bakker  

  3
  0
  Votes
  3
  Posts
  1646
  Views

  G

  Yes - that worked - thanks.
• W

  SOLVED AMD GPU Tuning - best practice Values
  • wesrig  

  3
  0
  Votes
  3
  Posts
  2156
  Views

  

  I use this resource to find the best BIOS https://anorak.tech/c/downloads
• S

  SOLVED Gputool error
  • spaceknight  

  5
  0
  Votes
  5
  Posts
  2625
  Views

  S

  thanks that worked
• B

  SOLVED Some errors (Failed to connect to Mir)
  • blaz.pivk  

  3
  0
  Votes
  3
  Posts
  2067
  Views

  B

  Thanks. That did it.
• 

  Nvidia Overclocking OC Example: Zotac GTX970s for ZEC
  • melt  

  1
  0
  Votes
  1
  Posts
  1581
  Views

  

  In this example we are simply guessing and doing some trial and error. With a few gputool commands and simple text editing, we will: Decrease the temps from 80C to 65C. Decrease power usage by 20W per eGPU. Hashrate remains about the same, up to a 10 h/s increase overall. Note: These may not be the best guesses or settings but we have made improvements within a few moments with little effort thanks to PIMP and gputool. Stock clocks: Temp: GPU0: 79C GPU1: 79C GPU0: 249 Sol/s GPU1: 247 Sol/s Total speed: 496 Sol/s +-----+-------------+--------------+ | GPU | Power usage | Efficiency | +-----+-------------+--------------+ | 0 | 144W | 1.73 Sol/W | | 1 | 138W | 1.79 Sol/W | +-----+-------------+--------------+ INFO 09:25:08: GPU1 Accepted share 85ms [A:5798, R:16] INFO 09:25:11: GPU1 Accepted share 86ms [A:5799, R:16] INFO 09:25:19: GPU1 Accepted share 86ms [A:5800, R:16] Temp: GPU0: 79C GPU1: 79C GPU0: 249 Sol/s GPU1: 244 Sol/s Total speed: 493 Sol/s +-----+-------------+--------------+ | GPU | Power usage | Efficiency | +-----+-------------+--------------+ | 0 | 144W | 1.73 Sol/W | | 1 | 137W | 1.78 Sol/W | +-----+-------------+--------------+ INFO: Detected new work: 685801cd7e8b81b5cd4a Temp: GPU0: 79C GPU1: 79C GPU0: 254 Sol/s GPU1: 241 Sol/s Total speed: 495 Sol/s Changed powerlimit to 130 and fans to 90: gpu-config.json: { "comment": "Please see https://getpimp.org for information about configuring this file", "gpuSettings": [ { "gpu_id": "0", "NVCOffset": "0", "NVMOffset": "0", "NVPLimit": "130", "fanspeed": "90", "temptarget": "70" }, { "gpu_id": "1", "NVCOffset": "0", "NVMOffset": "0", "NVPLimit": "130", "fanspeed": "90", "temptarget": "70" } ] } Temp: GPU0: 64C GPU1: 67C GPU0: 254 Sol/s GPU1: 250 Sol/s Total speed: 504 Sol/s +-----+-------------+--------------+ | GPU | Power usage | Efficiency | +-----+-------------+--------------+ | 0 | 138W | 1.84 Sol/W | | 1 | 135W | 1.85 Sol/W | +-----+-------------+--------------+ INFO 09:35:45: GPU1 Accepted share 132ms [A:5, R:0] Temp: GPU0: 64C GPU1: 67C GPU0: 248 Sol/s GPU1: 245 Sol/s Total speed: 493 Sol/s So we made a slight efficiency. Let's try bumping some clocks up. Zcash loves memclocks. Setting clocks to 60/300 to see what happens: gpu-config.json: { "comment": "Please see https://getpimp.org for information about configuring this file", "gpuSettings": [ { "gpu_id": "0", "NVCOffset": "60", "NVMOffset": "300", "NVPLimit": "130", "fanspeed": "90", "temptarget": "70" }, { "gpu_id": "1", "NVCOffset": "60", "NVMOffset": "300", "NVPLimit": "130", "fanspeed": "90", "temptarget": "70" } ] } Looks like we got another bump up: INFO 09:40:47: GPU1 Accepted share 146ms [A:1, R:0] Temp: GPU0: 58C GPU1: 60C GPU0: 256 Sol/s GPU1: 245 Sol/s Total speed: 501 Sol/s +-----+-------------+--------------+ | GPU | Power usage | Efficiency | +-----+-------------+--------------+ | 0 | 138W | 1.86 Sol/W | | 1 | 138W | 1.78 Sol/W | +-----+-------------+--------------+ INFO 09:41:21: GPU0 Accepted share 85ms [A:1, R:0] INFO 09:41:26: GPU1 Accepted share 86ms [A:2, R:0] Temp: GPU0: 61C GPU1: 63C GPU0: 257 Sol/s GPU1: 246 Sol/s Total speed: 503 Sol/s +-----+-------------+--------------+ | GPU | Power usage | Efficiency | +-----+-------------+--------------+ | 0 | 138W | 1.86 Sol/W | | 1 | 137W | 1.80 Sol/W | +-----+-------------+--------------+ INFO 09:41:46: GPU0 Accepted share 85ms [A:2, R:0] Bumping a little more to 70/500: gpu-config.json: { "comment": "Please see https://getpimp.org for information about configuring this file", "gpuSettings": [ { "gpu_id": "0", "NVCOffset": "70", "NVMOffset": "500", "NVPLimit": "130", "fanspeed": "90", "temptarget": "70" }, { "gpu_id": "1", "NVCOffset": "70", "NVMOffset": "500", "NVPLimit": "130", "fanspeed": "90", "temptarget": "70" } ] } Results: INFO 09:44:57: GPU0 Accepted share 88ms [A:2, R:0] Temp: GPU0: 61C GPU1: 64C GPU0: 250 Sol/s GPU1: 245 Sol/s Total speed: 495 Sol/s +-----+-------------+--------------+ | GPU | Power usage | Efficiency | +-----+-------------+--------------+ | 0 | 133W | 1.88 Sol/W | | 1 | 137W | 1.79 Sol/W | +-----+-------------+--------------+ INFO: Detected new work: d9041c48a4eb0619cecf Temp: GPU0: 63C GPU1: 65C GPU0: 252 Sol/s GPU1: 245 Sol/s Total speed: 497 Sol/s +-----+-------------+--------------+ | GPU | Power usage | Efficiency | +-----+-------------+--------------+ | 0 | 139W | 1.81 Sol/W | | 1 | 141W | 1.74 Sol/W | +-----+-------------+--------------+ INFO 09:45:49: GPU0 Accepted share 89ms [A:3, R:0] ## Bumping clocks up to 80/600: gpu-config.json: ```json { "comment": "Please see https://getpimp.org for information about configuring this file", "gpuSettings": [ { "gpu_id": "0", "NVCOffset": "80", "NVMOffset": "600", "NVPLimit": "130", "fanspeed": "90", "temptarget": "70" }, { "gpu_id": "1", "NVCOffset": "80", "NVMOffset": "600", "NVPLimit": "130", "fanspeed": "90", "temptarget": "70" } ] } Results: [/root]:# gputool --status PIMP GPU Tool v20171021 GPUs type: NVidia GPU 0: (GeForce GTX 970), Temp: 53C, Fan: 90%, Core Clock: 202 Mhz ( Offset), Memory Clock: 324 Mhz ( Offset), Performance state: 8, Power Usage: 22.4W (130W Max) GPU 1: (GeForce GTX 970), Temp: 54C, Fan: 90%, Core Clock: 696 Mhz ( Offset), Memory Clock: 810 Mhz ( Offset), Performance state: 5, Power Usage: 21.9W (130W Max) [Agent: LilJimmy01 (Running) Total HR: [0.00Kh/s] Miners running [0] GPUs [none active]] [09:46 AM][Uptime: 4d 16:33][root@pimp2(10.0.0.195)] [/root]:# gputool --config PIMP GPU Tool v20171021 GPUs type: NVidia Configuring 2 GPUs.. Set Fan speed to 90% on GPU 0 PowerLimit was set to 130 W for GPU 0 Core speed was offset 80 for GPU 0 Memory speed was offset 600 for GPU 0 Set Fan speed to 90% on GPU 1 PowerLimit was set to 130 W for GPU 1 Core speed was offset 80 for GPU 1 Memory speed was offset 600 for GPU 1 Temp: GPU0: 64C GPU1: 67C GPU0: 251 Sol/s GPU1: 245 Sol/s Total speed: 496 Sol/s +-----+-------------+--------------+ | GPU | Power usage | Efficiency | +-----+-------------+--------------+ | 0 | 137W | 1.83 Sol/W | | 1 | 137W | 1.79 Sol/W | +-----+-------------+--------------+ Temp: GPU0: 65C GPU1: 67C GPU0: 251 Sol/s GPU1: 242 Sol/s Total speed: 493 Sol/s +-----+-------------+--------------+ | GPU | Power usage | Efficiency | +-----+-------------+--------------+ | 0 | 139W | 1.81 Sol/W | | 1 | 136W | 1.78 Sol/W | +-----+-------------+--------------+ Conclusion: Decreased the temps from 80C to 65C. Decreased power usage by 20W per eGPU. Hashrate remains about the same, up to a 10 h/s increase overall. From: Temp: GPU0: 79C GPU1: 79C Total speed: 496 Sol/s | 0 | 144W | 1.73 Sol/W | | 1 | 138W | 1.79 Sol/W | To: Temp: GPU0: 65C GPU1: 67C Total speed: 493 Sol/s | 0 | 139W | 1.81 Sol/W | | 1 | 136W | 1.78 Sol/W |