Search content
Sort by
Showing 20 of 214 results by ben8jam
Why do the VEGAs on the PSU without the Mobo, use more power than when on mobo?
I have a 850W EVGA G3 and a 750 EVGA G3.
I have a Asrock connected to the 850W along with 3 VEGA 56.
On the 750W PSU I have two VEGA56.
When mining Cryptonight, the 850W psu reads 550W (the Mobo takes about 50-80W) which means the 3 Vega are only drawing about 150-160W.
But on the 750W psu it reads, 410W, which means those are running at 205W!
I can move the cards around between the mobos and the numbers stay exactly the same, so it's not a config or a card issue.
All running on risers. All identical cards. all identical settings.
What on earth would cause this?
I have a Asrock connected to the 850W along with 3 VEGA 56.
On the 750W PSU I have two VEGA56.
When mining Cryptonight, the 850W psu reads 550W (the Mobo takes about 50-80W) which means the 3 Vega are only drawing about 150-160W.
But on the 750W psu it reads, 410W, which means those are running at 205W!
I can move the cards around between the mobos and the numbers stay exactly the same, so it's not a config or a card issue.
All running on risers. All identical cards. all identical settings.
What on earth would cause this?
Stopped using power play tables?
Do the 18+ drivers allow you to change voltage on lower P states? As far as i know i've been using the power play tables and overdriventool to keep the power consumption down. Not needing the power play tables is new to me.
Yeh, I've seen this posted a few places about not needing PPT anymore. So if I delete that reg key there's no impact? I don't get that.
I stopped using power play tables since 18+ drivers. overdriventool is enough to achieve full hashrate at 165W with vega 64 and modified vega 56.
clock: set to 1600, voltage set to 850mV
mem: set to 1100, voltage set to 860mV
real clock is 1400 to 1500 depending of the card ; real voltage: 885 mV; shown in GPUZ.
4 cards rig is at 700W, system uses roughly 35W
clock: set to 1600, voltage set to 850mV
mem: set to 1100, voltage set to 860mV
real clock is 1400 to 1500 depending of the card ; real voltage: 885 mV; shown in GPUZ.
4 cards rig is at 700W, system uses roughly 35W
What is your modified 56? Did you flash the bios to 64? Love to see your OverdriveNT settings for the 56.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.3 (Windows/Linux)
Temperature control thread hangs, need to restart miner!
I'm getting this too. But on Linux. 10.2 version. Wasn't happening on 10.1. Happens quite a lot now but only on one rig.
Core clock used to stay locked on 1400, now bounces between 950 and 1450. VEGA56
So Windows update ran (I had tried in earnest to disable it, and ended up pausing it for a month, but the month ran out) and now having issues with the Vegas not pinning to their set clock speeds.
I noticed this because the indicator lights on the Vegas used to be always on when mining, but now they blink and dance. When checking HWMonitor I can see the core clock is fluctuating all over the place.
I use overdrivent and the blockchain driver (no wattman or amd software). This has been working fine without incident for a month.
I'm at a total loss. Anyone else have this issue with their Vega?
I've tested on both XMR-STAK and Claymore - same issue.
I noticed this because the indicator lights on the Vegas used to be always on when mining, but now they blink and dance. When checking HWMonitor I can see the core clock is fluctuating all over the place.
I use overdrivent and the blockchain driver (no wattman or amd software). This has been working fine without incident for a month.
I'm at a total loss. Anyone else have this issue with their Vega?
I've tested on both XMR-STAK and Claymore - same issue.
Re: Silly question-could an Arock H100 cause my Start button and Cortana to not work
Disable Cortana and may be try or create a new Windows user and check with it.
I might be saying Cortana wrong, I did disable it when I installed windows, but it's also the name of the search bar - which I need cause I can't remember how to navigate to half of the things anymore, like where is button to the dang control panel or system settings lol
So a y-splitter is no good, but the 8 pin to 2x-8pin that comes with my EVGA is okay?
I hope so, cause that's what I've been using.
You have 2x8pin really? Because I have 6+2 and a 6 pin on which I use 6 to 8 pin adaptorI hope so, cause that's what I've been using.
Yeh, my 750 and 850 G2/G3's come with 2 8pin->2x 8pin cables. So, I've been using those for the vegas.
Re: Silly question-could an Arock H100 cause my Start button and Cortana to not work
I had the same problem when using the AMD blockchain drivers with the Windows 10 v1709 (fall creator's update). Went back to the blockchain drivers on Windows 10 v1703 and it's working.
Wow... I heard that I needed 1709 in order to run more than 3 vegas - so might just have to suck it up. It's super annoying.
Silly question-could an Arock H100 cause my Start button and Cortana to not work
Running a windows machine for the first time in a while (been using Ubuntu for all my rigs) and having the oddest issue with a non-responsive Start menu button and Cortana search bar. It plum just doesn't do anything most of the time. I have to click in and out over and over and maybe it will register.
Yet, I just moved the SSD over to an Asus Z270a and no problem what so ever.
AND, on the ASROCK, I added a brand new M.2. drive with a clean windows install and back to the same, can't click start.
The only difference between the two mobos is one is being used to test GPUs and the other (the Asrock) has 5 Vegas hooked up to it. I have no issues with mining or hashrates or anything else... ironically.
Yet, I just moved the SSD over to an Asus Z270a and no problem what so ever.
AND, on the ASROCK, I added a brand new M.2. drive with a clean windows install and back to the same, can't click start.
The only difference between the two mobos is one is being used to test GPUs and the other (the Asrock) has 5 Vegas hooked up to it. I have no issues with mining or hashrates or anything else... ironically.
I have 850W PSU running on full capacity for about 3 month non-stop and it works fine 
If your kill-a-watt is registering 850W, then you PSU is only supplying 680 Watts if we assume 85% efficient at max power. If you bought a larger PSU, say 1000W and ran the same rig (680W draw) it would register 740W on the Kill-a-watt. So you are throwing away 100W per hour. Which is about $130 a year at .15c/kwh. Which is the cost of a 1000w psu about
If your PSU is less efficient than 85% at max, then you are wasting even more money.
If you were running a 1000W PSU at full capacity, meaning your components are pulling 1000W from the PSU, your Kill-a-watt would register somewhere close to 1175W (assuming your efficiency dropped to around 85% at full power). That's a lot of wasted energy due to heat.
So even if your kill-a-watt is sayin 950W, your PSU is probably only delivering 810ish watts.
The 80% rule is a very broad term that came from server PUDs and also applies to household fuses which will flip due to excess heat generated by running continously at over 80% of the circuits max load (usaully 15a or 20a for households).
So even if your kill-a-watt is sayin 950W, your PSU is probably only delivering 810ish watts.
The 80% rule is a very broad term that came from server PUDs and also applies to household fuses which will flip due to excess heat generated by running continously at over 80% of the circuits max load (usaully 15a or 20a for households).
Well this is not good to hear. I've got four Sapphires running great. My two new Gigabyte 56s just arrived.... Will let you know if I have same issues....
In the end I really dont even care about the extra 50h but I'm curious why the fck it does not work on Gigabytes.
Identical cards. Works like a charm on Sapphires on high mhz and low voltages. Does not work at all on Gigabytes.
On GB cards I can get the SoC to work on 1200mhz with my own reg files but then I am limited to 950mv minimum.
What gives ?
So I'm bad luck then, I have 4 gigabyte vega 56. Overclocking SOC to 1200 not working stable, miner stops working, miner freezes, pc freezes. Tried setting those numbers from C0,D4,01 to 38,C1,01 (for 1,15Ghz) but no luck SOC stays 1200 (1999). Increased Voltage for both GPU and memory, it works like stable, get about 2% more h/s but get about 12% compute error, which I never seen before.
In the end I really dont even care about the extra 50h but I'm curious why the fck it does not work on Gigabytes.
Identical cards. Works like a charm on Sapphires on high mhz and low voltages. Does not work at all on Gigabytes.
On GB cards I can get the SoC to work on 1200mhz with my own reg files but then I am limited to 950mv minimum.
What gives ?
Yours is pretty different from the 1100mhz 905mv version that we're all downloading. I just have no idea how to interpret all the hex.
https://1drv.ms/u/s!AsrdFd4FVQj_hUwryMPBjYMKsE1m
It's nothing special, guys
https://1drv.ms/u/s!AsrdFd4FVQj_hUwryMPBjYMKsE1m
It's nothing special, guys
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0008]
"PP_PhmSoftPowerPlayTable"=hex:9d,02,08,01,00,5c,00,37,07,00,00,ec,2b,00,00,1b,\
00,48,00,00,00,80,a9,03,00,f0,49,02,00,32,00,08,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,02,01,5c,00,36,02,2d,02,94,00,85,01,af,00,19,01,7a,00,8c,00,\
a3,01,00,00,00,00,59,02,00,00,90,00,8f,02,54,01,2a,01,7e,01,00,71,02,00,71,\
02,02,02,00,00,00,00,00,00,08,00,00,00,00,00,00,00,04,00,07,00,03,00,05,00,\
00,00,00,00,00,00,01,08,20,03,84,03,84,03,84,03,84,03,84,03,84,03,84,03,01,\
01,46,05,01,01,84,03,00,05,60,ea,00,00,00,dc,4a,01,00,01,00,77,01,00,02,90,\
91,01,00,03,c0,d4,01,00,04,01,08,d0,4c,01,00,00,00,80,00,00,00,00,00,00,88,\
bc,01,00,01,00,00,00,00,00,00,00,00,98,fc,01,00,02,00,00,00,00,00,00,00,00,\
90,0e,02,00,03,00,00,00,00,00,00,00,00,00,26,02,00,04,00,00,00,00,00,00,00,\
00,60,61,02,00,05,00,00,00,00,01,00,00,00,90,8b,02,00,06,00,00,00,00,01,00,\
00,00,98,ab,02,00,07,00,00,00,00,01,00,00,00,00,03,60,ea,00,00,00,dc,4a,01,\
00,00,90,5f,01,00,00,00,08,28,6e,00,00,00,2c,c9,00,00,01,f8,0b,01,00,02,80,\
38,01,00,03,90,5f,01,00,04,f4,91,01,00,05,d0,b0,01,00,06,c0,d4,01,00,07,00,\
08,6c,39,00,00,00,24,5e,00,00,01,fc,85,00,00,02,ac,bc,00,00,03,34,d0,00,00,\
04,68,6e,01,00,05,08,97,01,00,06,ec,a3,01,00,07,00,01,68,3c,01,00,00,01,04,\
3c,41,00,00,00,00,00,50,c3,00,00,00,00,00,80,38,01,00,01,00,00,24,71,01,00,\
02,00,00,01,08,00,98,85,00,00,78,b4,00,00,60,ea,00,00,50,c3,00,00,01,78,ff,\
00,00,40,19,01,00,b4,27,01,00,50,c3,00,00,02,80,38,01,00,dc,4a,01,00,dc,4a,\
01,00,50,c3,00,00,03,dc,4a,01,00,90,5f,01,00,90,5f,01,00,50,c3,00,00,04,90,\
5f,01,00,00,77,01,00,90,5f,01,00,50,c3,00,00,05,00,77,01,00,90,91,01,00,90,\
5f,01,00,50,c3,00,00,06,6c,b0,01,00,6c,b0,01,00,00,77,01,00,50,c3,00,00,07,\
c0,d4,01,00,c0,d4,01,00,90,91,01,00,50,c3,00,00,01,18,00,00,00,00,00,00,00,\
0b,e4,12,dc,05,fc,08,41,00,0f,00,54,03,90,01,90,01,90,01,90,01,90,01,90,01,\
90,01,00,00,00,00,00,02,04,21,07,08,01,08,01,08,01,2c,01,00,00,4a,00,69,00,\
4a,00,4a,00,5f,00,73,00,73,00,64,00,40,00,90,92,97,60,96,00,90,46,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,02,02,d4,30,00,00,02,10,60,ea,00,\
00,02,10
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0008]
"PP_PhmSoftPowerPlayTable"=hex:9d,02,08,01,00,5c,00,37,07,00,00,ec,2b,00,00,1b,\
00,48,00,00,00,80,a9,03,00,f0,49,02,00,32,00,08,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,02,01,5c,00,36,02,2d,02,94,00,85,01,af,00,19,01,7a,00,8c,00,\
a3,01,00,00,00,00,59,02,00,00,90,00,8f,02,54,01,2a,01,7e,01,00,71,02,00,71,\
02,02,02,00,00,00,00,00,00,08,00,00,00,00,00,00,00,04,00,07,00,03,00,05,00,\
00,00,00,00,00,00,01,08,20,03,84,03,84,03,84,03,84,03,84,03,84,03,84,03,01,\
01,46,05,01,01,84,03,00,05,60,ea,00,00,00,dc,4a,01,00,01,00,77,01,00,02,90,\
91,01,00,03,c0,d4,01,00,04,01,08,d0,4c,01,00,00,00,80,00,00,00,00,00,00,88,\
bc,01,00,01,00,00,00,00,00,00,00,00,98,fc,01,00,02,00,00,00,00,00,00,00,00,\
90,0e,02,00,03,00,00,00,00,00,00,00,00,00,26,02,00,04,00,00,00,00,00,00,00,\
00,60,61,02,00,05,00,00,00,00,01,00,00,00,90,8b,02,00,06,00,00,00,00,01,00,\
00,00,98,ab,02,00,07,00,00,00,00,01,00,00,00,00,03,60,ea,00,00,00,dc,4a,01,\
00,00,90,5f,01,00,00,00,08,28,6e,00,00,00,2c,c9,00,00,01,f8,0b,01,00,02,80,\
38,01,00,03,90,5f,01,00,04,f4,91,01,00,05,d0,b0,01,00,06,c0,d4,01,00,07,00,\
08,6c,39,00,00,00,24,5e,00,00,01,fc,85,00,00,02,ac,bc,00,00,03,34,d0,00,00,\
04,68,6e,01,00,05,08,97,01,00,06,ec,a3,01,00,07,00,01,68,3c,01,00,00,01,04,\
3c,41,00,00,00,00,00,50,c3,00,00,00,00,00,80,38,01,00,01,00,00,24,71,01,00,\
02,00,00,01,08,00,98,85,00,00,78,b4,00,00,60,ea,00,00,50,c3,00,00,01,78,ff,\
00,00,40,19,01,00,b4,27,01,00,50,c3,00,00,02,80,38,01,00,dc,4a,01,00,dc,4a,\
01,00,50,c3,00,00,03,dc,4a,01,00,90,5f,01,00,90,5f,01,00,50,c3,00,00,04,90,\
5f,01,00,00,77,01,00,90,5f,01,00,50,c3,00,00,05,00,77,01,00,90,91,01,00,90,\
5f,01,00,50,c3,00,00,06,6c,b0,01,00,6c,b0,01,00,00,77,01,00,50,c3,00,00,07,\
c0,d4,01,00,c0,d4,01,00,90,91,01,00,50,c3,00,00,01,18,00,00,00,00,00,00,00,\
0b,e4,12,dc,05,fc,08,41,00,0f,00,54,03,90,01,90,01,90,01,90,01,90,01,90,01,\
90,01,00,00,00,00,00,02,04,21,07,08,01,08,01,08,01,2c,01,00,00,4a,00,69,00,\
4a,00,4a,00,5f,00,73,00,73,00,64,00,40,00,90,92,97,60,96,00,90,46,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,02,02,d4,30,00,00,02,10,60,ea,00,\
00,02,10
What exactly does this mean?
By changing the marked values. Stock 6C,B0,01 = 110700
So if you want 1200mhz for example you need to exchange it with C0,D4,01
from here: http://www.overclock.net/t/1633446/preliminary-view-of-amd-vega-bios/570#post_26408383
By changing the marked values. Stock 6C,B0,01 = 110700
So if you want 1200mhz for example you need to exchange it with C0,D4,01
from here: http://www.overclock.net/t/1633446/preliminary-view-of-amd-vega-bios/570#post_26408383
I don't know what I am doing wrong. I cannot break 1400 H/s no matter what settings i use.
All I can say is I followed that guide to the letter and with 4 vega they run at 1950. I didn't try anything extra, like flashing the bios. I would start over and see if you can get 4 running at 1950 doing exactly what that guide says. Otherwise you have no control as to base you experimenting off of.
I figured it might be an issue with the cards so I did the whole disable/enable in device manager and now I have a card that whenever I do that it comes back up with error 43. I also have a card that whenever i reenable it the whole system crashes....
Man alive you're just not having great luck here....
I would format and reinstall. And follow that blogspot guide exactly. Don't install any other software device type software. Just AMD, and only the first option. The driver.
Maybe hold off on flashing the BIOS too. I didn't do that and 1950h/s is pretty good for just adjusting settings in Overdrive and Reg edit.
Also, maybe just start with 4 vega. I started with three. Got it working, then added in a fourth. It just required running the AMD driver install again, and then doing the reg fix for that fourth card. So if you get 4 working at 1950h/s then you can add the other two.
Can you do it all via on board graphics too? I think that makes things easier. If they crash you don't lose your display.
Any one share best timing straps for sapphire for eth mining.
for ETH mining, I followed these instructions to setup the cards https://vegamining.blogspot.com, than in GPU-Z changed the GPU= P7 1222/900 and the Memory= P3 1100/850 (the rest didn't touch), I get stable 44.xxx Mh/s per cards, and 08750 V VDDC volting...
What is your power draw at the wall for achieving 44 Mh/s on ETH?
This is my setup.
I run my monitor via the onboard Intergrated Graphics dvi port. I made the adjustments in the mobo BIOS to route everything to integrated - it showed up in two places. This way one of the vegas doesn't have to do dual duty.
Install windows. Disable all the "sleep and monitor dimming" settings.
Install AMD blockchain drivers. I installed the driver only. Unchecked everything else.
I did NOT flash my 56 to 64, still not sure if that is going to do much.
Did the reg-fix to all 4 cards.
Reboot.
On boot, disable all vegas. Then re-enable all vegas.
Run the script to apply the Overdrive settings. Fans kick in to 3000 rpms.
Run the miner (make sure you've updated the config for the miner so it can access dual mining on each vega). All four vegas running at 1950 h/s and about 150-170W. I haven't tried to adjust the mV to lower that draw.
I tried to install GPUz and HWinfo but I think that caused problems so uninstalled them. I do leave HWMonitor running on screen.
If I run into issues (like after I installed GPUz) I simply reinstall the AMD Blockchain drivers (drivers only again). Shut down. Power up and repeat the disable/enable -> overdrive script. I disable and re-enable the vegas on every boot up. I haven't had to reinstall windows yet - simply the AMD drivers. I think not having that crappy Wattman tool on the computer is half the battle.
I run my monitor via the onboard Intergrated Graphics dvi port. I made the adjustments in the mobo BIOS to route everything to integrated - it showed up in two places. This way one of the vegas doesn't have to do dual duty.
Install windows. Disable all the "sleep and monitor dimming" settings.
Install AMD blockchain drivers. I installed the driver only. Unchecked everything else.
I did NOT flash my 56 to 64, still not sure if that is going to do much.
Did the reg-fix to all 4 cards.
Reboot.
On boot, disable all vegas. Then re-enable all vegas.
Run the script to apply the Overdrive settings. Fans kick in to 3000 rpms.
Run the miner (make sure you've updated the config for the miner so it can access dual mining on each vega). All four vegas running at 1950 h/s and about 150-170W. I haven't tried to adjust the mV to lower that draw.
I tried to install GPUz and HWinfo but I think that caused problems so uninstalled them. I do leave HWMonitor running on screen.
If I run into issues (like after I installed GPUz) I simply reinstall the AMD Blockchain drivers (drivers only again). Shut down. Power up and repeat the disable/enable -> overdrive script. I disable and re-enable the vegas on every boot up. I haven't had to reinstall windows yet - simply the AMD drivers. I think not having that crappy Wattman tool on the computer is half the battle.