Jump to content

spurkza

Members
  • Content Count

    16
  • Joined

  • Last visited

About spurkza

  • Rank
    New Member

Recent Profile Visitors

1,782 profile views
  1. Quote Report reply tetonbob Replied: October 17 Thanks for that additional detail. For exclusions, I meant adding SpyShelter files into Malwarebytes exclusions from the Settings > Exclusions tab as detailed here: https://support.malwarebytes.com/docs/DOC-1130 Something else we might try if you don't mind, when you get time, would be to delay the protection start of Malwarebytes to see if letting it load later will help. That can be done from the Settings > Protection tab > Delay Real-Time Protection when Malwarebytes starts. I understand BSOD can be disruptive, but so far I've been unable to reproduce this issue, so any additional steps you'd be willing to try with 3.6.1 installed would be greatly appreciated. Quote Report repl tetonbob Replied: October 17 Report reply spurkza Replied: October 17 Tetonbob - I added folder C:\Program Files\SpyShelter Premium to the Malwarebytes exclusions list. I tried toggling from Off to On the setting for Delay Real-Time Protection when Malwarebytes starts, but every time leave the Protection settings screen, that setting unsets. Nonetheless, first reboot after reinstalling 3.6.1, no BSOD. But other troubleshooting, it took several reboots for the BSOD appears. I will be more comfortable if no BSOD appears after 48 hours, but no so far not yet in all the troubleshooting. As far as SpyShelter tech support, they are in Poland, several hours difference than USA time, so it may be tomorrow before hear back from them. Quote Report reply tetonbob Replied: October 17 OK, the exclusions added cover the SpyShelter.sys file being implicated in the crashes, which is the main file I was wanting to exclude. Interesting about the delay start setting. That should not happen. I wonder if you Quit Malwarebytes via the tray icon, relaunch and try again, if it remains in the On position. Another possible step to try to isolate if there is something in the new version of Malwarebytes causing the bad interaction between the 2 programs would be to disable Malware Protection for a time. Of course, that leaves the machine not as well protected, so I leave that decision in your hands. Quote Report reply tetonbob Replied: October 17 With regards the protection delay start setting, my colleagues noted there is a known issue where if you slide the toggle rather than click on it, the setting is not retained. Quote Report reply spurkza Replied: October 17 Hi Tetonbob - SpyShelter tech support provided me a unofficial test updated version of their software. So far so good after two reboots, but will continue to monitor the next day or so. p.s. While using their test version, I undid the MBAM exclusion and other setting change you mentioned above. Quote Report reply tetonbob Replied: October 17 Hi spurkza. Thanks for the continued updates. Please do keep me apprised of your status over the next few days. Quote Report reply tetonbob Replied: Monday at 08:49 AM Hi spurkza. I wanted to check in with you about the stability of your system, with the test version of SpyShelter alongside Malwarebytes 3.6.1 Our developers have not seen any indications implicating our drivers in the crash dumps. Thanks, Bob Quote Report reply spurkza Replied: Wednesday at 12:21 PM Hi Bob / tentonbob - As of today, I am testing a new test build from SpyShelter with MBAM 3.6.1. Three reboots so far, no BSODs, but giving this 24-36 hours until later tomorrow Thursday and let you know then. Thanks, Scott Quote Report reply tetonbob Replied: Wednesday at 12:40 PM Great, thanks Scott. You might also be interested to know, we have a new Component Update which is currently in Beta, and should be shipped later today. Version is 1.0.482 and it will be delivered in a metered fashion, or the metering can be bypassed by using the Settings > Application > 'Install Application Updates' button Kind regards, Bob Quote Report reply spurkza Replied: just now Hi Bob - After two days of testing a new test build from SpyShelter with MBAM 3.6.1, no BSODs. Drag files here to attach, or choose files... Accepted file types doc, csv, docx, dmp, gif, gz, jpg, log, mp3, mp4, png, pdf, psd, rar, wmv, xls, xlsx, zip, txt, 7zip, 7z, jpeg, mov, po · Max total size 58.59MB Insert other media
  2. Report reply tetonbob Replied: 33 minutes ago Hi spurkza. Thanks, I'll get this to the developers. Again, SpyShelter is the driver involved in the crash and our drivers are not in the stack. Have you reported this to their team as well? If you add exclusions for SpyShelter into Malwarebytes, does that resolve the issue? Does this crash happen during a scan, or when Windows loads, or at some other time? Thanks, Bob Quote Report reply spurkza Replied: just now Hi Tetonbob - The crash happens when Windows is nearly finished loading, that is the screen where you have the system and personal icons on the screen and in the system tray. In loading, SpyShelter loads early on, and Malwarebytes is the one of the last to load. MBAM 3.6.1 does not crash while scanning, at least not in the initial scan after installing before any reboots. When I install MBAM, rules are Automatically added to SpyShelter so it is a program it recognizes. I do not see anywhere for exclusions. I will open a support ticket with SpyShelter and refer them to the Malwarebytes forum thread on this issue and providing them also the Memory dump file.
  3. Hi Tetonbob - again the dreaded blue screen of death. I have reverted back to MBAM 3.5.1 which is at least stable on my system. With all done above, I am at a loss how to remedy to upgrade to 3.6.1. Removing SpyShelter anti-logging software permanently which encrypts keystrokes and data transmissions is not an option as this is protection as perceive the greater security threat - key loggers and screen capture which can readily steal your identity. Until now, MBAM and SpyShelter acted nicely together. I am sending to you in the next minutes a private message with the wetransfer link to the latest zipped version of MEMORY.DMP for your and your team's further analysis. Thanks.
  4. Had a couple of blue screen of death crashes yesterday. What done since was a clean uninstall of MBAM, rebooted, then deleted all security rules in SpyShelter and ZoneAlarm firewall which were related to MBAM prior version or versions installed and used, then reinstalled MBAM 3.6.1. A number of reboots later, fingers crossed, all is well.
  5. tetonbob Replied: 2 hours ago Hi spurkza - thanks for uploading the files. I've forwarded the crash dump to our Dev team for detailed analysis. At first glance in my own cursory analysis of the dump, it looks to me like SpyShelter.sys is implicated in the crash. If you temporarily uninstall or disable SpyShelter, does the crash still happen? I understand that what changed most recently on your system was Malwarebytes but our drivers are not in the stack trace, from what I can see. Thanks, Bob Quote Report reply tetonbob Replied: 1 hour ago Something I noticed while reviewing the FRST logs is that there are some Trend Micro drivers installed; two are running but not all are. Have you recently uninstalled Trend Micro Titanium? If so, you may want to run their uninstall tool: https://esupport.trendmicro.com/en-us/home/pages/technical-support/maximum-security/1115650.aspx?referral=1104855 I'm not saying this is related to the BSOD you reported, but it could help clear the decks of unnecessary drivers. Quote Report reply spurkza Replied: just now Thanks Tetonbob - I did have Trend Micro on the machine years ago, though uninstalled then, your link cleanly uninstalled it. With that gone after a reboot, I was able to install MBAM 3.6.1. On next reboot, blue screen of death, but on following reboot I quickly disabled and exited SpyShelter prior to MBAM loading which then loaded normally. The prior one-time disabling and exiting of SpyShelter I surmise must have allowed something to set properly in MBAM. A few reboots later, no blue screens of death and MBAM loading normally, so keeping my fingers crossed and monitoring for next few days.
  6. @tetonbob just sent you by private message the wetransfer link to the memory dump file (zipped), and the Farbar Recovery Scan Tool (FRST) logs
  7. MBAM 3.5.1 Premium for Windows 7 on a 32-bit Dell laptop worked fine. Tried to install MBAM 3.6.1 days ago first without clean install and BSOD upon reboot. Did a clean install today using the MBAM Support Tool and after rebooting and almost at the end of the reinstalling, a blue screen of death again. I have attached logs. I also have the MEMORY.DMP file zipped, but its 139 MB, so if you need, please let know how to send. I also ran a full drive security scan with MBAM v3.5.1 just prior to the 3.6.1 clean install and no malware found. Other security software on this machine Zone Alarm Firewall and Anti-Virus Pro v15.3.060.17669 and SpyShelter Premium v11.2, both latest versions. I have reverted back to MBAM v3.5.1 until this issue is resolved. mbst-grab-results.zip mbst-clean-results.txt
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.