Attached is my Memory Dump file, please help

What files?

Your .dmp file is showing a 0x3b general hardware fault and doesnt really show the cause of the crash, other than a hardware component is being overstressed... If you are overclocking anything, return it to its default values.. Overclocking stresses hardware components beyond their intended use. One consequence of overclocking is the increased chance of hardware failure due to the stresses that overclocking places on the components. This may not happen immediately, but it will definitely happen sooner than if you didn't overclock.

And, since overclocking stresses the system in unexpected ways, the BSOD's that result may not be very helpful. To test if this is an overclock related problem - reset everything to default. If you don't get a BSOD, then it's reasonable to assume that the overclocking is the cause.

Code:

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002dceefd, fffff88008badab0, 0}

Probably caused by : hardware ( nt!ObpWaitForMultipleObjects+2c7 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002dceefd, Address of the instruction which caused the bugcheck
Arg3: fffff88008badab0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
nt!ObpWaitForMultipleObjects+2c7
fffff800`02dceefd 8b0b            mov     ecx,dword ptr [rbx]

CONTEXT:  fffff88008badab0 -- (.cxr 0xfffff88008badab0)
rax=0000000000000002 rbx=000000000000028a rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000001 rdi=0000000000000001
rip=fffff80002dceefd rsp=fffff88008bae488 rbp=fffff88008baeca0
 r8=fffffa8006fe1bb8  r9=0000000000000000 r10=fffffffffffffffb
r11=00000000002faa00 r12=0000000000000000 r13=fffff8a00a63f010
r14=0000000000000002 r15=0000000000000002
iopl=0         nv up ei pl nz ac pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010212
nt!ObpWaitForMultipleObjects+0x2c7:
fffff800`02dceefd 8b0b            mov     ecx,dword ptr [rbx] ds:002b:00000000`0000028a=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
nt!ObpWaitForMultipleObjects+2c7
fffff800`02dceefd 8b0b            mov     ecx,dword ptr [rbx]

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002dceefd

STACK_TEXT:  
fffff880`08bae488 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x2c7


FOLLOWUP_IP: 
nt!ObpWaitForMultipleObjects+2c7
fffff800`02dceefd 8b0b            mov     ecx,dword ptr [rbx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObpWaitForMultipleObjects+2c7

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff88008badab0 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Try a memory test. Download a copy of Memtest86 and burn the ISO to a CD using ISO Recorder. Boot from the CD, and leave it running for at least 5 passes.

Memtest86+ - Advanced Memory Diagnostic Tool

ISO Recorder v3