Problem with Counterspy version 2

Discussion in 'other anti-malware software' started by ummaya, Feb 17, 2007.

Thread Status:
Not open for further replies.
  1. ummaya

    ummaya Registered Member

    Joined:
    Feb 17, 2007
    Posts:
    2
    I upgraded from version 1.5 to version 2 and I ran my first scan with the new version. After he finished scanning the Memory processes and the Files, Counterspy went to scan the Registry keys and there within half a second (no scanning process seemed to take place at all) the number 94 suddenly appeared in front of " Registry Keys scanned " and nothing more... Counterspy just got stuck there while my mouse pointer revolves around himself when I roll over Counterspy. I could only close Counterspy with Windows Task Manager. I tried 3 more times to scan and each time I got stuck at the same place (94 Registry Keys scanned...).

    Any idea what the problem is and how to solve it ?

    Thank you in advance
     
  2. one111

    one111 Registered Member

    Joined:
    Apr 6, 2005
    Posts:
    92
    I had the same problem and Eric sent me a fix for it and now it works fine.

    Are you also getting the 0x660101e5 error notice?

    By the way, Eric, the original fix you sent me got rid of the error notice also but the latest program
    update which was supposed to fix some bugs in Version 2 caused it to come back again. What can I do?
     
  3. eburger68

    eburger68 Privacy Expert

    Joined:
    Mar 4, 2002
    Posts:
    244
    ummaya:

    Are you using a non-English version of Windows? I ask, because we have a number of reports of similar scan freezes with non-English versions of Windows. The Sunbelt devs are working on a comprehensive fix for these problems.

    one111:

    The DLL I sent you was a private/test build of that DLL that did not make it into build 917. You'll have to replace the DLL in 917 with the one I sent you, just as before, in order to pick up the fixes in that special DLL.

    Eric L. Howes
     
  4. ummaya

    ummaya Registered Member

    Joined:
    Feb 17, 2007
    Posts:
    2
    From the moment I upgraded from version1.5 to version 2 I did get an error message shortly after I restarted Windows. I don't know if it was the "0x660101e5 error". It happened twice and I only remember that the word "scan" was somewhere in the message. But now I restarted Windows just to see if the error message was "0x660101e5" but this time I did not get any error message at all. I tried again to run an other scan with Counterspy but I still get stuck at the same place.

    No. I use the English version.

    Thanks anyway. I am waiting for an answer from Sunbelt to the message I sent to them ( an hopefully a fix ).
     
  5. one111

    one111 Registered Member

    Joined:
    Apr 6, 2005
    Posts:
    92
    Eric, I replaced the dll. with the one you sent me and it helped stop the
    scan from freezing in the middle but the 0x660101e5 warning came back for some reason. How can I fix this? Before this latest build the fix you sent me was able to prevent this message from coming up every time I opened an exe. file.
     
  6. eburger68

    eburger68 Privacy Expert

    Joined:
    Mar 4, 2002
    Posts:
    244
    one111:

    I don't have an immediate fix for the error you're referring to. Could you post a screenshot of the error?

    Thanks,

    Eric L. Howes
    Sunbelt Software
     
  7. one111

    one111 Registered Member

    Joined:
    Apr 6, 2005
    Posts:
    92
    The message appears in Hebrew but here is a translation:

    The instruction at 0x660101e5 referenced memory at 0x660101e5. The memory could not be read.
    Click on OK to terminate the Program
    Click on cancel to debug the program

    In the meanwhile I went back to version 1.5 and everything is working fine again.
     
  8. eburger68

    eburger68 Privacy Expert

    Joined:
    Mar 4, 2002
    Posts:
    244
    one111:

    See my email replay, just sent.

    Eric L. Howes
     
  9. one111

    one111 Registered Member

    Joined:
    Apr 6, 2005
    Posts:
    92
    I received the e-mail and responded.

    In the meanwhile the 1.5 version is working fine without any problems.

    It appears to be something in the new build that stops the fix you sent from working. The fix DID however stop the scan from freezing in the middle even in the new build. Strange.
     
  10. costcolio

    costcolio Registered Member

    Joined:
    Mar 1, 2007
    Posts:
    6
    Location:
    Athens, Georgia
    Does your icon in the lower right turn black and the scan freezes? I am experiencing the same problem with a full scan. The quick scan works fine. Can someone send me the file that your talking about. Thanks!

    ~Email address removed for users protection~
     
    Last edited by a moderator: Mar 1, 2007
  11. eburger68

    eburger68 Privacy Expert

    Joined:
    Mar 4, 2002
    Posts:
    244
    costcolio:

    The .DLL that was sent to another user was a very early private build. As it turned out, it did not fix the problem for all users, only some. We are currently testing a more comprehensive fix for the scan freeze/crash problem in-house. I would expect it to be released in the next few days or early next week.

    Best,

    Eric L. Howes
    Sunbelt Software
     
    Last edited: Mar 1, 2007
  12. costcolio

    costcolio Registered Member

    Joined:
    Mar 1, 2007
    Posts:
    6
    Location:
    Athens, Georgia
    Thanks for the prompt response, we look forward to the fix.
     
  13. eburger68

    eburger68 Privacy Expert

    Joined:
    Mar 4, 2002
    Posts:
    244
  14. costcolio

    costcolio Registered Member

    Joined:
    Mar 1, 2007
    Posts:
    6
    Location:
    Athens, Georgia
    Same problem with this new version, the full scan still freezes at around 9500 files scanned. The icon in the lower right tray turns black and has to be restarted. Very frustrating!

    BTW, I am running XP with all updates and Kaspersky Internet Security. I have tried turning off KIS to see if thats the problem, same thing happens.
     
  15. one111

    one111 Registered Member

    Joined:
    Apr 6, 2005
    Posts:
    92
    Just for the heck of it, I tried Version 2 again with this latest build and I'm happy to report that all of the problems disappeared, including the error notice and the scan freezing. All this even without the dll. fix I was originally sent.
    I can't say if it was this fix or another one as I've been using the 1.5 version
    since all the problems started. In any case, congratulations to the CounterSpy team and a special thanks to Eric for his continual support.
     
  16. costcolio

    costcolio Registered Member

    Joined:
    Mar 1, 2007
    Posts:
    6
    Location:
    Athens, Georgia
    Glad its working for you. Perhaps some other program is causing conflict.
     
  17. fcukdat

    fcukdat Registered Member

    Joined:
    Feb 20, 2005
    Posts:
    569
    Location:
    England,UK
    FYI Switching off a software dose not actually prevent it from loading its drivers and modules at bootup.

    Inorder to find out if it is KIS that is not playing well with CS you would have to uninstall it temporarly to find out that information.
     
  18. EASTER.2010

    EASTER.2010 Guest

    klif.sys of KIS6 takes up residence in many SDT Table locations in the Kernel which might be reason for some kind of issue noticed or other interference between security programs perhaps.

    As of this post i can confirm, at least for Win XP Pro SP1 with a mere 512Mb of RAM, that these programs co-exist fully stable together.

    klif.sys = KIS6
    safemon.sys = System Safety Monitor
    sp_rsdrv2.sys = Spyware Terminator
    ghostsec.sys = Ghost Security Suite
    guard.sys = AVG AS 7.5

    I yet to notice any conflicts when mixing/heaping the kernel/SDT Table hooks from those programs.

    As to CounterSpy, that is better left for those who already have examined matters at the SDT level after installing it and everything runs fine or not together with other Table hooks that deep.

    eburger68 is the chief CS specialist who can offer that manner of insight and more. Regards EASTER
     
    Last edited by a moderator: Mar 3, 2007
  19. costcolio

    costcolio Registered Member

    Joined:
    Mar 1, 2007
    Posts:
    6
    Location:
    Athens, Georgia
    Appreciate the responses. I was looking for folks that use KIS to see if they are having issues.

    Looks like its back to Spyware Doctor, no problems with that program.
     
    Last edited: Mar 4, 2007
  20. TopperID

    TopperID Registered Member

    Joined:
    Oct 1, 2004
    Posts:
    1,527
    Location:
    London
    I can only say that I use KAV 6 and have had nothing but trouble with CounterSpy 2, I believe that the two progs fight each other at bootup and KAV is the winner!

    I've not tried the latest 931 version as I am back to CS 1.5 which gives me no problems. A lot of kernal level progs do manage to co-exist together OK, so it's a pity that CS2 is not yet one of them.
     
  21. eburger68

    eburger68 Privacy Expert

    Joined:
    Mar 4, 2002
    Posts:
    244
    TopperID:

    Sorry to hear that you've encountered problems with KAV6 & CSC 2.1. I'm actually surprised to hear this because we have many users reporting that the program coexist fine. In fact, I've got both installed on one of my boxes at the moment.

    The one issue that I know of wrt KAV6 & CSC2 is an annoying Active Protection pop-up from CSC 2.1 about an "unknown x" application/process accessing varius areas of the Registry. In fact, the process is KAV6, which CSC 2.1 can't recognize (and thus ignore) when KAV's self-protection is turned on.

    I would encourage you to try build 931, and that resolved a number of timing issues wrt AP starting at boot. Several users with apparent conflicts with other AV programs reported that they disappeared with build 931.

    Eric L. Howes
    Sunbelt Software
     
  22. costcolio

    costcolio Registered Member

    Joined:
    Mar 1, 2007
    Posts:
    6
    Location:
    Athens, Georgia
    Looks like version 2.1.946 is working fine!
     
Loading...
Thread Status:
Not open for further replies.