BSOD 0x0000000A crash 5 mins after start up

Allot of important info is missing from your zip, please follow Blue Screen of Death (BSOD) Posting Instructions to grab all and upload a new report here.

Make sure your dump logging is enabled.

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. Check Write an even to the system log, and Automatically restart.
5. In the Write debugging information list, click Small memory dump (256k).

Location of Dumps:
C:\Windows\minidump

Code:

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


Loading Dump File [C:\Users\admin\Downloads\MARTYLAPTOP-Fri_12_12_2014_193039_74\Mini121214-03.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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18881.amd64fre.vistasp2_gdr.130707-1535
Machine Name:
Kernel base = 0xfffff800`02a1f000 PsLoadedModuleList = 0xfffff800`02be3e30
Debug session time: Sat Dec 13 09:13:05.044 2014 (UTC + 6:00)
System Uptime: 0 days 0:03:44.065
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffffa600b059d60, 0, 0}

*** WARNING: Unable to verify timestamp for NETw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5v64.sys
Probably caused by : NETw5v64.sys ( NETw5v64+5a0d )

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

1: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa600b059d60, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002c46080
GetUlongFromAddress: unable to read from fffff80002c46160
 ffffffffffffffff 

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

FAULTING_IP: 
+0
fffffa60`0b059d60 f8              clc

EXCEPTION_PARAMETER2:  ffffffffffffffff

BUGCHECK_STR:  0x1E_c0000005_R

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Dropbox.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f37b4c to fffff80002a86630

CONTEXT:  fffffa600b05a5d0 -- (.cxr 0xfffffa600b05a5d0)
rax=0000000000000963 rbx=0000000000000963 rcx=fffffa800664f4f0
rdx=0000000000000001 rsi=fffffa6002516000 rdi=fffffa6000001bb8
rip=fffff80002a86630 rsp=fffffa600b05ae30 rbp=fffff6fd300128b0
 r8=fffffa80008bbc90  r9=00000000e73fef11 r10=0000fffffffff000
r11=0000058000000000 r12=fffef2801a335b00 r13=000000000000096b
r14=fffffa800664f4e0 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!MmMapLockedPagesSpecifyCache+0x350:
fffff800`02a86630 410fb64c241a    movzx   ecx,byte ptr [r12+1Ah] ds:002b:fffef280`1a335b1a=??
Resetting default scope

STACK_TEXT:  
fffffa60`0b05ae30 fffff800`02f37b4c : fffffa80`0664f4b0 00000000`00002513 00000000`00000000 fffffa60`03a0e005 : nt!MmMapLockedPagesSpecifyCache+0x350
fffffa60`0b05aef0 fffff800`02f37423 : fffffa80`08414c30 fffffa80`08414c30 00000000`00000000 fffffa80`0664f4b0 : hal!HalpDmaSyncMapBuffers+0x54
fffffa60`0b05afa0 fffff800`02f3a399 : fffffa80`0619ceb8 fffffa80`08414c30 fffffa80`0664f4b0 fffffa80`061e4400 : hal!HalpDmaMapScatterTransfer+0xa3
fffffa60`0b05aff0 fffff800`02f3a312 : fffffa80`0619ceb8 fffffa80`0619ceb0 00000000`000005b4 00000000`00000001 : hal!HalpMapTransfer+0x79
fffffa60`0b05b070 fffff800`02f3980f : 00000000`00000000 fffff800`02f36e45 00000000`00000000 00000000`00000005 : hal!IoMapTransfer+0x8e
fffffa60`0b05b0b0 fffff800`02f399bd : fffffa80`08191050 fffffa80`08414c30 00000000`00000001 fffffa80`00000000 : hal!HalpAllocateAdapterCallback+0xc7
fffffa60`0b05b150 fffff800`02f39ff6 : fffffa80`08414c30 00000000`00000100 fffffa80`08414c00 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffffa60`0b05b180 fffff800`02f395df : fffffa80`066d8060 00000000`00000172 fffffa80`08414c30 fffffa80`0605bf10 : hal!HalAllocateAdapterChannel+0x11a
fffffa60`0b05b1c0 fffffa60`01609818 : fffffa80`05ae4cf0 fffffa80`0605bf50 00000000`000000a0 fffffa60`03c4e3f7 : hal!HalBuildScatterGatherList+0x2f3
fffffa60`0b05b230 fffffa60`03a07a0d : fffffa80`081911a0 fffffa60`03c4dff0 fffffa80`06028c10 fffff780`00000014 : ndis!NdisMAllocateNetBufferSGList+0x108
fffffa60`0b05b2d0 fffffa80`081911a0 : fffffa60`03c4dff0 fffffa80`06028c10 fffff780`00000014 00000000`00000000 : NETw5v64+0x5a0d
fffffa60`0b05b2d8 fffffa60`03c4dff0 : fffffa80`06028c10 fffff780`00000014 00000000`00000000 00000172`00000100 : 0xfffffa80`081911a0
fffffa60`0b05b2e0 fffffa80`06028c10 : fffff780`00000014 00000000`00000000 00000172`00000100 00000000`00000000 : NETw5v64+0x24bff0
fffffa60`0b05b2e8 fffff780`00000014 : 00000000`00000000 00000172`00000100 00000000`00000000 fffffa60`03a0faa9 : 0xfffffa80`06028c10
fffffa60`0b05b2f0 00000000`00000000 : 00000172`00000100 00000000`00000000 fffffa60`03a0faa9 fffffa60`03ccdba0 : 0xfffff780`00000014


FOLLOWUP_IP: 
NETw5v64+5a0d
fffffa60`03a07a0d ??              ???

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  NETw5v64+5a0d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETw5v64

IMAGE_NAME:  NETw5v64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49aec1b4

STACK_COMMAND:  .cxr 0xfffffa600b05a5d0 ; kb

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_NETw5v64+5a0d

BUCKET_ID:  X64_0x1E_c0000005_R_NETw5v64+5a0d

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

1: kd> lmvm NETw5v64
start             end                 module name
fffffa60`03a02000 fffffa60`03f3b000   NETw5v64 T (no symbols)           
    Loaded symbol image file: NETw5v64.sys
    Image path: NETw5v64.sys
    Image name: NETw5v64.sys
    Timestamp:        Thu Mar 05 00:00:20 2009 (49AEC1B4)
    CheckSum:         005300B6
    ImageSize:        00539000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You could update this driver: Driver Reference Table

Sometimes drivers remain and do not get completely uninstalled.

 Driver Removal Process:

• Download Driver Sweeper to the desired location.
• Extract the files from the zip.
• Uninstall the driver Program & Features - Control Panel.
• Run Driver Sweeper, check the drivers you want to uninstall or clean registry leftovers of.

Link to full tutorial: Drivers - Clean Left over Files after Uninstalling

Maybe google it yourself or you could use the Intel® Driver Update Utility