Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 5.6d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
by
kengriffin
on 27/02/2025, 13:50:34 UTC
Hi there,

I got a strange problem, not sure if anyone here can help.

I only mine during an off-peak time, appex 12hrs a day so I use windows 10 task scheduler set up the timers ex: when to start the miner and when to close. However, I note that when the miner is started by the task scheduler, the hashrate is lower (around 293mhs) than I check the miner shortcuts on my desktop myself (around 300mhs). I'm pretty sure that they are running the same file. I know it's odd, but when I close the miner which was started by the task scheduler and open it again via desktop shortcuts, I got a normal hashrate. So pretty sure, it's something to do with the task scheduler, but not sure where to start. I tried to set the task with high privilege, but still the same. ANy suggest??



It sounds like the way Task Scheduler is launching the miner is affecting its performance. Here are a few things to check and try:

1. Check the “Start In” Path
   •   In Task Scheduler, ensure that the “Start in (optional)” field is set to the miner’s working directory.
   •   If this is missing, the miner might be launching in a different context, leading to lower performance.
2. Use “cmd.exe” to Launch
   •   Instead of launching the miner directly, use cmd.exe and pass the miner’s executable as an argument:
cmd /c start /b miner.exe --your-arguments
   •   This ensures the miner is executed in the same environment as when launched manually.
3. Set CPU Priority to High
   •   If the miner benefits from higher CPU priority, modify your Task Scheduler action: (can read more here https://www.quantvps.com/blog)
cmd /c start /high miner.exe --your-arguments
4. Check Power Settings
   •   Windows might be running in a different power mode when Task Scheduler launches it.
   •   Go to Control Panel > Power Options and ensure it is set to High Performance.
5. Use “Run only when user is logged in”
   •   If set to “Run whether user is logged on or not,” the task might be running in a different session with limited performance.