Odczytanie pliku dmp i co jest przyczyna blue screena

[moloszek]

Witam, zdarza mi się, że wywali mi sie system (Windows 7 64 bit)

Nie wiem jaka jest tego przyczyna. Prosiłbym kogoś, kto na tym się zna o pomoc w rozwiązaniu tego problemu.

Komputer jest nowy
Parametry:
i5 4670k 3.4 (podkręcony do 4.5 Ghz)
8 GB ram G.Skill
Graifka Geforce Gtx 750 ti
Dysk SSD Kingston 120 GB
Dysk Toshiba 3 tb
Płyta Główna Asrock z87 Extreme
Zasilacz Thermaltake Smart SE Modular 530W Bronze

Dostępne tylko dla zarejestrowanych użytkowników - Tutaj plik błędu

Pojawiał się jeszcze jeden - powiazany z modemem tp link TL-WN722N - po wyjęciu jej podczas włączonego komputera pojawiał się blue screen. Nie wyjmuję jej po prostu i jest ok

Mam równiez w menadzerze urzadzeń wykrzyknik przy jednym z urządzeń
Nie wiem co to jest

Dostępne tylko dla zarejestrowanych użytkowników

Proszę o pomoc

[cosik_ktosik]

Zgodnie z Microsoftem można problem z Teredo pominąć
Dostępne tylko dla zarejestrowanych użytkowników

Jeśli nie używasz protokołu IPv6 to można go wyłączyć

Kod: Zaznacz cały

1. Click Start > All Programs > Accessories.
2. Right-click "Command Prompt".
3. Click "Run as Administrator".
4. Type this command, then press Enter:

netsh interface teredo set state disabled

Inne wyjście to aktualizuj ten sterownik, a zatem prawym przyciskiem na nim o wybierz Aktualizuj.

Co do problemu bluescreena, to musiałbyś mi odczytać ten plik DMP bo nie dam rady bez programu do niego (nie mam jak go tutaj ściągnąć, za wolne łącze).

Link tutaj http://www.hotfix.pl/bluescreen-bsod-sz ... mp-a17.htm

Część 1a pomiń, szkoda czasu.

[moloszek]

Chyba coś nie działa jak nalezy, zrobiłem według instrukcji.


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


Loading Dump File [C:\Windows\Minidump\050114-8314-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
*** 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 Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e4a000 PsLoadedModuleList = 0xfffff800`0308d6d0
Debug session time: Thu May 1 11:21:58.959 2014 (GMT+2)
System Uptime: 0 days 4:02:44.114
*********************************************************************
* 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
*** 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, fffffa800942d028, bf800000, 124}

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

-- 03 maja 2014, 11:49 --

Zrobiłem zrzut jeszcze innym programem:

Dostępne tylko dla zarejestrowanych użytkowników

Dzisiaj pojawił się tak samo ten błąd (chyba ten sam)

[robiwielki]

a aktualizowałeś sterowniki tp link TL-WN722N ??

Dostępne tylko dla zarejestrowanych użytkowników

a masz uaktualniony system windows ??? i pokaż fotkę jak to wykłada ten problem

-- 03 maja 2014, 15:21 --

a i jeszcze usuń czyli odinstaluj sterowniki tej kary i nie podłączaj jest po restarcie kompa i zobaczysz czy jest problem czy nie ma .

[Andziorka]

Zaktualizuj sterowniki - polecam darmowy program SlimDrivers. Sam wyszykuje, pobiera i instaluje.
Widać też problemy sprzętowe. Polecam sprawdzić kości pamięci Memtestem: http://www.hotfix.pl/instrukcja-obslugi-programu-memtest86+-sprawdzanie-pamieci-ram-a204.htm

[moloszek]

Jutro sprawdzę pamięć ram i ściągne slimdrivers

Aktualizacje windows robione są na bieżąco

Jak mi się wysypie to zrobię fotkę

[robiwielki]

Z tym programem slimdrivers bym raczej uważał, troszkę przetestowałem go i nie jest najlepszy.

[Andziorka]

Z tym programem slimdrivers bym raczej uważał, troszkę przetestowałem go i nie jest najlepszy.

A co w nim złego? Używam długi czas, znajomi używają i jest OK. W razie czego przywróci system, choć wątpię czy będzie to konieczne..

[robiwielki]

Z tym programem slimdrivers bym raczej uważał, troszkę przetestowałem go i nie jest najlepszy.

A co w nim złego? Używam długi czas, znajomi używają i jest OK. W razie czego przywróci system, choć wątpię czy będzie to konieczne..

Jak to bywa różnie z komputerami, ja aktualizowałem "coś" tym programem chociaż podobnym programem było skanowane (ta sama półka) i znalazł wiele rzeczy. I się okazało ze coś źle "pociągnął" i trzeba wrócił do starej wersji która inny program polecił. Ale to może wyjątkowo w moim wypadku takie pomyłka wystąpiła . Bo dziwne programy z tej samej półki a jeden aktualizuje do "najnowszych" sterów a tu nagle się okazuje ze drugim programem jest 7 nowszych sterowników. I w końcu nie wiadomo czy na 100 % są nowsze stery czy nie. Dlatego jak coś nowego wychodzi na światło dzienne to wole osobiście poszukać niż komercyjnymi programami ściągać. Ale to tylko mój osobisty wybór a jak ktoś robi inaczej to od niego zależy może dobrze może źle, ale to jest jego wybór, bo jest tyle programów do wyboru. Ja też 100 % pewności nie mam czy dane stery zadziałają z moim sprzętem na pewno i dlatego mamy zdolność wybór.