Witamy na forum PC Format Zapraszamy do REJESTRACJI


Użytkownicy przeglądający ten wątek: 1 gości

Problem z Blu screnem

#1
Problem z Blu screnem
Witam mam taki problem co pare dni wyrzuca mi BS dodam ze ekran nie jest niebieski tylko taki kolorowy i nic tam nie widać po chwili resetuje system i dostaje raport o błędzie prosze o pomoc.


Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\122016-20950-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`03459000 PsLoadedModuleList = 0xfffff800`0369c890
Debug session time: Tue Dec 20 17:03:38.526 2016 (GMT+1)
System Uptime: 0 days 0:00:14.650
*********************************************************************
* 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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800dd21038, 0, 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!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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 <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

Followup: MachineOwner
---------
 System operacyjny: windows_seven Przeglądarka: firefox
#2
RE: Problem z Blu screnem
Co to za komputer? Podaj konfigurację. Czy sprawdzałeś temperatury?
Przy "problemach po aktualizacji do Win10" oraz problemach ze "spadkami FPS w CS:GO"
Nie pomagam.

 System operacyjny: windows_eight Przeglądarka: firefox
#3
RE: Problem z Blu screnem
Procesor:Amd Fx-6100
Płyta główna:Asus M5A78L-M LX3
Karta Graficzna: Radeon R9 290x
RAM: Patriot 16GB 1600MHz DDR 3
Dysk: Sagate Green 1TB
Zasilacz:LC-Power 600W

Tak temperatury sprawdzałem w programie Everest i CPUID HWMonitor i w stanie spoczynku karta miała tylko 40 C a reszta podzespołów poniżej.Podczas obciążenia grając w gre przez 15 min karta miała 68 procesor 55 i reszta podzespołów w granicach 50
 System operacyjny: windows_seven Przeglądarka: firefox
#4
RE: Problem z Blu screnem
Zacząłbym od sprawdzenia zestawu na markowym zasilaczu.
 System operacyjny: windows_ten Przeglądarka: chrome
#5
RE: Problem z Blu screnem
jakąś konkretna markę zasilacza polecasz?
 System operacyjny: windows_seven Przeglądarka: firefox
#6
RE: Problem z Blu screnem
Gdzie kupiłeś ten komputer? Czy jest on na gwarancji?

Ogólnie rzecz biorąc- sprawdzenie na markowym zasilaczu jest w tym przypadku bardzo wskazane, jednakże każdy problem z wyświetlanym obrazem, czyli pojawiające się kolorowe kropki, paski etc. wskazują na kartę graficzną.
Przy "problemach po aktualizacji do Win10" oraz problemach ze "spadkami FPS w CS:GO"
Nie pomagam.

 System operacyjny: windows_eight Przeglądarka: firefox
#7
RE: Problem z Blu screnem
Niestety nie jest juz na gwarancji. Na serwisie sprawdzą czy to karta? bo jak napisałem wcześniej takie coś pojawia sie co pare dni np dzisiaj wszystko działa bez zarzutów
 System operacyjny: windows_seven Przeglądarka: firefox
#8
RE: Problem z Blu screnem
Jak nie masz gdzie sprawdzić samemu to tak serwis pozostaje.
 System operacyjny: windows_ten Przeglądarka: chrome
#9
RE: Problem z Blu screnem
czyli problem z systemem można na pewno wykluczyć bo myślałem czy nie przeinstalować Windowsa?
 System operacyjny: windows_seven Przeglądarka: firefox
#10
RE: Problem z Blu screnem
(21.12.2016, 20:56)tomek412 napisał(a): Niestety nie jest juz na gwarancji.
Pytałem też gdzie go kupiłeś. Wiesz dlaczego? Dziadowski zasilacz to jedno, ale ktoś zamontował Ci dysk z serii green, co oznacza że zamiast standardowych 7200rpm ma 5900. Jeżeli nie masz dysku SSD, to nic nie usprawiedliwia takiej fanaberii i IMO zostałeś zrobiony w wała. Nie wiem czy masz tego świadomość czy nie.

(21.12.2016, 21:13)tomek412 napisał(a): czyli problem z systemem można na pewno wykluczyć bo myślałem czy nie przeinstalować Windowsa?
Jeżeli objawy są takie jak mówisz, czyli kolorowe kropki na ekranie, to system nie ma na to żadnego wpływu. Pozostaje sprzęt.
Przy "problemach po aktualizacji do Win10" oraz problemach ze "spadkami FPS w CS:GO"
Nie pomagam.

 System operacyjny: windows_eight Przeglądarka: firefox
Programy: Polecane / Nowe / Inne




Podobne wątki (Problem z Blu screnem)
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
  Laptop Dell Blu scren vibson 1 705 17.06.2014, 17:17
Ostatni post: rooneyasd
Ściana pokazuje mi się error blu screen Piotrza2001 19 1439 13.02.2013, 11:43
Ostatni post: Piotrza2001

Skocz do:


Wybrane wątki (Problem z Blu screnem)
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
  Dziwne zielone paski niewiem98 1 648 27.07.2017 03:45
Ostatni post: lukashekluk
  Kontroler Xbox 360 rozłącza się Ortega 2 607 26.07.2017 21:28
Ostatni post: Ortega
  Po czyszczeniu wiatraki się nie kreca miodu12 0 621 25.07.2017 16:21
Ostatni post: miodu12
  Mysz bezprz. Lenovo N50 nie działa revar123 0 601 25.07.2017 15:28
Ostatni post: revar123
  Problemy z kartą Wi-Fi w Laptopie rocketman15 0 517 25.07.2017 11:12
Ostatni post: rocketman15
  Resetujacy sie komputer olejoo 2 603 25.07.2017 10:45
Ostatni post: MonteCristo
  Brak sygnału video na monitorze buum 9 1134 24.07.2017 21:48
Ostatni post: MonteCristo
  Dysk hdd i ssd Stanley99 4 664 24.07.2017 17:50
Ostatni post: Stanley99
  Komputer nie działa poprawnie, możliwe uszkodzenie dysku JokerTPoland 6 940 23.07.2017 20:46
Ostatni post: ~Anonim
  Cichszy dźwięk na tylnym wyjściu karty dźwiękowej (zintegrowana) Misiek 10 1687 21.07.2017 15:58
Ostatni post: Misiek
  Konsola zacina pod tv TRV13E 0 864 21.07.2017 11:41
Ostatni post: TRV13E
  [Stacjonarny]Dziwne dźwięki, szalejący obraz elpistolero 0 546 20.07.2017 18:43
Ostatni post: elpistolero
  Ścinki, odczuwalne spadki fps. marcin21 0 928 20.07.2017 17:26
Ostatni post: marcin21
  Komputer przywiesza się na chwilę i zawiesza przy ponownym uruchamianiu szewancki 4 886 20.07.2017 02:44
Ostatni post: broda99
  Spadki fps w cs:go i skaczący var kubbciu 0 1095 19.07.2017 19:56
Ostatni post: kubbciu