VoodooShield/Cyberlock

ok I know you don't want to hear about freezes but this last time running 333, I actually got a windows message saying something about memory manager.

 

Guess what? This version froze on me almost as soon as I'd rebooted and started using this machine.
Back to the SBS version, which is the only one of the recent betas that has run without this frustrating issue.
Logs sent.

 

Thank you for letting me know... believe it or not, this might be good news! All we have to do is try previous versions and see where the freeze first started, then once we know, I can compare the code, and it should be an easy fix. That would explain why the differences in the 3.08 and 3.09 code did not contain the freeze bug, and why I could not find it.

Here is 3.07 if you guys can please try it and see. It does not have the driver for the Windows 10 AU update, so it will not work for Windows 10 for now... I can change this if we need to. Also, it will ask you if you want to overwrite the driver, you can say yes if you want. Also, I think that since the digital signature was not time stamped, SmartScreen will flag it... this has since been fixed.

https://voodooshield.com/Download/beta3/InstallVoodooShield_3_07.exe

If this version freezes, you can use the same link to download 3.06, but just replace the 7 with a 6. Thanks again for all of your help, talk to you soon!

 

@VoodooShield

Dan,

You have checked the code over and over again. The chance of the freeze issue being a logic error is unlikely. Another clue is that the logs give you so little information, so it is most likely something happening outside VoodooShield (because VS using system feature in the wrong way). So think of two strategies:

