BSOD Driver left locked pages???

Your latest dump file indicate Driver Verifier was off.
Can you re-run the DV again?
I'm still suspecting 3rd driver as the culprit.

Code:

 
nt!PspProcessDelete+0x154:
fffff800`03191bb4 483bcd          cmp     rcx,rbp
fffff800`03191bb7 0f851e9f0800    jne     nt! ?? ::NNGAKEGL::`string'+0x36bab (fffff800`0321badb)
fffff800`03191bbd 488bcb          mov     rcx,rbx
fffff800`03191bc0 e8bb92d1ff      call    nt!MmCleanProcessAddressSpace (fffff800`02eaae80)
fffff800`03191bc5 488d4c2420      lea     rcx,[rsp+20h]
fffff800`03191bca e85185d7ff      call    nt!KeUnstackDetachProcess (fffff800`02f0a120)
fffff800`03191bcf 488bcb          mov     rcx,rbx
fffff800`03191bd2 e839100000      call    nt!MmDeleteProcessAddressSpace (fffff800`03192c10)

Memory manager delete and clean Process address = usual caused by 3rd party drivers or bad RAM.

You may try clean boot to check if the BSOD would stop in that mode.
How to Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista

If the problem remain in clean boot, then test your RAM:
RAM - Test with Memtest86+

You're welcome, stormfinder :)

Unfortunately your latest dump also doesn't reveal any faulting driver.
And for some reason I could not open your msinfo32.nfo because it's corrupted.

Some workaround you can try:
1] WDC Data Lifeguard → EXTENDED TEST
2] Reinstall your VGA driver (ATI), MSE antivirus and Windows Virtual PC
Since corrupted software/driver can causing problem.

3] For troubleshooting purpose, uninstall Webcam driver and Memory Card reader for a while and see if the BSOD problem persist.

Log

Code:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`03063650
Debug session time: Wed May 11 19:35:37.794 2011 (GMT-8)
System Uptime: 0 days 3:40:53.090
Loading Kernel Symbols
...............................................................
................................................................
................................................................

Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck CB, {fffff800032645b9, 0, fffffa8009d96830, a}

Probably caused by : memory_corruption ( nt!MmProbeAndLockProcessPages+59 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (cb)
Caused by a driver not cleaning up completely after an I/O.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff800032645b9, The calling address in the driver that locked the pages or if the
    IO manager locked the pages this points to the dispatch routine of
    the top driver on the stack to which the IRP was sent.
Arg2: 0000000000000000, The caller of the calling address in the driver that locked the
    pages. If the IO manager locked the pages this points to the device
    object of the top driver on the stack to which the IRP was sent.
Arg3: fffffa8009d96830, A pointer to the MDL containing the locked pages.
Arg4: 000000000000000a, The number of locked pages.

Debugging Details:
------------------


FAULTING_IP: 
nt!MmProbeAndLockProcessPages+59
fffff800`032645b9 eb06            jmp     nt!MmProbeAndLockProcessPages+0x61 (fffff800`032645c1)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xCB

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030f78ef to fffff80002e9dd00

STACK_TEXT:  
fffff880`0338ca98 fffff800`030f78ef : 00000000`000000cb fffff800`032645b9 00000000`00000000 fffffa80`09d96830 : nt!KeBugCheckEx
fffff880`0338caa0 fffff800`03155d77 : fffffa80`0be5d660 fffffa80`06cc6f30 fffffa80`00000000 fffffa80`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1831c
fffff880`0338cae0 fffff800`02ea7b14 : 00000000`00000000 fffffa80`0be5d660 fffffa80`0be5d630 00000000`00010286 : nt!PspProcessDelete+0x177
fffff880`0338cb40 fffff800`03172c47 : fffffa80`0be5d660 00000000`00000001 fffffa80`06d73040 fffff800`02e68c4b : nt!ObfDereferenceObject+0xd4
fffff880`0338cba0 fffff800`031725ed : fffffa80`0aa73030 fffffa80`0aa73060 fffffa80`06cc6de0 fffffa80`0aa73060 : nt!PspThreadDelete+0xe3
fffff880`0338cbe0 fffff800`02e8a123 : 00000000`00000000 00000000`00000000 fffffa80`0aa73060 00000000`00000001 : nt!ObpRemoveObjectRoutine+0x61
fffff880`0338cc40 fffff800`02e7da29 : 00000000`00000000 fffffa80`06d73040 fffffa80`0aa733f0 fffffa80`06d73040 : nt!ObfDereferenceObjectWithTag+0x93
fffff880`0338cc80 fffff800`02ea8021 : fffff800`02e7d990 fffff800`0303b310 fffffa80`06d73040 00000000`00000000 : nt!PspReaper+0x99
fffff880`0338ccb0 fffff800`0313a32e : 00000000`00000000 fffffa80`06d73040 00000000`00000080 fffffa80`06d4c040 : nt!ExpWorkerThread+0x111
fffff880`0338cd40 fffff800`02e8f666 : fffff880`0316a180 fffffa80`06d73040 fffff880`031750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0338cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!MmProbeAndLockProcessPages+59
fffff800`032645b9 eb06            jmp     nt!MmProbeAndLockProcessPages+0x61 (fffff800`032645c1)

SYMBOL_NAME:  nt!MmProbeAndLockProcessPages+59

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xCB_VRF_nt!MmProbeAndLockProcessPages+59

BUCKET_ID:  X64_0xCB_VRF_nt!MmProbeAndLockProcessPages+59

Followup: MachineOwner
---------

stormfinder said:

i was actually having this problem before installing the memory card driver, i installed it after noting the exclamation in device manager. i will shut down the webcam driver and see if it still does it. also i have found a couple of programsd that will ALWAYS, BSOD with this error code: Yahoo Messenger, and digsby IM. But only upon exiting the program... maybe that may help with the diagnosing...

Some programs didn't work properly, it maybe caused by viruses or corrupted OS.
Try to full scan with MSE and TDSS Killer.
If it found nothing then I recommend you to back up important files, then perform clean install Windows.
Clean Install Windows 7