More blue screens. Help!

I've been having blue screens, all associated with ntosrknl.exe in one way or another. I'm assuming this is the cause of it, so how do I go about fixing it? I have run memtest86 three times, no bumps. I have run chkdsk three times for both RAM and harddrive. It doesn't bluescreen, and when I'm running anything intensive, it randomly happens, so I have no idea what's causing it. I will put specs down below, any help's appreciated!

- AMD FX 6300 6 core, 3.5ghz
- 8 gb BALLISTIX ram, low profile, one stick
- Windows 7, 64-bit
- ASRock 970 Pro3 R2.0 mobo
- AMD r9 270X GPU
- 500 watt PSU
- Two Monitors, and I have about 300 gb used out of a TB of Western Digital Caviar Blue

------------------------------------------------------------------------------------------------------------------------------------------
Most Recent Three Errors: ****There were 20 before these, but they were for some reason deleted. I checked over them about a day before

they mysteriously vanished and they all had one thing in common, ntoskrnl.exe. It wasn't always the item that crashed, but it caused the

crashes if it wasn't crashing.

Crash dumps are enabled on your computer.

On Thu 10/16/2014 7:49:23 PM GMT your computer crashed
crash dump file: C:\Users\Zachs\Desktop\Misc\dump files\101614-24086-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF800038117D0)
Bugcheck code: 0x50 (0xFFFFF8000482C598, 0x0, 0xFFFFF800038117D0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another

driver on your system that cannot be identified at this time.



On Fri 10/10/2014 3:49:21 PM GMT your computer crashed
crash dump file: C:\Users\Zachs\Desktop\Misc\dump files\101014-17144-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF800037FB7D0)
Bugcheck code: 0x50 (0xFFFFF80004816598, 0x0, 0xFFFFF800037FB7D0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another

driver on your system that cannot be identified at this time.



On Thu 10/2/2014 9:33:54 PM GMT your computer crashed
crash dump file: C:\Users\Zachs\Desktop\Misc\dump files\100214-22136-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0xFFFFF88002FA4D20, 0x2, 0x1, 0xFFFFF800033C7EC1)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory

corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.