Raw.v5 10 Geschrieben 16. Februar 2006 Melden Teilen Geschrieben 16. Februar 2006 moin hab das problem das mein Server manchmal nachts (4 mal diesen monat) abschmiert und mir nach dem neustart folgendes im eventlog hinterlässt. Ereignistyp: Fehler Ereignisquelle: System Error Ereigniskategorie: (102) Ereigniskennung: 1003 Datum: 16.02.2006 Zeit: 09:32:03 Benutzer: Nicht zutreffend Computer: ComputerName Beschreibung: Fehlercode 00000077, 1. Parameter c0000185, 2. Parameter c0000185, 3. Parameter 00000000, 4. Parameter 001e3000. Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp. Daten: 0000: 53 79 73 74 65 6d 20 45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64 65 ror code 0018: 20 30 30 30 30 30 30 37 0000007 0020: 37 20 20 50 61 72 61 6d 7 Param 0028: 65 74 65 72 73 20 63 30 eters c0 0030: 30 30 30 31 38 35 2c 20 000185, 0038: 63 30 30 30 30 31 38 35 c0000185 0040: 2c 20 30 30 30 30 30 30 , 000000 0048: 30 30 2c 20 30 30 31 65 00, 001e 0050: 33 30 30 30 3000 bei eventid ist das plausibelste was ich gefunden habe ein defekt auf dem controller oder der verkabelung ..... meiner meinung nach müsste es dann aber regelmäßiger zum absturz kommen ....... der inhalt vom .dmp file: in den nächsten posts Zitieren Link zu diesem Kommentar
Raw.v5 10 Geschrieben 16. Februar 2006 Autor Melden Teilen Geschrieben 16. Februar 2006 Microsoft (R) Windows Debugger Version 6.6.0003.5 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Dokumente und Einstellungen\UserName\Desktop\Crash\Mini021606-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (2 procs) Free x86 compatible Product: Server, suite: TerminalServer SingleUserTS Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8 Debug session time: Thu Feb 16 04:00:29.859 2006 (GMT+1) System Uptime: 2 days 3:24:19.593 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols .................................................................................................................. Loading User Symbols Loading unloaded module list .... Zitieren Link zu diesem Kommentar
Raw.v5 10 Geschrieben 16. Februar 2006 Autor Melden Teilen Geschrieben 16. Februar 2006 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 77, {c0000185, c0000185, 0, 1e3000} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* Followup: MachineOwner --------- Zitieren Link zu diesem Kommentar
Raw.v5 10 Geschrieben 16. Februar 2006 Autor Melden Teilen Geschrieben 16. Februar 2006 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_STACK_INPAGE_ERROR (77) The requested page of kernel data could not be read in. Caused by bad block in paging file or disk controller error. In the case when the first arguments is 0 or 1, the stack signature in the kernel stack was not found. Again, bad hardware. An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates the data could not be read from the disk due to a bad block. Upon reboot autocheck will run and attempt to map out the bad sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging file is on a SCSI disk device, then the cabling and termination should be checked. See the knowledge base article on SCSI termination. Arguments: Arg1: c0000185, status code Arg2: c0000185, i/o status code Arg3: 00000000, page file number Arg4: 001e3000, offset into page file Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* Zitieren Link zu diesem Kommentar
Raw.v5 10 Geschrieben 16. Februar 2006 Autor Melden Teilen Geschrieben 16. Februar 2006 ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* MODULE_NAME: nt FAULTING_MODULE: 80800000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 42435b14 ERROR_CODE: (NTSTATUS) 0xc0000185 - Das E/A-Ger t hat einen E/A-Fehler gemeldet. DISK_HARDWARE_ERROR: There was error with disk hardware BUGCHECK_STR: 0x77_c0000185 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP LAST_CONTROL_TRANSFER: from 8084a89b to 80827451 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. f7912cbc 8084a89b 00000077 c0000185 c0000185 nt+0x27451 f7912d34 8084b73f c07bc770 0002437a 00000001 nt+0x4a89b f7912d68 8084b7d5 8679bb40 f7912d78 f78ef000 nt+0x4b73f f7912d8c 8088724e 8679bb40 00000000 86792020 nt+0x4b7d5 f7912da4 8088785e 8679bba0 80948bb2 00000000 nt+0x8724e f7912ddc 8088d4d2 808877e2 00000000 00000000 nt+0x8785e 00000000 00000000 00000000 00000000 00000000 nt+0x8d4d2 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_NAME: MachineOwner BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- hab hier und auch per google bis auf eventid 1003 und Fehlercode 00000077 leider keine gemeinsamkeiten gefunden thx a lot edit: es handelt sich um einen Primergy TX200 S2 Zitieren Link zu diesem Kommentar
Empfohlene Beiträge
Schreibe einen Kommentar
Du kannst jetzt antworten und Dich später registrieren. Falls Du bereits ein Mitglied bist, logge Dich jetzt ein.