Blue screen


(Tomdewil) #1

Po zainstalowaniu na laptopie Toshiba A200 Windows-a XP co pewien czas pojawia mi się niebieski ekran "IRQL_NOT_LESS_OR_EQUAL". Zrobiłem test debugger-em i za bardzo nie wiem na co zwrócić uwagę tzn gdzie szukać przyczyny.

Zrzut z debugger-a:

Microsoft ® Windows Debugger Version 6.11.0001.402 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [E]

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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \WINDOWS\system32\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

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0

Debug session time: Tue Feb 24 04:04:40.312 2009 (GMT+1)

System Uptime: 0 days 2:37:48.084

*********************************************************************

* 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \WINDOWS\system32\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

................

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {e8, 2, 1, 80701a16}

*** WARNING: Unable to verify timestamp for mssmbios.sys

*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys

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

*** WARNING: Unable to verify timestamp for hal.dll

*** ERROR: Module load completed but symbols could not be loaded for hal.dll

*************************************************************************

*** ***

*** ***

*** 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 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Probably caused by : ntoskrnl.exe ( nt+9aac )

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: 000000e8, 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: 80701a16, 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 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 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: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48a4044a

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

000000e8

CURRENT_IRQL: 2

FAULTING_IP:

hal+2a16

80701a16 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 00000000 to 804e0aac

STACK_TEXT:

80557028 00000000 000000e8 00000002 00000001 nt+0x9aac

STACK_COMMAND: kb

FOLLOWUP_IP:

nt+9aac

804e0aac ?? ???

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+9aac

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner



(Cosik Ktosik) #2

Błędy systemu Windows (kody BSOD)

Niestety ntoskrnl.exe mało mówi, a więc zajrzyj do dziennika podglądu zdarzeń: Podgląd zdarzeń - zapisywanie dzienników (XP, Vista).


(Tomdewil) #3

poszukałem i znalazłem::

1.Protokół TCP/IP osiągnął limit zabezpieczeń ustalony dla liczby równoczesnych prób połączeń TCP.

2.Nie można znaleźć opisu dla identyfikatora zdarzenia ( 54 ) w źródle ( AvgTdiX ). Być może komputer lokalny nie ma wymaganych informacji rejestru lub plików DLL potrzebnych do wyświetlania komunikatów z komputera zdalnego. Możesz użyć flagi /AUXSOURCE= do pobrania tego opisu; więcej informacji można znaleźć w Pomocy i obsłudze technicznej. Następujące informacje są częścią zdarzenia: .

po paru błędach następuję "blue screen" z komunikatem IRQL_NOT_LESS_OR_EQUAL


(suchmen) #4

1.Problem z pamięcią ram-memtest zrób

2.W przypadku stabilnego działania pamięci ram sprawdź sterowniki do karty sieciowej/lub karta uszkodzona.

-- Dodane 24 lut 2009, o 21:58 --

U mnie osobiście winą były sterowniki do karty sieciowej więc zainstalowałem starsze ale od producenta a nie ze strony realteka i pomogło.Jednak ja bym zrobił test ramu bo te errory i w końcu BS to coś jakby z ramami było.


(Cosik Ktosik) #5

Zapisz i daj dziennik do analizy.


(suchmen) #6

IRQL_NOT_LESS_OR_EQUAL - Błąd ten pojawia się najczęściej poprzez działanie złego sterownika lub niezgodności sprzętu lub oprogramowania . Oznacza on, że w trybie jądra proces próbował uzyskać dostęp do innego procesu, podczas gdy sam miał niższe uprawnienia IRQL od tego drugiego. To jest zabronione.

Rozwiązanie:

-Użyj ostatniej znanej dobrej konfiguracji lub przywracania systemu.

-Uaktualnij sterownik, którego dotyczy problem .

Mówiłem-jednak sterownik karty sieciowej najprawdopodobniej-zobacz w trybie awaryjnym czy problem występuje


#7

tomdewil , proszę zapoznaj się z tą stroną oraz tym tematem, a następnie popraw tytuł tematu, używając przycisku ac7a4cd89050aa6e.gif