CSRSS.EXE BSOD Error" VISTA_DRIVER_FAULT"

Original Title: CSRSS.EXE BSOD

 

I started having issues with the computer freezing and BSODing, or freezing with a pink or blue blank screen and then restarting.  I was able to get a minidump and it is as follows:


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: fffffa800f62fb30, Terminating object
Arg3: fffffa800f62fe10, Process image file name
Arg4: fffff800029927b0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa800f62fb30

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`05fe6e38 fffff800`02a1bab2 : 00000000`000000f4 00000000`00000003 fffffa80`0f62fb30 fffffa80`0f62fe10 : nt!KeBugCheckEx
fffff880`05fe6e40 fffff800`029c6abb : ffffffff`ffffffff fffffa80`0eab9b50 fffffa80`0f62fb30 fffffa80`0f62fb30 : nt!PspCatchCriticalBreak+0x92
fffff880`05fe6e80 fffff800`02946674 : ffffffff`ffffffff 00000000`00000001 fffffa80`0f62fb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`05fe6ed0 fffff800`0268ce53 : fffffa80`0f62fb30 fffff800`c0000006 fffffa80`0eab9b50 00000000`00980e00 : nt!NtTerminateProcess+0xf4
fffff880`05fe6f50 fffff800`02689410 : fffff800`026d882f fffff880`05fe7a38 fffff880`05fe7790 fffff880`05fe7ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`05fe70e8 fffff800`026d882f : fffff880`05fe7a38 fffff880`05fe7790 fffff880`05fe7ae0 00000000`00981b10 : nt!KiServiceLinkage
fffff880`05fe70f0 fffff800`0268d242 : fffff880`05fe7a38 00000000`00013600 fffff880`05fe7ae0 00000000`009815e8 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`05fe7900 fffff800`0268bdba : 00000000`00000000 000007fe`fda2d8c0 00000000`00000001 00000000`00013600 : nt!KiExceptionDispatch+0xc2
fffff880`05fe7ae0 00000000`77c69c42 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00981530 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c69c42


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


I have run spybot and malware bytes and hasn't seemed to fix anything.  Thanks for any input.
 

Question Info


Last updated September 5, 2018 Views 1,399 Applies to:
Answer
Answer
VB

There was an IO error causing a critical process to terminate.  I would start by running a system file check & CHKDSK


Please run a system file check (SFC)

All instructions are in our Wiki article below...
Should you have any questions please ask us.




CHKDSK /R /F
Chkdsk disclaimer: While performing chkdsk on the hard drive if any bad sectors are found  any data available on that sector might be lost so as usual backup your data.
Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.
Do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.
It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.
http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/


 See "CHKDSK LogFile" below in order to check the results of the test.

CHKDSK LogFile:

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post. 

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.