[Fixed] Bsod Stop Error Caused By Bdfwfpf.sys

crankyoldbugger · January 2016

This issue is mentioned in the Bitdefender 2015 forums as well.

I am getting several (at least four) reboots every day preceeded by BSOD screens that say the failure is caused by bdfwfpf.sys.

Is there any fix for this yet?

I am using Biddefender Total Security 2016 on a Windows 7 SP1 machine.

Rohugh · January 2016

Hiya, love your user name so welcome to the forums.

Have you run a repair of Bitdefender? If not, run one - Windows Control Panel>Programs and Features>Bitdefender. Double click it and choose "Repair". When it is all done and your system has rebooted let us know if that has solved the problem.

Ro.

crankyoldbugger · January 2016

Hiya, love your user name so welcome to the forums.

Have you run a repair of Bitdefender? If not, run one - Windows Control Panel>Programs and Features>Bitdefender. Double click it and choose "Repair". When it is all done and your system has rebooted let us know if that has solved the problem.

Ro.

Thanks, Ro. Sorry I didn't get your message until tonight. I will do the repair now and let you know what happens.

Also, under Programs and Features I have both "Bitdefender Total Security 2016" and "Bitdefender Agent". I'll test with the first one tonight.

crankyoldbugger · January 2016

Thanks, Ro. Sorry I didn't get your message until tonight. I will do the repair now and let you know what happens.

Also, under Programs and Features I have both "Bitdefender Total Security 2016" and "Bitdefender Agent". I'll test with the first one tonight.

OK, I think that made things a bit worse! (not criticizing you, Ro)

I did the Repair option, and now the BD firewall won't start. The main screen says "You are at risk, Fix all issues!" If I click on "Fix all", it says that the firewall is disabled (status Not started). If I click on Fix, it looks fixed for a moment then goes back to disabled.

I woke this morning to a login screen which tells me that the firewall is still crashing the computer.

What's the next plan?

Georgia · January 2016

Hi crankyoldbugger,

Try this fix for the Bitdefender firewall on Windows 7 machines:

http://www.bitdefender.com/support/cannot-...ewall-1536.html

If the BSOD still occurs, we need the latest dump from C:\Windows\Minidump and a Bitdefender diagnostic log from the affected PC.

Thank you!

crankyoldbugger · January 2016

Hi crankyoldbugger,

Try this fix for the Bitdefender firewall on Windows 7 machines:

http://www.bitdefender.com/support/cannot-...ewall-1536.html

If the BSOD still occurs, we need the latest dump from C:\Windows\Minidump and a Bitdefender diagnostic log from the affected PC.

Thank you!

Hi Georgia,

Unfortunately the instructions on that link didn't do anything; I'm still unable to start the firewall. And this morning my computer crashed again, so we're not much further ahead.

I did however run the the diagnostic tool, so hopefully you got that report sent in. I've also attached the latest minidump (zipped).

Thanks to you and Ro for your assistance thus far.

Georgia · January 2016

Hello, where did upload the reports? I didn't receive them here on the forums nor at bitsy@bitdefender.com

Could you please upload them to a file transfer site such as https://www.wetransfer.com/ and either post back the download link or send it to us at the above mentioned email address?

Thank you so much for your cooperation.

crankyoldbugger · January 2016

Hello, where did upload the reports? I didn't receive them here on the forums nor at bitsy@bitdefender.com

Could you please upload them to a file transfer site such as https://www.wetransfer.com/ and either post back the download link or send it to us at the above mentioned email address?

Thank you so much for your cooperation.

Hi Georgia,

I just resent them to bitsy@bitdefender.com. Please let me know if you got them, or not.

Thanks,

Jeff

Georgia · January 2016

Hello,

I have received your email. I will need a complete memory dump to forward it to our developers for a fix.

I will open a ticket in our support platform and send you an email asap.

*later edit: the ticket number is 2016011511480001

This is what I see in the minidump:

Executable search path is:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.19110.amd64fre.win7sp1_gdr.151230-0600

Machine Name:

Kernel base = 0xfffff800`03014000 PsLoadedModuleList = 0xfffff800`0325b730

Debug session time: Thu Jan 14 13:45:31.243 2016 (UTC + 2:00)

System Uptime: 0 days 0:02:03.804

Loading Kernel Symbols

.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.

..............................................................

................................................................

...........................................

Loading User Symbols

Loading unloaded module list

......

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {12, fffff88001a72b88, 0, 2}

Probably caused by : bdfwfpf.sys ( bdfwfpf!BdfDispatch+0 )

Followup: MachineOwner

---------

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)

The IO manager has caught a misbehaving driver.

Arguments:

Arg1: 0000000000000012, IRQL not equal across call to driver dispatch routine

Arg2: fffff88001a72b88, Driver dispatch routine address.

Arg3: 0000000000000000, IRQL before calling driver dispatch routine.

Arg4: 0000000000000002, Current IRQL.

Debugging Details:

------------------

