Windows Server 2003 - BSOD

[vilden]

Hallo,

hab hier nen Rechner der andauernd ausgeht :/

AMD Athlon(tm) XP 2400+ ~ 2000MHz
Gigabyte GA-7VAXFS
1,5 GB DDR SDRAM
ATI Radeon X850PRO
Windows Server 2003 Standard Edition
---------------------------------------------------------------
Temperaturen:
Motherboard: 35°C
CPU: 34°C
GPU: 47°C
HDD: 42°C

Hab da auf der PCPraxis so nen tool gefunden "Debugging Tools for Windows" - " WINDbg" damit kann man die Blue Screen dump datei auslesen... da kam das heraus

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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Windows Server 2003 Kernel Version 3790 UP Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_rtm.030324-2048
Kernel base = 0x804de000 PsLoadedModuleList = 0x80568c08
Debug session time: Tue Mar 4 17:36:38.531 2008 (GMT+1)
System Uptime: 0 days 0:40:16.109
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Loading Kernel Symbols
.................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffdf00c). Type ".hh dbgerr001" for details
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000005, 804e0c4d, ba7b1bb0, 0}

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

Page c41d not present in the dump file. Type ".hh dbgerr004" for details
*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Page c41d not present in the dump file. Type ".hh dbgerr004" for details
Page c41d not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : hardware ( win32k!EngLpkInstalled+8db9 )

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

Kennt das problem evtl. jemand und die passende Lösung dafür ?

 

[HisN]

Für die Leute die sich nicht mit dem Debugger auskennen wäre auch der STOP-Code vom BSOD ein guter Hinweis was falsch läuft.

 

[vilden]

Ok, also in der Ereignisanzeige steht folgendes:

Der vom Benutzer ***\Administrator angegebene Grund für das unerwartete Herunterfahren des Computers: Systemfehler: Abbruchfehler
Begründung: Code: 0x805000f
Fehlerkennung:
Fehlercheckzeichenfolge: 0x0000008e (0xc0000005, 0x804e0c4d, 0xba7b1bb0, 0x00000000)
Kommentar: 0x0000008e (0xc0000005, 0x804e0c4d, 0xba7b1bb0, 0x00000000)

 

[TheCadillacMan]

Klick mich!

 

[vilden]

Danke für den Link

hab mal den RAM gewechselt und momentan läuft er seit 2 Stunden 35minuten schonmal besser als 10min ^^

 

[Frightener]

So kannst Du mit dem Debugger nichts anfangen:

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. *

Gib das bei Symbol File Path ein:
SRV*C:\WebSymbols*http://msdl.microsoft.com/download/symbols