Questions

What might be the cause of this blue screen of death?

+
0 Votes
Locked

What might be the cause of this blue screen of death?

majestic84
All I can tell from the information below is that csrss.exe is the culprit, but I know that csrss.exe is an essential component of Windows. Any resolution ideas for this issue would be greatly appreciated.

Output of WinDbg.exe:

3: 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: fffffa800aaadc10, Terminating object
Arg3: fffffa800aaade48, Process image file name
Arg4: fffff80001ef5640, Explanatory message (ascii)

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


DISK_IO_READ_FAILURE: WARNING: Disk IO Read of 0 Bytes Occurred 4 time(s).

PROCESS_OBJECT: fffffa800aaadc10

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: csrss.exe

EXCEPTION_CODE: (Win32) 0xb6d22a0 (191701664) - <Unable to get error code text>

BUGCHECK_STR: 0xF4_B6D22A0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffffa60`057c2c68 fffff800`01f707a3 : 00000000`000000f4 00000000`00000003 fffffa80`0aaadc10 fffffa80`0aaade48 : nt!KeBugCheckEx
fffffa60`057c2c70 fffff800`01e8a218 : fffffa80`0b6d22a0 fffffa80`0b6d22a0 fffffa60`057c3c20 fffffa60`057c3ae0 : nt!PspCatchCriticalBreak+0x93
fffffa60`057c2cb0 fffff800`01ebd920 : fffffa80`0b6d22a0 00000000`00000008 fffffa60`057c3c20 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x10f86
fffffa60`057c2d00 fffff800`01c70f33 : fffffa80`0aaadc10 fffffa80`0b6d22a0 fffffa60`057c2de0 fffffa60`057c3c20 : nt!NtTerminateProcess+0xd8
fffffa60`057c2d60 fffff800`01c71440 : fffff800`01cd12fd fffffa60`057c3540 fffffa60`057c3ca0 fffffa60`057c3c20 : nt!KiSystemServiceCopyEnd+0x13
fffffa60`057c2ef8 fffff800`01cd12fd : fffffa60`057c3540 fffffa60`057c3ca0 fffffa60`057c3c20 00000000`00000038 : nt!KiServiceLinkage
fffffa60`057c2f00 fffff800`01d31f41 : fffffa60`057c3540 fffffa60`057c3540 fffffa60`057c3c20 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x2935c
fffffa60`057c3500 fffff800`01c73060 : fffffa60`057c3540 fffffa60`057c35e0 fffffa80`0b6d22a0 00000000`00000000 : nt!KiRaiseException+0x141
fffffa60`057c3ae0 fffff800`01c70f33 : 00000000`00000008 fffffa60`057c3ca0 00000000`00000001 00000000`00000000 : nt!NtRaiseException+0x80
fffffa60`057c3c20 00000000`77954fb6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00e4ef30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77954fb6


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_B6D22A0_IMAGE_csrss.exe

BUCKET_ID: X64_0xF4_B6D22A0_IMAGE_csrss.exe

Followup: MachineOwner
---------
+
1 Votes
OH Smeg

For a 64 Bit Version of Vista. It reads like you have the wrong driver or maybe a 32 Bit driver in use.

Col

+
0 Votes
majestic84

Thanks OH Smeg, I shall review the drivers today and report back with my findings.

+
0 Votes
hgale

It is probably a driver issue and/or a firmware issue

In response to SMEG, Windows64 bit does not allow you to install 32 bit or unsigned drivers.

Is this constantly happening or was it a one time issue?

+
0 Votes
dayen

Need more info like were you doing update or installing any software when it crash or was this on a reboot or cold boot

+
1 Votes
Slayer_

Maybe run a surface scan on your HDD, and run a SMART test (Assuming your system boots)

+
0 Votes
Spitfire_Sysop

That was my first thought. Make a backup of crucial data before running any scans because the scan could be the straw that breaks your camel's ability to read data ever again.

The scans also may show no problems and then the drive could die tomorrow.