BSOD on startup. Everytime, works only in safe mode

This was an easy one. I do not care if you paid for it or its free, uninstall AVG, but make a system restore point first. For testing purposes download the free Microsoft Security essentials. MSE is made for windows, no one has ever had a BSOD due to MSE. Once you are satisfied that the BSODs have come to an end you can continue with MSE or use AVAST. both are free.

Code:

 Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_GEC-PC-sri_14_01_2015__220012,68.zip\011415-17596-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
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03006000 PsLoadedModuleList = 0xfffff800`03249890
Debug session time: Wed Jan 14 02:50:40.616 2015 (UTC - 5:00)
System Uptime: 0 days 0:01:17.990
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffff80000003, fffff80003073a38, 2, 0}
Unable to load image \SystemRoot\system32\DRIVERS\avgmfx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgmfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx64.sys
Probably caused by : avgmfx64.sys ( avgmfx64+3902 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff80003073a38, The address that the exception occurred at
Arg3: 0000000000000002, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
 
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
FAULTING_IP: 
nt!DebugPrompt+18
fffff800`03073a38 c3              ret
EXCEPTION_PARAMETER1:  0000000000000002
EXCEPTION_PARAMETER2:  0000000000000000
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.
BUGCHECK_STR:  0x1E_80000003
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff800030c6738 to fffff8000307bbc0
STACK_TEXT:  
fffff880`0b24ab48 fffff800`030c6738 : 00000000`0000001e ffffffff`80000003 fffff800`03073a38 00000000`00000002 : nt!KeBugCheckEx
fffff880`0b24ab50 fffff800`0307b242 : fffff880`0b24b328 fffff880`0121cab0 fffff880`0b24b3d0 00000000`000001e7 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`0b24b1f0 fffff800`0307a8f3 : 3d206564`6f43726f 7349202c`35783020 3d20676e`69676150 6f4e202c`30783020 : nt!KiExceptionDispatch+0xc2
fffff880`0b24b3d0 fffff800`03073a38 : fffff800`03109a1b fffff880`0121cab0 fffff800`030b6878 fffff880`0121cab0 : nt!KiDebugServiceTrap+0xf3
fffff880`0b24b568 fffff800`03109a1b : fffff880`0121cab0 fffff800`030b6878 fffff880`0121cab0 00000000`000001e7 : nt!DebugPrompt+0x18
fffff880`0b24b570 fffff880`0123f4bb : 00000000`00000000 00000000`00000000 fffff880`0123f060 00000000`00000007 : nt!DbgPrompt+0x3b
fffff880`0b24b5c0 fffff880`0123fc4a : 00000000`0000003a fffffa80`08346c60 fffffa80`082b5d70 00000000`00000005 : fltmgr!FltpvPrintErrors+0x11b
fffff880`0b24b820 fffff880`0123ea0d : 00000000`00000018 fffffa80`083a6c60 fffffa80`0a375b40 fffff880`0b24b940 : fltmgr!FltpvVerifyIoIrqlStatus+0xaa
fffff880`0b24b890 fffff880`01c8c902 : fffffa80`0a332e50 00000000`00000004 fffff880`0b24bb88 00000000`00000000 : fltmgr!FltvQueryInformationFile+0x2d
fffff880`0b24b8d0 fffffa80`0a332e50 : 00000000`00000004 fffff880`0b24bb88 00000000`00000000 fffff880`00000005 : avgmfx64+0x3902
fffff880`0b24b8d8 00000000`00000004 : fffff880`0b24bb88 00000000`00000000 fffff880`00000005 00000000`00000000 : 0xfffffa80`0a332e50
fffff880`0b24b8e0 fffff880`0b24bb88 : 00000000`00000000 fffff880`00000005 00000000`00000000 00000000`00000000 : 0x4
fffff880`0b24b8e8 00000000`00000000 : fffff880`00000005 00000000`00000000 00000000`00000000 fffff800`0351b6e7 : 0xfffff880`0b24bb88
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
avgmfx64+3902
fffff880`01c8c902 ??              ???
SYMBOL_STACK_INDEX:  9
SYMBOL_NAME:  avgmfx64+3902
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: avgmfx64
IMAGE_NAME:  avgmfx64.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  54319ef0
FAILURE_BUCKET_ID:  X64_0x1E_80000003_VRF_avgmfx64+3902
BUCKET_ID:  X64_0x1E_80000003_VRF_avgmfx64+3902
Followup: MachineOwner
---------

I have bolded the AVG driver responsible.