BlueScreen Windows 7

Mam pewien problem z Windowsem 7. Gdy normalnie korzystam z komputera to nic się nigdy nie dzieje, problem pojawia się gdy zaczynam coś uploadować do internetu, np.: gdy zaczynam stremować (Upload wideo na żywo z komputera) bądź wysyłam pliki na youtube. Nigdy czegoś takiego nie widziałem, testowałem na laptopie instalując ten sam system, z tej samej płyty i bluescreena nie dostawałem.

To otrzymałem po otworzeniu minidump programem ‘Debugging Tools for Windows’

Byłbym wdzięczny za pomoc.

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 7600 MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50

Debug session time: Sat May 26 09:52:41.696 2012 (GMT+2)

System Uptime: 0 days 0:36:33.756

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

* 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

Loading unloaded module list

......

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck A, {8, 2, 0, fffff80002a1833e}


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


*** WARNING: Unable to verify timestamp for hal.dll

*** ERROR: Module load completed but symbols could not be loaded for hal.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: 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***

******

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

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

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

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

Unable to load image \SystemRoot\System32\drivers\tcpip.sys, Win32 error 2

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

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

Probably caused by : ntoskrnl.exe ( nt+71f00 )


Followup: MachineOwner

---------

afd i tcpip to sterowniki sieciowe, ntoskrnl.exe to plik jądra i zwykle wskazuje na problemy sprzętowe

Analiza plików minidump: wylacza-sie-komputer-t477584.html?hilit=minidump

Rozwiązania z internetu:

Zdaje się, że aktualizacja sterowników pomogła. Upewnię się jeszcze i dam znać gdyby coś się działo lub wszystko się uspokoiło.

Dziękuję wielce!