Log z Microsoft Debugging Tools


(Dawidd64) #1

Witam!

Dziś pojawił mi się BluScreen podczas grania w CS 1.6

BCCode: a

BCP1: 000000000000002F

BCP2: 0000000000000002

BCP3: 0000000000000001

BCP4: FFFFF80001AADDF2

Użyłem do tego programu Microsoft Debugging Tools, z którego niżej podaje log

Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C]

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 \SystemRoot\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 Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0xfffff800`01a4b000 PsLoadedModuleList = 0xfffff800`01c10db0

Debug session time: Sun Sep 14 11:38:29.759 2008 (GMT+2)

System Uptime: 0 days 0:32:09.449

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

* 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 \SystemRoot\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, {2f, 2, 1, fffff80001aaddf2}


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

******

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

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

******

******

***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 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+62df2 )


Followup: MachineOwner

---------

Błąd powoduje plik ntoskrnl.exe ( nt+62df2 ). Na różnych forach mówią, że plik ten powoduje błąd ze sprzętem, czy faktycznie tak jest ? Aha, 2 dni wcześniej pojawił mi się inny BluScreen.

Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C]

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 \SystemRoot\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 Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0xfffff800`01a07000 PsLoadedModuleList = 0xfffff800`01bccdb0

Debug session time: Fri Sep 12 19:57:46.386 2008 (GMT+2)

System Uptime: 0 days 0:00:57.933

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

* 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 \SystemRoot\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

.....

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

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

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 124, {0, fffffa8004009030, b2000040, 800}


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


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

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

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

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

******

******

***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 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 : hardware


Followup: MachineOwner

---------

Domyślam się, że problem powoduje jakichś program, ale jak to sprawdzić ?


(Seba86mu) #2

Sprawdź temperatury podzespołów programem Everest Ultimate Edition (ikona "Komputer" -> ikona "Czujnik").

Podaj konfigurację sprzętową komputera + zasilacz (producent, moc).


(Dawidd64) #3

Temperatury

Płyta główna 34 °C (93 °F)

Procesor 34 °C (93 °F)

Procesor nr 1 / rdzeń nr 1 25 °C (77 °F)

Procesor nr 1 / rdzeń nr 2 28 °C (82 °F)

Procesor graficzny 42 °C (108 °F)

Seagate ST3160812AS [TRIAL VERSION]

CPU: C2D E6420 @ 2.13

MB: Foxconn P35A-S

GPU: GF 7600 GS 128/128 Zalman

DDR2: 3 x 1 GB Kingmax ( 2 kości 1066 MHz, 1 800 MHz )

PSU: Topower P5 U12 400W


(system) #4

Dziwny zasilacz...


(Seba86mu) #5

Wręcz przeciwnie -> bardzo dobry zasilacz.

dawidd64 , Podłączyłeś wszystkie przewody zasilające do gniazd na płycie głównej ?


(Dawidd64) #6

Tak, wszystkie przewody są podłączone.


(Dawidd64) #7

I co żadnych pomysłów ? :slight_smile:

Naprawdę jest to dla mnie ważne.


(Olixxx94) #8

dawidd64 , co do pliku ntoskrnl.exe, to spróbuj go podmienić w konsoli odzyskiwania wpisując:

Najpierw MAP ARC żeby dowiedzieć się, pod jaką literą jest napęd

Potem :arrow:

expand X:/i386/ntoskrnl.ex_ C:\WINDOWS\SYSTEM32\ntoskrnl.exe

Pamietaj o spacjach po expand i ntoskrnl.ex_


(Dawidd64) #9

Wczoraj pożyczyłem ramy od kumpla , może to właśnie z nimi jest problem. Jeżeli wystąpi jeszcze raz ten BlueScreen to zastosuje tą komendę.


(Dawidd64) #10

Jak wpisuje te polecenie to mi wyskakuje taki komunikat:

Nie można otworzyć pliku wejściowego e:/i386/ntoskrnl.exe


(Dawidd64) #11

Kurde nikt nic nie wie ?

Aha windows to vista oczywiście


(system) #12

Ktoś, coś na pewno odpowie, ale może to trochę potrwać, nie jesteś sam na tym forum :!:


(Cosik Ktosik) #13

0x0000000A IRQL_NOT_LESS_OR_EQUAL, to błąd sterownika. Uaktualnij wszystkie, które Dasz radę. Zajmij się głównie sterownikami od karty graficznej. Na Viście był przez jakiś czas problem ze sterownikami Nvidii.

Pliku ntoskrnl.exe nie ruszaj !!


(Dawidd64) #14

Czyli problem, np. z ramami mogę wykluczyć ? Pamiętam, że kilka miesięcy temu jak instalowałem Vistę to ten sam błąd był.

Problem nie występował tylko na Windows Server, ale może Vista jest bardziej uczulona na tego typu rzeczy :stuck_out_tongue:

Kurcze, wszystkie sterowniki mam zainstalowane na najnowsze, ale spróbuję je przeinstalować.


(Cosik Ktosik) #15

Niekoniecznie, coś spowodowało drugi błąd, który był błędem sprzętowym. Ale pamięć dość łatwo przetestować, wystarczy darmowy programik memtest86+.

Co do sterowników, to tak, jak pisałem, zajmij się głównie sterownikami Nvidii.


(Dawidd64) #16

Zastanawia mnie właśnie to czy tego zwisu nie powoduje jedna kość ramu 800 MHz ( dwie pozostałe są1066 MHz ) i jeżeli bym sprawdzał to każdą kość oddzielnie, czy może tą 800 MHz, a może wszystkie razem, chociaż jak będzie błąd to mi nie pokaże, która kość ma błędy.


(Cosik Ktosik) #17

Sprawdź najpierw oddzielnie każdą z pamięci. Jak nie będzie błędów, to włóż wszystkie i sprawdź je razem. Jeżeli błąd powoduje jedna kość to się o tym dowiesz testując właśnie ją. Jeżeli moduły nie mogą działać razem, to błąd wyskoczy podczas testowania ich razem.