You have given us many reports showing the cause of the BSODs. There, however are only 2 primary reasons given for the cause of your problem.

BC A
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility and
BC 1E
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

Code:

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2 (5).zip\Windows_NT6_BSOD_jcgriff2\Mini060511-02.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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`0245c000 PsLoadedModuleList = 0xfffff800`02620dd0
Debug session time: Sun Jun  5 18:23:06.835 2011 (GMT-4)
System Uptime: 0 days 0:02:25.460
Loading Kernel Symbols
...............................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, 0, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29117 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
+0
00000000`00000000 ??              ???
EXCEPTION_PARAMETER1:  0000000000000008
EXCEPTION_PARAMETER2:  0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002683080
 0000000000000000 
CUSTOMER_CRASH_COUNT:  2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  conime.exe
CURRENT_IRQL:  0
TRAP_FRAME:  fffffa60039c65d0 -- (.trap 0xfffffa60039c65d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8005a15870
rdx=fffffa80056cb421 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffffa60039c6760 rbp=fffffa8005a15840
 r8=fffffa80056cb420  r9=0000000000007e00 r10=fffffa8003c6c5c0
r11=fffffa80059e9c10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000000 ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002498ac7 to fffff800024b6490
STACK_TEXT:  
fffffa60`039c5de8 fffff800`02498ac7 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
fffffa60`039c5df0 fffff800`024b62e9 : fffffa60`039c6528 00000000`00000000 fffffa60`039c65d0 fffff880`00000200 : nt! ?? ::FNODOBFM::`string'+0x29117
fffffa60`039c63f0 fffff800`024b50e5 : 00000000`00000008 fffffa80`04eb9748 fffffa80`04eb7300 00000000`00000000 : nt!KiExceptionDispatch+0xa9
fffffa60`039c65d0 00000000`00000000 : 00000000`00000000 fffffa80`00000000 fffffa80`05963c10 00000000`00000000 : nt!KiPageFault+0x1e5
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+29117
fffff800`02498ac7 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+29117
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4cb7275f
FAILURE_BUCKET_ID:  X64_0x1E_nt!_??_::FNODOBFM::_string_+29117
BUCKET_ID:  X64_0x1E_nt!_??_::FNODOBFM::_string_+29117
Followup: MachineOwner
---------

One of the reports gave driver SPTD as a likely suspect.
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs
DuplexSecure - Downloads
Use this SPTD uninstaller when you're done:
Test the computer after this driver is uninstalled. If you do not experience any more BSODs, please report back. Since I feel this is unlikely, but feel that a driver is responsibile, please test with the driver verifier.

Since the driver that crashed you has not been listed you shouldrun driver verifier
Please run Verifier with these settings:
[quote]
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'lltell you what the driver is. But sometimes it'll crash and won't tell you thedriver. Other times it'll crash before you can log in to Windows. If you can'tget to Safe Mode, then you'll have to resort to offline editing of the registryto disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've gotaccess to another computer so you can contact us if problems arise. Then make aSystem Restore point (so you can restore the system using the Vista/Windows 7Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and pressEnter
- Select "Create custom settings (for code developers)" and click"Next"
- Select "Select individual settings from a full list" and click"Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click"Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limitedexperimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to useyour system normally, and if you know what causes the crash, do thatrepeatedly. The objective here is to get the system to crash because DriverVerifier is stressing the drivers out. If it doesn't crash for you, then let itrun for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by goingback in and selecting "Delete existing settings" on the first page,then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from yourinstallation DVD to set the system back to the previous restore point that youcreated.





Enable the driver verifier
www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html

Again test the system to see if the problem has been resolved. I think that the above procedure will stop further BSODS.
In the event that you continue to have BSODs please perform a memory test.
Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run for 8 passes
Ifit passes try a good stick in each slot for 3 passes
If it fails do the same for 8 passes.

Regardless of the cause of the problem, please perform these tests to ensure that you will be problem free and to avoid future problems.
SFC /scannow
System Files - SFC Command
Scan with your Anti Virus
I, also, suggest installing Microsoft Security Essentials in lieu of your current AV. Other AV have been know to cause BSOD problems. Even if not the cause now, better not to have to come back with new problems.

Although I think that these steps will solve the problem, if it does not I will summon the help of virus expert to give her opinion.

The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receivethe more clues are made available improving our chances of finding a solution to your problem. Each remedy suggested must be performed regardless ofplacement in this report or other variables. You may have to experience severalmore BSODs until the final answer is discovered.

I have examined the new dump reports, which are basically like the ones previously submitted. None show that the BSODs were caused by the verifier. Please be sure that it was set up correctly and run for 36 hours. If we do not get additional evidence from the verifier, I will tackle this in another way.

Have you installed any new hadware or software in the last 6 months?

Have you recently updated the OS or any other harware (bios) or software?

Check the System Log in Event Viewer for additional information that might help determine the device or driver that is causing the problem. To open Event Viewer, click Start, click Control Panel, double-click Administrative Tools, and then double-click Event Viewer.

Also, complete all the steps that I mentioned in my first post.

Go to device manager and make sure that drivers for graphics and audio are up to date.

If you can operate the computer, now in safe mode, try a clean boot and report back
http://support.microsoft.com/kb/929135

Glad that it worked out for you.