Search content
Sort by
Showing 20 of 37 results by Hackintoshihope
Re: PhoenixMiner 5.6d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
The new beta version is finally ready. You can download PhoenixMiner 5.7a from here:
PhoenixMiner_5.7a_Windows.zip (GitHub)
PhoenixMiner_5.7a_Linux.tar.gz (GitHub)
The new features in this release are:
The support for -ttj, -ttmem, -tmaxj, and -tmaxmem for Nvidia 3090 and 3080 GPUs is not yet ready for release. We hope to have it ready for the final 5.7 release.
For more robust integrity check, you can use our GPG public key, which was verifyed with ETH transaction from our main devfee account as explained here: https://bitcointalk.org/index.php?topic=2647654.msg56755869#msg56755869.
Please let us know if you have any problems or questions related to PhoenixMiner 5.7a.
PhoenixMiner_5.7a_Windows.zip (GitHub)
PhoenixMiner_5.7a_Linux.tar.gz (GitHub)
The new features in this release are:
- Added lock core clock
- The problem with the missing GPU temperatures on Nvidia GPUs is fixed
- Added native kernels for AMD RX6700 GPUs. These are faster than the generic kernels and produce a lot less stale shares
- Increase the max supported DAG epoch to 550 (should be enough to about Jan 2023)
- Full support for setting clocks, fan speeds, voltages, and memory timings of AMD RX6900/6800/6700 cards
- The specific hashrate is now shown in the form of kilo hashes per joule (kH/J). Example: if a GPU has hashrate of 30 MH/s with 100W power usage, the specific hashrate is 300 kH/J
- Added new command-line parameters -ttj and -ttmem, allowing automatic fan speed control based on GPU hotspot (junction), and memory temperatures respectively. Example: -ttmem 83 will keep the GPU memory temperature at or bellow 83C by increasing the fan speed as necessary. These parameters can be combined with -tt, as well as with each other. These options are supported only on AMD GPUs that report junction and memory temperatures
- Added new command-line parameters -tmaxj and -tmaxmem, allowing to decrease the GPU usage when the GPU hotspot (junction), or GPU memory temperatures are above the specified thresholds. These options are supported only on AMD GPUs that report junction and memory temperatures
- Added support for AMD Windows drivers 21.3.2, and 21.3.1
- Added support for AMD Linux drivers 20.50.x. Use this drivers only if you have Polaris or older GPUs, or the latest RX6x000 GPUs. WARNING: Vega, Radeon VII, and Navi GPUs won't work with these drivers!
- Turn off the zero fan feature on AMD cards whenever a fixed fan speed is used (e.g. -tt -40), or when an auto fan with min fan speed is used (e.g. -tt 63 -minfan 35). To disable this feature, add -fanstop 1 command-line parameter
- When -mcdag 1 is specified under Linux, the miner will not wait for the daggen.sh script to finish before starting to generate the DAGs. Instead it will for a fixed 7 seconds. This allows you to do all the following in the daggen.sh: turn off the overclocking of Nvidia GPUs, sleep for 30-60 seconds to allow time for DAG generation, and then re-apply the overclocking of the Nvidia GPUs
- Other small improvements and fixes
The support for -ttj, -ttmem, -tmaxj, and -tmaxmem for Nvidia 3090 and 3080 GPUs is not yet ready for release. We hope to have it ready for the final 5.7 release.
For more robust integrity check, you can use our GPG public key, which was verifyed with ETH transaction from our main devfee account as explained here: https://bitcointalk.org/index.php?topic=2647654.msg56755869#msg56755869.
Please let us know if you have any problems or questions related to PhoenixMiner 5.7a.
Re: PhoenixMiner 5.5c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
I tried new PhoenixMiner 5.6a with the same settings from working 5.5c and I got this error:
https://ibb.co/jLcPZHw
"Video driver consistency error. Please go back to version 5.5c"
Driver version is 20.11.1
Does anyone have this issue?
https://ibb.co/jLcPZHw
"Video driver consistency error. Please go back to version 5.5c"
Driver version is 20.11.1
Does anyone have this issue?
You are using the virus that is 5.5d not 5.6a...
Re: PhoenixMiner 5.5c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Why doesnt this work anymore?
phoniex miner cant set memory clock delta -137
I get the above error when trying to do this: -mclock +1000,+1000,+1250,+950,+1000,+1000,+1000,+950
phoniex miner cant set memory clock delta -137
I get the above error when trying to do this: -mclock +1000,+1000,+1250,+950,+1000,+1000,+1000,+950
did you run phoenixminer as administrator?
This was it I forgot I needed to do this...
Re: PhoenixMiner 5.5c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Why doesnt this work anymore?
phoniex miner cant set memory clock delta -137
I get the above error when trying to do this: -mclock +1000,+1000,+1250,+950,+1000,+1000,+1000,+950
phoniex miner cant set memory clock delta -137
I get the above error when trying to do this: -mclock +1000,+1000,+1250,+950,+1000,+1000,+1000,+950
Re: T-Rex 0.19.11 NVIDIA GPU miner (Ethash, Octopus, Kawpow, MTP)
so far so good T-Rex ok ))
I don't know what kind of trick you're trying to pull. Are you selling innocent people a virus through this forum?
Anyway, a 3070 laptop CANNOT be faster than a 3070 Desktop card. So stop boasting with lies, you're only making yourself a fool.
A 3070 in a laptop has the same memory bandwidth as a 3060 ti and 3070 and more cuda cores then a 3060 ti. It can be faster then a desktop 3070 with an unlocked tdp vbios and/or a shunt mod. My laptop 3070 mines at 62 MHS.
Re: NVIDIA is cutting the 3060's Hash Rate in Half & NEW Mining specific GPU's
Would it be possible to edit 3060 BIOS or flash 3060ti BIOS on it. I believe the problem is in BIOS because one dude used current drivers and the card still downclocked
Possible? Yes likely no... We still do not have an ethlargement pill for 20 series cards.
Re: NVIDIA is cutting the 3060's Hash Rate in Half & NEW Mining specific GPU's
What's their problem? 
What business does geforce and nvidia have with miners that makes them want to lower hashrate for RTX3060? People don't just buy costly gpu for gaming only, in fact everyone has the right to do what they like with their gpu since they paid for them, what's nvidia business in mining ? This is weird to be honest
What business does geforce and nvidia have with miners that makes them want to lower hashrate for RTX3060? People don't just buy costly gpu for gaming only, in fact everyone has the right to do what they like with their gpu since they paid for them, what's nvidia business in mining ? This is weird to be honest The right procedure here is make their gpu miners better than gaming gpus, limiting gpus will only make it worse.
I think their goal is to dump all their low binned dies that they had no use for in these mining cards.
Sadly this isnt true they are running and it looks like it isnt a drive issue rather a vbios one... See here: https://www.facebook.com/groups/MineEth/permalink/1128928574187552/?comment_id=1128993570847719&reply_comment_id=1129021457511597
Re: PhoenixMiner 5.5c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Just registered to post my thoughts!
I’ve been a “reader/browser” for a very long time. Reading and learning, strictly!
But since last few months and 50 pages long, holy crap! So many dumb questions from newbies as dumb as how to turn on their computers!
C’mon!
Reddit is even worse full with same basic questions. I can tell most of these wanna-be miners never even touched computers but ETH price has given them huge erection to pop in!
I’ve been a “reader/browser” for a very long time. Reading and learning, strictly!
But since last few months and 50 pages long, holy crap! So many dumb questions from newbies as dumb as how to turn on their computers!
C’mon!
Reddit is even worse full with same basic questions. I can tell most of these wanna-be miners never even touched computers but ETH price has given them huge erection to pop in!
and whats bad on that? you knew everything? dont post like that.. and dont offtopic..
if you are here to help others go on, or else dont quote any of newbies comments..
act like professional.. not like you are now..
have more questions? you dont like something???
pm no problem
how annoying people like you are, acting like you know everything, dont you even dare to reply this quote
Dude, I am looking at your posts and all I see is how do I do this ... how do I do that!!
Learn to read / search / google before wasting resources.
Each and every one of these kind people who help newbies like yourself used to be newbie but they did their homework first. Read the documentation, learn Windows / Linux whatever OS you want to run your rigs. Then when you hit something difficult, search all these messages first before posting your questions.
Look up annoying and professional then ask me not to be one or act like one!
On the same note, you owe all these people who help you ETH! They give you free advice but do NOT abuse it.
Windows virtual memory set up? How hard is it to grab a calculator and do the math??
No! I don’t know everything but I am wasting so much time jumping topics to topics to learn something NEW - not crappy questions.
And when same people on this very thread ask you to do some stuff on your own by reading previous questions and learn, you lose your temper which proves IF you knew something, you would not bother to even help.
As a matter of fact, even I am trying to teach you something. But, you have no clue what the hell I mean!!!!!
How about we mine ETH for you using own own rigs?? It makes life easier for all of us!!
I have read them, and I know what you mean. However sometimes we might just be bored at home sick and want to help
Re: PhoenixMiner 5.5c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
After my miner was running for 65 Hours without any rejected or invalid shares it randomly stopped with fatal error debugger detected. I’m not sure what this means and how to troubleshoot. Is there something where I can see what could of possibly caused the issue? This is a rig with 2 3060 ti, 4 3070’s, and 1 3090. With 900MHz memory overclocks (3070 and 3060 Ti), 750 memory overclocks (3090).
Yeah these 3090 with their 24gb (lol) vram are a complete nightmare to cool, the 3080's as well to some extent but not as bad as the 3090.
My way of thinking for my 4x 3090 is fully water-cooled or don't bother.. 3080's are a bit better on air but not massively.
My way of thinking for my 4x 3090 is fully water-cooled or don't bother.. 3080's are a bit better on air but not massively.
All you have to do is replace thermal pads with gelid extreme... fixed my memory heat problems on 3090.
So here are some examples:
Re-padded Gigabyte OCs 3080 with Thermal Grizzly 8 Pads:
98°C, 98°C, 94°C, 96°C
Stock ASUS TUF OCs 3080:
100°C, 104°C, 106°C, 104°C.....
I dont like that. Should I consider doing a pad replacement on the ASUS, too? Worry about warranty.
Re-padded Gigabyte OCs 3080 with Thermal Grizzly 8 Pads:
98°C, 98°C, 94°C, 96°C
Stock ASUS TUF OCs 3080:
100°C, 104°C, 106°C, 104°C.....
I dont like that. Should I consider doing a pad replacement on the ASUS, too? Worry about warranty.
I used gelid extreme and saw drops 59 the 80’s from stock...
I have an Asus Strix RTX 3090 OC along with a Gigabyte 1660 Super. I mine ETH using t-rex and phoenix miner 5.4c and am getting very low hash rates with my 3090.
When I start the miner, my 3090's core clock drops from 1860mhz to fluctuating around 900-1200mhz and memory clock drops from 9751mhz to 9501mhz. Temp is about 50 and 270W. Hash rate starts around 100 then drops to around 92.
No issues with my 1660 Super. If I unplug the 1660 Super, I still have the same problem with the 3090.
I have a relatively new build (Asus X570 MB, Ryzen 7 3800X). The 3090 performs great on bench mark test (userbenchmark) and stress tests (Kombustor) where I can go +160 mhz core clock and +1000mhz memory clock and be stable. When I turn those OC settings on with MSI Afterburner when mining, my hash rate actually goes down even further (core clock sticks about 900, memory clock goes up to 1051 with hash rate of 90) .
Any idea what could be causing the problem and how to fix it so I can get around a 120 hash rate?
When I start the miner, my 3090's core clock drops from 1860mhz to fluctuating around 900-1200mhz and memory clock drops from 9751mhz to 9501mhz. Temp is about 50 and 270W. Hash rate starts around 100 then drops to around 92.
No issues with my 1660 Super. If I unplug the 1660 Super, I still have the same problem with the 3090.
I have a relatively new build (Asus X570 MB, Ryzen 7 3800X). The 3090 performs great on bench mark test (userbenchmark) and stress tests (Kombustor) where I can go +160 mhz core clock and +1000mhz memory clock and be stable. When I turn those OC settings on with MSI Afterburner when mining, my hash rate actually goes down even further (core clock sticks about 900, memory clock goes up to 1051 with hash rate of 90) .
Any idea what could be causing the problem and how to fix it so I can get around a 120 hash rate?
Yes memory power throttle you need air flow on the backplate of your 3090.
EVGA XC3 ULTRA GAMING, getting 102 MH/s when not using the monitor, no throttling.
Fans at 60%, +1500 memory, -200 GPU, 70 PL @ ~240W.
Had a Gigabyte Gaming OC before; was thermal throttling with PL 60, was pulling between 85-91 MH/s. Glad to be rid of it.
Fans at 60%, +1500 memory, -200 GPU, 70 PL @ ~240W.
Had a Gigabyte Gaming OC before; was thermal throttling with PL 60, was pulling between 85-91 MH/s. Glad to be rid of it.
I tall depends on the backplate and location of thermal pads, if they are good the memory will not throttle!
Re: T-Rex 0.19.7 NVIDIA GPU miner (Ethash, Octopus, Kawpow, MTP)
T-Rex 0.19.7
* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs
* ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues)
* Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions
* (API) Add new "pause" command for "control" handler to pause and resume mining
* (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error
Bug fixes:
* ("x21s") "incorrect size of extranonce2" error
* (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled
* (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations
* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs
* ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues)
* Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions
* (API) Add new "pause" command for "control" handler to pause and resume mining
* (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error
Bug fixes:
* ("x21s") "incorrect size of extranonce2" error
* (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled
* (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations
Completely unreliable for a 7 card 30series rig with medium memory overclocks 3060Ti +800MHz, 3070 +700MHz and +800MHz, 3090 +350MHz... It cannot create the DAG reliably it will hang and crash miner. However if memory overclocks are reduced by 200MHz on each card it will create DAG why is this? It works perfectly with version 0.19.5 and 0.19.4 (these I have tested with these settings).
This is absolutely not a stable build for me... It just hangs unless used with an extremely low memory overclock.
I use 60% power. I do not want to run the memory at such inflated values as it will degrade the memory 700 to 800 I have found to be stable in gaming and normal workloads so I am satisfied with this long term performance. However as stated .19.7 is completely unreliable when creating the DAG.
That could or could not be an issue. I have 3 year warranty on my cards so I don't really care if the card is gonna blow up because it's up do Nvidia to limit overclocking capabilities. We're not doing bios mod or anything out of the ordinary.
It is not the issue as .19.5 works with 0 issue also I do care as an RMA can take months.
Re: T-Rex 0.19.7 NVIDIA GPU miner (Ethash, Octopus, Kawpow, MTP)
T-Rex 0.19.7
* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs
* ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues)
* Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions
* (API) Add new "pause" command for "control" handler to pause and resume mining
* (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error
Bug fixes:
* ("x21s") "incorrect size of extranonce2" error
* (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled
* (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations
* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs
* ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues)
* Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions
* (API) Add new "pause" command for "control" handler to pause and resume mining
* (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error
Bug fixes:
* ("x21s") "incorrect size of extranonce2" error
* (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled
* (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations
Completely unreliable for a 7 card 30series rig with medium memory overclocks 3060Ti +800MHz, 3070 +700MHz and +800MHz, 3090 +350MHz... It cannot create the DAG reliably it will hang and crash miner. However if memory overclocks are reduced by 200MHz on each card it will create DAG why is this? It works perfectly with version 0.19.5 and 0.19.4 (these I have tested with these settings).
This is absolutely not a stable build for me... It just hangs unless used with an extremely low memory overclock.
I have the same issue oddly enough with a 9 GPU rig, my 8 and 7 GPU 3060ti rigs work with no issues.
I also freeze on DAG generation at the start of mining causing the rig to reboot.
Im glad that you are having the same issue... at first I thought my GPUs were just degrading but the previous version works without issue. Do you notice the same behavior reducing memory clocks increases stability with this release?
I am going crazy with my two 3090s. Both run at about 105Mh/s. The MSI Triple is the primary and runs without issues, but the Gigabyte secondary either wants to spin the fans up to 100%, or throttle GPU down to 800Mhz, and crank out only 80MH/s. I have tried power limiting, GPU downclocking, and memory overclocking, however could not resolve the issue. I have a healthy Corsair 1200W power supply which previously ran 4x1070s and a single 1080 with no issues. Power draw shows 350W on the MSI, and 250W on the Gigabyte (on a riser). Both have their PCIE power inputs fully populated with clean power. Any ideas?
You have to have a huge memory downclock with a fan blasting air on the backplate... Also you must make sure that whatever 3090 you are using has memory cooling pads that touch the backplate. The issue is the GDDR6X gets extremely hot and overwhelmed with an overclock passed 500MHz and then the core is downclocked to try and cool it.
Re: T-Rex 0.19.7 NVIDIA GPU miner (Ethash, Octopus, Kawpow, MTP)
T-Rex 0.19.7
* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs
* ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues)
* Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions
* (API) Add new "pause" command for "control" handler to pause and resume mining
* (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error
Bug fixes:
* ("x21s") "incorrect size of extranonce2" error
* (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled
* (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations
* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs
* ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues)
* Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions
* (API) Add new "pause" command for "control" handler to pause and resume mining
* (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error
Bug fixes:
* ("x21s") "incorrect size of extranonce2" error
* (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled
* (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations
Completely unreliable for a 7 card 30series rig with medium memory overclocks 3060Ti +800MHz, 3070 +700MHz and +800MHz, 3090 +350MHz... It cannot create the DAG reliably it will hang and crash miner. However if memory overclocks are reduced by 200MHz on each card it will create DAG why is this? It works perfectly with version 0.19.5 and 0.19.4 (these I have tested with these settings).
This is absolutely not a stable build for me... It just hangs unless used with an extremely low memory overclock.
I use 60% power. I do not want to run the memory at such inflated values as it will degrade the memory 700 to 800 I have found to be stable in gaming and normal workloads so I am satisfied with this long term performance. However as stated .19.7 is completely unreliable when creating the DAG.
Re: T-Rex 0.19.7 NVIDIA GPU miner (Ethash, Octopus, Kawpow, MTP)
T-Rex 0.19.7
* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs
* ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues)
* Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions
* (API) Add new "pause" command for "control" handler to pause and resume mining
* (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error
Bug fixes:
* ("x21s") "incorrect size of extranonce2" error
* (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled
* (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations
* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs
* ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues)
* Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions
* (API) Add new "pause" command for "control" handler to pause and resume mining
* (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error
Bug fixes:
* ("x21s") "incorrect size of extranonce2" error
* (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled
* (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations
Completely unreliable for a 7 card 30series rig with medium memory overclocks 3060Ti +800MHz, 3070 +700MHz and +800MHz, 3090 +350MHz... It cannot create the DAG reliably it will hang and crash miner. However if memory overclocks are reduced by 200MHz on each card it will create DAG why is this? It works perfectly with version 0.19.5 and 0.19.4 (these I have tested with these settings).
Re: [ANN] TeamRedMiner 0.4.4 - Cryptonight Thread - High hashrate, Low Power
I've been killing myself over this one... Maybe, someone else from the outside can help me...
I recently upgraded my ATX 1000w PSU to a 1200w server PSU/breakout board. Upon that upgrade, as I was applying my overclocks and such through a bat file with ODnT, my system started freezing. If I applied this settings manually, no issues.
So, I did what any good miner would do.. DDU and start over.. Same thing... I DDU'd a 3rd time and upgraded to the latest drivers along with ODnT 2.8. Since then, my system hasn't had any issues applying the clock n suck through a bat file.
However, my hashrate that the miner shows vs what the miner shows pool side has been off... I've tried different settings in ODnT, lowered memory, more power and none of my tests are matching up..
I will run the miner for 12 hours, get both miner/pool hashrate to match up at 5.5 khs, stop miner, start again and run for 12 more hours and then they aren't matched anymore... 5.5 vs 5.3.... Sometimes the same test will result even worse at 5.2 or 5.1 -- I understand luck is in play, but I don't think luck should effect it this much.
My other rigs show Miner and Pool to be very close..
I have fixed diff at 55000 on Support XMR.
Moddest overclocks.
570s run 1150/875 and memory 1925/875.
580s run 1200/900 and meomry 2000/900.
I'll run the same clocks back to back and get different reported values each time... There are times where I have cards running 300-400 hs less than expected on the pool
I've tried more power, less memory, more memory...
I'm at a loss..
I recently upgraded my ATX 1000w PSU to a 1200w server PSU/breakout board. Upon that upgrade, as I was applying my overclocks and such through a bat file with ODnT, my system started freezing. If I applied this settings manually, no issues.
So, I did what any good miner would do.. DDU and start over.. Same thing... I DDU'd a 3rd time and upgraded to the latest drivers along with ODnT 2.8. Since then, my system hasn't had any issues applying the clock n suck through a bat file.
However, my hashrate that the miner shows vs what the miner shows pool side has been off... I've tried different settings in ODnT, lowered memory, more power and none of my tests are matching up..
I will run the miner for 12 hours, get both miner/pool hashrate to match up at 5.5 khs, stop miner, start again and run for 12 more hours and then they aren't matched anymore... 5.5 vs 5.3.... Sometimes the same test will result even worse at 5.2 or 5.1 -- I understand luck is in play, but I don't think luck should effect it this much.
My other rigs show Miner and Pool to be very close..
I have fixed diff at 55000 on Support XMR.
Moddest overclocks.
570s run 1150/875 and memory 1925/875.
580s run 1200/900 and meomry 2000/900.
I'll run the same clocks back to back and get different reported values each time... There are times where I have cards running 300-400 hs less than expected on the pool
I've tried more power, less memory, more memory...
I'm at a loss..
Sadly these server PSUs only output 900W on 120V (normal US output) unless you are on 240V this could explain why you are having power issues as the server psu is not able to output the required power. Please correct me if anything Ive assumed is wrong.