Nachdem mich seit 2 Tagen ein regelmäßiger Stop-Fehler (0x000000F4) quält (vielmehr mein System) bin ich mittlerweile nach stundenlanger Internetrecherche immerhin bei den debugging-tools für Windows angekommen und hier nun der Bericht mit windbg. Die Explanatory message war bei den letzten 3 Berichten immer die Selbe. Hardware oder Software?
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\\windows\\minidump\\mini042105-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\\windows\\i386
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Apr 21 22:29:05.734 2005 (GMT+2)
System Uptime: 0 days 0:00:44.322
Loading Kernel Symbols
...................................................................................................................................
Loading unloaded module list
........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, 85fb8da0, 85fb8f14, 805c7478}
Probably caused by : csrss.exe
Followup: MachineOwner
---------
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: 00000003, Process
Arg2: 85fb8da0, Terminating object
Arg3: 85fb8f14, Process image file name
Arg4: 805c7478, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: 85fb8da0
IMAGE_NAME: csrss.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: csrss
FAULTING_MODULE: 00000000
EXCEPTION_RECORD: edb789d8 -- (.exr ffffffffedb789d8)
ExceptionAddress: 75b1b129
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000008
Parameter[1]: 75b1b129
Parameter[2]: c000009d
Inpage operation failed at 75b1b129, due to I/O error c000009d
EXCEPTION_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
BUGCHECK_STR: 0xF4_IOERR_C000009D
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: csrss.exe
LAST_CONTROL_TRANSFER: from 805c65a9 to 804f8925
STACK_TEXT:
edb78520 805c65a9 000000f4 00000003 85fb8da0 nt!KeBugCheckEx+0x1b
edb78544 805c7523 805c7478 85fb8da0 85fb8f14 nt!PspCatchCriticalBreak+0x75
edb78574 8053c808 85fb8fe8 c0000006 edb789b0 nt!NtTerminateProcess+0x7d
edb78574 804fe699 85fb8fe8 c0000006 edb789b0 nt!KiFastCallEntry+0xf8
edb785f4 804fc962 ffffffff c0000006 edb789f8 nt!ZwTerminateProcess+0x11
edb789b0 804ff8ed edb789d8 00000000 edb78d64 nt!KiDispatchException+0x3a0
edb78d34 80540049 0052fbe8 0052fc08 00000000 nt!KiRaiseException+0x175
edb78d50 8053c808 0052fbe8 0052fc08 00000000 nt!NtRaiseException+0x31
edb78d50 75b1b129 0052fbe8 0052fc08 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0052fed0 00000000 00000000 00000000 00000000 0x75b1b129
FOLLOWUP_NAME: MachineOwner
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0xF4_IOERR_C000009D_IMAGE_csrss.exe
BUCKET_ID: 0xF4_IOERR_C000009D_IMAGE_csrss.exe
Followup: MachineOwner
---------
Ich hab ja mein Raid 0 mit 2 Samsung SP0812C in Verdacht aber vielleicht wisst ihr ja genaueres...
jim clark
