BSD, blue screen of death suddenly.

[ng2015gr 0]

Hi, I have used Emisoft Internet Security for some months, without problems.

 

Suddenly one or two weeks ago, can't remember, it started the computer to have blue screen of death constantly.

 

I thought it was some kind of program, maybe a vpn driver or so, so I formated the laptop ( DELL I7 N5110 with ssd samsung) and installed everything from scratch and then made a backup with Acronis True Image  for just in case.

 

Again, after installation of EIS it started t have blue screens. Here is what it says...

 

______________

 

Ticket ID     #RER-253-96236
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 9/12/2014 7:42:30 πμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\120914-10264-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002E80C3F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed

paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware

problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver

that cannot be identified at this time.



On Tue 9/12/2014 7:42:30 πμ GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fwwfp764.sys (fwwfp764+0x623B)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002E80C3F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Program Files (x86)\Emsisoft Internet Security\fwwfp764.sys
product: Emsisoft Firewall SDK
company: Emsisoft GmbH
description: Emsisoft Firewall Engine
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed

paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware

problem.
A third party driver was identified as the probable root cause of this system error. It is

suggested you look for an update for the following driver: fwwfp764.sys (Emsisoft Firewall

Engine, Emsisoft GmbH).
Google query: Emsisoft GmbH IRQL_NOT_LESS_OR_EQUAL

________________

Can you please tell me what to do ?

Thank you.

[ng2015gr 0]

Forgot to attach the file

120914-10264-01.dmp

[ng2015gr 0]

the hotfix from microsoft says it's not applicable to my computer.

Windows 6.1- KB2958399-X86

 

Edited.

I installed the x64 version of the above file, now it rebooted, I'll check if will show up blue screen or not, actually, when online it shows and it gets shown up more  quickly if I use google chrome...God Bless Google lol...and Vpn...actually it makes sense, since vpn is for hiding and google is for nothing to hide...LOL!...just joking, will inform you if anything got better.

[ng2015gr 0]

After installing the update x64 and rebooting, am still testing the I7, am currently logged in with vpn and surfing with Google chrome, I wanted to ask also something else.

With online armor, when I tested the computer with shields up through www.grc.com  all ports were stealth, now when I test it with EIS lots of ports are just closed but not stealth. When you combined the two of them in one, did you take off some of the security that the firewall had?

 

Thank you.

[Fabian Wosar 390]

Did you go to GRC with your VPN enabled? If you did, Shields Up will scan your VPN exit node and not your system. Same is true if you use some kind of router. In that case Shields Up will scan your router but not your system. Port scan services on the internet only work if your system is connected directly to the internet.

[badsektor 0]

Hi there,

 

I have the same problem from some time (~1 month). I did not change anything in my hardware. Yesterday I did complete format, I double check my RAM with memtest (0 errors), hdd - no bad sectors,

I still have random crash with Error: IRQL_NOT_LESS_OR_EQUAL

 

Here are the results of my crashes (files in attachment):

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 2014-12-09 06:39:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120914-8205-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002ED3C3F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 2014-12-09 06:39:59 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fwwfp764.sys (fwwfp764+0x623B)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002ED3C3F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Program Files (x86)\Emsisoft Internet Security\fwwfp764.sys
product: Emsisoft Firewall SDK
company: Emsisoft GmbH
description: Emsisoft Firewall Engine
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: fwwfp764.sys (Emsisoft Firewall Engine, Emsisoft GmbH).
Google query: Emsisoft GmbH IRQL_NOT_LESS_OR_EQUAL



On Tue 2014-12-09 06:38:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120914-7488-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002EE3C3F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

My PC spec is:

- P8Z77-V PRO

- i5-3570K

- 16GB RAM DDR3 2400

- SSD 120gb samsung 830

- Windows 7 x64

 

Unlike to our collegue above I have only Firefox and IE. I do not connect via VPN. I am connected by UPC modem through cable.

I do not change anything in EIS after install.

In past I had no problem with AM or OA. After some time with EIS I got this weird bsod.

 

Please let us know how we can handle this issue.

Thanks in advance!

120914-7488-01.dmp

120914-8205-01.dmp

[badsektor 0]

the hotfix from microsoft says it's not applicable to my computer.

Windows 6.1- KB2958399-X86

 

Edited.

I installed the x64 version of the above file, now it rebooted, I'll check if will show up blue screen or not, actually, when online it shows and it gets shown up more  quickly if I use google chrome...God Bless Google lol...and Vpn...actually it makes sense, since vpn is for hiding and google is for nothing to hide...LOL!...just joking, will inform you if anything got better.

 

I skipped this post huh..

Fix installed.. now I am waiting for results. I will let know if bsod happen again.

[Fabian Wosar 390]

Fix installed.. now I am waiting for results. I will let know if bsod happen again.

It won't . Your mini dumps indicate your system was missing that hot fix. Since you installed the hot fix now, the BSOD won't happen again.