BSOD with multiple errors

Question

Hi,

So I've been getting constant errors all of a sudden due to which I keep getting the BSOD! I ran a WhoCrashed analysis to check the issue and it seems that there are multiple different errors, most common being DRIVER_IRQL_NOT_LESS_OR_EQUAL

However it isn't just one module but multiple ones that keep failing. The most common one seems to be bddci.sys which is related to BitDefender although I've never installed BitDefender on my laptop.

Does anyone have any idea of what might be the issue. I've pasted a the analysis report below:

On Mon 11-10-2021 00:37:17 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101121-15156-01.dmp
This was probably caused by the following module: ndu.sys (0xFFFFF8056CF14425)
Bugcheck code: 0xD1 (0xFFFFB88EEBAB3140, 0x2, 0x1, 0xFFFFF8056CF14425)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ndu.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Network Data Usage Monitoring Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Mon 11-10-2021 00:37:17 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ndu.sys (0xFFFFF8056CF14425)
Bugcheck code: 0xD1 (0xFFFFB88EEBAB3140, 0x2, 0x1, 0xFFFFF8056CF14425)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ndu.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Network Data Usage Monitoring Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Sun 10-10-2021 19:33:26 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101021-16046-01.dmp
This was probably caused by the following module: bddci.sys (0xFFFFF80725A0F6BF)
Bugcheck code: 0xD1 (0xFFFFF80625A2BE20, 0x2, 0x0, 0xFFFFF80725A0F6BF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\bddci.sys
product: Bitdefender BDDCI
company: Bitdefender
description: BDDCI filter driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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: bddci.sys (BDDCI filter driver, Bitdefender).
Google query: bddci.sys Bitdefender DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Sun 10-10-2021 18:34:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101021-13656-01.dmp
This was probably caused by the following module: cng.sys (0xFFFFF8075EEE5F75)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8075EEE5F75, 0xFFFFCA8D321A6D20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Sun 10-10-2021 18:31:31 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101021-13406-01.dmp
This was probably caused by the following module: bddci.sys (0xFFFFF801604FF6BF)
Bugcheck code: 0xD1 (0xFFFFF8006051BE20, 0x2, 0x0, 0xFFFFF801604FF6BF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\bddci.sys
product: Bitdefender BDDCI
company: Bitdefender
description: BDDCI filter driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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: bddci.sys (BDDCI filter driver, Bitdefender).
Google query: bddci.sys Bitdefender DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Sun 10-10-2021 17:42:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101021-13156-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF804220FA320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.

Answer 1

Hi RoystenD'Sa

I am Dave, I will help you with this.

Yes, bddci.sys is a virtual driver associated to BitDefender.

Open File Explorer, then navigate to C:\Windows\System 32

Search for bddci.sys

If that file is found, then right click and choose rename, then rename that file to bddci.sys.old that will stop that driver loafing

Also, your network card driver seems to be causing the crashes, go to the support page for your PC on the manufacturers website, then from there, download and install the version of network card drivers they recommend.