Frequent BSODs

Sometimes happening more than once a week (other weeks none at all), I've been getting BSODs. Using WhoCrashed, I know it's being caused by ntsokrnl.exe and ntkrnlmp.exe. Which are basic Windows processes, or in the kernel... thing (NT Kernel & System).

 WhoCrashed log from today

On Tue 7/24/2012 12:24:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-40919-01.dmp
This was probably caused by the following module: [SIZE=2]ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x31, 0xFFFFFA80056EA0D0, 0xFFFFF880080B4000, 0xFFFFF8A00CB62BA4)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
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 which cannot be identified at this time.
[/SIZE]

On Tue 7/24/2012 12:24:24 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [SIZE=2]ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x31, 0xFFFFFA80056EA0D0, 0xFFFFF880080B4000, 0xFFFFF8A00CB62BA4)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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 which cannot be identified at this time.[/SIZE]

 Previous dumps from other modules or whatever

On Thu 5/24/2012 9:27:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052412-56909-01.dmp
This was probably caused by the following module: [SIZE=2]fltmgr.sys (fltmgr+0x23178)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x11244AD0, 0xFFFFF8A0111DB3C0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that the current thread is making a bad pool request.
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 which cannot be identified at this time.
[/SIZE]
On Wed 5/16/2012 2:33:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051512-33212-01.dmp
This was probably caused by the following module: [SIZE=2]ntfs.sys (Ntfs+0xABF76)
Bugcheck code: 0xA (0xED481, 0x2, 0x1, 0xFFFFF800032EDF3C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 which cannot be identified at this time.
[/SIZE]

Though, keep in mind that ntsokrnl and ntkrnlmp have both appeared previously as well.

I'm pretty good at solving computer issues but this is beyond me. This sounds, well, terrible. Any solutions?