Topic: BFGMiner 5.5.0: CPU/GPU/FPGA/ASIC mining software, GBT+Stratum, RPC, Linux/Win64 - page 42. (Read 834507 times)

downloaded 5.1 from another repository, no issues...
 

Windows Defender.

Win 7 basic

not sure I trust anything free from Microstiff...



J

what  Security software are you running  ?


what  windows  10, 8.1, 7. ?.  btw windows 10 is free upgrade if your win 7 sp1 or win 8.1 is legal .


 if your OS is 64 bit use the 64 bit BFGMINER .

When I try to open the 32bit windows version of 5.2, windows deletes the bfgminer.exe. says there is a Trojan in it. Skeeyah.C!plock ...

Is there a clean version available somewhere?

J   

More GPUs = losing money faster...

You can't earn anything by mining with it! You will have to either by a lot of GPUs or buy SHA-256 ASIC miner(s).

hi, i am having computer Intel Inbuilt graphics , how can i start minning with BFGMiner software, please help me out

Honestly, it's just a worthless piece of crap. I'm not buying anything Bitmain puts out without waiting a couple weeks next time.

And an hour after posting that, after more than 2 weeks of this U3 working with comm errors, it has now died and bfg doesn't even see it any more.  God, I hate the U3, why do I keep torturing myself with it? 

Yea, I'm familiar with the random deaths, but this one isn't dying.  It spits out the errors several per second, but not continuously, and it hashes away just fine, but at some point its hash drops from the pool despite bfgminer showing it hashing away just fine.

Nope, never seen comm errors here. Although the U3 does like to randomly die :/

Luke-Jr, any ideas on the comms errors I've reported above?  My U3 seems to be running fine in all other aspects, but it seems the comms errors cause it to drop off the pool I have it pointed to (or the pool boots it off, not sure).  Thank you.

Check that they match my signature, but AVs have indeed been known to flag BFGMiner as a false positive.

I downloaded the Win32.zip version of your file and scanned it with my antivirus software and it said it has 2 high risk threats.  Are these real threats or just my antivirus acting up?

That was the ticket! Thanks!

I went through that once but the second time was the charm. I still get those errors but the system sees the grids now and I am mining. Thanks!

Drivers installed or the right ones and  try

bfgminer.exe --scrypt -S gsd:all -o stratum+tcp://{pool} -u {user} -p {pw} --set gsd:clock=800


Link to those drivers its been a while sense i use BFG or CG  in windows


http://www.st.com/web/en/catalog/tools/PF257938

I only get the comms error on the webisect version of 5.2.0 you posted for me.  I just tried the release of 5.2.0 using --scan antminer@0001 in the command line again and it results in the U3 hashing <10GH/s and dropping to 0 over the course of a minute or two.  So whatever was changed in the websect version also "fixed" it so my U3 hashes consistantly (although it appears to ignore the freq and volt settings and hashes at stock speed ~40GH/s).  Unfortuntelly like I have posted, it spits those comm errors all day and unless I reset it twice a day (unplug/replug USB) then the U3 hash drops from the pool it's pointed at despite appearing to continue to hash along just fine in bfgminer.


I wish I knew enough how to dig in a figure out what the error is caused by, but all I could do was google and nothing useful came up.

I just downloaded BFGminer 5.2.0. I am running it on Windows 8.1 as 64 bit (tried 32 bit too) and am trying to connect to 2 Gridseed blades (4 devices). I have run from a Admin command windows (as well as lesser cmd) and get the following messages:

Do not have user privileges required to open \\.\COM4

It appears 4 times (once for each board) followed by the following error:

Failed to open Device Parameters registry key in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():556: The system cannot find the file specified.

As expected I also get the red status of "NO DEVICED FOUND: Press 'M' and '+' to add" but when I do, I get an empty list (i.e. no devices listed). I was running cgminer but had issues with the Blades all staying mining at the same time so decided to give this a try. I uninstalled the ZAG drivers and installed the STM drivers. My devices shows 4 of these:

Eject STM32 Virtual COM Port

So I think that is right. I have tried different command arguments but am currently running this way:

bfgminer.exe --scrypt -o stratum+tcp://{pool} -u {user} -p {pw} -S all --set-device gridseed:clock=825

I know the pool and user info is good as it works fine (when it does) under cgminer. I did reboot as well as tried it all again. No change. The files are all under c:\bfgminer and I changed the command window directory to there before launching the batch file.

Any thoughts?

Why not try setting per miner and use PI's as your controllers or one rasp pi  ? windows 10 is due out on the 29 th and has a PI 2 version you might want to look at if you want windows as your miner/controller and look at minera ? .I use 5.2 on my cyclone and it runs way better now that minera fixed it's Calculation issue no over heating PSU never had that issue any way  it just runs a lot better with 5.2 holds a steady 21 to 23 MH at default setting. why even over clock any of them sense Ive found OC is just a waste of power there not worth OC, if you are.


--scrypt -S zus:all --set zus:chips=96 --set zus:clock=330  for the cyclone or T X2 .

per miner setting with minera or without

--scrypt -S zus:/dev/ttyUSB0 --set zus:chips= --set zus:clock= -S zus:/dev/ttyUSB1 --set zus:chips= --set zus:clock=

I'm real amazed the above setting even work and don't over heat every thing. you have set .

I'm not even sure what Zeus has 213 chip per miner and runs with no clock set very well or clock set at 151

The clock setting i know of are 240 to 345 safe clock setting that depends on the miner for best results with any version of BFG miner that supports ZeusMiners.
some setting in older version of BFG you may need to use you don't need with 5.2 but can still use them if you want to.


Last question what Zeus Miner are they ? .)

I left it running all night, and at some point the U3 hashrate dropped off the pool it was pointed at.  When I looked at the bfgminer window in the morning the U3 was still running and spitting out those comms errors, several per second every couple seconds.

This comms error seems to be the last hurdle in getting the U3 to be happy on this machine.  It successfully submits shares even with the errors, but obviously something isn't right still.