I see in my log file:
"Dag has been damaged" - what does it mean?
"Dag has been damaged" - what does it mean?
Lower your overclock until this message is gone.
Topic: GMiner v3.24 Ergo+KASPA+ZIL/KAWPOW/Equihash/Cortex - page 25. (Read 307024 times)
Lower your overclock until this message is gone.
I see in my log file:
"Dag has been damaged" - what does it mean?
"Dag has been damaged" - what does it mean?
I have just started to using gminer for ethash on my 4 NVIDIA rigs. RTX3060Ti & RTX3070
I really like dag information when i set high overclock memory value feature.
I hope you will add octopus algorithm for RTX3060 non-ti.
I really like dag information when i set high overclock memory value feature.
I hope you will add octopus algorithm for RTX3060 non-ti.
can you add flag --worker?on some pools with "address.worker" miner cant start?
I'm on Ubuntu 16.04.7
I have RX570 4GB cards
amdgpu-pro-18.30 drivers
Can I mine Beam using latest gminer?
When I try to run it I get error
"gpu not supported"
I have RX570 4GB cards
amdgpu-pro-18.30 drivers
Can I mine Beam using latest gminer?
When I try to run it I get error
"gpu not supported"
nice work on windows 7! @Zminer777
just noticed that there is no need for system ram to follow ETH DAG size.
i was using 6gb and and 8gb on my rigs.
i found out in one rig with version 2.45 works with 4gb when i was troubleshooting the RAM
BTW the issue was a reduce hashrate when using system ram lower than the DAG size
just noticed that there is no need for system ram to follow ETH DAG size.
i was using 6gb and and 8gb on my rigs.
i found out in one rig with version 2.45 works with 4gb when i was troubleshooting the RAM
BTW the issue was a reduce hashrate when using system ram lower than the DAG size
Please check 2.47 hope it solves problem
I can confirm that it works now for me in Windows 10.
Time to test which one is stable for me and my memory overclock.
GMiner v2.47 available for download
v2.47
+ improved memory tweaks under windows (now works on Windows 7)
+ fixed startup crash on some rigs under HiveOS/RaveOS
+ improved compatibility with anti-viruses (minimize anti-hacking errors)
+ support running from go app without anti-hacking error
+ fixed bug with ignoring api parameter in configuration files
+ improved stability
Ethash fee is 0.65%
KAWPOW fee is 1%
v2.47
+ improved memory tweaks under windows (now works on Windows 7)
+ fixed startup crash on some rigs under HiveOS/RaveOS
+ improved compatibility with anti-viruses (minimize anti-hacking errors)
+ support running from go app without anti-hacking error
+ fixed bug with ignoring api parameter in configuration files
+ improved stability
Ethash fee is 0.65%
KAWPOW fee is 1%
I am having difficulties running the miner in Admin privileges. Even though I have made the the miner always run as Admin when I start the Bat file it says: Memory tweaks initialization failed, run miner with admin privileges.
Any help would be apreciated.
Please check 2.47 hope it solves problem Any help would be apreciated.
I am having difficulties running the miner in Admin privileges. Even though I have made the the miner always run as Admin when I start the Bat file it says: Memory tweaks initialization failed, run miner with admin privileges.
Any help would be apreciated.
Any help would be apreciated.
Anyone who knows how wo setup eth+zil?
The example just shows zil-only pool, no hint how to setup eth one
The example just shows zil-only pool, no hint how to setup eth one
Quote
can you share a sample command line for nvidia inspector? Thanks
You set it in the gui. If you reinstall the driver, you have to set it again. (nvidia profile inspector (windows))
35.5 mhs here with 9xp104-100 PL 70 (125w) +200 core + 200 mem + mt 6
my nvidia profile inspector shows P2 state on.. do i have to set it to zero even with these cards?
solved.. nvidia profile inspector doens work with these cards!
thanks
alex
Quote
can you share a sample command line for nvidia inspector? Thanks
You set it in the gui. If you reinstall the driver, you have to set it again. (nvidia profile inspector (windows))
My 1070Ti hash with 31Mh/s with --mt 4.
Disable force P2 state with nvidia inspector, and coreclock at 1900. memclock at 4500, (micron memory)
power limit is 65% and my core clock do not drop from 1900Mhz.
I use powerlimit 77% for 34 mhash.- More power, more stable on high memory clocks
Disabled P2 state, but my memory only clocks to +425 for 4233Mhz. After that it becomes unstable. Hashrate still 30-31Mh/s.
Did you try to increase the power? Higher clocks need more power, or else the cards will trottle. Also make sure that the core clock don't drop. with 1800 core I get ~33.5 (MSI Aero 1070ti). I also use the kernel --oc 5
whats the syntax if I have 1 4gb gpu at index 0 and I want to set a --daglimit option on it. (470 4gb, or is this zombie mode dead for 4gb cards?)
How do i state it so it doesnt apply the dag limit to the rest of the cards.
How do i state it so it doesnt apply the dag limit to the rest of the cards.
Try this
Quote
for example gpu0 4GB and gpu1 8GB
--dag_limit 4048 7256 --dag_mode 1 0
--dag_limit 4048 7256 --dag_mode 1 0
Disabled P2 state, but my memory only clocks to +425 for 4233Mhz. After that it becomes unstable. Hashrate still 30-31Mh/s.
Did you try to increase the power? Higher clocks need more power, or else the cards will trottle. Also make sure that the core clock don't drop. with 1800 core I get ~33.5 (MSI Aero 1070ti). I also use the kernel --oc 5
My 1070Ti hash with 31Mh/s with --mt 4.
Disable force P2 state with nvidia inspector, and coreclock at 1900. memclock at 4500, (micron memory)
Disabled P2 state, but my memory only clocks to +425 for 4233Mhz. After that it becomes unstable. Hashrate still 30-31Mh/s.
My 1070Ti hash with 31Mh/s with --mt 4.
Disable force P2 state with nvidia inspector, and coreclock at 1900. memclock at 4500, (micron memory)
Jump to: