Recurring BSODs after using openVPN

Hello everyone,
I installed openVPN recently to channel my traffic through a virtual private network. I've been using it in conjunction with other p2p software. The problem seems to reoccur heavily when I'm on p2p (Vuze, then utorrent). I uninstalled Vuze shortly after it caused heavy BSODs. uTorrent has been a bit forgiving, but I noticed the system restarted earlier while I was away from the computer.

Now, I'm not sure if the root of the problem is due to openVPN or p2p. The system is stable while I'm on the VPN using openVPN and doing other tasks (browsing, etc). I've had about 5-6 BSODs since yesterday, so I'm targeting the issue to be a recent outbreak in the system.
The BSODs so far (and as far as I know) have always occurred while I'm downloading and uploading via p2p. I haven't had the problem occur during other tasks. I've attached the system report as directed. I'd appreciate any help regarding this. Thank you.

Dump analysis if that helps in identifying the problem. From what I've learned, this could be an issue relating to BitDefender.
Any help would be much appreciated. Thank you

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 4/14/2014 8:19:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041414-20311-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0xFFFFFFFF, 0x2, 0x0, 0xFFFFF8000320C9BC)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 4/14/2014 8:19:26 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC5 (0xFFFFFFFF, 0x2, 0x0, 0xFFFFF8000320C9BC)
Error: DRIVER_CORRUPTED_EXPOOL
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 4/14/2014 1:42:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041314-26598-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x290008, 0xFFFFFA800FCE1610)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Sun 4/13/2014 10:21:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041314-29281-01.dmp
This was probably caused by the following module: bdfndisf6.sys (0xFFFFF88001C0BA4A)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF88001C0BA4A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\bdfndisf6.sys
product: BitDefender Firewall
company: BitDefender LLC
description: BitDefender Firewall NDIS6 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 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: bdfndisf6.sys (BitDefender Firewall NDIS6 Filter Driver, BitDefender LLC).
Google query: BitDefender LLC DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sun 4/13/2014 10:00:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041314-31824-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x3, 0xFFFFF8000321D950, 0x285E613200000000, 0xFFFFF8000321D950)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 4/12/2014 5:57:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041214-23368-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0xFFFFFFFF, 0x2, 0x0, 0xFFFFF800031F79BC)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Bump.. anybody ? Could use some help :)