So lately my computer has been blue screening randomly. Sometimes it wont do it for a few days, other times it will do it multiple times in a row within minutes of each other. I reinstalled windows but that didn't change anything so I think it may be a hardware issue. The message varies, but the most frequent would be the driver IRQL not less or equal message. Thanks in advance for any information you guys can give me

.
Heres the dump. (These things are hard to open :/ )
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Spiffy\Desktop\100512-17612-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.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02c62000 PsLoadedModuleList = 0xfffff800`02ea6670
Debug session time: Fri Oct 5 17:44:27.461 2012 (UTC - 7:00)
System Uptime: 0 days 0:03:32.600
Loading Kernel Symbols
...............................................Unable to add module at ffffffff`ffffffff
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {44200010007, 2, 1, fffff88008f6761d}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000044200010007, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88008f6761d, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f10100
0000044200010007
CURRENT_IRQL: 0
FAULTING_IP:
+3463663239363634
fffff880`08f6761d ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from fffff80002ce9ce9 to fffff88006b547f2
STACK_TEXT:
fffff800`03fffc98 fffff800`02ce9ce9 : 00000000`003723ad fffffa80`050ea548 fffff800`02e61cc0 00000000`00000001 : 0xfffff880`06b547f2
fffff800`03fffca0 fffff800`02cd8e9c : fffff800`02e53e80 fffff800`00000000 00000000`00000000 fffff800`02df9130 : nt!PoIdle+0x52a
fffff800`03fffd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PoIdle+52a
fffff800`02ce9ce9 0fba2557e617000f bt dword ptr [<Unloaded_Unknown_Module_00000000`00000000>+0x17e657 (00000000`0017e657)],0Fh
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!PoIdle+52a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3
FAILURE_BUCKET_ID: X64_0xD1_nt!PoIdle+52a
BUCKET_ID: X64_0xD1_nt!PoIdle+52a
Followup: MachineOwner
---------