Loading Profile...
Current Cost GUI gives BSOD on Vista, on my machine.
Just installed CurrentCost GUI for use with my CC128. noted the topic about forcing the CC128 to output data by pressing Down and OK together.
Problem is that every time the CC128 outputs it's data, it causes a BSOD and restarts my PC (it's every time the counter gets to "5").
i'm running windows Vista (64 bit) and the driver from the Cooldrives link on the Current Cost site.
Tony
Problem is that every time the CC128 outputs it's data, it causes a BSOD and restarts my PC (it's every time the counter gets to "5").
i'm running windows Vista (64 bit) and the driver from the Cooldrives link on the Current Cost site.
Tony
I’m frustrated
4
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company thinks this is not a problem.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Sorry, I don't have access to a Vista computer to try this, so am unable to investigate it.
I would note that it seems unlikely that my software is the source of the BSOD. The nature of a Python script is such that it extremely unlikely to be able to lead to a BSOD. It is far more likely that the problem lies in the drivers you are using.
I realise that pointing at something else is an unhelpful answer - sorry. But I would advise that finding alternate drivers would be more likely to result in a solution. -
Inappropriate?I have the same problem, on vista 32 machine. While downloading data from cc128, BSOD and system reboots. Data does transfer about 1in 5 downloads. -
Inappropriate?Have also run the software on an XP system without any problems. So it would appear to be a vista thing.
-
Inappropriate?As I said above, I don't think it's fair to "blame" Vista. BSODs are most often a result of faulty drivers. And as you are using different drivers on Vista to XP, I would expect that the most likely source of the crash is the serial driver trying to do something that it shouldn't.
Does anyone know of any alternative sources of Vista drivers?
EMPLOYEE
