Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 273. (Read 784965 times)

Windows Defender and all other similar programs  act and behave like a b***h ... today she loves you - tomorrow she calls you Trojan!
Just add it to exception!!

It will make you easy (lower fan speed %) to keep the temperature bellow 45 degree and this may indirectly reduce the memory temperature.

Hi there,

I've been running 5e for a couple of days, but just today, Windows Defender is saying it's detected a Trojan:

Trojan:Win32/Bomitag.D!ml
E:\PhoenixMiner_5.0e_Windows\PhoenixMiner.exe

Any comments?

I use Radeon Software Crimson ReLive Edition Beta for Blockchain Compute Driver for Windows® 10 64-bit, Windows 10 Pro x64, and Version PhoenixMiner 5.0e

solve trouble with pool switch crashing. old bat file option -retrydelay 1 bad. change to -retrydelay 10 all ok

Thank you very much for answering but I don't think that's the problem, because the temperature of my GPUs is between 45 and 55 degrees all day.

What temperature should the memory have to avoid having blocking problems with a higher OC? I didn't know that reducing the core clock would lower the memory temperature, is this true?

If you want to be stable after overclock you should raise the voltage and/or lower the target temperature. As the voltage of memory could not be change for 5700XT your only chance is to lower the target temperature -tt which will indirectly reduce the memory temperature. You can aslo lower -cclock and -cvddc in order to reduce the temperature of the memory indirectly too.

Could you help me with this? I watch a lot of videos in information about the 5700XT, with Hashrate of 56/57 MHS ...

I have managed to reach that speed by modifying the timings of the BIOS, but the RIG crashes, I can only keep it stable around 54.5Mhs, if I upload OC from memory to get more speed, it hangs in a few minutes or in several hours.

Is there a way to make the 5700XT stable with 56MHS and the Rig not crash?

   We only can detect a part of stale shares - these that are discovered after we have received a new job. However, due to the delay in the pool itself and the network latency, most stale shares can not be discovered at miner level. So we send these shares and nicehash rejects them. We could take into account when the job last changed and if a share is rejected soon after a job has changed we can count it as stale instead of rejected but this won't be 100% reliable. However the bigger problem is that nicehash really doesn't count the stale shares at all unlike other pool that give reduced reward for stale shares, so it won't be correct to count them as stale in the statistics - you won't get any reward from them anyway.



  Yes, make two different bat files and run them both. You will have two console windows, it's not possible to combine them as they are independent from each other. One thing to be aware of, if you are using remote control port, is to change the port number in one of the bat files to something else than the default port with this command-line argument: -cdmport 3334 (this will change the remote control port to 3334, the default is 3333).




   An obvious question but are you running PhoenixMiner 5.0e? If so, please send us a log to check for any problems in it.



  Please tell us the driver version and the Windows version, and the version of PhoenixMiner that you are running. Also, the log from the start would help much more than just the last several lines.

why did my miner stop when I started to DAG # 352? and doesn't reboot by itself,

2020.06.11:05:45:24.320: GPU5 GPU5: Starting up... (0)
2020.06.11:05:45:24.320: GPU5 GPU5: Generating ethash light cache for epoch #352
2020.06.11:05:45:24.342: GPU3 GPU3: Starting up... (0)
2020.06.11:05:45:24.398: GPU6 GPU6: Starting up... (0)
2020.06.11:05:45:24.444: GPU2 GPU2: Starting up... (0)
2020.06.11:05:45:24.559: GPU4 GPU4: Starting up... (0)
2020.06.11:05:45:24.604: GPU1 GPU1: Starting up... (0)
2020.06.11:05:45:27.189: main Eth speed: 0.000 MH/s, shares: 5/0/0, time: 0:02
2020.06.11:05:45:27.189: main GPUs: 1: 0.000 MH/s (1) 2: 0.000 MH/s (0) 3: 0.000 MH/s (1) 4: 0.000 MH/s (1) 5: 0.000 MH/s (1) 6: 0.000 MH/s (1)
2020.06.11:05:45:28.011: GPU5 Light cache generated in 3.7 s (16.3 MB/s)
2020.06.11:05:45:28.248: GPU3 GPU3: Allocating DAG (3.77) GB; good for epoch up to #354
2020.06.11:05:45:28.280: GPU3 GPU3: Generating DAG for epoch #352
2020.06.11:05:45:28.520: GPU6 GPU6: Allocating DAG (3.77) GB; good for epoch up to #354
2020.06.11:05:45:28.575: GPU6 GPU6: Generating DAG for epoch #352
2020.06.11:05:45:28.814: GPU2 GPU2: Allocating DAG (3.77) GB; good for epoch up to #354
2020.06.11:05:45:28.849: GPU2 GPU2: Generating DAG for epoch #352
2020.06.11:05:45:29.109: GPU4 GPU4: Allocating DAG (3.77) GB; good for epoch up to #354

thank you for your help

I have resolved the problem increasing the virtual memory
Control Panel --> System and Security --> System --> Advanced System Settings --> Performance: Settings --> Advanced --> Virtual Memory: Change --> Custom size: Initial size=64000, Maximum size 64000 --> OK

I am glad

and it is also giving me the error ( Cuda error in cudaprogram.cu :373 out of memory )

Is there a problem with PhoenixMiner 5.e windows 10
I can not mine it continues to shut down
Not as stable as it was to be 

Run notepad as administrator.

If you see "Unknown OpenCL driver version! Hashrate and stale shares may suffer" than clean reinstall your driver. If your virtual memory is less then (GPUS_count + 1) * 4 GB, than increase it.
If you don't have integrated video or 8GB card set as first GPU than exclude first GPU from mining: -gpus 2,3,..., LAST_GPU_INDEX
Run second instance of PM and mine another EtHash algo based coin (Ethereum still possible until epoch 250, after that choose one of these: https://2cryptocalc.com/ethash-algorithm ) with the first GPU, by adding: -gpus 1

Yes with two .bat files. It is not possible to do this with one instance of PM. If you use config.txt: Create one config1.txt for the first instance and one config2.txt for the second instance. In the .bat file for the first instance add/ or replace  -config parameter: ... -config config1.txt ... . In the .bat file for the second instance add/replace  ... -config config2.txt ...

Using PhoenixMiner 5.e windows 10

I can not edit the bat file as usual what is the problem

hello,

I have 2 rigs where the GPU 1 still don't mine ETH :/
and the one which works, have the same problem when I bench epoch 360

W10, latest AMD drivers, 4Go GPU, -eres 0.

Problem is, on the opposite of claymore, phoenix reboot the miner automatically instead of having GPU 1 at 0 hashrate and letting the rest mine.
normallyall my rigs have the same configuration, I don't know why it works better on somme than on other.

Does someone have an idea?
thx

How to make this? With a 2 bat files? I will have 2 miners on the screen or is it possible to make in one?

 more correct way is to switch to another pool / as Phoenix wrote: