Quote from: PhoenixMiner on September 09, 2018, 03:16:19 PM

Quote from: borox on September 08, 2018, 04:23:02 PM

v3.5a detects all devices but then ends with error

Code:

Phoenix Miner 3.5a Windows/msvc - Release build
-----------------------------------------------

Available GPUs for mining:
GPU1: GeForce GTX 1070 (pcie 2), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU2: GeForce GTX 1070 (pcie 3), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU3: GeForce GTX 1070 (pcie 5), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU4: GeForce GTX 1070 (pcie 7), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU5: GeForce GTX 1070 (pcie 8), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU6: GeForce GTX 1070 (pcie 9), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
FATAL ERROR: Debugger detected

Please try the new 3.5b version, which should fix the problem. Here is how to download and verify it: https://bitcointalk.org/index.php?topic=2647654.msg45442768#msg45442768

Quote from: simcity4 on September 08, 2018, 05:21:13 PM

don't work
old 3.0c work

Code:

1970.01.04:05:04:49.399: unkn OpenCL driver version: 17.31.0
2018.09.08:20:15:21.223: main Phoenix Miner 3.5a Windows/msvc - Release build
2018.09.08:20:15:21.223: main Cmd line: -amd -coin clo -pool stratum+tcp://moac.bylt.gq:5005 -wal mywalletxxxxxx -worker amd -pass x -log 1 -tstop 70 -cdm 0 -retrydelay 0 -cclock 965 -mclock 1875 -powlim 0 -cvddc 850 -mvddc 900 -clgreen 1
2018.09.08:20:15:21.223: main Available GPUs for mining:
2018.09.08:20:15:21.223: main GPU1: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
2018.09.08:20:15:21.265: main ADL library initialized

please add moac coin

Do you have only one GPU? Is the miner just freezes, or crashes? Please try the new 3.5b version, which may fix the problem. Here is how to download and verify it: https://bitcointalk.org/index.php?topic=2647654.msg45442768#msg45442768

Quote from: byrd1083 on September 08, 2018, 11:07:03 PM

Using 3.5a and can not get it to work. I have Gigabyte Vega56 oc gaming with regmod Burnsted editor.

Everytime I launch it connects fine, acts like it is mining but hash rate is 0 then crashes after a while. I can run stable on Fireice currently 1900 h/s. Do you have any recommendations to get stable in Phoenix or even to get any hash rate at all?

It's possible that your OC settings are not stable for ETH mining. Vega is notoriously power hungry, so we suggest to start with fairly low core clocks (around or under 1000 Mhz) and power limit -10% or even less. If the problem persists, you can try he new 3.5b version, which may fix the problem. Here is how to download and verify it: https://bitcointalk.org/index.php?topic=2647654.msg45442768#msg45442768. If nothing else helps, please send the log from the beginning to see if the DAG is constructed properly, etc.

Quote from: 53nsk on September 09, 2018, 03:06:03 AM

3.5a won't start at all, 3.0c working perfectly since release

Please try the new 3.5b version, which may fix the problem. Here is how to download and verify it: https://bitcointalk.org/index.php?topic=2647654.msg45442768#msg45442768. If this doesn't help, please send us the log file to see what exactly goes wrong.

Quote from: Marvell2 on September 09, 2018, 09:00:10 AM

anyone seen this error ? happens right when i launch, happens even after a fresh install wtf ?

Code:

Faulting application name: PhoenixMiner.exe, version: 0.0.0.0, time stamp: 0x5b12b632
Faulting module name: igdrclneo64.dll, version: 0.0.0.0, time stamp: 0x5a96b19b
Exception code: 0xc0000005
Fault offset: 0x0000000000030819
Faulting process id: 0x12e0
Faulting application start time: 0x01d4481ab1bcf677
Faulting application path: C:\Latest PhoenixMiner\PhoenixMiner.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_250db833a1cd577e\igdrclneo64.dll
Report Id: 032ad2c0-acc2-4048-b285-f7afb3049b2e
Faulting package full name:

Please try the new 3.5b version, which should fix the problem. Here is how to download and verify it: https://bitcointalk.org/index.php?topic=2647654.msg45442768#msg45442768. If this doesn't help, please send us the log file to see when the error occurs, which may gives us a clue what is causing it.

Quote from: Soliqesh on September 09, 2018, 02:34:59 PM

https://imgur.com/a/kTCssZG its normal?? Thats -clgreen 1

Yes, the optimal GT values for the green kernels are completely different from the other kernels (just as the GT values for -clkernel 1 and -clkernel 2 are usually also quite different from each other). So, you are doing the right thing letting auto-tune to find them. Also, please note that even if all GPUs are the same model, there are always differences and not every time the optimal GT values are the same.

Quote from: TAGTRAUM on September 09, 2018, 12:17:32 PM

3.5 working fine with 14 GPU rig (nvidia), no difference in hashrate, same stable as 3.0

Quote from: deadsix on September 09, 2018, 08:51:14 AM

I finally gave it a try now that profitability has tanked and I was shutting my farm down.
Good miner, similar to Claymore, easy to setup and use and lots of information displayed.

Works well on my AMD Rx 570's, with maximum tweaking I am getting about 0.2 mh per care more with Phoenix and consuming 4W power less compared to claymores.
Also this miner has a lower devfee, so theres three title advantages in all - 1% extra hash rate, 4% lower power, and 0.35% lower fee.
If I ever boot up my farm again, I would use this miner going forward. Also appreciate the regular updates to it, which hasn't been the case for claymores.

Good news!

Almost every message after releasing new version is about problems (which is quite normal and alright), so it's quite nice to get a few positive reports. Don't hesitate to write us with any ideas for improvements, etc.

ok ill try the new version