Any debuggers about?

[BliarOut]

Just trying to track down random BSOD's on a box.... Changed the RAM, changed the MOBO only thing left from the original machine is the PSU, the CPU and the HDD. From the debug analysis it still look like RAM, but it's unlikely as all sticks have been changed (unless they're all bad )

Anyone got any thoughts on the debug?

The broken machine said:

*******************************************************************************
* *
* 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: 00000003, Process
Arg2: 81cf2d88, Terminating object
Arg3: 81cf2eec, Process image file name
Arg4: 8095aa0e, Explanatory message (ascii)

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


PROCESS_OBJECT: 81cf2d88

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 3e800160

MODULE_NAME: csrss

FAULTING_MODULE: 4a680000 csrss

EXCEPTION_RECORD: f867e9dc -- (.exr fffffffff867e9dc)
ExceptionAddress: 75a96607 (winsrv!wsprintfW)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: 75a96607
Parameter[2]: c00000b5
Inpage operation failed at 75a96607, due to I/O error c00000b5

EXCEPTION_CODE: (NTSTATUS) 0xc00000b5 - {Device Timeout} The specified I/O operation on %hs was not completed before the time-out period expired.

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

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

IO_ERROR: (NTSTATUS) 0xc00000b5 - {Device Timeout} The specified I/O operation on %hs was not completed before the time-out period expired.

EXCEPTION_STR: 0xc0000006_c00000b5

FAULTING_IP:
winsrv!wsprintfW+0
75a96607 ?? ???

BUGCHECK_STR: 0xF4_IOERR_C00000B5

STACK_TEXT:
f867e528 80996ecf 000000f4 00000003 81cf2d88 nt!KeBugCheckEx+0x1b
f867e54c 8095a9d2 8095aa0e 81cf2d88 81cf2eec nt!PspCatchCriticalBreak+0x75
f867e57c 8082337b ffffffff c0000006 f867e9b4 nt!NtTerminateProcess+0x7a
f867e57c 8082262d ffffffff c0000006 f867e9b4 nt!KiFastCallEntry+0xf8
f867e5fc 808553bf ffffffff c0000006 f867e9fc nt!ZwTerminateProcess+0x11
f867e9b4 808772dc f867e9dc 00000000 f867ed64 nt!KiDispatchException+0x390
f867ed34 80826c45 0051f26c 0051f28c 00000000 nt!KiRaiseException+0x120
f867ed50 8082337b 0051f26c 0051f28c 00000000 nt!NtRaiseException+0x31
f867ed50 75a96607 0051f26c 0051f28c 00000000 nt!KiFastCallEntry+0xf8
0051f554 75a9af6a 0016c908 75a9b458 75a81e20 winsrv!wsprintfW
0051fe64 75a9b5bd 00186a68 0000000c 0051fed8 winsrv!GetHardErrorText+0x7de
0051fe84 75a9b787 00000000 0051fed8 00000000 winsrv!UserHardErrorEx+0xf8
0051fe98 75a5433f 00000000 0051fed8 75a58ca0 winsrv!UserHardError+0x12
0051feb8 75a54abc 00000000 0051fed8 000000c8 CSRSRV!QueueHardError+0x101
0051fff4 00000000 00000080 00000000 00000000 CSRSRV!CsrApiRequestThread+0x1e4


STACK_COMMAND: kb

FOLLOWUP_IP:
csrss!_imp__CsrServerInitialization <PERF> (csrss+0x0)+0
4a680000 4d dec ebp

FAULTING_SOURCE_CODE:


FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xF4_IOERR_C00000B5_IMAGE_csrss.exe_DATE_3_25_2003

BUCKET_ID: 0xF4_IOERR_C00000B5_IMAGE_csrss.exe_DATE_3_25_2003

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

[GreenV8S]

No ideas on the debug but my thought is dodgy PSU.

[Einion Yrth]

Bad MMU?

[ThatPhilBrettGuy]

Looks like it was trying to write to a log file (or the event log) and it failed. HDD / cable or PSU then.

[BliarOut]

ThatPhilBrettGuy said:

Looks like it was trying to write to a log file (or the event log) and it failed. HDD / cable or PSU then.

That makes sense.... There's nothing about the crash in the event viewer, there's just a black hole where the event would usually have been recorded.

I know the SCSI controller has been changed but I'm not sure about the cable. I'll check that with the guy who replaced the hardware. In the meantime I'll update the SCSI drivers (doubtful) and run a surface check on the HDD.