Jump to content

gow

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by gow

  1. Thanks for the info. In my case, the mini-dump file seems to suggest a file on my system, namely "C:\Windows\System32\drivers\XMS1563K.SYS", may be the problem. Searching Google about this file produced conflicting reports. One site says it's an important Windows file while another says it's a virus and part of a rootkit. Spyhunter from Enigma Software claims they can remove this rootkit but also say that Malwarebytes must be uninstalled in order to do so because Malwarebytes flags Spyhunter as a potentially undesired program. I'll have to pay for Spyhunter to use it's removal properties. I'm running a 32-bit version of Windows 10 and note that the file XMS1563.SYS does not exist in the same folder on a 64-bit system. Do I have an infection or not and what to do or not to do, that is the question.
  2. Another Update: Seems like it's not an MBAM problem at all as the BSOD is happening after I uninstalled MBAM and rebooted. Could have something to do with the November Feature Update. I'm at a loss. According to the latest minidump file, it could be a driver problem. Anyway thanks for your help. 111817-31687-01.dmp
  3. Update: Un-installed and reinstalled MBAM 3.3.1.2183. Web Protection now working. BSOD still happening
  4. Hi Porthos 1. Bitdefender Antivirus Free only allows the option to add exclusions when a threat is detected on the file being scanned. I scanned each file individually (as listed on this link https://support.malwarebytes.com/docs/DOC-1123 ) and no threats were found by Bitdefender and therefore I could not add to exclusion list. 2. The clean tool ran OK, the PC rebooted, then MBAM 3.3.1.2183 was installed. This is the version I had already installed a few days earlier. Ran File Explorer and the BSOD problem still exists. PC rebooted. 3. I uninstalled Bitdefender and rebooted the PC. Ran File Explorer and the BSOD problem STILL exists. Now also, MBAM refuses to turn on Web Protection. 4. Some of the earlier Windows minidump files from this morning mention the Windows Container Isolation FS Filter Driver whereas the latest two minidump files as described above show MBAM farflt.sys as the culprit. All minidump files created today are attached Hope you can help. mb-clean-results.txt 111817-25828-01.dmp 111817-28078-01.dmp 111817-36656-01.dmp 111817-40046-01.dmp 111817-46953-01.dmp
  5. I recently installed the latest version of MBAM (3.3.1). I too have been getting the BSOD error Unexpected_Kernel_Mode_Trap. The Windows minidump file (attached) confirms that the MBAM Ransomware file "farflt.sys" is the culprit. In my case, the BSOD specifically happens in File Explorer. In the left pane of File Explorer, if I single-click on the "+" sign next to C drive to view the sub-folders, the BSOD immediately occurs every time. Interestingly, if I instead double-click the C drive in the right pane of File Explorer, the subfolders are displayed and the BSOD does not occur. To avoid this problem, I have temporarily turned off Ransomware detection in MBAM. I've attached the minidump and and mb-check-results.zip files. Hope this matter can be resolved soon. Thanks Alex mb-check-results.zip 111817-36656-01.dmp
Back to top
×
×
  • 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.