1. One is backtracking (testing)
You are focussing on VoodooShield (first release 1.09 to 1.08 now 1.08 to 1.07). Did it cross you mind that the error could be in VoodooShield for a long time, but that Windows changed something in memory management, making it a problem all of sudden? So Windows update just coincided with a VoodoooShield release and now you attribute the changed code in VoodooShield as the cause, making you look in the wrong place! Still going back in time is a good strategy, firstly because it may isolate the problem and secondly it is testing related hopefully performed by loyal users of VoodooShield (, so it does not eat all your capacity away. This post is also a call to help Dan out by testing older versions.

2. Solving every problem you know of (coding)
This is the problem you mentioned in post #12028. It is a problem you have to solve anyway, so it is usefull way to spend your time. With luck you could solve the freeze issue, because memory leak/page faults can make the memory manager go haywire and cause a program to freeze. Also the trigger situation matches what a lot of members describe (unattended PC usage) and boredog mentioned he noticed a message from the memory manager in post 12076 (top of this page). When you solved this one, move on to the next one. Add memory leak tools or other debuggers to the latest version and hopefully members will offer help to test this version also.

Dan, it may feel bad that you have to juggle time and priorities between VoodooShield and your consultancy firm and you have to debug code written by Vlad, but REMEMBER your Artificial Intelligence engine is BETTER than Cylance who have a batallion of scientists and programmers working on it. So the future of VS should be bright!

Dan you have dedicated so much time and effort to forum members (and generously giving away licenses) , time to ask some favours back and organize the two strategies above (people testing older versions and people testing the latest debugging version).

I am going to travel for two and half weeks, so I apologize to all members for asking help and commitment while I am dropping out myself:

Regards Kees

 

Your cloud option on VS settings

 

I have the exact same configuration, except 16 gb ram, and I never had any freeze either.

 

Well...I'm a little confused with VS notifications.

How do I know which are those two files, how do I find them?
I asume that those two files be in quarantine bcz they are highlighted on the GUI of VS.
In logs I seen bunch of blocked files and why those files are not highlighted in the up right corner of GUI?

It says: ( RED = Blocked / Quarantined ) and you see in my screenshot that also say: ( Threats Blocked:2 ),where to find those 2 threats if not in Quarantine and if they not suposed to be in quarantine,why they are highlighted in GUI and bunch of other blocked files are not?

This confuzes me...

 

Sorry, I missed this post earlier... yeah, exactly, we will have to do something like this... thank you for the suggestion!

 

Cool, this version should have the disabled mode blocks fixed: https://voodooshield.com/Download/beta3/InstallVoodooShield.exe

 

Sounds great, thank you... I added this to my to do list and can work on it once we have the freeze issue fixed. There are a lot of little usability tweaks like this that we can add to VS to make it even more user-friendly, but I really want to fix the freeze issue first.

 

Cool, thank you. I was looking through the old versions prior to 3.08 to see where the freeze bug might have first occurred, and I am quite sure that it first appeared in 3.06. I am not sure if you guys remember this or not, but there was a bug that Vlad fixed known as the heap corruption bug... it made VS completely crash on some systems. Basically, it did not freeze, it just completely crashed. Looking at the code, I can easily see where the freeze bug might have been introduced here.

So I am betting that 3.06 and later versions freeze, and that 3.05 does not freeze... although on some systems, 3.05 will crash out of the blue. So if you guys want to test this for me and see, I think it should be a really easy fix once we know for sure. Please keep in mind that a lot of the old bugs such as the dismhost bug are in these versions, but we should only have to test for a few days. Here are the links, thank you!

https://voodooshield.com/Download/beta3/InstallVoodooShield_3_05.exe

https://voodooshield.com/Download/beta3/InstallVoodooShield_3_06.exe

 

Cool, this was added in 3.33, so it should be good, if not, please let me know, thank you!

 

Ohhh, that is where this command line comes from... good to know, thank you!

 

Cool, thank you... yeah, I think this is related to the heap corruption stuff... I think we are getting close!

 

Thank you Kees for the encouragement and advice! Yeah, I really think the freeze issue occurred between 3.05 and 3.06, and once we know for sure, it should be pretty easy to fix because those versions had a lot less changes between them and the distinctions are better documented.

We could always try to find another developer to help me, but once we get over this freeze issue, it should be smooth sailing from now on . Then I can just add all of the usability tweaks and new features as we go. Besides, if we did find another developer, they would have to familiarize themselves with all of the code, and that could take some time. I have not heard back from Rajesh, hopefully I will soon, because he is pretty familiar with the code.

This whole freeze issue was kind of a perfect storm (in a bad way), because the bug was not discovered until a week or so before Vlad had to stop working on VS. But it's cool... I am up for the challenge as long as everyone else is . Thanks again for everyone's help and patients!

Have a great time on vacation Kees, talk to you soon!

 

Cool, thank you... just to be sure, do you mean "Synchronize and backup my whitelist snapshot to the cloud"?

 

Yeah, that is a great point... especially since the VS driver acts as a hardware component... I will look into that, and if other users want to post their config, that will help, thank you!

 

Thank you!

 

I see... the threats blocked count does not necessarily mean that the file was quarantined. A while back, I believe it was guest who suggested that we add the blacklist and VoodooAi columns (among other items) to these logs. It is on my to do list, and we will do that once the freeze issue is fixed. I will also look at your suggestions and implement them all together so that it makes sense for everyone, thank you!

 

So anyone who is experiencing the freeze issue and would like to help test... we need to verify that the freeze issue occurred between 3.05 and 3.06... here are these versions, thank you for your help!

https://voodooshield.com/Download/beta3/InstallVoodooShield_3_05.exe

https://voodooshield.com/Download/beta3/InstallVoodooShield_3_06.exe

As I was saying above... So I am betting that 3.06 and later versions freeze, and that 3.05 does not freeze... although on some systems, 3.05 will crash out of the blue. So if you guys want to test this for me and see, I think it should be a really easy fix once we know for sure. Please keep in mind that a lot of the old bugs such as the dismhost bug are in these versions, but we should only have to test for a few days.

And please keep in mind that these versions will not work with Windows 10 AU!!!

 

Hi Dan,
It was me that first reported the Heap corruption bug in Win 7 that caused crashes and which Vlad fixed in VS 3.06 - I had to stay on VS 2.86 until Vlad sorted it. Just to confirm though I've never had the freeze issue and I'm using VS 3.33 Beta presently without any problems.
So maybe it's all my fault ?

Regards
Gordon

 

Hey Gordon... yeah, I found that in the old emails and notes, that you and Vlad were working on the heap corruption issue. The odd thing is that no one noticed the freeze issue until 3.09, which was when I first noticed it as well (it just took a little while for people to start experiencing the bug)... so all along I have been looking in the wrong place . I really think this is the issue, and if it is, it should be super easy to fix... all we have to do is confirm that 3.05 does not freeze, but 3.06 does... then the bug is isolated, and there are very, very few changes between those versions (and we know right were it is).

As I was saying before, this has been a major pain for everyone involved, but it did uncover a few bugs that probably would not have been discovered for a long time otherwise, so as much frustration as it has been for everyone, hopefully it will be worth it . Thank you!

Edit: I forgot to mention that I think fixing the heap corruption issue introduced the freeze bug... and looking at the code... I am not a betting man (even though I joke about Vegas all the time), but I would bet that is what happened.

 

Don't know if it's any help at all, as the above post seems hopeful towards pinpointing the cause, but I've been running on autopilot mode for a while now (3.33) with no freezing issues whatsoever. Switched back to smart mode earlier today, and just came back to the desktop to find VS frozen again.

 

Desktop PC (Custom built) - = NO FREEZES WITH ANY VS VERSION

OS: Windows 10 Professional (64-bit, version 10.0.1493 Build 14393)
MOTHERBOARD: ASUSTeK Computer INC. M4N72-E
CPU: AMD Phenom II X4 965 Black Edition (3.40 GHz Quad Core)
RAM: 16GB DDR2 Komputerbay memory
GPU: 2GB R9 270 (Gigabyte Windforce OC DDR5)
PSU: Cooler Master 1000 Watt
SSD/HD: 1 Kingston HyperX 3K 120GB SSD (SH103S3120G), 2 Western Digital 500GB HDD 7200RPM (WD50000AAKS-00YGA0)
DVD/CD/BD: ATAPI iHOS104 Blu-Ray drive
KB & MOUSE: Logitech G710+ Mechanical Keyboard, Logitech G700s mouse
SOUND: SB X-Fi Surround 5.1 Pro (SB1095)
NETWORK: TP-LINK Archer T6E AC1300 Dual Band Wireless Card 802.11ac (PCIe)

LAPTOP (With custom parts) - = NO FREEZES WITH ANY VS VERSION
Model #: Toshiba Satellite C75D-A7102 17.3"
OS: Windows 10 Home (64-bit, version 10.0.1493 Build 14393)
CPU: AMD Quad-Core A6-5200M 2.0GHz
RAM: 16GB DDR3 Memory
GPU: AMD Radeon HD 8400
SSD: SAMSUNG 840 EVO 250GB SSD
DVD/CD: TSSTCorp CDDVDW SU-208FB
SOUND: Conexant SmartAudio HD
NETWORK: Realtek RTL8188EE Wireless LAN 802.11n

 

Cool, thank you for letting me know... that actually makes perfect sense. In an earlier post, I talked about how the mini prompts or user prompts were causing the memory utilization to go crazy... I am assuming that this is because after the process is handled, the process is not properly disposed of, so I think it is all tied together!

If that is the case, and we are certain that it was the heap corruption bug fix (between 3.05 and 3.06) that caused the freeze issue, it should be pretty easy to fix... we can just add some logging or message boxes, and whenever it acts up, we will have an error message to work from. Thank you!