frozen

I have a Windows 10 Pro 1809 fully updated system running on a 1 TB Samsung SSD that was a clean install back in Dec 2018. Over the last week or so I noticed that on a cold startup the system would not load properly I would login but I would get no desktop icons nor were there icons in the system tray other than the display icon, notifications. The start button would show up but non of these would work properly. If I pressed the reset button on the case and rebooted the system it would load fine. Since I had installed a couple of applications recently I figured perhaps that was the issue. Uninstalling that did not help. Booting into safe mode worked and could see the desktop and systray icons. When I disabled all the MBAM shields powered off the system and booted up the system loaded fine. mbst-grab-results.zip

I have a Windows 10 Pro 1809 fully updated system running on a 1 TB Samsung SSD that was a clean install back in Dec 2018. Over the last week or so I noticed that on a cold startup the system would not load properly I would login but I would get no desktop icons nor were there icons in the system tray other than the display icon, notifications. The start button would show up but non of these would work properly. If I pressed the reset button on the case and rebooted the system it would load fine. Since I had installed a couple of applications recently I figured perhaps that was the issue. Uninstalling that did not help. Booting into safe mode worked and could see the desktop and systray icons. When I disabled all the MBAM shields powered off the system and booted up the system loaded fine.

Why not just install the beta if you are having the issue?

Well I am running that beta build to try to help out here with that issue to provide more data. So far with MBAM all enabled no BSOD for about 3 days but as past experience is any indication that does not mean much. Will submit any memory dumps should they occur

Self protection was enabled. I disabled it. The thing is I have changed 3 things now today so if the system here stabilizes I will not have any idea if one of these 3 changes helped. I still am not running any MBAM protection but the next step would be a total cleanse of the system to see if it is indeed causing these BSOD even though MBAM is not have any of its modules enabled for several weeks now.

I currently have MBAM still installed here but all options disabled from loading. Today I had 2 BSOD which did not point to any specific cause. These BSOD occurred while I was away from the computer. All this time I had Eset Security 11.2.49 installed. Today I uninstalled it and switched to another security product. I have not yet fully removed MBAM entirely and had a pressing deadline item to attend to today. I have yet given any thought on downloading this test version of MBAM since this system is still not stable and I have no idea if it is MBAM still causing it. Both of these BSOD were while Chrome was loaded although MBAM extension was loaded. It has since been deactivated. I want to see if this system is stable or not before I start adding any other software to it.

Personally I just disabled everything in MBAM there is nothing in it that is enabled.

The only time I used extension was when MBAM was enabled except for web protection. During that test I received spurious blocks and a BSOD which could of been simply MBAM not fully disabled.

Thing is I don't particular want to run any MBAM software currently. Sorry but over the past 6 weeks I have lost count on how many BSODs I have seen here on Windows7. This is especailly the case since no apparent solution to the BSOD other than disabling, at least in my case MBAM entirely.

Well I too had tried the Chrome MBAM web extension when MBam was still enabled except for web protection. I found that the extension through threw up more block sites that were erroneous vs when MBAM web protection was enabled. I have been running with MBAM totally disabled along with the Chrome extension disabled. Only using NDO32 antivirus on Windows7 here

@dcollins I assume that you got the last 2 memory dumps and I can delete them off my OneDrive account?

LInk to my last BSOD in WIn7 this is BEFORE I totally disabled MBAM https://1drv.ms/u/s!AjeWNAchT2IxmeAESTNU0jkISsOMPA

OOps spoke too soon BSOD numero deux. Was in the process of copying the Memory.dmp to temp storage when system BSOD 2nd time within 15 minutes. Lost memory.dmp file from first BSOD. In order to preserve what sanity I have left I have disabled ALL protection in MBAM and have disabled it from loading on startup of Windows.

Another day another BSOD on Windows7 here. Today was patch Tuesday install day here.

