random BSoD's and other problems with desktop

[ErrorFairy]

i have had 4 BSoD's in 2 days, it just started out of nowhere. it makes me upset because i built this computer about a month ago and was hoping i would come across no problems. so my operating system is Windows 7 home premium 64 bit. the problems started right after i updated oovoo, since that was the only recently installed software i uninstalled it. still had a BSoD so i found out it had installed Ask toolbar on all my browsers, i then uninstalled ask toolbar from the list of programs and the browsers, then ran Microsoft security essentials and it found nothing. then another BSoD followed by an abnormally long wait time for my desktop to load. when it finally loaded i entered my password and it said "preparing your desktop..." then loaded a black desktop with the only icon being the recycling bin and the windows 7 theme completely gone and reverted to windows classic. it also displayed a message saying "location is not available. C:\windows\system32\config\systemprofile\desktop refers to a location that is unavailable..." so i restarted and it was back to normal. i have no idea why all these problems have suddenly appeared.

if anyone can help me resolve this issue that would be fantastic


i have included the dump files as well as all the other files SF Diagnostic Tool grabs.

here are other crash reports that have happened as well.

host process for windows task

Problem signature:
Problem Event Name: BEX64
Application Name: taskhost.exe
Application Version: 6.1.7601.17514
Application Timestamp: 4ce796f7
Fault Module Name: StackHash_d670
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 000051fefe48aa70
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: d670
Additional Information 2: d6701eab17003dba10bfb15694180f4c
Additional Information 3: aed9
Additional Information 4: aed90531a1330f9fa92019587da72201

NVIDIA crash

Problem signature:
Problem Event Name: APPCRASH
Application Name: nvtray.exe
Application Version: 7.17.13.142
Application Timestamp: 4fb20fcd
Fault Module Name: easyDaemonAPIU64.DLL
Fault Module Version: 1.8.15.0
Fault Module Timestamp: 4fb2023c
Exception Code: c0000005
Exception Offset: 0000000000011adb
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: a9a2
Additional Information 2: a9a21f351a591aac831cbea0c3809ed2
Additional Information 3: 80bf
Additional Information 4: 80bf70f195e009438f86708cf723e6a1

 

[koolkat77]

Welcome

BSOD Analyze

BSOD Index | STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.
[COLOR=Blue]
BugCheck 1E,[/COLOR] {ffffffffc0000005, fffff800030a10d9, 0, ffffffffffffffff}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[COLOR=Blue] memory_corruption[/COLOR]

Followup: [COLOR=Blue]memory_corruption[/COLOR]
---------

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

[COLOR=Blue]KMODE_EXCEPTION_NOT_HANDLED (1e)[/COLOR]
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: fffff800030a10d9, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, 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: 
nt!KiSwapContext+d9
fffff800`030a10d9 c3              ret

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032cd100
 ffffffffffffffff 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800030e8d88 to fffff8000309e1c0

STACK_TEXT:  
fffff880`07887d38 fffff800`030e8d88 : 00000000`0000001e ffffffff`c0000005 fffff800`030a10d9 00000000`00000000 : nt!KeBugCheckEx
fffff880`07887d40 fffff800`0309d842 : fffff880`07888518 ffff4880`09db4200 fffff880`078885c0 ffff3680`09db42c0 : nt! ?? ::FNODOBFM::`string'+0x48d3d
fffff880`078883e0 fffff800`0309c14a : 00000000`00000000 00000000`00000000 fffffa80`0769cb50 fffff800`030a1587 : nt!KiExceptionDispatch+0xc2
fffff880`078885c0 fffff800`030a10d9 : ffff1000`03093bd2 ffff4e80`09db4200 fffffd80`09db4200 0000d500`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`07888758 ffff1000`03093bd2 : ffff4e80`09db4200 fffffd80`09db4200 0000d500`00000000 ffffb300`00000006 : nt!KiSwapContext+0xd9
fffff880`07888760 ffff4e80`09db4200 : fffffd80`09db4200 0000d500`00000000 ffffb300`00000006 00000000`00000000 : 0xffff1000`03093bd2
fffff880`07888768 fffffd80`09db4200 : 0000d500`00000000 ffffb300`00000006 00000000`00000000 00000000`00000000 : 0xffff4e80`09db4200
fffff880`07888770 0000d500`00000000 : ffffb300`00000006 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffd80`09db4200
fffff880`07888778 ffffb300`00000006 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : 0xd500`00000000
fffff880`07888780 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff880`07888a8f : 0xffffb300`00000006


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800030a13a2 - nt!SwapContext_PatchXSave+2
    [ 01:21 ]
    fffff800030a1486 - nt!SwapContext_PatchXRstor+2 (+0xe4)
    [ 09:29 ]
    fffff800030a1642 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bc)
    [ 01:21 ]
    fffff800030a1728 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe6)
    [ 09:29 ]
4 errors : !nt (fffff800030a13a2-fffff800030a1728)

MODULE_NAME: [COLOR=Blue]memory_corruption
[/COLOR] 
IMAGE_NAME:  [COLOR=Blue]memory_corruption[/COLOR]

FOLLOWUP_NAME:  [COLOR=Blue]memory_corruption[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  0

[COLOR=Blue]MEMORY_CORRUPTOR:  ONE_BIT_LARGE[/COLOR]

FAILURE_BUCKET_ID:  [COLOR=Blue]X64_MEMORY_CORRUPTION_ONE_BIT_LARGE[/COLOR]

BUCKET_ID:  [COLOR=Blue]X64_MEMORY_CORRUPTION_ONE_BIT_LARGE[/COLOR]

Followup:[COLOR=Blue] memory_corruption[/COLOR]

ONE of your dumps show memory corruption the other show no definite cause. Lets start with testing your ram one stick at a time for 8 passes with memtest86+ (preferably overnight) following instructions on the link below:
:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Take your time and post back results