PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Vista - Kann Minidump nicht richtig auswerten


Chip4000
2009-05-29, 15:28:52
Hallo!
Hatte eben einen Bluescreen.
Den habe ich mit dem Debugger ausgelesen, aber ich werde daraus nicht schlau.
Kann mir hier vielleicht jemand helfen?
Hab hier mal ein Bild von dem Minidump.
http://www.imgwelt.de/thumbs/M32HZ01ABQ4.jpg (http://www.imgwelt.de/show.php?code=M32HZ01ABQ4)

Chip4000
2009-05-29, 16:25:22
Hab das Minidump-File mal kopiert und hier eingefügt.

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


Loading Dump File [C:\Windows\Minidump\Mini052909-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x81e51000 PsLoadedModuleList = 0x81f68c70
Debug session time: Fri May 29 16:18:24.280 2009 (GMT+2)
System Uptime: 0 days 0:02:22.999
*********************************************************************
* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** 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
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {92fc, 2, 1, 81ec33ae}

*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** WARNING: Unable to verify timestamp for fltmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltmgr.sys
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntkrnlpa.exe ( nt+723ae )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000092fc, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 81ec33ae, address which referenced memory

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

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: 81e51000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 49e0199e

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
000092fc

CURRENT_IRQL: 0

FAULTING_IP:
nt+723ae
81ec33ae ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 81ec33ae to 81e9efb9

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a51c12bc 81ec33ae badb0d00 000092fc 84361251 nt+0x4dfb9
a51c1358 81ec3435 00000000 00000000 9c2e2238 nt+0x723ae
a51c13ac 81e8829c 87ca96ec 00000000 00000001 nt+0x72435
a51c1444 8a2879a6 87ca96ec 00000000 00000000 nt+0x3729c
a51c1498 8a2829e1 01429de0 9c306320 00000000 Ntfs+0x7f9a6
a51c1534 8a287d13 88429de0 853890d8 00000001 Ntfs+0x7a9e1
a51c15b0 8a288209 88429de0 87d0f188 2f387f36 Ntfs+0x7fd13
a51c1618 81e95976 85389020 87d0f188 87d0f188 Ntfs+0x80209
a51c1630 89e38ba7 85d4c9d0 87d0f188 00000000 nt+0x44976
a51c1654 89e38d64 a51c1674 85d4c9d0 00000000 fltmgr+0x5ba7
a51c168c 81e95976 85d4c9d0 87d0f188 87d0f188 fltmgr+0x5d64
a51c16a4 820976a1 87d0f188 884b7500 87e8df50 nt+0x44976
a51c16c4 8205cb97 85d4c9d0 87e8df50 00000000 nt+0x2466a1
a51c1730 81e9bc7a 80000800 a51c17f0 a51c1a04 nt+0x20bb97
a51c1740 81e99db5 badb0d00 a51c17b8 00000000 nt+0x4ac7a
a51c1a04 82129172 a51c1a4c 00000004 81f51b04 nt+0x48db5
a51c1a68 8212a4fc 00000001 2b3b1573 a51c1ba4 nt+0x2d8172
a51c1b90 81e9bc7a 00000006 00000000 00000004 nt+0x2d94fc
a51c1ba4 81e9ab9d badb0d00 a51c1c1c a5001bcc nt+0x4ac7a
a51c1d44 82103ad7 00000006 00000004 c0000004 nt+0x49b9d
a51c1d58 81e9bc7a 00000002 0015fd34 77935e74 nt+0x2b2ad7
a51c1d64 77935e74 badb0d00 0015fd1c 00000000 nt+0x4ac7a
a51c1d68 badb0d00 0015fd1c 00000000 00000000 0x77935e74
a51c1d6c 0015fd1c 00000000 00000000 00000000 0xbadb0d00
a51c1d70 00000000 00000000 00000000 00000000 0x15fd1c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+723ae
81ec33ae ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt+723ae

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

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

Gast
2009-05-29, 16:34:51
kenn mich zwar auch nicht so damit aus aber soweit ich noch in erinnerung habe ist der wirklichen ursache dieser fehlermeldung ohne weiteres nicht auf den grund zu kommen.

Exec
2009-05-29, 17:00:23
Wer nichtmal ein LOG lesen kann, dass nach SYMBOLS schreit, dem traue ich auch den Umgang mit einem Debugger sowie den dazugehörigen Anleitungen nicht zu. :devil:


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



SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

sry.. aber das war eine zu schöne Vorlage für den Situationsjoke ;)

