Pages:
Author

Topic: [Cast XMR] high speed XMR/CryptoNight miner for RX Vega GPUs (2 KHash/s) - page 8. (Read 206424 times)

member
Activity: 146
Merit: 10
So, after 5 hours found out what caused stalling at this point:
Initializing GPU, loading kernel ...

It was intergrated graphics driver. After removing old drivers with DDU xmr stak was searching integrated graphics instead opencl.
Two ways to solve it:
a) disable intergrated graphics

b) dont use DDU, just install new drivers in top of old ones. After install it gives error. Restart. Make powerplay in registry. Restart. Renew OverdriveNTool and atiadlxx.dll and atiadlxy.dll under Windows\SysWOW64
Disable enable cards and it starts mining again.



Followed this post.

Also needed to follow this post for OverdriveNtool, otherwise it wont work:

Do you have atiadlxx.dll or atiadlxy.dll in C:\Windows\SysWOW64 directory? If not, unpack driver package and copy atiadlxy.dll into C:\Windows\SysWOW64 Rename it to atiadlxx.dll and copy atiadlxy.dll again so you will have 2 identical files atiadlxx.dll and atiadlxy.dll.

And grande finale:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  Cast XMR 1.5.0 CryptoNight mining optimized for AMD Radeon Vega GPUs

  Coded by [glph3k] for more info visit http://www.gandalph3000.com
  Donating 1.5% mining power to developer. Thanks.

  For current stats press 's'
  For seamless exit press 'q'

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[14:35:55] Initializing GPU, loading kernel ...

And this way it stays.. mining wont start.
Somebody else with problem like that?


Same with SRBMiner:
Initializing OpenCL devices, please wait..





Hello dear mates, I hope this shoots some light to people stuck with this hardfork or people without wanting to use SoftPowerPlayTables

I installed CastXMR v1.5.0 using same drivers 18.4.1 as when using CastXMR 1.4, the day before the hardfork hashing OK
Now the day after hardfork each vega 56 is hashing 800h/s.

Solution to fix it
1) Uninstalled Adrenalin Drivers v18.4.1 using DDU 18.0.0.2, restart
2) Installed Adrenalin Drivers v18.5.1, restart

After these two steps, overclocks/undervolt are not taking place using OverdriveNtool v0.2.6  applying one dummy overclock first, then applying desired overclock second as used to be working for me with CastXMR v1.4. After some digging, I found that applying Ati patcher was the solution to fix my setup.  After all this i'm hashing 7% slower than before.

