BSOD when my computer open followed by a shotdown.

Please read the following and report back :)

https://www.sevenforums.com/crashes-d...tructions.html

Updated post*

I've taken a look at your dump files, one dump shows BitDefender as the culprit. Please uninstall BitDefender and install Microsoft Security Essentials for testing purposes.

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff880010a56c0, The address that the exception occurred at
Arg3: fffff88003386628, Exception Record Address
Arg4: fffff88003385e80, 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`010a56c0 4c8b7120        mov     r14,qword ptr [rcx+20h]

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

CONTEXT:  fffff88003385e80 -- (.cxr 0xfffff88003385e80)
rax=fffff880033868f8 rbx=0000000000000000 rcx=41575610245c8948
rdx=fffff88007e59e1d rsi=fffffa8009a52880 rdi=0000000000000000
rip=fffff880010a56c0 rsp=fffff88003386860 rbp=fffff8000307d2b8
 r8=00000000000001b9  r9=fffff88007e5a090 r10=0000000000000001
r11=fffffa8005f0a010 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`010a56c0 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 fffff8000310f100
 ffffffffffffffff 

FOLLOWUP_IP: 
avckf+183d
fffff880`07e0183d ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88007e0183d to fffff880010a56c0

STACK_TEXT:  
fffff880`03386860 fffff880`07e0183d : 00000000`00000000 fffff800`0307d2b8 fffffa80`09a52880 00000000`00000000 : fltmgr!FltUnregisterFilter+0x20
fffff880`03386900 00000000`00000000 : fffff800`0307d2b8 fffffa80`09a52880 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 0xfffff88003385e80 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_avckf+183d

BUCKET_ID:  X64_0x7E_avckf+183d

Followup: MachineOwner

Seems to be solved. Thanks for the help.

Glad to hear, have a great day :)