tabbert69
May 29, 2007, updated at Jun 05, 2007 (UTC)
view6834
view8
0
Goto Top

Probleme mit Windows 2003

GermansolvedQuestionWindows ServerMicrosoft
Ich bekomme bei unserem Server ständig diesen Fehlercode 1000008e, 1. Parameter c0000005, 2. Parameter bf8e8d73, 3. Parameter f49dfb24, 4. Parameter 00000000. Vorher stürtzt der Server sporadisch ab und fährt wieder hoch. Betriebsystem ist windows Server 2003. An Wochenenden wenn keiner arbeitet läuft er aber stabil! Kennt jeman diesen Fehler?
comment-contentCommentShareShare
Share on Facebook Share on Twitter Share on Reddit Share on Linkedin

Content-Key: 60046

Url: https://administrator.de/contentid/60046

Printed on: May 6, 2024 at 14:05 o'clock

8 Comments
Latest comment
Goto Top
Member: cykes
cykes May 29, 2007 at 09:57:42 (UTC)
Goto Top
Hi,

der x0...08E Fehler ist meist auf ein Treiberproblem zurückzuführen oder (ich hatte den neulich
auch mal) auf eine defekte Platte. Bei mir machte eine SATA Platte Probleme beim Lesen und diese
geht nach Sicherung der Daten in den Service...

Wurde in letzter Zeit irgendwas and er Hardware/Software geändert bzw. installiert?

Gruß

cykes
Member: tabbert69
tabbert69 May 31, 2007 at 17:16:58 (UTC)
Goto Top
Ich habe mal die mini.dmp ausgelesen. Kann damit jemand was anfangen?

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [T:\Mini053107-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\ntoskrnl.exe, Win32 error 2
* WARNING: Unable to verify timestamp for ntoskrnl.exe
* ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2003 Kernel Version 3790 UP Free x86 compatible
Product: LanManNt, suite: Enterprise TerminalServer
Kernel base = 0x804de000 PsLoadedModuleList = 0x80568c08
Debug session time: Thu May 31 14:48:18.921 2007 (GMT+2)
System Uptime: 1 days 6:16:28.511
*
  • 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\ntoskrnl.exe, Win32 error 2
* WARNING: Unable to verify timestamp for ntoskrnl.exe
* ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* WARNING: Unable to verify timestamp for win32k.sys
* ERROR: Module load completed but symbols could not be loaded for win32k.sys
*
  • *
  • Bugcheck Analysis *
  • *
*

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf8e990e, f33bfe80, 0}

* Kernel symbols are WRONG. Please fix symbols to do analysis.

* 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 *
* *
*
Probably caused by : win32k.sys ( win32k+e990e )

Followup: MachineOwner
Member: cykes
cykes Jun 01, 2007 at 06:38:49 (UTC)
Goto Top
Hi,

führe zunächst einmal ein BIOS Update für das Mainboard durch.
Dann such mal nach aktuellen Mainboardtreibern (Chipsatz, AGP/PCIe, SATA, IDE usw.)
und installiere diese.

Wenn das Problem dann immer noch besteht, melde Dich nochmal.

Gruß

cykes
Member: tabbert69
tabbert69 Jun 01, 2007 at 07:01:15 (UTC)
Goto Top
Danke erst mal für die schnelle Antwort! Ich werde mich am Wochenende drüber her machen!
Melde mich dann Montag.
Member: tabbert69
tabbert69 Jun 04, 2007 at 09:08:41 (UTC)
Goto Top
Hallo cykes

kann es sein, das ein Kernelmodustreiber eines Faxkombigerätes von Panasonic das Problem verursacht? Die Treiber sind alle akutell

Gruß Andre
Member: cykes
cykes Jun 05, 2007 at 07:18:05 (UTC)
Goto Top
Hi,

dafür kann jeglicher Treiber verantwortlich sein. Insbesondere unsignierte Treiber verursachen
derartige Probleme häufig.

Die Platten und die Ereignisanzeige hast Du inzwischen mal durchgescheckt?

Gruß

cykes
Member: tabbert69
tabbert69 Jun 05, 2007 at 10:24:23 (UTC)
Goto Top
Ja hab ich! Heute habe ich die Speichermodule getauscht, weil in der mini.dmp etwas von einem Speicherproblem stand.
Member: tabbert69
tabbert69 Jun 05, 2007 at 12:04:24 (UTC)
Goto Top
Heute nach dem Speichertausch kam das??????????????????

Microsoft (R) Windows Debugger Version 6.6.0007.5

Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]

Kernel Complete Dump File: Full address space is available




WARNING: Dump file has been truncated. Data may be missing.



Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:



THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.



Unable to read PsLoadedModuleList



THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.



KdDebuggerData.KernBase < SystemRangeStart

Windows Server 2003 Kernel Version 3790 UP Free x86 compatible

Product: LanManNt, suite: Enterprise TerminalServer

Kernel base = 0x00000000 PsLoadedModuleList = 0x80568c08

Debug session time: Tue Jun 5 13:49:39.687 2007 (GMT+2)

System Uptime: 0 days 5:28:20.265



THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.



Unable to read PsLoadedModuleList



THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.



KdDebuggerData.KernBase < SystemRangeStart

Loading Kernel Symbols

Unable to read PsLoadedModuleList

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

CS descriptor lookup failed

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

Unable to get program counterGetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

*

  • *

  • Bugcheck Analysis *

  • *

*


Use !analyze -v to get detailed debugging information.


BugCheck 8E, {c0000005, bf8e8d73, f3b9bb24, 0}


* Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


GetContextState failed, 0x80070026

Unable to read selector for PCR for processor 0

GetContextState failed, 0x80070026

Unable to read selector for PCR for processor 0

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

GetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

GetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

GetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

GetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

GetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

Unable to get current machine context, Win32 error 38

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )


Followup: MachineOwner




GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026

GetContextState failed, 0x80070026
GermansolvedQuestionWindows ServerMicrosoft
Hotly discussed
LinuxeroWireguard with systemd and nftablesLinuxero - 9 Comments