Jump to content

Recommended Posts

Hi,

I've been experiencing random BSODs since updating to KIS 2018. After digging around in the dump file (see attached), I've noticed that wcnfs.sys is the culprit. After searching for wcnfs.sys, it lead me to Kaspersky Internet Security. Is there some kind of errant bug that made it past beta testing? My PC is no more than 2 months old, and is running Windows 10 Pro 1705 x64.

 

Peter 

082817-33875-01.dmp

Share this post


Link to post

Welcome. 1. Please post your GetSystemInfo report link, instructions are located in the third (3rd) pinned topic. 

Please see the small print that is located at the bottom of this message. 

 

2. Please contact Tech Support: https://my.kaspersky.com/support/

Please attach the following items to your Tech Support request: 

1. Description of the issue. 

2. GSI

3. Traces Please disable traces when done, or your hard drive will get full. 

4. Full Dump (MEMORY.DMP) Please, no mini-dumps, kernel dumps etc.

Share this post


Link to post

Hi richbuff

Thanks for the reply, I've just submitted the issue to Tech Support with all the relevant files. Seems to be a software bug or driver issue to me.

Share this post


Link to post

Same problem for me.

I remove kis 2018, downloaded and install 2017: now no more BSOD.

 

Please, have you find an resolution to this issue ?

(i have only 3 minidumps)

Share this post


Link to post

Hi acetone802000

Many thanks for your post. The recommendation from Kaspersky labs Moscow is to stick with KIS 2017, as the bug found is so deep within the code that it cannot be fixed until the 2019 version. I hope this helps.

Peter 

Share this post


Link to post

Good day,

Actually it's planned to released the fix into upcoming patch D for 2018

Share this post


Link to post

 

В 15.09.2017 в 18:59, wagnerp сказал:

Hi

Many thanks for the update. Is there a ETA for when patch D is likely to come out?

Hello, @wagnerp!

we expect the patch release at the middle of october.

 

Share this post


Link to post

Hello @Mefodys,

Many thanks for the update. I shall wait for patch D before upgrading to KIS 2018. But for now, I'll stick with the more stable KIS 2017.

Share this post


Link to post

Hello all

Looking into Patch D release notes, there is no mention to this bug.

Is it fixed or not?

Share this post


Link to post

×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.