bluescreen problem

[davidini]

Witam
Od kilku dni mam problem z moim lenovo t420. Samoczynnie się restartuje.
Specyfikacja:
intel i5 2450m
2x8gb corsair 1333mhz
intel 330 ssd 120gb
nvidia 4200 nvs + intel 3000hd

wklejony raport z minidump:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\051114-17316-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
Machine Name:
Kernel base = 0xfffff800`03011000 PsLoadedModuleList = 0xfffff800`032546d0
Debug session time: Sun May 11 13:12:48.778 2014 (GMT+2)
System Uptime: 0 days 0:22:18.855
*********************************************************************
* 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
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff78008000008, 2, 0, fffff800030893a3}

***** 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 <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 : ntoskrnl.exe ( nt+783a3 )

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

[djkamil09061991]

Nic ciekawego z raportu nie wynika, podaj na początek smart:
sprzet-komputerowy/odczytanie-smart-programem-hd-tune-t512.html

[davidini]

Chwilowo nie mogę go podać- już miałem hd tune pro i wygasło. Wrócę z roboty to podeślę. Także dzięki za zainteresowanie i do później:)

-- 11 maja 2014, 20:21 --

HD Tune Pro: INTEL SSDSC2CT120A3 Health

ID Current Worst ThresholdData Status
(05) Reallocated Sector Count 100 100 0 0 ok
(09) Power On Hours Count 0 0 0 901139 ok
(0C) Power Cycle Count 99 99 0 1650 ok
(B5) Program Fail Count 0 0 0 0 ok
(B6) Erase Fail Count 0 0 0 0 ok
(C0) Unsafe Shutdown Count 100 100 0 60 ok
(E1) Host Writes 100 100 0 134769 ok
(E8) Available Reserved Space 100 100 10 0 ok
(E9) Media Wearout Inidcator 100 100 0 0 ok
(F1) LifeTime Writes from Host 100 100 0 134769 ok
(F2) LifeTime Reads from Host 100 100 0 236115 ok
(F9) (unknown attribute) 100 100 0 5819 ok

Health Status : ok

To ze smart. Memtest pamięci też wyszedł bez błędów.

[djkamil09061991]

Podaj jeszcze screena z programu HWMonitor tak aby było wszystko widac oraz inne raporty z bluescreenów jesli posiadasz.

[robiwielki]

A aktualizowało się ostatnio jakieś podzespoły ??

-- 11 maja 2014, 19:39 --

i tak na uwadze, masz 16 GB RAM ??

[davidini]

Jak wkleić screen na tym forum?
Tak mam 16GB ram - aktualizowane z 8GB jakieś 2 tygodnie temu. Najpierw pomyślałem o pamięciach ale memtest wykazał pass ok, no error.

[djkamil09061991]

wstaw np. tutaj:
Dostępne tylko dla zarejestrowanych użytkowników

i podaj link.

[davidini]

Myślałem że można gdzieś tu wkleić. Sprawdźcie czy uda Wam się odtworzyć z screen shootera Dostępne tylko dla zarejestrowanych użytkowników

[robiwielki]

jest

-- 11 maja 2014, 20:27 --

według mnie zdjęcie z programu HWMonitor jest w porządku. Ale to tylko moja opinia, poczekamy jak inni się wypowiedzą.

[davidini]

więc jaka diagnoza? skąd się wziął bluescreen pierwszy raz od października 2010?;)

[djkamil09061991]

Skoro dysk oki, pamięc też, temperatury również to zostaje aktualizacja tudzież zmiana sterowników na inną wersje niż posiadasz od grafy, sieci, dzwięku.

[davidini]

i teraz wyskoczył znowu bluescreen, takie dane:
0x0000001E (0xFFFFFFFFC00001D, 0xFFFFFA800FAB5586, 0x0000000000000000, 0x0000000000800000)

[robiwielki]

a masz system 7 sp1 uaktualnij je jak masz nie aktualne. A jak dalej będzie to samo to o pamieć chodzi

[davidini]

system aktualny, myślisz że obie kości? bo jeśli tak to mam gwarancję rozruchową i mogę zwrócić. tylko ze memtest kompletnie nic nie wykazał:/

[robiwielki]

a możesz wyciągnąć tą kość która ostatnia włożyłeś ?? i niech pochodzi na jednej i zobaczymy czy błąd się powtórzy czy nie