1423277 - blue screens (KMODE EXPECTION NOZ HANDLED) since Firefox 57.0

Status: RESOLVED FIXED

(External Software Affecting Firefox :: Other, defect)

Description

[Gaspedal]

Attachment: 120317-9453-01.dmp

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20171024165158

Steps to reproduce:

I have sometimes Bluescreens since Update to 57.0.0 or .1
Every time during closing Tabs or after Closing Firefox Window, after wathing Youtube Videos and closing the tab...

Error message: 

KMODE EXPECTION NOZ HANDLED
CLASSPNP.SYS

A lot of users have the same issue after Update to Firefox 57.x
I'm now going back to 56.0.2 and it works fine and I don't have blue screens with firefox.

I have Intel i7 2600k, 16 GB Ram DDR3, GTX 1080, Windows 10 Fall Creators Update


Actual results:

After closing Firefox or a Tab I have get a blue screen 


Expected results:

nothing, only closing Firefox Windows or Tab without bluescreen

Comment 1

[YF (Yang)]

https://www.tenforums.com/bsod-crashes-debugging/99421-bsod-kmode_exception_not_handled-classpnp-sys.html

This may be a compatibility issue from Kaspersky driver.

Comment 2

[Gaspedal]

yes, I use Kaspersky too. As said, Firefox 56.0.2 works fine, only the 57.0.1 causes blue screens.

Comment 3

[Gaspedal]

A user has wrote: "I can confirm that is the case for me as well. The last time I got it I just closed Firefox.... and the time before it I was just browsing YouTube."

I can confirm this, exactly the same thing!

Comment 4

[Gaspedal]

tracking? Sorry for my bad english. You missing a info?

Comment 5

[YF (Yang)]

(In reply to Gaspedal from comment #4)
> tracking? Sorry for my bad english. You missing a info?

No, this is a message to release managers.
https://wiki.mozilla.org/BMO/UserGuide#Tracking_Flags

Comment 6

[Marco Castelluccio [:marco]]

Can you reproduce this bug if you uninstall Kaspersky?

Comment 7

[Marco Castelluccio [:marco]]

Anyway, I've contacted Kaspersky about this problem.

Comment 8

[Gaspedal]

Thanks! not tested yet,  I'll today test it without kaspersky after work.

Comment 9

[Alexey Totmakov]

It is our (Kaspersky) fault. We have “anti-cryptor” feature, which can safe user files, if malicious software crypt it. There were bug in this feature driver, which sometimes lead to BSOD. There was one more bug, FireFox 57 identifies as unknown software, which should be deeply monitored. Combination of this two bugs lead to often BSOD if Kaspersky 2018 and FireFox 57 installed on the computer.

Tomorrow we are going to update our bases, to minimize the problem. I let you know, when update happens. Complete fix will be with KIS2018 patch E before 15-Dec-2017. Also let you know.

Comment 10

[Gaspedal]

great news! Thanks a lot in advance for this great support!

Comment 11

[Alexey Totmakov]

We update our (Kaspersky) bases, problem with FireFox 57 should not reproduced any more.

Comment 12

[Marco Castelluccio [:marco]]

Gaspedal, can you verify that you can't reproduce this problem anymore with the latest Kaspersky?

Comment 13

[Gaspedal]

I'll test it. Have today installed 57.0.2 again.

Comment 14

[Gaspedal]

seems to work, no BSOD today :)

Comment 15

[Marco Castelluccio [:marco]]

Thanks!

Comment 16

[xlollomanx]

I'm still getting this bsod. I reinstalled kaspersky yesterday and all works fine, but today I get this bsod again.
I have AMD Ryzen 1600,8GB Ram DDR4,GTX 1060, Windows 10 (1709)

Comment 17

[Alexey Totmakov]

(In reply to xlollomanx from comment #16)
> I'm still getting this bsod. I reinstalled kaspersky yesterday and all works
> fine, but today I get this bsod again.
> I have AMD Ryzen 1600,8GB Ram DDR4,GTX 1060, Windows 10 (1709)

Did you update to latest version of Kaspersky bases? What Kaspersky version do you have?

Comment 18

[xlollomanx]

(In reply to Alexey Totmakov from comment #17)
> (In reply to xlollomanx from comment #16)
> > I'm still getting this bsod. I reinstalled kaspersky yesterday and all works
> > fine, but today I get this bsod again.
> > I have AMD Ryzen 1600,8GB Ram DDR4,GTX 1060, Windows 10 (1709)
> 
> Did you update to latest version of Kaspersky bases? What Kaspersky version
> do you have?

I'm on KIS 18.0.0.405(d) and firefox 57.0.2. I force update on kaspersky so I think I'm good...right? I tried to attach my minidump but I get error or maybe I'm doing something wrong.

Comment 19

[Alexey Totmakov]

(In reply to xlollomanx from comment #18)
> I think I'm good...right? I tried to attach my minidump but I get error or

It seems to me you did all right.

But as i wrote in comment #9, with latest base updates we minimize the problem, but not completely solve it. To completely solve the problem we are going to release KIS2018 patch E during this week.

Comment 20

[xlollomanx]

(In reply to Alexey Totmakov from comment #19)
> (In reply to xlollomanx from comment #18)
> > I think I'm good...right? I tried to attach my minidump but I get error or
> 
> It seems to me you did all right.
> 
> But as i wrote in comment #9, with latest base updates we minimize the
> problem, but not completely solve it. To completely solve the problem we are
> going to release KIS2018 patch E during this week.

Yes, I imagine something like that...before the patch I got almost 10 crash in a day, today I got only one crash. I'll wait patiently the update :)

Comment 21

[Alexey Totmakov]

KIS2018 patch E was fully published today. BSOD from Kaspersky should be gone.

Comment 22

[Marco Castelluccio [:marco]]

(In reply to xlollomanx from comment #20)
> (In reply to Alexey Totmakov from comment #19)
> > (In reply to xlollomanx from comment #18)
> > > I think I'm good...right? I tried to attach my minidump but I get error or
> > 
> > It seems to me you did all right.
> > 
> > But as i wrote in comment #9, with latest base updates we minimize the
> > problem, but not completely solve it. To completely solve the problem we are
> > going to release KIS2018 patch E during this week.
> 
> Yes, I imagine something like that...before the patch I got almost 10 crash
> in a day, today I got only one crash. I'll wait patiently the update :)

xlollomanx, can you verify that you are no longer experiencing the crash?

Comment 23

[xlollomanx]

Yes, completely fixed. Sorry for this late reply, but on normal github this notification was not segnaled