Hello:On May 17th, my AVAST program sent a warning of a possible Virus I picked up. Immediately I ranAVAST's Quick Scan and had0 infections. Than I ran Malwarebytes it found0 infections; and Than Ad-Aware, still0 infections. Let me stop here and tell you what's been going on, which brought me here. Normally I go toGeeks-To-Go, great web site, but it really depends which Geek takes on your problem, will I got a person who is not really helping me as I need, so here I am. As I stated above, this problem has been going on since May 17th. The 1st problem was thisBlue Screen of Death, I typed out that message below as what it said. This Blue screen has happened only twice, thank God, but where I'm having my problems are the freezes, which have happened, I know at least,15-20 times. I always have to do a HARD SHUT down, before my Systems Tray loads. Just this morning, I did 4 Hard Shut downs before I was able to move on my Desktop. It appears that my System is becoming more unstable because this problem is NOT being dealt with. So, this is where I am now. Also, this Geek that's been looking at the problems, gave me this Tool called "WhoCrashed", I don't know if any of you are aware of this tool, but please just look at the Log so you can see for yourselves what it says. Below is what the Blue screen said:A problem has been detected and Windows has been shut down to prevent damage to your computer.A process or thread crucial to system operation has unexpectedly exited or been terminated.If this is the 1st time you've seen this stop error screen, restart your computer.Check to make sure any new hardware or software is properly reinstalled. If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing.Then it talks about using Safe Mode to remove or disable any components.Then it gave this information:STOP: 0x000000F4 (0x00000003, 0x86FF92B0, 0x86FF9424, 0x805FB146)Then it says:Beginning dump of physical memory.Physical memory dump complete.END Here is the "WhoCrashed Log" Analysis---------------------------------------------------------------- Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Mon 5/17/2010 5:49:06 PM your computer crashedThis was likely caused by the following module: csrss.exeBugcheck code: 0xF4 (0x3, 0x86EA74E0, 0x86EA7654, 0x805FB146)Error: CRITICAL_OBJECT_TERMINATIONDump file: C:\WINDOWS\Minidump\Mini051710-01.dmpfile path: C:\WINDOWS\system32\csrss.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Client Server Runtime ProcessThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Sun 5/16/2010 4:30:14 AM your computer crashedThis was likely caused by the following module: csrss.exeBugcheck code: 0xF4 (0x3, 0x86FF92B0, 0x86FF9424, 0x805FB146)Error: CRITICAL_OBJECT_TERMINATIONDump file: C:\WINDOWS\Minidump\Mini051610-02.dmpfile path: C:\WINDOWS\system32\csrss.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Client Server Runtime ProcessThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Sun 5/16/2010 2:44:53 AM your computer crashedThis was likely caused by the following module: csrss.exeBugcheck code: 0xF4 (0x3, 0x86EAF4E8, 0x86EAF65C, 0x805FB146)Error: CRITICAL_OBJECT_TERMINATIONDump file: C:\WINDOWS\Minidump\Mini051610-01.dmpfile path: C:\WINDOWS\system32\csrss.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Client Server Runtime ProcessThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Mon 2/1/2010 3:35:41 AM your computer crashedThis was likely caused by the following module: csrss.exeBugcheck code: 0xF4 (0x3, 0x86F55B10, 0x86F55C84, 0x805FB066)Error: CRITICAL_OBJECT_TERMINATIONDump file: C:\WINDOWS\Minidump\Mini020110-03.dmpfile path: C:\WINDOWS\system32\csrss.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Client Server Runtime ProcessThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Mon 2/1/2010 2:21:04 AM your computer crashedThis was likely caused by the following module: csrss.exeBugcheck code: 0xF4 (0x3, 0x86FBF1A8, 0x86FBF31C, 0x805FB066)Error: CRITICAL_OBJECT_TERMINATIONDump file: C:\WINDOWS\Minidump\Mini020110-02.dmpfile path: C:\WINDOWS\system32\csrss.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Client Server Runtime ProcessThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Mon 2/1/2010 2:12:06 AM your computer crashedThis was likely caused by the following module: csrss.exeBugcheck code: 0xF4 (0x3, 0x872F07C8, 0x872F093C, 0x805FB066)Error: CRITICAL_OBJECT_TERMINATIONDump file: C:\WINDOWS\Minidump\Mini020110-01.dmpfile path: C:\WINDOWS\system32\csrss.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Client Server Runtime ProcessThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Fri 1/29/2010 11:24:24 AM your computer crashedThis was likely caused by the following module: csrss.exeBugcheck code: 0xF4 (0x3, 0x872E0DA0, 0x872E0F14, 0x805FB066)Error: CRITICAL_OBJECT_TERMINATIONDump file: C:\WINDOWS\Minidump\Mini012910-01.dmpfile path: C:\WINDOWS\system32\csrss.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Client Server Runtime ProcessThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Fri 1/1/2010 12:10:56 AM your computer crashedThis was likely caused by the following module: win32k.sysBugcheck code: 0x1000008E (0xC0000005, 0xBF8124E9, 0xEE41333C, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_MDump file: C:\WINDOWS\Minidump\Mini010110-01.dmpfile path: C:\WINDOWS\system32\win32k.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Multi-User Win32 DriverThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.----------------------------------------------------------------Conclusion ---------------------------------------------------------------- 8 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.1 person needs an answerI do too

Is csrss.exe located in the windows system 32 folder or elsewhere? If elsewhere its a virus / trojan

Hello Palcouk: I have NO idea, I don't even know what csrss.exe is. How would I find out if it's a Folder or not ??? I have run all the Programs and Tools on my PC, and every thing came up0infections. But have to tell you, all the Programs I've run have not been anyFULL Scans. Because I'm not Technical, if you instruct me to do something, please walk me thru because I only know how to turn on my PC.Let me also mention, I went to the DELL web site, to their Support page, there I read about this ("DST"), I followed their instructions and here is what I got after that Diagnostics was finished:Diskette drive 0 seek failurePrimary IDEDrive 0: WDC WD800BB-75JHCQ - PASSDrive 1: No IDE deviceSecondary IDEDrive 0: HL-DT-ST GCE-8487B - Diagnostics not supportedDrive 1: No IDE deviceI just want to know if it's my Hard Drive. Thank U !!!

you might try to boot up the diagnostic boot menu.then select "last known good configuration" and see if you can reboot normally.if the above proves futile then select safe mode and try to execute a "clean boot"if the above proves futile then you may need to boot up with a xp cd and execute a check disk.db`...> DatabaseBen, Retired Professional - Systems Analyst - Database Developer - Accountancy - Veteran of the Armed Forces - @Hotmail.com "share the nirvana mann" - dbZen ~~~~~~~~~~~~~~~ > >