[nobody is perfect]

Hallo Mellosun



wenn ich die Datei anklicke wird sie direkt mit Editor geöffnet




nobody is perfect

[Mellosun]

OK, nachdem ich sie aufs Desktop kopiert habe, wird mir auch was angezeigt.....nur da blickt ja niemand durch!

Habe sie mal als Anhang beigefügt, vielleicht sieht das bei euch anders aus? Musste sie allerdings in txt unbennen, sonst klappte das mit dem anhängen net!

Angehängte Datei(en)

•  Mini012108_01.txt (135,02K)
  Anzahl der Downloads: 121

[Crapshit]

Zum Öffnen der DUMP-Datei benötigen Sie ein entsprechendes Debugging-Tool, welches Sie sich von Microsoft herunterladen können:

Download (11,3 MB): http://msdl.microsoft.com/download/symbols...x86_6.4.7.2.exe

Keine Ahnung obs das aktuelleste ist. www.google.de
Das kann dir das Problem zeigen. Zum Beispiel obs ein Treiberproblem wäre.
Wenns Hardware ist wird die das Dump File nur bedingt weiter helfen bis gar nicht.

Dieser Beitrag wurde von alphazero bearbeitet: 21. Januar 2008 - 22:40

[Mellosun]

So, jetzt hat das auch mit dem öffnen geklappt:

Hoffe das wird nicht zu lang und Ihr könnt was draus erkennen!

Microsoft ® Windows Debugger Version 6.4.0007.2
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini012108-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 2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Longhorn Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Mon Jan 21 19:22:30.341 2008 (GMT+1)
System Uptime: 0 days 11:29:49.717
**************************************************
*******************
* 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 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 unloaded module list
.....
Loading User Symbols
**************************************************
*****************************
* *
* Bugcheck Analysis *
* *
**************************************************
*****************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 113d, 84b0005, 869667b0}

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

Unable to load image \SystemRoot\system32\drivers\ndis.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
Unable to load image \SystemRoot\system32\DRIVERS\klim6.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for klim6.sys
*** ERROR: Module load completed but symbols could not be loaded for klim6.sys
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
**************************************************
***********************
*** ***
*** ***
*** 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!_POOL_HEADER ***
*** ***
**************************************************
***********************
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
unable to get nt!MiSessionPoolStart
unable to get nt!MiSessionPoolEnd
**************************************************
***********************
*** ***
*** ***
*** 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!_POOL_HEADER ***
*** ***
**************************************************
***********************
**************************************************
***********************
*** ***
*** ***
*** 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!_POOL_TRACKER_BIG_PAGES ***
*** ***
**************************************************
***********************
Cannot get _POOL_TRACKER_BIG_PAGES type size
**************************************************
***********************
*** ***
*** ***
*** 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 ***
*** ***
**************************************************
***********************
Probably caused by : klim6.sys ( klim6+1eb0 )

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

[Crapshit]

Zitat (Erazor84: 21.01.2008, 22:51)

also laut deinem log, ist kaspersky antivirus schuld am bluescreen! klim6.sys gehört zu kaspersky ...

Mich verwundert viel mehr das so oft unable to load xyz da steht.

[Crapshit]

Benutz mal die letzte Version:

http://msdl.microsoft.com/download/symbols...x86_6.8.4.0.msi

Und btw. hast du Kaspersky im Einsatz ? ^^

Dieser Beitrag wurde von alphazero bearbeitet: 21. Januar 2008 - 23:03

[Mellosun]

Zitat (Erazor84: 21.01.2008, 23:51)

also laut deinem log, ist kaspersky antivirus schuld am bluescreen! klim6.sys gehört zu kaspersky ...

Na das nenne ich doch mal nen Ansatz.....erstmal THX dafür!
Ist sowieso nur ne Testversion von Kaspersky, weil die Deutsche NOD32 V.3 noch net da ist!

@alphazero

Was kann daran schuld sein bzw. was steckt dahinter?
Also was sagt einem die Aussage?

OK, werd mal die letzte Version laden und gleich das Ergebnis posten!


THX erstmal....Ihr seid supi!

Dieser Beitrag wurde von Mellosun bearbeitet: 21. Januar 2008 - 23:05

[Crapshit]

Zitat (rolf-hagert: 21.01.2008, 22:59)

Hi Erazor84,

Find ich cool,

wo kann man so was lernen?

Danke

Opa Rolf

Was willst du lernen @ Rolf ?

Zitat (Mellosun: 21.01.2008, 23:02)

Na das nenne ich doch mal nen Ansatz.....erstmal THX dafür!
Ist sowieso nur ne Testversion von Kaspersky, weil die Deutsche NOD32 V.3 noch net da ist!

@alphazero

Was kann daran schuld sein bzw. was steckt dahinter?
Also was sagt einem die Aussage?

OK, werd mal die letzte Version laden und gleich das Ergebnis posten!


THX erstmal....Ihr seid supi!

Also eigentlich ist dies die Vorgehensweise bei dem Dump File.
Analysieren per Tool. Dann nach dieser Zeile gucken:

Probably caused by : klim6.sys
Und kurz googlen hilft meistens. @ Erazor84 war schneller *gg*
Falls es Kaspersky sein sollte sag bitte bescheid, sodass andere User davon profitieren!

Dieser Beitrag wurde von alphazero bearbeitet: 21. Januar 2008 - 23:07

[Mellosun]

So, hier der Log mit der letzten Version von dem Progie:

Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini012108-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 Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Mon Jan 21 19:22:30.341 2008 (GMT+1)
System Uptime: 0 days 11:29:49.717
**************************************************
*******************
* 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 C2, {7, 113d, 84b0005, 869667b0}

*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
*** WARNING: Unable to verify timestamp for klim6.sys
*** ERROR: Module load completed but symbols could not be loaded for klim6.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!PVOID ***
*** ***
**************************************************
***********************
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
**************************************************
***********************
*** ***
*** ***
*** 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!_POOL_HEADER ***
*** ***
**************************************************
***********************
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
**************************************************
***********************
*** ***
*** ***
*** 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!_POOL_HEADER ***
*** ***
**************************************************
***********************
**************************************************
***********************
*** ***
*** ***
*** 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!_POOL_TRACKER_BIG_PAGES ***
*** ***
**************************************************
***********************
Cannot get _POOL_TRACKER_BIG_PAGES type size
**************************************************
***********************
*** ***
*** ***
*** 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 ***
*** ***
**************************************************
***********************
**************************************************
***********************
*** ***
*** ***
*** 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 ***
*** ***
**************************************************
***********************
**************************************************
***********************
*** ***
*** ***
*** 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 : klim6.sys ( klim6+1eb0 )

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

[Crapshit]

Zitat (Mellosun: 21.01.2008, 23:06)

So, hier der Log mit der letzten Version von dem Progie:


Probably caused by : klim6.sys ( klim6+1eb0 )

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

!analyze -v <-- gib dies mal bitte in die console ein

[Mellosun]

Zitat (alphazero: 22.01.2008, 00:09)

!analyze -v <-- gib dies mal bitte in die console ein

Da kommt: Wird nicht gefunden......Prüfen sie bitte usw.

[Crapshit]

Hmm mom ich lad mir grad mal das tool und machs bei mir mal.
Also wie gesagt deinstalliere mal Kaspersky und falls es nicht mehr auftreten sollte in den Zeitintervallen, die du nun kennst, dann könnte es sein, dass es das war.

Ich geb gleich nochmal ein Response, also wart noch einen Moment dann geh ich auch schlafen