ps. @ TOPIC das System auch nicht

Chip4000
2009-05-29, 18:10:29
Hier kann man es besser sehen.
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini052909-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x81e51000 PsLoadedModuleList = 0x81f68c70
Debug session time: Fri May 29 16:18:24.280 2009 (GMT+2)
System Uptime: 0 days 0:02:22.999
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
...........................
Loading User Symbols
Loading unloaded module list
........
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {92fc, 2, 1, 81ec33ae}

Probably caused by : memory_corruption ( nt!MiComputeFlushRange+22d )

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

Hab memtest mehrmals laufen lassen, allles ohne Fehler.
Prime95 läuft auch stabil.
Ich habe ja am Dienstag meinen 9950BE in Rente geschickt und dafür mir den P2 940BE eingebaut.
Kann es vielleicht damit zusammen hängen?
Zocken konnte ich bis jetzt ohne probleme.

Exec
2009-05-29, 22:30:18
Symbols sind drin.. aber
"!analyze -v" Kommando fehlt..

Meine Bitte ausserdem benutze für solche langen Quotes z.B. die Funktion
Erhöht die Lesbarkeit und Benutzerfreundlichkeit, oder häng bei langen Sachen ein File an den Post an.

Wenn jemand nicht direkt ungefragt erschlagen wird erhöht sich auch die Warscheinlichkeit, dass sich jemand kompetentes die Zeit nimmt es zu lesen.

Dass ich dir jedoch bei deinem wirklichen Problem weiterhelfen kann ist leider unwarscheinlich :frown: (nix Programmierer)

mr orange
2009-05-29, 22:34:07
IRQL_NOT_LESS_OR_EQUAL
BugCheck A

msdn artikel (http://msdn.microsoft.com/en-us/library/ms854226.aspx)

kann durch fehlerhafte Treiber, Hard- oder Software hervorgerufen werden.
ich würde anstatt prime 95 einen stabilitätstest mit intelburntest und memtest (siehe zitat) machen und die treiber auf ihre aktualität prüfen.

der intelburntest (http://www.xtremesystems.org/forums/showthread.php?t=197835) verwendet das programm linpack (im neuen OCCT auch enthalten), das intel selbst zum austesten ihrer cpus verwendet. mit dem programm werden hauptsächlich cpu und ram getestet. dauer ca. 10 minuten bei 10 durchläufen (recommend). da das programm relative hohen cpu temperaturen erzeugen kann, sollten diese stets mit zb. coretemp (http://www.alcpu.com/CoreTemp/) beobachtet werden. fehler machen sich durch ungleichen resultate unter "linpack test results" oder bluescreens bemerkbar.

den nicht verwendeten speicher unter windows kann man auch mit dem programm memtest (http://www.hcidesign.com/memtest/) schnell auf fehler testen. es können mehrere instanzen des programms gestartet werden um wirklich den gesamten freien speicher zu testen.

Chip4000
2009-05-30, 18:11:17
So, hab den Fehler nach 4 Stunden gefunden.
Es war die Samsung 750GB Festplatte.
Samsung und ihre Ausfallraten.
Gerade mal einen Monat alt.
Nie wieder Samsung.
Hab die jetzt gegen eine Hitachi 750 getauscht und jetzt läßt sich Vista ohne Fehler installieren.