Ich bekomme leider im Laufenden Betrieb von XP in unregelmäßigen Zeitabständen immer Bluescreens. Zuerst bleibt alles hängen (Bild ist noch da) und nach ein paar Sekunden hab ich dann den Bluescreen.
Wenn ich das automatisch erstellte Speicherabbild mit den Windows Debugging Tools überprüfe kommt dabei das raus:
Ich hoffe mal das Irgendjemand daraus schlau werden kann.
xblax
Wenn ich das automatisch erstellte Speicherabbild mit den Windows Debugging Tools überprüfe kommt dabei das raus:
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINXP\MEMORY.DMP]
Kernel Complete Dump File: Full 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 ntkrpamp.exe -
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.050928-1517
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sun Jan 22 18:53:29.437 2006 (GMT+1)
System Uptime: 0 days 5:27:26.020
WARNING: Process directory table base 0037B000 doesn't match CR3 06C40020
WARNING: Process directory table base 0037B000 doesn't match CR3 06C40020
*********************************************************************
* 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 ntkrpamp.exe -
Loading Kernel Symbols
.................................................................................................................................
Loading unloaded module list
......................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {4, 8054d5f0, b2000000, 70f0f}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** ERROR: Symbol file could not be found. Defaulted to export symbols for halmacpi.dll -
Followup: MachineOwner
---------
Ich hoffe mal das Irgendjemand daraus schlau werden kann.
xblax