BSOD minidump IRQL at or soon after start up

[batvomit]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: FFFFF80000BA7000
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF80002B34DC9
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\082217-22448-01.dmp
C:\Users\Matt\AppData\Local\Temp\WER-64475-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[ICIT2LOL]

Hello and welcome Matt please follow this first
Now before we can help we do need to know what is in your machine so please do this System Info - See Your System Specs - Windows 7 Help Forums
or either enter the specs of your system in your forum profile the specs will appear when we click on that little box bottom left of the post screen it is for me the preferable option as it is easy. As you may appreciate it is very hard when you don’t know what one is working with for example a diesel or petrol engine.
*(pretyped to save time)

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: [COLOR="Red"]fffff80000ba7000, memory referenced[/COLOR]
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: [COLOR="red"]fffff80002b34dc9, address which referenced memory[/COLOR]

In the meantime after seeing this I would suggest you follow this as well please follow this to the letter the only time you can stop the test for sure is if errors appear straight away or very shortly into the test.
Now to make absolutely we are on the same page the memtest linked here is the only*one we recommend and it MUST be run for at least 8 passes or you may as well not bother. It is rather lengthy and best left for a downtime for that machine - overnight is good. Having said that you can stop the test if errors show up while you are around and then it is a matter of tracking down the bad stick of RAM.* RAM - Test with Memtest86+ - Windows 7 Help Forums
(This is pretyped to save time)