deaf_2_intel_qaeda_hoores

Member
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About deaf_2_intel_qaeda_hoores

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I am well aware and doing this for the sake of advancement of technology, in hopes you guys will do your part and fix these drivers. I already deleted the program until this driver has been updated.
  2. On Sun 3/17/2019 8:27:32 PM your computer crashed or a problem was reported crash dump file: C:\Windows\MEMORY.DMP This was probably caused by the following module: fltmgr.sys (0xFFFFF8012E9941C2) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8012E9941C2, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\fltmgr.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Microsoft Filesystem Filter Manager 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. The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK. On Sun 3/17/2019 8:27:32 PM your computer crashed or a problem was reported crash dump file: C:\Windows\Minidump\031719-12312-01.dmp This was probably caused by the following module: fltmgr.sys (0xFFFFF8012E9941C2) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8012E9941C2, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\fltmgr.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Microsoft Filesystem Filter Manager 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. The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
  3. I am receiving BSOD's in windows without driver verifier, one such driver that continues to experience BSOD is Microsoft File System Filter Manager, FltMgr.sys, which emisoft File System Filter depends upon (epp.sys), here is the crash dump: More info from Microsoft Insider MVPs, who also suggested I remove these unstable drivers that do not pass windows driver verification. In order to be fully compatible and stable, they must pass windows driver verifier. Until then I will no longer use emisoft emergency kit, and see if the BSOD's disappear. I will keep you posted on my results in the coming days. More info below
  4. this should be reproducible on any win 10 machine with windows driver verifier enabled.
  5. Sandboxie had the same issue, when I told sandboxie staff, developers responded telling me Windows Driver Verifier was not compatible with sandboxie, Microsoft MVP dump specialist told me: That is absurd. The likely reason that Sandboxie "doesn't work" with Driver Verifier is because Driver Verifier flags the driver as it is probably poorly written and can't pass Driver Verifier's checks. System up-time was just 43 seconds when Sandboxie was flagged. It also somehow dragged win32k.sys (Microsoft driver) in with it. Every 3rd party driver should be able to pass Driver Verifier's tests. I in fact believe they do to be digitally signed.
  6. The latest stable release driver does not pass windows driver verification tests in windows 10 x64. https://www.wilderssecurity.com/threads/windows-firewall-control-wfc-by-binisoft-org.347370/page-198