Quote from: noct on November 29, 2013, 11:01:10 PM

Same here. Windows 7 x64.
bfgminer -D -d? finds this:

[2013-11-30 00:47:06] lowlevel_scan: Found hid device at hid:\\?\hid#vid_fa04&p
id_0011#6&11d06e40&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} (path=\\?\hid#v
id_fa04&pid_0011#6&11d06e40&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vid=f
a04, pid=0011, manuf=StarFury Laboratories, prod=HashBuster.nano Project, serial
= )

But i only get "waiting for devices: press m+ to add, or q to quit."
Can anyone help?

I need the whole output from -D -d?

Quote from: purelithium on November 29, 2013, 11:05:37 PM

Quote from: purelithium on November 28, 2013, 01:38:31 AM

I'm baffled as to why bfgminer keeps crashing on this system. Why is it looking for USB devices when I'm trying to mine scrypt?

Code:

C:\Mining\bfgminer-3.7.0-win64>bfgminer.exe --scrypt -T
[2013-11-27 20:36:26] Started bfgminer 3.7.0
[2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
[2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
[2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
[2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
[2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
[2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
[2013-11-27 20:36:26] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
[2013-11-27 20:36:26] Failed to get PortName registry key value in lowl-vcom.c
_vcom_devinfo_scan_windows__hubport():443: The system cannot find the file speci
fied.

[2013-11-27 20:36:26] Failed to ioctl (1) in lowl-vcom.c windows_usb_get_root_h
ub_path():497: The operation completed successfully.

C:\Mining\bfgminer-3.7.0-win64>

I used WeBisect session "purelithiumNov29" to try and bisect the problem. This is what it gave me once I bisected all I could:

Code:

There are only 'skip'ped commits left to test.
The first bad commit could be any of:
e61f3a480388cfabe4dd7ddcbd643c6d7390c751
745bd11dc27a745f42fdb2361da60e0ca5bc5fa6
dd43825dbb5300d8509e7da8bba4d4599a98f719
ebf66582ace0fe5b7162f2d896a5b59043707a85
fd7d89dfef7398bedfd7d6f00ac6601a441a2d28
a651e94616c4c3c5eb9aefc7b2c350e8793e6628
ce4eba9042cdd3070a9770699987cd3d4005fc2f
f84c1a473f8618c46750701c249eddbf940d240f
We cannot bisect more!

The build I got before that message didn't have the error I described in my quoted message, but It did have another issue of crashing almost immediately on connecting to a pool. Not sure how I could bisect that one... As of right now 3.2.1 is the only functional build for my machine.

Please test the latest git: http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bfgminer