Windows 7 crash

Windows goes very badly and slow..

After a restart or crash the system runs perfectly....

Plz help

herah said:

Windows goes very badly and slow..

After a restart or crash the system runs perfectly....

Plz help

with only this one crash to go by our results are limited.

This one was caused by csrss.sys (a windows 7 files that handles graphic input and output)

I would run a system file check to verify and repair your system files. Check the log genereated at the end of it and if it says violations were found but could not be repaired you may have to do a repair install. Please upload the cbs.log file generated.



Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.

Ken

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\031211-21200-01.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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0325c000 PsLoadedModuleList = 0xfffff800`034a1e90
Debug session time: Sat Mar 12 05:18:04.501 2011 (GMT-4)
System Uptime: 0 days 0:09:59.280
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

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

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8006a42b30, fffffa8006a42e10, fffff800035dfdb0}

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: fffffa8006a42b30, Terminating object
Arg3: fffffa8006a42e10, Process image file name
Arg4: fffff800035dfdb0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8006a42b30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`04711b08 fffff800`03664982 : 00000000`000000f4 00000000`00000003 fffffa80`06a42b30 fffffa80`06a42e10 : nt!KeBugCheckEx
fffff880`04711b10 fffff800`036120ab : ffffffff`ffffffff fffffa80`05546b60 fffffa80`06a42b30 fffffa80`06a42b30 : nt!PspCatchCriticalBreak+0x92
fffff880`04711b50 fffff800`03595698 : ffffffff`ffffffff 00000000`00000001 fffffa80`06a42b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17ad6
fffff880`04711ba0 fffff800`032db8d3 : fffffa80`06a42b30 fffff880`c0000006 fffffa80`05546b60 fffffa80`06a49060 : nt!NtTerminateProcess+0xf4
fffff880`04711c20 00000000`77be15da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0162ea78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77be15da


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

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

haii i ran the windows file test and found no errors.. it crashed again but without leaving a dumb file.. i toke 2 screenshoots....

thx again