Latest BSOD attached doesn't look like it's verifier enabled, so I assume you enabled it after that BSOD.
That dump attached is a 3B pointing to memory corruption, so it sounds like your memory is on its way out, or a 3rd party driver is really corrupting memory here. If Driver Verifier shows nothing, the next thing I'd like you to do is Memtest. We'll worry about that when we need to.
Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Cardbox\Downloads\050712-19515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030ab650
Debug session time: Mon May 7 16:42:15.654 2012 (UTC - 4:00)
System Uptime: 0 days 1:01:22.246
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002f8e37f, fffff88007871c90, 0}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
Followup: MachineOwner
---------
0: 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: fffff80002f8e37f, Address of the instruction which caused the bugcheck
Arg3: fffff88007871c90, 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!MiIdentifyPfn+26f
fffff800`02f8e37f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh
CONTEXT: fffff88007871c90 -- (.cxr 0xfffff88007871c90)
rax=0000000000000001 rbx=020000000017ba6a rcx=0200000000000020
rdx=00000000000d6151 rsi=0000000000000000 rdi=fffffa8007447720
rip=fffff80002f8e37f rsp=fffff88007872670 rbp=fffffa8009309b30
r8=00000000000d5d92 r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=fffff80003058e80 r13=0000000000000000
r14=fda30e931c218e6d r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!MiIdentifyPfn+0x26f:
fffff800`02f8e37f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh ds:002b:fda30e93`1c218eb5=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002f8e37f
STACK_TEXT:
fffff880`07872670 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiIdentifyPfn+0x26f
FOLLOWUP_IP:
nt!MiIdentifyPfn+26f
fffff800`02f8e37f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiIdentifyPfn+26f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4f558b55
STACK_COMMAND: .cxr 0xfffff88007871c90 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiIdentifyPfn+26f
BUCKET_ID: X64_0x3B_nt!MiIdentifyPfn+26f
Followup: MachineOwner
---------