Search content
Sort by
Showing 20 of 52 results by bostonvex
Next version in a day or two
have a litle trouble
algo heavy
cards rx470-570 4gb
double treads work fine
in config "intensity" : 29, "double_threads" : true
single treads dont work with error
Error CL_INVALID_BUFFER_SIZE when creating scratchpad buffer for DeviceID 0 (Thread 0)
in config "intensity" : 57, "double_threads" : false
if set intensity 0 setting 44 and slow rate
same rig work fine with config "intensity" : 58, "double_threads" : false
same drivers version 18.2.1 same swap size 60gb for 12 card same windows version 1709
CL_INVALID_BUFFER_SIZE errors means you're running out of GPU mem. Reduce your intensity.
This used to be a good thread...all about collaboration and sharing ideas.
BUT then it became all about pushing product and trying to make money in a questionable way.
This thread is RIGGED and OVER AND OUT. Not really yelling just mocking.
BUT then it became all about pushing product and trying to make money in a questionable way.
This thread is RIGGED and OVER AND OUT. Not really yelling just mocking.
Re: good wallet that stores most or many major coins on binance?
Hardware wallets and paper wallets. I use a combination since the hardware wallets don't support all coins. I have a Trezor and Ledger Nano plus paper wallets because I'm paranoid.
Odd...how much did you overclock?
Paste OverdriveNtool.ini or your settings for memclock etc.
Paste OverdriveNtool.ini or your settings for memclock etc.
nothing extreme
Hate to ask this, but I'm assuming you already did DDU, reinstalled drivers, tried a different PCI slot.
My guess is the card is suspect. Can you isolate this card on another system by itself to see if the issue carries over?
I have three Vega 56 cards mining monero. A friend wrote the drivers for me and they are in Minnesota running in below zero degree weather. Pulling 6350 hashes currently. Wouldn't recommend any other card for monero mining.
Interesting friend...is he the unicorn farmer in the Dos Equis commercial...
Would love a screenshot.
My rigs would run fine for hours and then out of the blue Cast XMR hangs. I have JJs monitoring script running and because the values can be read from JSON it doesn't pick it up as a hang. Essentially the timestamp remains stagnant, bolded below, with no additional increments. Only solution is to force the Cast window closed and let the monitoring script restart the Cast cmd shell instance.
[16:36:35] GPU0 | 51°C | Fan 3245 RPM | 1913.2 H/s
I know I can modify the hash monitor script to do a check on the timestamp.
Anyone else seen this type of issue?
I have 2 rigs with the following config:
4GB Corsair RAM
ASUS Z270-a mobo
3 x Vega 56 stock bios, memclock at 920mhz for all
[16:36:35] GPU0 | 51°C | Fan 3245 RPM | 1913.2 H/s
I know I can modify the hash monitor script to do a check on the timestamp.
Anyone else seen this type of issue?
I have 2 rigs with the following config:
4GB Corsair RAM
ASUS Z270-a mobo
3 x Vega 56 stock bios, memclock at 920mhz for all
anyone mining bytecoin or electronic dollar - new cryptonight coin? what pool are you using?
I'm gonna try bytecoin.party
This issue has been discussed multiple times. Heres a recap:
Shirty AMD drivers...HBM craps out any time you remove a monitor or power save kicks in and various other undocumented reasons.
Solution:
Don't install Wattman
Get HDMI dongles
Use a hashrate monitoring script to
- Disable GPUs
- Enable GPUs
- Set speed etc via OverdriveNtool
- start Miner
- monitor hashrate
Script can be found here along with many other tips and tweaks:
http://vega.miningguides.com/#Script
Shirty AMD drivers...HBM craps out any time you remove a monitor or power save kicks in and various other undocumented reasons.
Solution:
Don't install Wattman
Get HDMI dongles
Use a hashrate monitoring script to
- Disable GPUs
- Enable GPUs
- Set speed etc via OverdriveNtool
- start Miner
- monitor hashrate
Script can be found here along with many other tips and tweaks:
http://vega.miningguides.com/#Script
Out of curiosity, is it possible to install Windows 10 Pro and running it without registering it, just like you can with the home version?
Yeah in currently running one machine still not registered with no issues so far, been running for a couple months now.
Mike, I had the same issue after installing a Windows Update and always thought it was that causing the issue. Eventually reinstalled Windows and didn't update and the issue dissipated.
This guy had a similar issue...https://bitcointalk.org/index.php?topic=2317406.msg23534925#msg23534925
No worries at all, it was funny and made me laff. Love this community, we all learn and grow together.
That build looks awesome. I have 4 Vega 56s doing 7600H/s mining XMR. My second rig has 2 x 56s so far...waiting on a 64.
That build looks awesome. I have 4 Vega 56s doing 7600H/s mining XMR. My second rig has 2 x 56s so far...waiting on a 64.
ventured into the NTool as pointed out by dragonmike above
WHAT A GREAT TOOL!!!
thnx for the tip dm
gotta love this community, its not only about monetary gain and people prove it actively here
shout out to the forum and its memebers
WHAT A GREAT TOOL!!!
thnx for the tip dm
gotta love this community, its not only about monetary gain and people prove it actively here
shout out to the forum and its memebers
DragonMike....Bostonvex...
..heck we all look a like here anyways...you're welcome.https://bitcointalk.org/index.php?topic=2549085.msg26151310#msg26151310
Hi. RIGED`s bro here.
The Crimson drivers from 17.11.1 and up supports up to 12 Vegas on the Asrock BTC+. Have runned them stable with the 17.11.1 now for quite some time.
Tried mining XMR for a day but ended up with multiple hangs and therefore went back to ETH mining. Have anybody here got any good stable settings for XMR in wattman running Crimson 17.11.1 driver? Not possible to install the
Blockchain driver with so many cards.
Will get another Asrock BTC+ next week hopefully and will splitt the rig and try Electroneum with blockchain drivers to hopefully se the 2000H per card. Fingers crossed..
Thamez
The Crimson drivers from 17.11.1 and up supports up to 12 Vegas on the Asrock BTC+. Have runned them stable with the 17.11.1 now for quite some time.
Tried mining XMR for a day but ended up with multiple hangs and therefore went back to ETH mining. Have anybody here got any good stable settings for XMR in wattman running Crimson 17.11.1 driver? Not possible to install the
Blockchain driver with so many cards.
Will get another Asrock BTC+ next week hopefully and will splitt the rig and try Electroneum with blockchain drivers to hopefully se the 2000H per card. Fingers crossed..
Thamez
Yeah, don't use Wattman at all. Use OverdriveNtool and Devcon.exe to reset Vegas.
Check out the scripts to automate and monitor/restart as hashrate drops.
http://vega.miningguides.com/
I run stable with the following on Vega 56 stock Bios, note I have not done reg hack:
Code:
[general]
MainWindowLeft=736
MainWindowTop=69
[Profile_0]
Name=rxvega
GPU_P0=852;800
GPU_P1=991;900
GPU_P2=1138;950
GPU_P3=1269;1000
GPU_P4=1312;1050
GPU_P5=1474;1100
GPU_P6=1272;950
GPU_P7=1282;950
Mem_P0=167;800
Mem_P1=500;800
Mem_P2=800;900
Mem_P3=920;950
Fan_Min=3000
Fan_Max=4900
Fan_Target=75
Fan_Acoustic=2400
Power_Temp=85
Power_Target=-10
MainWindowLeft=736
MainWindowTop=69
[Profile_0]
Name=rxvega
GPU_P0=852;800
GPU_P1=991;900
GPU_P2=1138;950
GPU_P3=1269;1000
GPU_P4=1312;1050
GPU_P5=1474;1100
GPU_P6=1272;950
GPU_P7=1282;950
Mem_P0=167;800
Mem_P1=500;800
Mem_P2=800;900
Mem_P3=920;950
Fan_Min=3000
Fan_Max=4900
Fan_Target=75
Fan_Acoustic=2400
Power_Temp=85
Power_Target=-10