Blue Screeny


(Cyro17pl) #1

Witam, ostatnio mam błedy BSOD na nowo wgranym systemie na nowym dysku. Miałem już sporo problemów z Bsodami na starym dysku i byłem przekonany że to od tego wadliwego dysku są błędy, lecz po zakupie nowego dysku problem pozostał. Co prawda nie jest już tak często jak ostatnimi czasy lecz jest to bardzo uciążliwe. Sprawdzałem 2 razy pamięć RAM Memtestem lecz nie wykrył on błędów. 

Specyfikacja komputera:

  • System - Windows 7 Ultimate x64

  • Procesor - AMD Phenom II 4x 3.40GHz

  • Karta graficzna - Nvidia Geforce GTS250

  • Płyta główna - Asrock a780 full hd

  • Pamięć Ram - 2gb x2 DDR2 PCi2-6400 Goodram

  • Dysk - Sata Sageate 500gb

  • Zasilacz - SilentumPC vero V1

 

kod błedu, miałem ich wiecej ale sie usuneły jakims cudem nic poki co jest jeden jak bedzie wiecej to wkleje

Loading Dump File [C:\Windows\Minidump\041115-19656-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 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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02ea1890
Debug session time: Sat Apr 11 18:45:41.270 2015 (UTC + 2:00)
System Uptime: 0 days 0:42:52.708
*********************************************************************
* 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
......Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6fc400591c0, 0, fffff80002ced3ff, 9}

***** 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***
******
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+903ff )

(Dimatheus) #2

Hej,

A nie jest to przypadkiem jakaś modyfikowana wersja systemu?

Pozdrawiam,

Dimatheus


(Cyro17pl) #3

Jest to czysta wersja win7 sp1


(adam9870) #4

Czy sprawdzałeś dysk, zasilacz i temperatury podzespołów? Jeżeli nie - sprawdź.


(Cyro17pl) #5

Sprawdziłem, wszystko w porządku, przed momentem miałem Bsod’a kolejnego oto kod

Loading Dump File [C:\Windows\Minidump\041315-17656-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0xfffff800`02c65000 PsLoadedModuleList = 0xfffff800`02ea9890
Debug session time: Mon Apr 13 12:45:36.456 2015 (UTC + 2:00)
System Uptime: 0 days 4:27:24.720
*********************************************************************
* 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, fffff80002e0f627, fffff88006f38d60, 0}

***** 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***
******
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+1aa627 )

(adam9870) #6

 

  • Czy niebieskie ekrany z błędami pojawiają się zawsze w określonych okolicznościach, np. podczas grania?
  • Kiedy orientacyjnie rozpoczęły pojawiać się problemy? 
  • Czy w ostatnim czasie, tj. mniej więcej w momencie kiedy rozpoczęły się problemy, były instalowane aktualizacje oprogramowania i / lub nowe oprogramowanie?
  • Pobierz oraz zainstaluj HD Tune, uruchom, przejdź na zakładkę Health i wykonaj zrzut ekranu / dołącz go do swojej wiadomości
  • Pobierz oraz zainstaluj HD Tune, uruchom, przejdź na zakładkę Error Scan, kliknij Start, poczekaj aż program zakończy skanowanie i wykonaj zrzut ekranu / dołącz go do swojej wiadomości
  • Czy w trybie awaryjnym wszystko jest w porządku? Aby uruchomić system w trybie awaryjnym, uruchom komputer i naciskaj na klawiaturze F5 i / lub F8 do czasu ujrzenia następującego ekranu, a następnie - korzystając ze strzałek “góra”, "dół’ na klawiaturze, wybierz z listy “Tryb awaryjny” i naciśnij Enter
  • Pobierz i uruchom HWiNFO, kliknij na “Sensors” i przedstaw zrzut ekranu na forum
  • Czy zauważyłeś coś Twoim zdaniem istotnego, co może mieć znaczenie dla problemu, np. laptop  jest gorący z lewej strony w momencie gdy jest wyświetlany bluescreen, albo na klawiaturę coś się wczoraj wylało?