BSOD every time on starting, after uninstal Norton.

Welcome.

Caused by Avast!

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\Compressed\YB035469W-24_12_2014_184041_61\122414-21013-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0325d000 PsLoadedModuleList = 0xfffff800`034a2670
Debug session time: Wed Dec 24 19:32:56.038 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:06.912
Loading Kernel Symbols
...............................................................
........................
Loading User Symbols
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880012b0847, fffff880009a8e68, fffff880009a86c0}

Probably caused by : aswSP.SYS ( aswSP+3e847 )

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

0: 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: fffff880012b0847, The address that the exception occurred at
Arg3: fffff880009a8e68, Exception Record Address
Arg4: fffff880009a86c0, 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: 
aswSP+3e847
fffff880`012b0847 48897008        mov     qword ptr [rax+8],rsi

EXCEPTION_RECORD:  fffff880009a8e68 -- (.exr 0xfffff880009a8e68)
ExceptionAddress: fffff880012b0847 (aswSP+0x000000000003e847)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000008
Attempt to write to address 0000000000000008

CONTEXT:  fffff880009a86c0 -- (.cxr 0xfffff880009a86c0)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004f9d8b0
rdx=0000000000000002 rsi=fffff8a0002bbce0 rdi=fffffa8006f1e710
rip=fffff880012b0847 rsp=fffff880009a90a0 rbp=0000000000000000
 r8=0000000000008e08  r9=0000000000000030 r10=fffff8000325d000
r11=000000000000038d r12=fffffa8006f15000 r13=fffff88001272000
r14=0000000000000001 r15=fffff880009a92e0
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
aswSP+0x3e847:
fffff880`012b0847 48897008        mov     qword ptr [rax+8],rsi ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

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:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000008

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350c100
GetUlongFromAddress: unable to read from fffff8000350c1c0
 0000000000000008 Nonpaged pool

FOLLOWUP_IP: 
aswSP+3e847
fffff880`012b0847 48897008        mov     qword ptr [rax+8],rsi

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffffa8006f15000 to fffff880012b0847

STACK_TEXT:  
fffff880`009a90a0 fffffa80`06f15000 : 00000000`00000000 00000000`49777361 00000000`000007ff fffff880`009a91b0 : aswSP+0x3e847
fffff880`009a90a8 00000000`00000000 : 00000000`49777361 00000000`000007ff fffff880`009a91b0 fffff800`00000008 : 0xfffffa80`06f15000


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  aswSP+3e847

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  50334f72

STACK_COMMAND:  .cxr 0xfffff880009a86c0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_aswSP+3e847

BUCKET_ID:  X64_0x7E_aswSP+3e847

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

0: kd> lmvm aswSP
start             end                 module name
fffff880`01272000 fffff880`012cf000   aswSP    T (no symbols)           
    Loaded symbol image file: aswSP.SYS
    Image path: \SystemRoot\System32\Drivers\aswSP.SYS
    Image name: aswSP.SYS
    Timestamp:        Tue Aug 21 15:05:54 2012 (50334F72)
    CheckSum:         00060B45
    ImageSize:        0005D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Uninstall and use MSE in its place.

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

Good and Free system security combination.

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.