Minidump datei Analysieren. Hilfe

[waldemar011]

Hallo zusammen, ich hab folgendes Problem.
Mein Rechner hat sich immer bei spielen von COD4 aufgehängt. Bluesrceen kamm mit der Meldung
IRQL_NOT_LESS_OR_EQUAL

STOP: 0X0000000A, (0X00000000, 0X000000FF, 0X00000000, 0X806ESEA0

So diesen Fehler hab ich dann versucht so zu beheben.

Start > Ausführen > dxdiag > Alle infos Speicher> unter Temp als (.xml) datei.
Nachdem ich das alles gemacht hab lief es bei Spielen problemlos ohne Fehler bzw BS.

Jetzt fängt es wieder an das der PC sich selber Neustartet. Ohne Fehlermeldung
Ich hab jetzt die Minidump datei Ausgelesen. Befindet sich Windows>Minidump Ordner. Das problem ist, ich verstehe da nur Japanisch
Kann mir da einer weiter helfen.

DAS IST DIE AUSGELESENE MINIDUMP DATEI

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


Loading Dump File [C:\WINDOWS\Minidump\Mini103008-02.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 ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Oct 30 15:10:12.656 2008 (GMT+1)
System Uptime: 0 days 3:57:59.359
*********************************************************************
* 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 ntoskrnl.exe, Win32 error 0n2
*** 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
..................
*** ERROR: Module load completed but symbols could not be loaded for halmacpi.dll
*** WARNING: Unable to verify timestamp for AmdK8.sys
*** ERROR: Module load completed but symbols could not be loaded for AmdK8.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {0, ff, 0, 806e5ea0}

***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 ( AmdK8+3332 )

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

0: 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: 00000000, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, 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: 806e5ea0, 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000000

CURRENT_IRQL: ff

FAULTING_IP:
hal+ea0
806e5ea0 8b1d00000000 mov ebx,dword ptr ds:[0]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

MISALIGNED_IP:
hal+ea0
806e5ea0 8b1d00000000 mov ebx,dword ptr ds:[0]

UNALIGNED_STACK_POINTER: 805513c1

LAST_CONTROL_TRANSFER: from ba19b332 to 806e5ea0

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805513c0 ba19b332 badb0d00 0000000b b497c3c2 hal+0xea0
80551400 eb5b2fe6 ffdff9c0 ffffffff 3f28488f AmdK8+0x3332
80551404 ffdff9c0 ffffffff 3f28488f 8a662818 0xeb5b2fe6
80551408 ffffffff 3f28488f 8a662818 ffdffc50 0xffdff9c0
8055140c 3f28488f 8a662818 ffdffc50 ffdffc70 0xffffffff
80551410 8a662818 ffdffc50 ffdffc70 80551450 0x3f28488f
80551414 ffdffc50 ffdffc70 80551450 80551428 0x8a662818
80551418 ffdffc70 80551450 80551428 ba19b332 0xffdffc50
8055141c 80551450 80551428 ba19b332 00000008 0xffdffc70
80551420 80551428 ba19b332 00000008 00000246 nt+0x7a450
80551450 80545d4c 00000000 0000000e 00000000 nt+0x7a428
80551454 00000000 0000000e 00000000 00000000 nt+0x6ed4c


STACK_COMMAND: kb

FOLLOWUP_IP:
AmdK8+3332
ba19b332 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: AmdK8+3332

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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

0: kd> lmvm hardware
start end module name
0: kd> lmvm hardware
start end module name
0: kd> lmvm hardware
start end module name
0: 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: 00000000, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, 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: 806e5ea0, 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

READ_ADDRESS: 00000000

CURRENT_IRQL: ff

FAULTING_IP:
hal+ea0
806e5ea0 8b1d00000000 mov ebx,dword ptr ds:[0]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

MISALIGNED_IP:
hal+ea0
806e5ea0 8b1d00000000 mov ebx,dword ptr ds:[0]

UNALIGNED_STACK_POINTER: 805513c1

LAST_CONTROL_TRANSFER: from ba19b332 to 806e5ea0

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805513c0 ba19b332 badb0d00 0000000b b497c3c2 hal+0xea0
80551400 eb5b2fe6 ffdff9c0 ffffffff 3f28488f AmdK8+0x3332
80551404 ffdff9c0 ffffffff 3f28488f 8a662818 0xeb5b2fe6
80551408 ffffffff 3f28488f 8a662818 ffdffc50 0xffdff9c0
8055140c 3f28488f 8a662818 ffdffc50 ffdffc70 0xffffffff
80551410 8a662818 ffdffc50 ffdffc70 80551450 0x3f28488f
80551414 ffdffc50 ffdffc70 80551450 80551428 0x8a662818
80551418 ffdffc70 80551450 80551428 ba19b332 0xffdffc50
8055141c 80551450 80551428 ba19b332 00000008 0xffdffc70
80551420 80551428 ba19b332 00000008 00000246 nt+0x7a450
80551450 80545d4c 00000000 0000000e 00000000 nt+0x7a428
80551454 00000000 0000000e 00000000 00000000 nt+0x6ed4c


STACK_COMMAND: kb

FOLLOWUP_IP:
AmdK8+3332
ba19b332 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: AmdK8+3332

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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

 

[Nookiewww]

Ehh also den Dump kann man mit den debugging tools von microsoft lesen. Aber das is etwas aufwendig.
Denke nich das das wirklich notwendig ist.
Googel doch mal nach "IRQL_NOT_LESS_OR_EQUAL"
Da findest du eine Menge!
Ich würde auf einen IRQ Konflikt tippen...

 

[waldemar011]

Also die Minidump hab ich mit dem Tool auch aufgemacht.
Die Dump datei hab ich ausgelesen und hier eingefügt

 

[waldemar011]

Googel doch mal nach "IRQL_NOT_LESS_OR_EQUAL"

Ich hab schon danach gegoogelt und nix kamm raus

 

[BlackMan]

Die fehlenden Symbole sind im Visual Studio C/C++ / WIN SDK enthalten. Aber selbst wenn dein zweiter Name C, ASSEMBLER und WINAPI ist wirst du damit wenig anfangen können.

Der IRQL_NOT_LESS_OR_EQUAL wird fast immer bei Hardware- oder Treiberfehlern ausgelöst.

Hardware Fehler durch Benutzer verursacht:
übertaktet oder over-/undervolted (CPU / GPU)
Speichertimings und VDIMM
Sonstige:
Speicher mit memtest86+ prüfen
Prozessor im BIOS bekannt.
Netzteil hat ausreichende Leistung und verträgt die Lastwechsel (z.B. einige ältere BQ steigen bei Lastwechsel aus).
Kühlung ausreichend.
Festplatte 100% in Ordnung.

Treiber: Grafikkarte, Soundkarte, Chipsatz und andere 'exotitische' non Windows nativ Treiber.
Alle deinstallieren und nach und nach einspielen bis der Fehler wieder auftritt, bingo.
-------------------------
Tritt der fehler erst nach einer gewissen Laufzeit unter Last auf:
Siehe durch Benutzer verursachte Hardwarefehler, Kühlung, Netzteil in seltenen Fällen Festplatte.

 

[Kratschbert]

http://support.microsoft.com/kb/314063/de

 

[waldemar011]

Also der Support bei Microsoft hat mir nichts gebracht. Schon gemacht.

Mein System lief bis vor ca. einem Monat einwandfrei und das auch eine sehr lange zeit. Ich habe nie was übertaktet. Dann vor ca. nem monat hat sich mein netzteil verabschiedet obwohl es Ziemlich neu war. Bequiet Dark power Pro 550 Watt.

Ich habe erst gedacht das wäre Mainboard und dann der CPU. War es aber net. Netzteil defekt. Hab aber mir ein neues Mainboard gekauft un es instaliert, bis ich gemerkt habe das es das netzteil war.

Neues Netzteil bekommen und altes Mainboard eingebaut. Und dann paar wochen später find das mit den Fehler an.