Open Microsoft Store Version Wechat Blue Screen after Installing eset

[Chinese users 0]

I come to China, your agents in China can not provide technical support, I can only go to the official forum for help, only after installing eset, open Microsoft Store version of Wechat will be directly blue screen, I use WinDbg analysis, when the blue screen occurs, Windows Defender and ESET may conflict, because the stack of third-party applications only appear ESET and windows defender driver. I have acquired the full memory dump of the blue screen, but its storage capacity is too large. The original dump exceeds 8GB and is close to 3GB after compression. Please contact me to get the dump and find out the reason for the blue screen as soon as possible. Other security software does not have this problem. Only ESET has this problem.

The above is from Baidu Translation

Here's a screenshot of the blue screen of Microsoft Store.

[Marcos 5,074]

Most likely there's a problem with the OS. Windows Defender may not be active after installation of ESET and registration to the Security Center. Windows is supposed to turn it off completely.

[Chinese users 0]

4 minutes ago, Marcos said:

Most likely there's a problem with the OS. Windows Defender may not be active after installation of ESET and registration to the Security Center. Windows is supposed to turn it off completely.

We have tried to reinstall the system. The system is mirrored in the original version. The problem still exists. Give me an email address and I'll send the dump file.

[Marcos 5,074]

Please try the following:

- uninstall ESET
- rebuild WMI as per https://blogs.technet.microsoft.com/askperf/2009/04/13/wmi-rebuilding-the-wmi-repository/
- reinstall ESET
- check if Windows Defender is not active.

You can drop me a personal message with a link to a complete memory dump from a crash, however, if it's caused by Windows Defender there's nothing we could do. In such case you should try to install Windows from scratch, not to restore it from a mirror.

You can check it as follows:
With WD driver enabled:

C:\>sc query wdfilter

SERVICE_NAME: wdfilter
        TYPE               : 2  FILE_SYSTEM_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

With WD driver disabled:

C:\>sc query wdfilter

SERVICE_NAME: wdfilter
        TYPE               : 2  FILE_SYSTEM_DRIVER
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

 

[Chinese users 0]

7 hours ago, Marcos said:

Please try the following:

- uninstall ESET
- rebuild WMI as per https://blogs.technet.microsoft.com/askperf/2009/04/13/wmi-rebuilding-the-wmi-repository/
- reinstall ESET
- check if Windows Defender is not active.

You can drop me a personal message with a link to a complete memory dump from a crash, however, if it's caused by Windows Defender there's nothing we could do. In such case you should try to install Windows from scratch, not to restore it from a mirror.

You can check it as follows:
With WD driver enabled:

C:\>sc query wdfilter

SERVICE_NAME: wdfilter
        TYPE               : 2  FILE_SYSTEM_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

With WD driver disabled:

C:\>sc query wdfilter

SERVICE_NAME: wdfilter
        TYPE               : 2  FILE_SYSTEM_DRIVER
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

 

I'll wait until you finish the dump analysis before doing the operation. I just looked at it briefly before, maybe not the final conclusion.

Dump file download address: 

https://mail.qq.com/cgi-bin/ftnExs_download?k=09393966e7303937de71980e1e35004d56095a030d0653541a08005f5a180657560e145e0f53564f055b5a5f015157010f0d0d52383c322f72747634611b05183704&t=exs_ftn_download&code=799f852b

[Chinese users 0]

On 1/26/2019 at 3:02 AM, Marcos said:

Please try the following:

- uninstall ESET
- rebuild WMI as per https://blogs.technet.microsoft.com/askperf/2009/04/13/wmi-rebuilding-the-wmi-repository/
- reinstall ESET
- check if Windows Defender is not active.

You can drop me a personal message with a link to a complete memory dump from a crash, however, if it's caused by Windows Defender there's nothing we could do. In such case you should try to install Windows from scratch, not to restore it from a mirror.

You can check it as follows:
With WD driver enabled:

C:\>sc query wdfilter

SERVICE_NAME: wdfilter
        TYPE               : 2  FILE_SYSTEM_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

With WD driver disabled:

C:\>sc query wdfilter

SERVICE_NAME: wdfilter
        TYPE               : 2  FILE_SYSTEM_DRIVER
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

 

Does the dump file analysis come to a conclusion?