No idea and do not want to enable Web protection. I have seen enough BSOD in the past month and half and will await further confirmation. If that is forth coming only time will tell whether in fact the issue is fixed once and for all

@dcollins Here is the Dropbox link to the full memory dump file https://1drv.ms/u/s!AjeWNAchT2Ixmd94gSR-9hYY4iVTYA

Well just like all the other times when I posted that I had not had a BSOD after changing something blam. Crash dump directories: C:\Windows C:\Windows\Minidump On Sun 7/8/2018 4:18:55 PM your computer crashed or a problem was reported crash dump file: C:\Windows\MEMORY.DMP This was probably caused by the following module: ntkrnlmp.exe (nt!longjmp+0x5FF9) Bugcheck code: 0x4A (0x7766991A, 0x1, 0x0, 0xFFFFF8800E184CA0) Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Its bee close to 1 week without Glasswire 1.0 running but Eset Antivirus installed and MBAM 3.5.1 running without Web protection. No BSOD so far but one never knows with this issue..

I haven't removed Glasswired because if I do it will remained uninstalled. This because Glasswire has removed the download link for last version of Glasswire 1.2.121 version off their site. I only have an older version of the software and it will not update to that version I believe it will update to the much more limited free version 2.x. All I am using Glasswire for is blocking certain apps from outbound connections. With Glasswire 2.x I would have to pay $57 Cdn a year to allow me to block outbound connections on one computer.

Well I have just now disabled the Chrome Extension for MBAM to see if any further BSOD occurs. I have had Glasswire 1.0 installed on this box for years and version 1 being deprecated it is no longer being updated.

Alsa got my first BSOD since disabling web protection. One thing is that I installed MWAB to Chrome and Chrome was running at the time. I use Vercrypt to encrypt sensitive information and I have 1.22 installed on this system I was in the process of updating the traveller disk aka a USB flash drive which I use elsewhere. The traveller disk option was run from the Veracrypt app and Veracrypt traveller disk said it was stopped responding. I also had received the Windows pop up notice to that effect. I killed off Veracrypt in the process list and shortly after that the system crashed with a 1E crash. Upon analysis here it pointed to Glasswire sys driver. I am using Glasswire 1.0 which has been deprecated simply as a software firewall. I rebooted the system and performed the traveller disk creation process without any BSOD. Crash dump directories: C:\Windows C:\Windows\Minidump On Sat 6/30/2018 8:41:55 AM your computer crashed or a problem was reported crash dump file: C:\Windows\MEMORY.DMP This was probably caused by the following module: gwdrv.sys (gwdrv+0x424E) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800BA4FEB0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\gwdrv.sys product: GlassWire company: SecureMix LLC description: GlassWire Driver Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: gwdrv.sys (GlassWire Driver, SecureMix LLC). Google query: gwdrv.sys SecureMix LLC KMODE_EXCEPTION_NOT_HANDLED

Well I am into day 3 of running MBAM 3.5.1 with web protection disabled and ESET Antivirus installed on Windows7 and no BSOD but time will tell.

Believe me I have been dealing with these BSOD for almost a month now and its MBAM interacting with other software not just Eset. I lost count on how many times I have seen Windows7 BSOD. Sometimes these BSOD have no reference to Eset whatsoever . Both of Eset and MBAM worked fine for months without any exclusions and others here have BSOD and they do not even have ESET installed. As with all software testing one should not change multiple items/settings as that does not help indicate what has fixed the issue. Currently using MBAM 3.5.1 without web protection and ESET without any exclusions for each other. The BSOD may take several days before it occurs on this Windows7 computer.

I checked for updates within the MBAM app last night and I am now sitting at I have Eset Antivirus installed and have web protection disabled.

So now I do not know if I try to get MBAM which is at 3.5.1 to auto update back to 3.5.4 and uninstall NOD32 and go to with MS Security Essentials or just leave MBAM 3.5.1 totally disable and run NOD32.