BUGCHECK_STR: 0xc9_12

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 12

FAULTING_IP:

bdfwfpf!BdfDispatch+0 [d:\work\fw\15.0.0.1\src\ndisim\bdflibf\libmain.c @ 330]

fffff880`01a72b88 4883ec28 sub rsp,28h

FOLLOWUP_IP:

bdfwfpf!BdfDispatch+0 [d:\work\fw\15.0.0.1\src\ndisim\bdflibf\libmain.c @ 330]

fffff880`01a72b88 4883ec28 sub rsp,28h

PREVIOUS_IRQL: 0

CURRENT_IRQL: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: vsserv.exe

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

DEVICE_OBJECT: fffffa80106c2dc0

LAST_CONTROL_TRANSFER: from fffff80003114d00 to fffff80003087c00

STACK_TEXT:

fffff880`09f75898 fffff800`03114d00 : 00000000`000000c9 00000000`00000012 fffff880`01a72b88 00000000`00000000 : nt!KeBugCheckEx

fffff880`09f758a0 fffff800`03533b6b : fffffa80`0e419e40 fffff800`03393f9b fffffa80`107cc270 fffff880`01a72bb3 : nt!VfBugCheckNoStackUsage+0x30

fffff880`09f758e0 fffff800`03539d5e : fffff980`175c0ee0 fffff980`175c0ee0 00000000`00000002 fffffa80`0e419e40 : nt!VfAfterCallDriver+0x22b

fffff880`09f75930 fffff800`03393f9b : 00000000`00000002 fffffa80`106c2dc0 00000000`00000000 fffffa80`107cc270 : nt!IovCallDriver+0x57e

fffff880`09f75990 fffff800`033a7dfa : fffffa80`106c2dc0 00000000`00000000 fffffa80`106c2dc0 00000000`00000000 : nt!IopSynchronousServiceTail+0xfb

fffff880`09f75a00 fffff800`033a7e96 : fffff880`09f75bf8 00000000`0000104c 00000000`00000000 00000000`259852f0 : nt!IopXxxControlFile+0xc27

fffff880`09f75b40 fffff800`03086e93 : 00000000`00001084 fffff880`09f75ca0 00000000`00000000 fffff800`033737cb : nt!NtDeviceIoControlFile+0x56

fffff880`09f75bb0 00000000`77bbda2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000000`2591fbb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bbda2a

STACK_COMMAND: .bugcheck ; kb

FAULTING_SOURCE_LINE: d:\work\fw\15.0.0.1\src\ndisim\bdflibf\libmain.c

FAULTING_SOURCE_FILE: d:\work\fw\15.0.0.1\src\ndisim\bdflibf\libmain.c

FAULTING_SOURCE_LINE_NUMBER: 330

SYMBOL_NAME: bdfwfpf!BdfDispatch+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bdfwfpf

IMAGE_NAME: bdfwfpf.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 508e7540

IMAGE_VERSION: 7.0.0.8

FAILURE_BUCKET_ID: X64_0xc9_12_VRF_bdfwfpf!BdfDispatch+0

BUCKET_ID: X64_0xc9_12_VRF_bdfwfpf!BdfDispatch+0

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xc9_12_vrf_bdfwfpf!bdfdispatch+0

FAILURE_ID_HASH: {6d214bd7-da9f-7b94-d643-edcba8b4ba02}

Followup: MachineOwner

---------

0: kd> lmvm bdfwfpf

start end module name

fffff880`01a6c000 fffff880`01a94000 bdfwfpf (private pdb symbols) c:\lsym\bdfwfpf.pdb\D6B9283350874877BDAEB09BF35C961A1\bdfwfpf.pdb

Loaded symbol image file: bdfwfpf.sys

Mapped memory image file: c:\lsym\bdfwfpf.sys\508E754028000\bdfwfpf.sys

Image path: \??\C:\Program Files\Common Files\Bitdefender\Bitdefender Firewall\bdfwfpf.sys

Image name: bdfwfpf.sys

Timestamp: Mon Oct 29 14:23:28 2012 (508E7540)

CheckSum: 0001DBFA

ImageSize: 00028000

File version: 7.0.0.8

Product version: 7.0.0.8

File flags: 8 (Mask 3F) Private

File OS: 40004 NT Win32

File type: 3.6 Driver

File date: 00000000.00000000

Translations: 0409.04b0

CompanyName: BitDefender LLC

ProductName: BitDefender Firewall

InternalName: bdfwfpf.sys

OriginalFilename: bdfwfpf.sys

ProductVersion: 7.0.0.8

FileVersion: 7.0.0.8 built by: WinDDK

FileDescription: BitDefender Firewall WFP Filter Driver

Georgia · March 2016

Hi,

Just a quick update to let you know that the cause of this BSOD was addressed in the latest build version 20.0.26.1418 which required a system reboot.

I now declare this topic closed.

[Fixed] Bsod Stop Error Caused By Bdfwfpf.sys

Comments

All Time Leaders

Categories

Defenders of the month