Ciągłe BSODy na laptopie Toshiba


(shiftF2) #1

Witam.

Mam problem z moim laptopem 3 letnim Toshiba Satellite.

Mianowicie od jakiegoś czasu mam ciągle BSODy, temperatury są w normie, system przeinstalowany został, a mimo wszystko problem nie ustąpił.

Niżej załączam zrzuty minidump:

Microsoft (R) Windows Debugger Version 6.6.0003.5

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C]

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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030

Kernel base = 0xfffff800`0280c000 PsLoadedModuleList = 0xfffff800`02a50670

Debug session time: Mon Oct 8 20:14:56.783 2012 (GMT+2)

System Uptime: 0 days 0:02:53.671

*********************************************************************

* 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2

*** 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

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck C2, {7, 109b, 4e55c98, fffff88002d1b7d0}


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


Unable to load image \SystemRoot\system32\drivers\ndis.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for ndis.sys

*** ERROR: Module load completed but symbols could not be loaded for ndis.sys

unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

*************************************************************************

******

******

***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!_POOL_HEADER***

******

*************************************************************************

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

*************************************************************************

******

******

***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!_POOL_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!_POOL_TRACKER_BIG_PAGES***

******

*************************************************************************

Cannot get _POOL_TRACKER_BIG_PAGES type size

*************************************************************************

******

******

***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!_POOL_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!_POOL_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!_POOL_TRACKER_BIG_PAGES***

******

*************************************************************************

Cannot get _POOL_TRACKER_BIG_PAGES type size


Followup: MachineOwner

---------

Pamięci są sprawne, testowałem je 19 godzin i wszystko zakończyło się sukcesem.

Wina sterowników chyba też odpada, bo po przeinstalowaniu systemu problem nie ustąpił.


(Fanboj O) #2

Ale przed przeinstalowaniem i po przeinstalowaniu stosowałeś ten sam sterownik nVidii? Spróbuj popracować na laptopie z odinstalowanym sterownikiem grafiki.


(pawcio1212) #3

czyli w trybie awaryjnym działa ??

format jeszcze raz i instalujesz po 1 sterowniku i test parę godzin po czym następny sterownik


(shiftF2) #4

Karta to radeon, 3 lata pracował na sterowniku bez błędu, potem zaczęło się samemu tak dziać.

Przeinstalowałem na sterownik producenta - to samo, przeinstalowałem na oficjalny sterownik radeona - to samo.

teraz zainstalowałem 7 i nie instalowałem sam żadnych sterowników, zostało to co zainstalował Windows 7.

I to samo…

Teraz potrafię odpalić uTorrenta i wyskakuje ten BSOD…


(pawcio1212) #5

hwmonitor pobierz i pokaż napięcia