573 Aufrufe
Gefragt in WindowsXP von hallo34 Einsteiger_in (3 Punkte)
Hallo


Ich habe seit 3 Tagen ein Problem und zwar freezt mein PC in unregelmäßigen Abständen ein, am meisten passiert es wenn ich World of Warcraft spiele ich kann max. 5 Minuten spielen dann freeze und manchmal bekomme ich einen Bluescreen. Aber manchmal kann ich auch 3-4 Stunden problemlos zocken ohne Freeze. Ich dachte das läge an Windows XP, habs neu installiert = Problem bleibt bestehen. Dann Festplatte gewechselt XP installiert = Problem bleibt bestehen. Danach habe ich mal den RAM mit Memtest86 geprüft es wurden 0 Fehler gefunden. Ich weiß langsam nicht mehr was ich tun soll dieses ständige gefreeze nervt tieriesch. In dem Bluescreen steht drin 0x000000F4 (0x00000003,0x866B810,0x866B8F14,0x8060577E)


Hab jetzt mal einen Bluescreen mit WinDbg geöffnet in dem steht:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, 866b8da0, 866b8f14, 8060577e}

Probably caused by : csrss.exe

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

1: 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: 866b8da0, Terminating object
Arg3: 866b8f14, Process image file name
Arg4: 8060577e, Explanatory message (ascii)

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


PROCESS_OBJECT: 866b8da0

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: csrss

FAULTING_MODULE: 00000000

EXCEPTION_RECORD: b804d9d8 -- (.exr ffffffffb804d9d8)
ExceptionAddress: 75b1b3b9
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: 75b1b3b9
Parameter[2]: c000000e
Inpage operation failed at 75b1b3b9, due to I/O error c000000e

EXCEPTION_CODE: (NTSTATUS) 0xc000000e - Ein nicht vorhandenes Ger t wurde angegeben.

BUGCHECK_STR: 0xF4_IOERR_C000000E

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: csrss.exe

LAST_CONTROL_TRANSFER: from 80635e9d to 805376ba

STACK_TEXT:
b804d520 80635e9d 000000f4 00000003 866b8da0 nt!KeBugCheckEx+0x1b
b804d544 8060573c 8060577e 866b8da0 866b8f14 nt!PspCatchCriticalBreak+0x75
b804d574 804dd99f 866b8fe8 c0000006 b804d9b0 nt!NtTerminateProcess+0x7d
b804d574 804e46c7 866b8fe8 c0000006 b804d9b0 nt!KiFastCallEntry+0xfc
b804d5f4 80522230 ffffffff c0000006 b804d9f8 nt!ZwTerminateProcess+0x11
b804d9b0 8051849c b804d9d8 00000000 b804dd64 nt!KiDispatchException+0x3a0
b804dd34 804e12ba 00dafbe8 00dafc08 00000000 nt!KiRaiseException+0x175
b804dd50 804dd99f 00dafbe8 00dafc08 00000000 nt!NtRaiseException+0x33
b804dd50 75b1b3b9 00dafbe8 00dafc08 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00dafed0 00000000 00000000 00000000 00000000 0x75b1b3b9


FOLLOWUP_NAME: MachineOwner

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xF4_IOERR_C000000E_IMAGE_csrss.exe

BUCKET_ID: 0xF4_IOERR_C000000E_IMAGE_csrss.exe

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







Und in dem 2. Bluescreen wo im Minidump Ordner war
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8056ed77, b7afa970, 0}

Probably caused by : ntkrnlmp.exe ( nt!NtWaitForMultipleObjects+1b0 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8056ed77, The address that the exception occurred at
Arg3: b7afa970, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.

FAULTING_IP:
nt!NtWaitForMultipleObjects+1b0
8056ed77 8b4048 mov eax,[eax+0x48]

TRAP_FRAME: b7afa970 -- (.trap ffffffffb7afa970)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=fdffffff edx=85aedd01 esi=85aedd00 edi=865c2da8
eip=8056ed77 esp=b7afa9e4 ebp=b7afad48 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!NtWaitForMultipleObjects+0x1b0:
8056ed77 8b4048 mov eax,[eax+0x48] ds:0023:00000048=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 804dd99f to 8056ed77

STACK_TEXT:
b7afad48 804dd99f 00000002 028ffc68 00000001 nt!NtWaitForMultipleObjects+0x1b0
b7afad48 7c91e514 00000002 028ffc68 00000001 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
028ffc3c 00000000 00000000 00000000 00000000 0x7c91e514


FOLLOWUP_IP:
nt!NtWaitFo

1 Antwort

0 Punkte
Beantwortet von saarbauer Profi (15.6k Punkte)
Hallo,

hier einige Hinweise zu dem Bluescreen

www.jasik.de/shutdown/stop_fehler.htm#F4


Gruß

Helmut
...