BSOD - BugCheck 3B - ntoskrnl.exe

[binczu]

Witam, od kilku tygodni wyskakuje mi ekran smierci, najczesciej podczas korzystania z mozilli, ogladania filmikow. Co dalej?

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\040813-14851-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\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`02a5a000 PsLoadedModuleList = 0xfffff800`02c9e670
Debug session time: Mon Apr 8 11:35:12.966 2013 (UTC + 2:00)
System Uptime: 0 days 1:15:26.574
*********************************************************************
* 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\ntoskrnl.exe, Win32 error 0n2
*** 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 3B, {c0000005, fffff80002adec36, fffff8800722de20, 0}

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 : ntoskrnl.exe ( nt+84c36 )

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

[seba86mu]

Zainstaluj program => Dostępne tylko dla zarejestrowanych użytkowników, którym dokonasz odczytu plików DMP.
Po otwarciu program automatycznie zlokalizuje pliki DMP. Zaznacz kolejno pliki i wybierz:
File => Save Selected Items
Wklej tutaj raporty.
Możesz również wkleić screen zmaksymalizowanego ekranu głównego programu.

Podaj odczyty temperatur z programu => Dostępne tylko dla zarejestrowanych użytkowników (screen okna programu)

Pokaż odczyt SMART z programu => Dostępne tylko dla zarejestrowanych użytkowników => zakładka Health

Wykonaj godzinny test pamięci RAM programem Memtest => http://www.hotfix.pl/instrukcja-obslugi ... m-a204.htm

Jaki posiadasz sprzęt ? (procesor, karta graficzna, zasilacz)

[binczu]

Blue Screen view
Dostępne tylko dla zarejestrowanych użytkowników
HW Monitor
Dostępne tylko dla zarejestrowanych użytkowników
HD Tune nie wyswietla mi nic w tej zakladce
Ram test wykonam jutro bo zaraz do pracy ;[
Athlon x2 6000+/ 7950 GIGABYTE wf3/ StealthXSTREAM 600W

[seba86mu]

HD Tune nie wyswietla mi nic w tej zakladce

CrystalDiskInfo => Dostępne tylko dla zarejestrowanych użytkowników

Napisz jeszcze jaką posiadasz płytę główną.
Dziwne, bo posiadasz kartę graficzną od AMD, a większość błędów wskazuje na sterowniki NVIDII.
Czy przypadkiem nie miałeś wcześniej karty graficznej od NVIDII ?
Może masz płytę główną bazującą na chipsecie nForce ?

Temperatury bez zastrzeżeń.

[binczu]

Tak, kiedys mialem 9800gtx i wymienilem na hd7950, mysle ze poprawnie odinstalowalem wszystkie stery od nvidi i nie jestem pewny czy w miedzy czasie nie robilem formata, a jesli chodzi o plyte to Gigabyte M61PM-S2(Stara strasznie) i chyba chipset nForce(nvidia geforce 6100/nForce 430)

[lewy]

0x3B to często problem właśnie z dyskiem. Podaj co pokazuje CrystalDiskInfo. Jak i tam nic nie ma to zobacz SMART w programie AIDA64.

[binczu]

CrystalDiskInfo
Dostępne tylko dla zarejestrowanych użytkowników

[seba86mu]

Dysk wygląda na zdrowy.

Zainstaluj ten sterownik do chipsetu => Dostępne tylko dla zarejestrowanych użytkowników

Wykonaj test pamięci.