BSOD Help please!!!

Whalecake, welcome to the forums. I am sorry you are having problems. I will take a look. I looked at your four dumps from today. All of them are error code F4 which is a hardware error code. Memory corruption is shown in all four dumps.

Error code F4, CRITICAL_OBJECT_TERMINATION - BSOD Index.

Code:

Kernel base = 0xfffff800`02a08000 PsLoadedModuleList = 0xfffff800`02c45e50
Debug session time: Fri Oct 15 18:17:10.610 2010 (GMT-4)
System Uptime: 0 days 21:25:16.186
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80061e9060, fffffa80061e9340, fffff80002d835d0}

Probably caused by : csrss.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80061e9060, Terminating object
Arg3: fffffa80061e9340, Process image file name
Arg4: fffff80002d835d0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa80061e9060

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_RECORD:  fffff88002185b78 -- (.exr 0xfffff88002185b78)
ExceptionAddress: 00000000778e592d
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 00000000004d0e58
Attempt to write to address 00000000004d0e58

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  00000000004d0e58

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb00e0
 00000000004d0e58 

FOLLOWUP_IP: 
+5acb952f01b2d8cc
00000000`778e592d ??              ???

FAULTING_IP: 
+5acb952f01b2d8cc
00000000`778e592d ??              ???

FAILED_INSTRUCTION_ADDRESS: 
+5acb952f01b2d8cc
00000000`778e592d ??              ???

BUGCHECK_STR:  0xF4_C0000005

STACK_TEXT:  
fffff880`021850f8 fffff800`02e04652 : 00000000`000000f4 00000000`00000003 fffffa80`061e9060 fffffa80`061e9340 : nt!KeBugCheckEx
fffff880`02185100 fffff800`02dad3e3 : ffffffff`ffffffff fffffa80`06266b60 fffffa80`061e9060 fffffa80`061e9060 : nt!PspCatchCriticalBreak+0x92
fffff880`02185140 fffff800`02d3580c : ffffffff`ffffffff 00000000`00000001 fffffa80`061e9060 fffff6fb`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17946
fffff880`02185190 fffff800`02a77993 : fffffa80`061e9060 fffff800`c0000005 ffffe7af`d79a86ea fffffa80`06266b60 : nt!NtTerminateProcess+0x20c
fffff880`02185210 fffff800`02a73f30 : fffff800`02ab2dbc fffff880`02185b78 fffff880`021858e0 fffff880`02185c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`021853a8 fffff800`02ab2dbc : fffff880`02185b78 fffff880`021858e0 fffff880`02185c20 00000000`004d20e0 : nt!KiServiceLinkage
fffff880`021853b0 fffff800`02a77d82 : fffff880`02185b78 00000000`00071288 fffff880`02185c20 00000000`004d1bb8 : nt!KiDispatchException+0x53b
fffff880`02185a40 fffff800`02a768fa : 00000000`00000001 00000000`00071288 00000000`00000001 fffffa80`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02185c20 00000000`778e592d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`004d0e60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778e592d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

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

To begin troubleshooting, I recommend that you completely uninstall Eset NOD 32 using this uninstall tool: Tool. Eset has been known to cause crashes on some Win 7 systems. You can reinstall it after you get your system stable; but I do not recommend doing so. Download and install Microsoft Security Essentials in its place.

You have some out of date drivers on your system; some are quite obsolete. Out of date drivers can and do cause memory corruption and crashes. While I cannot say these drivers are causing your crashes, I can say they are not contributing to the stability of your system. Up date the following driver or uninstall the hardware/software they are associated with.

MSILiveVirtualCamera.sys Mon Jan 29 02:40:57 2007 - This is an XP driver. MSI Live Virtual Camera, MSI Corporation. MSI Europe - Notebook, Netbook, Nettop and All in One support page. Try to update the driver. If you can't, uninstall this device/software and upgrade to something certified to be compatible with Win 7.

NTGLM7X64.sys Sun Dec 07 22:23:19 2008 - I cannot find anything definitive on this driver. I think it is an MSI driver. You might try to update it it from your computer manufacturer's website.

nvm62x64.sys Fri Oct 17 17:01:06 2008 - nVidia Ethernet Networking Driver (nForce chipset driver) Drivers - Download NVIDIA Drivers

RushTop64.sys Tue Mar 17 22:56:51 2009 - This is another MSI driver. I cannot find definitive information on it. Try to update from your computer manufacturer's website or from MSI.

Update the above drivers, especially those in red font. How to update drivers -

- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

After you have taken care of these drivers, run your system and see how it does. If you get another BSOD, upload it to us. Then test your RAM with Memtest. Follow the instructions in this tutorial:

RAM - Test with Memtest86+

Post the results of the test.

Refresh this page. I have finished and given you more information. Good job on uninstalling Eset. What we are trying to do is eliminate all possible causes of crashes sine the dumps do not point to a specific cause. We will have to do this in steps.

You need to update your chipset drivers. Do that from either your computer manufacturer's website, your motherboard manufacturer's website or the NVidia website. Generally, we do not recommend using a third party tool to update drivers; we recommend going to the appropriate website, downloading the drivers and installing them.