Mourning the loss of our friend, WhitPhil.
There's no such thing as a stupid question, but they're the easiest to answer.
JoinTour
Login
Search
 
General Security
Tag Cloud
access audio blue screen boot bsod connection crash dell desktop driver drivers dvd email error excel excel 2003 firefox hard drive hardware internet keyboard laptop malware monitor motherboard network networking outlook problem processor ram recovery router safe mode screen slow sound spyware trojan upgrade vba video virus vista vundo windows windows 7 windows vista windows xp wireless
Search
Search for:
Tech Support Guy Forums > Security & Malware Removal > General Security >
ZoneAlarm causing Blue Screen of Death (BSOD) referencing fwpkclnt.sys

Tip: Click here to scan for System Errors and Optimize PC performance
[ Sponsored Link ]

Closed Thread
 
Thread Tools
jonseyh09's Avatar
Computer Specs
Junior Member with 26 posts.
 
Join Date: Sep 2006
Experience: Intermediate
09-Dec-2007, 07:52 PM #1
Angry ZoneAlarm causing Blue Screen of Death (BSOD) referencing fwpkclnt.sys
I am running Windows Vista Home Premium on a laptop about 2 months old. I have completely removed all traces of the pre-installed Norton 360 program using Symantec's removal program.

I am running AVG Anti-Virus (Free Version Only) I have disabled Windows Firewall and Windows Defender prior to installation, and downloaded the latest certified Vista-Compatible version.

The installer has been attempted "Run as Administrator" and also normally.

It gets to either 99% installed and then the BSOD happens or else it gets to Setting up ZoneAlarm and then the BSOD happens.

I see

STOP 0x000000D1 IRQL_NOT_LESS_OR_EQUAL

and fwpkclnt.sys a bit further down on the screen.

Windows does a full memory dump. I have tried everything I can find on ZoneAlarm's support forums and still no luck! (http://forum.zonelabs.org/zonelabs/b...ssage.id=74279)

What is ZoneAlarm's problem with Windows Vista and any idea what to do to fix it?
I don't want to use Windows built-in crappy firewall!

and yes, I do know that fwpkclnt.sys has something to do with the Windows Firewall....I just want a better firewall than that POS!

Operating System: Windows Vista Home Premium
ZoneAlarm Software Version: 7.1.x (Vista-compatible)
Product Name: ZoneAlarm (Free)

I have also posted this in the Windows Vista forum, because I couldn't figure out which to use. Sorry.
jonseyh09's Avatar
Computer Specs
Junior Member with 26 posts.
 
Join Date: Sep 2006
Experience: Intermediate
09-Dec-2007, 08:25 PM #2
UPDATE: I ran Microsoft Windows Debugging Tools (available at: http://www.microsoft.com/whdc/devtoo...g/default.mspx) and this is what I got.

Hope this helps!

*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000078, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8e6831f2, address which referenced memory

Debugging Details:
------------------






READ_ADDRESS: 00000078

CURRENT_IRQL: 2

FAULTING_IP:
fwpkclnt!FwpsQueryPacketInjectionState0+46
8e6831f2 8b4878 mov ecx,dword ptr [eax+78h]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: 9b62f52c -- (.trap 0xffffffff9b62f52c)
ErrCode = 00000000
eax=00000000 ebx=00002006 ecx=9a860da0 edx=00000000 esi=9a957c98 edi=84062a98
eip=8e6831f2 esp=9b62f5a0 ebp=9b62f5a4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
fwpkclnt!FwpsQueryPacketInjectionState0+0x46:
8e6831f2 8b4878 mov ecx,dword ptr [eax+78h] ds:0023:00000078=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8e6831f2 to 81c8fd84

STACK_TEXT:
9b62f52c 8e6831f2 badb0d00 00000000 88ba342d nt!KiTrap0E+0x2ac
9b62f5a4 88ba3688 9a957c98 860ce1d0 9b62f664 fwpkclnt!FwpsQueryPacketInjectionState0+0x46
WARNING: Stack unwind information not available. Following frames may be wrong.
9b62f65c 87837ded 9b62f8f4 9b62f7dc 860ce1d0 avgwfp+0x3688
9b62f6a4 878391f4 00000004 9b62f8f4 9b62f7dc NETIO!ProcessCallout+0x10e
9b62f6d4 878391a2 00000004 9bf071a0 9b62f8f4 NETIO!ProcessFastCalloutClassify+0x2c
9b62f7b4 8e703243 00000004 9b62f8f4 9b62f7dc NETIO!KfdClassify+0xb2
9b62f90c 8e701669 8e9f7020 977da284 8e9f6008 tcpip!ShimIpPacketOutV4+0x15b
9b62f940 8e6c4480 00000000 8e9f7020 977da284 tcpip!IppInspectLocalPacketsOut+0x5c
9b62f994 8e701e41 9b62f9bc 8e74b9c8 00000000 tcpip!IppLoopbackEnqueue+0xa1
9b62f9d0 8e701601 8e74b9c8 860c10c0 8e74b9c8 tcpip!IppDispatchSendPacketHelper+0x130
9b62fa68 8e700e01 0062fadc 8e74b9c8 8e9f4008 tcpip!IppPacketizeDatagrams+0x7ea
9b62fbc0 8e729a9a 00000000 00000004 8e74b9c8 tcpip!IppSendDatagramsCommon+0x4ab
9b62fc58 8e683e9d 00000000 00000004 86ffbc28 tcpip!IppInspectInjectTlSend+0xd7
9b62fcb4 a9842b73 840209e8 00000000 0000000e fwpkclnt!FwpsInjectTransportSendAsync0+0x220
9b62fd04 a9842d0c 86ffbc28 8458ad00 84538520 vsdatant+0x25b73
9b62fd2c a9843088 8458ad00 00000000 84538520 vsdatant+0x25d0c
9b62fd40 a9841d9c 84538520 84538520 9b62fd7c vsdatant+0x26088
9b62fd50 a9841e92 84538520 841f8020 00000000 vsdatant+0x24d9c
9b62fd7c 81e25526 a986b8c0 9b624680 00000000 vsdatant+0x24e92
9b62fdc0 81c9159e a9841e00 a986b8c0 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
fwpkclnt!FwpsQueryPacketInjectionState0+46
8e6831f2 8b4878 mov ecx,dword ptr [eax+78h]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: fwpkclnt!FwpsQueryPacketInjectionState0+46

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: fwpkclnt

IMAGE_NAME: fwpkclnt.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4549b2f6

FAILURE_BUCKET_ID: 0xD1_fwpkclnt!FwpsQueryPacketInjectionState0+46

BUCKET_ID: 0xD1_fwpkclnt!FwpsQueryPacketInjectionState0+46

Followup: MachineOwner
---------
Closed Thread Bookmark and Share

THIS THREAD HAS EXPIRED.
Are you having the same problem? We have volunteers ready to answer your question, but first you'll have to join for free. Need help getting started? Check out our Welcome Guide.

Smart Search

Find your solution!



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
WELCOME TO TECH SUPPORT GUY! Are you looking for the solution to your computer problem? Join our site today to ask your question -- for free! Our site is run completely by volunteers who want to help you solve your computer problems. See our Welcome Guide to get started.

Thread Tools


You Are Using:
Server ID
Advertisements do not imply our endorsement of that product or service.
All times are GMT -5. The time now is 11:57 AM.
Copyright © 1996 - 2009 TechGuy, Inc. All rights reserved.
Powered by vBulletin, Copyright © 2000 - 2009, Jelsoft Enterprises Ltd.
Powered by Cermak Technologies, Inc.