Windows 10: Windows Crashes once every time it is started works the 2nd time - driver verifier causes...

Hi,
Since the latest Windows Update my PC always crashes once after booting before showing the login mask but than reboots normally.
The related errors are:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050
and
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c4 0x0000000000002000, 0xfffff800bf221d93, 0x0000000000000000, 0x0000000000726274. A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: bdff82c6-115f-4337-aaf8-124354743c16.
and
Windows failed fast startup with error status 0xC0000001

I used driver verifier and it said "DRIVER_VERIFIED_DETECTED_VIOLATION"

I can also find some warnings such as:
WLAN Extensibility Module has stopped.
Module Path: C:\Windows\system32\IntelIHVRouter08.dll
But don't know if they are related

Minidumps:
https://1drv.ms/u/s!AkQc7QTqH_EOkaoqufXXPTun5fISGw?e=9ituqn

:)

 

Driver Verifier causes crashes incriminating

Hello, today I runned the tool "Driver Verifier" in order to stress my drivers to assure everything is okay. After rebooting, t got a BSOD caused by the antivirus Bitdefender.

On Mon 26/06/2017 14:13:44 your computer crashed

crash dump file: C:\Windows\Minidump\062617-8578-01.dmp

This was probably caused by the following module: bdfwfpf.sys (bdfwfpf+0x1203)

Bugcheck code: 0xC4 (0x2000, 0xFFFFF80D7DA11203, 0x0, 0x57464442)

Error: DRIVER_VERIFIER_DETECTED_VIOLATION

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

product: BitDefender Firewall

company: BitDefender LLC

description: BitDefender Firewall WFP Filter Driver

Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.

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: bdfwfpf.sys (BitDefender Firewall WFP Filter Driver, BitDefender LLC).

Google query: BitDefender LLC DRIVER_VERIFIER_DETECTED_VIOLATION

Is this normal or should I do something about it ?

Sorry but english is not my language.

Thanks.

 

Driver Verifier not cause windows 7 crashing

Hi,

Enabling driver verifier means it would stress the drivers. It is not necessary that a driver would crash. Poorly coded drivers or bad drivers causing BSOD only crash.

 

Driver Verifier BSOD on Start Up DRIVER_VERIFIER_DETECTED_VIOLATION

OK I'm going to keep this thread updated as I go through troubleshooting this issue.

As I have received no help with my minidumps, I am going through the process of learning to do it myself.

This seems
like a good guide to learn the very basics.

What has happened so far:

• New computer build, unstable windows install, slowly degrades to where the computer is unusable. Happens on multiple clean installs.

• Continuous error and critical messages in Event Viewer, some events of note are:
  • Event 219 Kernel-PnP, failed to load driver
  • Event 7031 service control manager (dozens on start up)

• First crash will happen on start up and it eventually degrades with below events.
  • Event 5 kernel general
  • Event 2 kernel-event-tracing
  • Event 3 kernel-event-tracing
  • Event 29 kernel-boot

• Tested hardware - no faults found

• Ran Driver Verifier and Windows will keep crashing with DRIVER_VERIFIER_DETECTED_VIOLATION until Driver Verifier is reset in safe mode

• Started this thread, PC became too unstable and had to do a system restore, restore had minimal changes (see above)
• Have not installed the applications and drivers removed after system restore.
• PC is heading down same road again, BSOD now appearing on startup.
• Ran Driver Verifier again - same resuslts
• Installed WinDBG to start analyzing new dumps from crashes that have been happening on startup.
  • dump 1 - pool_corruption
  • dump 2 - memory_corruption
  • dump 3 - memory_corruption
  • dump 4 - ntkrnlmp.exe

From the limited knowledge I got from the guide the only information I can get from WinDBG is shown above.

So that's where I am at the moment. My next step is to run Driver Verifier again and see what I can find.