BSOD BUGCODE_USB_DRIVER crashes

You problem is the '
BitDefender Active Virus Control Kernel Filtering driver
'. It's causing all this mess.
The fact that you mentioned you were using it, kind of leads me to believe you may have already known.

Code:

Probably caused by : avckf.sys ( avckf+183d )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800131b6c0, The address that the exception occurred at
Arg3: fffff8800358e768, Exception Record Address
Arg4: fffff8800358dfc0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
fltmgr!FltUnregisterFilter+20
fffff880`0131b6c0 4c8b7120        mov     r14,qword ptr [rcx+20h]

EXCEPTION_RECORD:  fffff8800358e768 -- (.exr 0xfffff8800358e768)
ExceptionAddress: fffff8800131b6c0 (fltmgr!FltUnregisterFilter+0x0000000000000020)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800358dfc0 -- (.cxr 0xfffff8800358dfc0)
rax=fffff8800358ea38 rbx=0000000000000000 rcx=41575610245c8948
rdx=fffff88002f18e1d rsi=fffffa80072ead40 rdi=0000000000000000
rip=fffff8800131b6c0 rsp=fffff8800358e9a0 rbp=fffff8000307e2b8
 r8=00000000000001b9  r9=fffff88002f19090 r10=000000000000000f
r11=fffffa80031684f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
fltmgr!FltUnregisterFilter+0x20:
fffff880`0131b6c0 4c8b7120        mov     r14,qword ptr [rcx+20h] ds:002b:41575610`245c8968=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003110100
 ffffffffffffffff 

FOLLOWUP_IP: 
avckf+183d
fffff880`02ec083d ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88002ec083d to fffff8800131b6c0

STACK_TEXT:  
fffff880`0358e9a0 fffff880`02ec083d : 00000000`00000000 fffff800`0307e2b8 fffffa80`072ead40 00000000`00000000 : fltmgr!FltUnregisterFilter+0x20
fffff880`0358ea40 00000000`00000000 : fffff800`0307e2b8 fffffa80`072ead40 00000000`00000000 00000000`00000000 : avckf+0x183d


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  avckf+183d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: avckf

IMAGE_NAME:  avckf.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e5ce456

STACK_COMMAND:  .cxr 0xfffff8800358dfc0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_avckf+183d

BUCKET_ID:  X64_0x7E_avckf+183d

Followup: MachineOwner
---------

If the debugger is to be believed it's the current cause of ...well everything.

I can tell you it's complaining about a usb device ...still.
I can't get a track on what is causing it exactly this time though.

Let's try turning off the advanced usb power features and see if that calms it.

To Disable Selective Suspend:

open the control panel
go to power options (you may have to set view to small icons)
click change plan settings
in the window that opens:
click change plan settings
click change advanced power settings, expand usb and ensure usb selective suspend is disabled.