Quote from: Mudbankkeith on March 17, 2014, 11:04:13 PM

Quote from: derpberp on March 17, 2014, 09:14:38 PM

Quote from: Cascaders28 on March 17, 2014, 05:36:24 PM

Was it a single Windows Update or several? What was it an update for? If it was only one update, I'd probably try uninstalling that single update to see if that made things work again. As much as I don't like this option, a System Restore to sometime last week might be worth trying too.

None of the above would explain why it won't work on multiple PCs but I'm using 2 Chilis on a Windows 7 x64 PC without any issues. One thing I'll say though is that I actually disabled auto-updates because I didn't want it restarting in the middle of the night and losing hashing time. I just check for and install them manually once a week or so but its a very bare bones PC with little more than mining software on it.

It was just one update - Dev is helping me too, Thank you so much Dev. I tried a system restore to last week, it didnt work sadly. I tried removing all the updates, I tried removing the driving currently on the miner, ive tried plugging the miner into another computer and even there it doesn't have the original normal information that it used to, that's what I don't understand. It acts normal but none of the normal information is there when you plug it in. When you try to program it with Chili flash on either computer, it doesn't show up on any USB port, so it won't let me reprogram it. Its frustrating because I know the computer notices it, it says "Downloading driver for new item plugged in" which always fails to download of course. then it just says unknown device and thats it. or "USB Composite device". It doesn't register as a ASIC Miner anymore.

If your room temperature is to high, then the power circuit may not be resetting.

If that is the case then try to get the chili temperature below 20c and try again.

I had a month ago a something similar issue, Tried first reinstalling FTDI drivers but solved replacing 4 port USB Hub connected to Chilli boards. But I use windows server 2008 so maybe is not same problem