WildRig Multi 0.44.0
- improved qhash for AMD RDNA1, RDNA2 and RDNA3 architectures
- significantly improved qhash for NVIDIA Ampere and older architectures
- fixed low hashrate on CMP 170HX for qhash(use parameter --qhash-kernel 2)
- up to 20% improvements for NVIDIA Ada Lovelace and Blackwell
- CPU usage decreased again
problem on windows... Error CL_MEM_OBJECT_ALLOCATION_FAILURE when initialize DAG this error means not enough memory to initialize DAG. Also it can be low Virtual Memory on Windows, so increase it. i try increase .. no effect ( [21:30:27] kernel 1 compiled for sm86 [21:30:27] Error CL_MEM_OBJECT_ALLOCATION_FAILURE when initialize DAG [21:30:29] kernel 1 compiled for sm86 [21:30:30] Error CL_MEM_OBJECT_ALLOCATION_FAILURE when initialize DAG [21:30:32] Error CL_MEM_OBJECT_ALLOCATION_FAILURE when calling clEnqueueNDRangeKernel for kernel 'search' [21:30:33] Error CL_MEM_OBJECT_ALLOCATION_FAILURE when calling clEnqueueNDRangeKernel for kernel 'search' [21:30:35] Error CL_MEM_OBJECT_ALLOCATION_FAILURE when calling clEnqueueNDRangeKernel for kernel 'search' [21:30:36] Error CL_MEM_OBJECT_ALLOCATION_FAILURE when calling clEnqueueNDRangeKernel for kernel 'search' [21:30:37] Error CL_MEM_OBJECT_ALLOCATION_FAILURE when calling clEnqueueNDRangeKernel for kernel 'search' what coin is that? And exact cards |
|
|
|
WildRig Multi 0.44.0
- improved qhash for AMD RDNA1, RDNA2 and RDNA3 architectures
- significantly improved qhash for NVIDIA Ampere and older architectures
- fixed low hashrate on CMP 170HX for qhash(use parameter --qhash-kernel 2)
- up to 20% improvements for NVIDIA Ada Lovelace and Blackwell
- CPU usage decreased again
problem on windows... Error CL_MEM_OBJECT_ALLOCATION_FAILURE when initialize DAG this error means not enough memory to initialize DAG. Also it can be low Virtual Memory on Windows, so increase it. |
|
|
|
|
WildRig Multi 0.44.0
- improved qhash for AMD RDNA1, RDNA2 and RDNA3 architectures
- significantly improved qhash for NVIDIA Ampere and older architectures
- fixed low hashrate on CMP 170HX for qhash(use parameter --qhash-kernel 2)
- up to 20% improvements for NVIDIA Ada Lovelace and Blackwell
- CPU usage decreased again
|
|
|
|
WildRig Multi 0.43.8
- improved qhash for AMD, Intel and NVIDA(4000/5000 series only)
- improved auto-tune for qhash and added parameter --qhash-blocks
NOTE:
- on weak gpu's auto-tuning may take few minutes
- CPU load can be still high for NVIDIA gpu's
Hello,agaib qhash high cpu usage and worse perf. on windows 10 nvidia gpus.. Unfortunately nothing can be done with current implementation, maybe in 0.44.0 I will fix the issue |
|
|
|
|
WildRig Multi 0.43.8
- improved qhash for AMD, Intel and NVIDA(4000/5000 series only)
- improved auto-tune for qhash and added parameter --qhash-blocks
NOTE:
- on weak gpu's auto-tuning may take few minutes
- CPU load can be still high for NVIDIA gpu's
|
|
|
|
|
WildRig Multi 0.43.7
- improved qhash on different gpu's
- reduced CPU usage for qhash
|
|
|
|
|
WildRig Multi 0.43.4
- implemented qhash(5% dev-fee)
|
|
|
|
|
WildRig Multi 0.43.2
- a lot of old algorithms are zero fee now
- implemented evohash(0% dev-fee)
|
|
|
|
Hello , clc mining windows 10 rx5700 with 0.43.0 , [00:06:52] Intel(R) HD Graphics 610 is unsupported... skip
[00:06:55] Initializing GPUs...
[00:06:55] GPU #0: AMD Radeon RX 5700 [busID: 3] [arch: gfx1010] [driver: 3380]
[00:06:55] threads: 1, intensity: 22, cu: 36, mem: 8176Mb
[00:06:56] GPU #1: AMD Radeon RX 5700 [busID: 6] [arch: gfx1010] [driver: 3380]
[00:06:56] threads: 1, intensity: 22, cu: 36, mem: 8176Mb
[00:06:56] GPU #2: AMD Radeon RX 5700 [busID: 9] [arch: gfx1010] [driver: 3380]
[00:06:56] threads: 1, intensity: 22, cu: 36, mem: 8176Mb
[00:06:57] GPU #3: AMD Radeon RX 5700 XT [busID: 12] [arch: gfx1010] [driver: 3380]
[00:06:57] threads: 1, intensity: 22, cu: 40, mem: 8176Mb
[00:06:58] GPU #4: AMD Radeon RX 5700 [busID: 15] [arch: gfx1010] [driver: 3380]
[00:06:58] threads: 1, intensity: 22, cu: 36, mem: 8176Mb
[00:06:58] GPU #5: AMD Radeon RX 5700 [busID: 18] [arch: gfx1010] [driver: 3380]
[00:06:58] threads: 1, intensity: 22, cu: 36, mem: 8176Mb
[00:06:59] GPU #6: AMD Radeon RX 5700 [busID: 21] [arch: gfx1010] [driver: 3380]
[00:06:59] threads: 1, intensity: 22, cu: 36, mem: 8176Mb
[00:06:59] GPU #7: AMD Radeon RX 5700 [busID: 25] [arch: gfx1010] [driver: 3380]
[00:06:59] threads: 1, intensity: 22, cu: 36, mem: 8176Mb
[00:07:00] Failed to start OpenCL threads
Custom command here Increase pagefile size, it should be something like 80Gb minimum in your case |
|
|
|
|
WildRig Multi 0.42.5
- improved progpow family algorithms on AMD gpu's
|
|
|
|
|
WildRig Multi 0.42.4
- implemented support of AMD RDNA4(RX 9000 Series)
|
|
|
|
|
WildRig Multi 0.42.1
- updated progpow-quai to support mainnet for Quai
- some progpow related fixes
|
|
|
|
|
WildRig Multi 0.42.0
- initial support NVIDIA Blackwell
|
|
|
|
|
WildRig Multi 0.41.6
- fixed support Intel Arc Battlemage gpu's
|
|
|
|
|
WildRig Multi 0.41.4
- fixed crash on big nvidia rigs(8+ gpu's) for progpow family algorithms
- implemented initial support of Intel Arc Battlemage gpu's
|
|
|
|
|
WildRig Multi 0.41.0
- implemented algorithm phihash
- fixed dev-fee for algorithm memehash
|
|
|
|
As far as I can see, WildRig Multi supports sha256 and sha256d algorithms. Does this mean that I can mine Bitcoin with GPU with WildRig Multi ?
And what is fee on this algorithms
Note : (I know what I'm doing)
yes, it can. Fee is 0.75% |
|
|
|
|
WildRig Multi 0.40.9
- returned back progpow-quai(0.75% dev-fee, testnet phase, tested with luckypool only)
|
|
|
|
|
WildRig Multi 0.40.8
- better Intel gpu's support
- implemented algorithm x7
- implemented algorithm meowpow(0.75% dev-fee)
- implemented algorithm progpow-telestai(0.75% dev-fee)
|
|
|
|
Will you readd progpow for quai back again? Would be really nice as they dont have another windows miner.
Developers of that coin have no interest in 3rd party miners, and they see "intensive marketing" everywhere(as I was told), so I have no plans to communicate with them anymore and do anything  But when public pools arrive, maybe I will implement it again. |
|
|
|
|
Show Posts