My setup working with overclock and undervolt no need for SoftPowerPlayTables is the following:
don't know if you can get the best undervolt/overclock using this method or using SoftPowerPlayTables, but works fine for me
-CastXMR v1.5.0
-Adrenalin Drivers v18.5.1 settings by default (HBCC comes off by default as well as crossfire is off by default even having more than 1 gpu)
-Apply AtiPixelClockPatcher v1.4.6 (https://www.monitortests.com/forum/Thread-AMD-ATI-Pixel-Clock-Patcher)
-OverdriveNTool v2.7 beta 4 (http://www.dropbox.com/s/equ297p3otqu28n/OverdriveNTool 0.2.7beta4.7z?dl=1)
-Added a small tweak to the script so I apply one dummy overclock using OverdriveNTool.exe, then apply another overclock which is the desired. The first overclock is to make the second overclock happen, just a trick Wink. If you want to test different overclocks you need to restart to make it work or maybe disable and enable your cards
-Watchdog script: HashMonitor.ps1 (https://github.com/fiddlefingers/Fiddlefingers-cast_xmr-hashrate-monitor-and-restart-tool/blob/master/HashMonitor.ps1)


Cheers
newbie
Activity: 6
Merit: 0
Hi every one, i got around 20% power consumption increase in v8 compare to v7 and it leads to higher fan speed and hbm temp...
Is it normal?!
jr. member
Activity: 73
Merit: 2
I got another computer working. Did a clean install and just installed amd drivers 18.5.1 and cast 1.5. Left windows without updating and everything is running good. A bit slower a more power hungry but its working. The version of windows im using is 1609. I don't know why but some of my motherboards have always been sensitive to windows revisions. Next i just want to get those numbers up while keeping power the same of less if possible.
newbie
Activity: 164
Merit: 0


hi dev , thanks for your hard work . 
last update i mange to run 4 vega cards with no problem  . (-G 0,1,2,3)
but the miner stuck if i add 5th card (-G 0,1,2,3,4) .


any reason why is this happens ! 

newbie
Activity: 8
Merit: 0
Does anyone know if Vega  FE is supported with 1.5.0 miner?  I don't see any hashrate data for it on http://www.gandalph3000.com/.

copper member
Activity: 97
Merit: 0


I made this interface for your JSON data. Do you like it?

It's beautiful Wink

Updated and possible final version of the web interface Cheesy


Don't know why the image is not showing a preview, you can click the link to see it
jr. member
Activity: 80
Merit: 1
I'm using Cast XMR 1.5 with 18.5.1 drivers with Vega FE, mining CryptoNight Heavy on NiceHash.

After the 7th GPU (so 8th GPU) on the same mother board with intensity set to 9 for all I get the following errors.

Error CL_MEM_OBJECT_ALLOCATION_FAILURE calling clEnqueueNDRangeKernel for kernel 0

If I change intensity to 1 on 8th GPU I get the same error.  I've tried this on multiple rigs and different AMD drivers but results are the same only 7 GPUs are max.

You need to increase your pagefile size(Virtual Memory) in Windows. Need to set it to at least 70GB based on the number of Vega GPUs that you have.
newbie
Activity: 46
Merit: 0
copper member
Activity: 97
Merit: 0


I made this interface for your JSON data. Do you like it?
newbie
Activity: 8
Merit: 0
I'm using Cast XMR 1.5 with 18.5.1 drivers with Vega FE, mining CryptoNight Heavy on NiceHash.

After the 7th GPU (so 8th GPU) on the same mother board with intensity set to 9 for all I get the following errors.

Error CL_MEM_OBJECT_ALLOCATION_FAILURE calling clEnqueueNDRangeKernel for kernel 0

If I change intensity to 1 on 8th GPU I get the same error.  I've tried this on multiple rigs and different AMD drivers but results are the same only 7 GPUs are max.
newbie
Activity: 2
Merit: 0
Mine has been locking up at this point...even removed the vega 56's from the bat file...
https://imgur.com/Pk4oWGm
member
Activity: 357
Merit: 26
Restored to blockchain drivers.
Managed to get pp tables and everything working in short order to restore things as they were. So, I haven't lost my touch yet. It's AMD who sucks... lol

Switching to ETH for now.
Enjoy my absence of hash power !


I might have to do that. two rigs now misbehaving, hashrate drops every hour or so, still missing two cards on one. Complete mess. Those beta blockchain drivers were at least stable.
newbie
Activity: 62
Merit: 0
So i switched to SRBminer the hashrate are uncompareable with cast xmr it was nice time i was mining with cast xmr since it started but it cant be best 4ever  cya '' thx for great mining  software
jr. member
Activity: 58
Merit: 4
Restored to blockchain drivers.
Managed to get pp tables and everything working in short order to restore things as they were. So, I haven't lost my touch yet. It's AMD who sucks... lol

Switching to ETH for now.
Enjoy my absence of hash power !
jr. member
Activity: 58
Merit: 4
Pffft
Just as anticipated. I upgraded from blockchain driver (or should I say downgraded) to 18.5.1

Hashrate went down compared to before and power consumption went up by 60%. Powerplay settings or voltage control obviously has no effect.
My server PSUs started to sound like F16:s spooling up and the Vegas ran the fans at full speed to keep up with this crap.

Every time, I reboot, the system behaves differently. Device ID:s not recognized, Cast locks up immediately, shares not accepted, the entire system typically crashes after 3 minutes and auto reboots.

Seems this driver is completely unstable. Tried switching to mining ETH instead. Computer crashes during DAG file creation.
AMD never ceases to produce useless software.

Anyone want to buy a bunch of Vegas?
member
Activity: 146
Merit: 10
Followed this post.

Also needed to follow this post for OverdriveNtool, otherwise it wont work:

Do you have atiadlxx.dll or atiadlxy.dll in C:\Windows\SysWOW64 directory? If not, unpack driver package and copy atiadlxy.dll into C:\Windows\SysWOW64 Rename it to atiadlxx.dll and copy atiadlxy.dll again so you will have 2 identical files atiadlxx.dll and atiadlxy.dll.

And grande finale:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  Cast XMR 1.5.0 CryptoNight mining optimized for AMD Radeon Vega GPUs

  Coded by [glph3k] for more info visit http://www.gandalph3000.com
  Donating 1.5% mining power to developer. Thanks.

  For current stats press 's'
  For seamless exit press 'q'

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[14:35:55] Initializing GPU, loading kernel ...

And this way it stays.. mining wont start.
Somebody else with problem like that?


Same with SRBMiner:
Initializing OpenCL devices, please wait..





Hello dear mates, I hope this shoots some light to people stuck with this hardfork or people without wanting to use SoftPowerPlayTables

I installed CastXMR v1.5.0 using same drivers 18.4.1 as when using CastXMR 1.4, the day before the hardfork hashing OK
Now the day after hardfork each vega 56 is hashing 800h/s.

Solution to fix it
1) Uninstalled Adrenalin Drivers v18.4.1 using DDU 18.0.0.2, restart
2) Installed Adrenalin Drivers v18.5.1, restart

After these two steps, overclocks/undervolt are not taking place using OverdriveNtool v0.2.6  applying one dummy overclock first, then applying desired overclock second as used to be working for me with CastXMR v1.4. After some digging, I found that applying Ati patcher was the solution to fix my setup.  After all this i'm hashing 7% slower than before.

My setup working with overclock and undervolt no need for SoftPowerPlayTables is the following:
don't know if you can get the best undervolt/overclock using this method or using SoftPowerPlayTables, but works fine for me
-CastXMR v1.5.0
-Adrenalin Drivers v18.5.1 settings by default (HBCC comes off by default as well as crossfire is off by default even having more than 1 gpu)
-Apply AtiPixelClockPatcher v1.4.6 (https://www.monitortests.com/forum/Thread-AMD-ATI-Pixel-Clock-Patcher)
-OverdriveNTool v2.7 beta 4 (http://www.dropbox.com/s/equ297p3otqu28n/OverdriveNTool 0.2.7beta4.7z?dl=1)
-Added a small tweak to the script so I apply one dummy overclock using OverdriveNTool.exe, then apply another overclock which is the desired. The first overclock is to make the second overclock happen, just a trick Wink. If you want to test different overclocks you need to restart to make it work or maybe disable and enable your cards
-Watchdog script: HashMonitor.ps1 (https://github.com/fiddlefingers/Fiddlefingers-cast_xmr-hashrate-monitor-and-restart-tool/blob/master/HashMonitor.ps1)


Cheers
newbie
Activity: 5
Merit: 0
Hey Guys,
I managed to process through the network upgrade flawlessly.
After the initial block, I stopped mining CryptoNightV7 and ran an updated bat file.
I use NiceHash and the only thing I needed to do was to change a server address and port.

Overall my hashrate dropped around 5% and power consumption increased up to 25W more for a single card (8% increase).

Adrenalin Driver 18.10.1
HBCC Off
Cast XMR 1.5.0


I'm kinda same
Adrenalin Driver 18.7.1 (not planning to update until i know is stable)
Using soft power tables(not sure if it really helps)
Cast XMR 1.5.0  (algo 10)
HBCC - have no idea, same as it was for V7, didn't touch it for this fork
power: 4 x vega64 liquid cooled ~860W (was 740W on V7)
Hashrate: 7610H/s (was ~7900H/s on V7)


I got the similar hashs but more power (6 card for 1050w on V7 and 1250w on V8), don't know what happens 
member
Activity: 357
Merit: 26
Hashrate on cnv8 has cratered. Vega 64s/blockchain drivers/HBCC enabled. intensity 7. hashing at under 1k...

This is a known problem with the blockchain drivers. Update to 18.5.1, they are more stable and don't need the hardware reset trick and will fix performance with V8. HBCC should be turned off. Vega64 can go with intensity 9 if used headless (no desktop running on it),


Hmmm. That seems to have worked for all but two of the gpus, which are still hashing in the low hundreds. I did DDU, and device manager says all vegas are using hte same driver...

Like a bad nightmare, 'disable crossfire, disable upls' has floated into my head... Which hasn't worked. Bastard Vegas.

Anybody else having a similar issue? 5card vega rig, updated drivers, 3 cards running as standard, 2 running at 120 and 300h/s. DDUed several times, crossfire etc disabled, HBCC on or off makes no difference. intensity set to 7... Arrrgh.


The solution is to run a dummy plug.  When I have a monitor plugged in I have the exact same issue.  Put in an hdmi dummy plug. reboot, and its back to normal

Fraid not, I run with a dummy plug as standard. Is this a known issue with 18.5.1? Someone else must have experienced this. Overdrive seems to be working, as both the low-hashing cards have fans set high. It's like some invisible crossfire setting...grrrrr...
newbie
Activity: 5
Merit: 0
will they take a solution to re-mine with the h/s before or will we be screwed with this change they made forever? they would have left it as it was before
newbie
Activity: 20
Merit: 1
How much of h/s do you get with that trick Germini?

It depends of the lottery silicon, gpu and overclock/undevolt. I am getting average 1800h/s for vegas 56

I hope it helps, I didn't like to use soft power tables not very convenient if want to change something even though overdriventool can modify reg files easily

cheers
Pages:
Jump to: