Jump to content
colebantam

KIS related BSOD on Windows Update KB3013769

Recommended Posts

Installing KB3013769 (December Update Rollup for Windows 8.1) resulted in a BSOD on my Notebook Windows 8.1 Pro 32Bit. On my Desktop (64Bit) with KIS 2014 the update went fine.

I was able to spot klif.sys in the short Bluescreen error-report. Disabling protection didn't resolve the problem, updating definitions also. I'll uninstall KIS and try to install the update then. Ill update that report when I have news..

 

Wanted to give a quick feedback on that...

Share this post


Link to post

OK, problem is confirmed for me...

 

After Uninstall of KIS 2015 (v15.0.1.415), KB3013769 installed without a problem.

After I reinstalled KIS, the Notebook crashed again on Boot.

Share this post


Link to post

Update:

The Notebook crashes on all versions of KIS since 2014 now, with KB3013769 installed.

On the Boot with KIS 2014, the Errormessage stayed a bit longer on top, so I was able to read, that its "kl1.sys" causing the problem, not klif.sys as I told before.

Since there are quiete some views on this topic, but no replies now, I'll open a case with Kaspersky Support Team.

Share this post


Link to post

Win 8.1 32-bit. Kaspersky Internet Security 2014. Microsoft's December 2014 roll up of recommended updates ran fine.

After all completed and rebooted, I then installed two optional updates: KB3013769 and KB3013816. Machine blue-screened.

I recovered with Advanced Repair Options -> Trouble Shoot -> Advanced Options -> Windows Startup Settings -> Restart. After this sequence Win8.1 fixed itself by removing both of these optional updates.

 

I have no idea if Kaspersky was responsible for the problem, but it was present.

Edited by markf2748

Share this post


Link to post

Hallo,

 

same problem with Win 8.1, 32 bit and Internet Security 2015 15.0.0.463 b. But no chrash on Systems with a Win 8.1 64 bit Version...

 

The problem comes definitely with the optional Win KB3013769 Update. I had to set the computer to a restore point. At the Moment it runs fine without KB3013769.

 

Any solutions?

 

Greets,

 

Matthias

Edited by Matte

Share this post


Link to post

Same here with KAV 15.0.1.415(B). After installing KB3013769 Windows 8.1 Update 1 x86 crashes during boot (BSOD) with following message: SYSTEM_THREAD_EXCEPTION kl1.sys. I will post GSI if necessary.

 

Now we will probably have to wait for new kl1.sys or KB3013769v2.

Edited by Sass Drake

Share this post


Link to post

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

 

Please attach the following items to your Tech Support request:

 

1. Description of the issue.

2. Causing task/component, if known.

3. GSI

4. Causing task/component Report.

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

If causing component is known, we need traces only with this component enabled.

Share this post


Link to post
I have the same problem with KB3013769 and Windows 8.1. I use KAV 2015.

 

I forgot, it is a 32bit.

Share this post


Link to post
Installing KB3013769 (December Update Rollup for Windows 8.1) resulted in a BSOD on my Notebook Windows 8.1 Pro 32Bit. On my Desktop (64Bit) with KIS 2014 the update went fine.

I was able to spot klif.sys in the short Bluescreen error-report. Disabling protection didn't resolve the problem, updating definitions also. I'll uninstall KIS and try to install the update then. Ill update that report when I have news..

 

Wanted to give a quick feedback on that...

 

Hello.

 

Please follow the steps richbuff provided. In addition to that, please collect and attach a complete memory dump to the incident.

 

Thank you.

Share this post


Link to post

Hello all, my Lenovo Miix 2 8 Windows 8 32-bit tablet is getting a BSOD preventing boot up when installing this update.

 

Initially I wasn't sure what it was or which update caused it so I done a full clean reset and began installing the updates. By time I got round (1.5GB of updates later) to installing KB3013769 I received another BSOD.

 

I currently don't have Kaspersky AV 2015 installed after my second clean install and I'm plain refusing to install the update due to the time it takes to download and re-install 1.5GB of updates. I'll send a report to support without a memory dump etc. as I'm now not willing to replicate the issue (for a third time).

 

Which reminds me, I need to check my Dad's laptop later and hide the update. I've used Kaspersky for the last 6 years, disappointing to say the least.

Edited by nick0323

Share this post


Link to post
Which reminds me, I need to check my Dad's laptop later and hide the update. I've used Kaspersky for the last 6 years, disappointing to say the least.

 

 

I would blame Microsoft rather than Kaspersky. :)

 

Share this post


Link to post

Same problem here after installing MS KB3013769 on Win 8.1 32 bit. I am running KAV 15.0.1.415(B.) on my computer. Had to use restore point to get computer to boot up. Installed regular updates with no problem after restoring.

 

edit: (b.) sted cool.gif.

Edited by richbuff

Share this post


Link to post

Hi everybody!

Yes, the problem is reproduced only on x86. Thank you all for the information, we already contacted with Microsoft to solve this issue.

Share this post


Link to post
Installing KB3013769 (December Update Rollup for Windows 8.1) resulted in a BSOD on my Notebook Windows 8.1 Pro 32Bit. On my Desktop (64Bit) with KIS 2014 the update went fine.

I was able to spot klif.sys in the short Bluescreen error-report. Disabling protection didn't resolve the problem, updating definitions also. I'll uninstall KIS and try to install the update then. Ill update that report when I have news..

 

Wanted to give a quick feedback on that...

 

Dear Friends,

 

Please be kindly informed that On December 10, Microsoft released an update - labeled KB3013769 - Optional update for Windows 8.1 and Windows Servers 2012 R2. Unfortunately, installation of this patch on PCs with some of Kaspersky Lab’s products has resulted in system errors including the inability to boot their machines. KB3013769 is not a critical system patch, and its installation is optional. Incompatibility was detected only with Windows 8.1 x86.

 

In case this update was already installed, a workaround to restore computer functionality is available by contacting Kaspersky Lab’s technical support team.

 

Also please check the workaround if you don’t want to contact tech support:

 

1) At the Windows 8.1 “Automatic Repair” error screen following an unsuccessful boot, select “Advanced Options,” followed by the “Troubleshoot” button on the next screen. Then, in the Troubleshoot menu, select the “Advanced Options” button.

2) Select the “System Restore” button, and log in as an Administrator with the proper password. Select the most recent system restore point that was created before the Microsoft patch was installed.

3) Follow the prompts to restore the PCs settings to their previous state, then reboot the PC.

 

Our experts are working in cooperation with Microsoft specialists to develop an update that will automatically fix this issue. Kaspersky Lab apologizes for any inconvenience this incident may have caused.

 

Best Regards,

Kaspersky Lab Technical Support

Share this post


Link to post

Damn, I should have looked into the thread earlier, before I tried to collect a Crash-Dump two times today - would have saved me a lot of time ;)

 

Well, at least I can say, it seems not to be possible to collect a crashdump. Tried it with "FullMemoryDump" and "KernelMemoryDump". In both settings, the notebook is not able to write a dump, the %-counter stays at 0%. The exact error in the screen is: SYSTEM_THREAD_EXEPTION_NOT_HANDLED (kl1.sys)

 

I'm desolate seeing KL blaming Microsoft. I'm guessing its all about Kaspersky still doing Kernel-patching on 32bit systems thus leading to that crash. In my opinion, Microsoft (as being the manufacturer) has all rights to modify the kernel internally. The question is, should Kaspersky really continue to rely on kernel patching? Especially when the most current systems are 64bit by the times now, and kernel patching isn't possible there any more (luckily).

 

As said, I'm only guessing and I'm not a developer, but this makes sense. My personal recommendation (or plea ;)) to KL is - disable the kernel patching on 32bit systems (saves also developer resources ;)) and don't worry about kernel-updates in the future any more...

Share this post


Link to post

Hello everybody,

 

it works now :) - the update was installed successfully.

 

Thanks

Wulf

 

Share this post


Link to post
Guest
This topic is now closed to further replies.

×
×
  • 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.