That is awesome news.
That is awesome news.
I set up the affinity today and take a lot of logs with WB.
What should I say, the issues with the frozen channels Comes never again. Some logs was 20+ minutes.
But if I close the scanner and start it again... I need to setup the affinity again to 1 CPU. It's there a possibility to fix that permanent to one CPU?
Henry
It is possible.
You'll need to adjust this to your specific install path for the VCM suite, but you just need to make a shortcut to the following (for example):
Since so many of us have had such good luck with this trick, I'm sure Keith and the crew have an idea of how to fix it however, so don't keep using it forever once they release an update for the issue.C:\Windows\System32\cmd.exe /C START "VCM Scanner" /affinity 1 "C:\Program Files (x86)\HP Tuners\VCM Suite\VCM Scanner.exe"
Last edited by sevinn; 03-02-2016 at 08:20 AM.
Hopefully that fixes it for all of us! I haven't had a chance to try it yet
Just wanted to update. My wife's laptop had the issue and setting the affinity seems to have worked around it on there too.
Seems to have fixed mine too
I'm late to the party on this one, but i am experiencing the same problem. I didn't realize there was a thread going on this issue.
I wont belabor the pont since it seems like you guys have made some headway.... I'll just add that i am on a new intel I7 machine as well. logging MPVI channel 1 and getting various lock up situtations requiring restarts etc.
I just want to follow the thread to see a hopeful resolution as much as anything.
Additionally, i noted when i was going through a log i saved from when it crashed... The data points being read on the plotted graphs, did not correspond to the data in the chart. The AFR etc shown in the plot was not the AFR corresponding to the chart for instance.
Might be unrelated.
Setting affinity fixed mine, got some good logs today. Vcm controls kinda failed on me though.
2001 Z06
JCR fabbed Twin Turbo
affinity.jpg
I found affinity...which one do you uncheck and check?
You only want one of them checked, so uncheck either CPU 0 or CPU 1
Please reset your affinity settings, and try the latest beta and report back.
We got this guy Not Sure, ...
New 3.0.50 up, that SHOULD fix the issue. It appears to fix it on our bench with a customer supplied laptop that we were able to duplicate the issue with, and then solve it.
The affinity fix you guys found helped point us in the right direction.
We got this guy Not Sure, ...
You can use the regular public/stable 3.0 version.
We got this guy Not Sure, ...
I know what I'll be trying later tonight. Thanks Keith and crew.