witam, zaraz po zainstalowaniu systemu, zaczęło mi wywalać bluescreen’y
oto ostatni z nich
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [K]
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 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
Machine Name:
Kernel base = 0xfffff803`7b083000 PsLoadedModuleList = 0xfffff803`7b34da80
Debug session time: Thu Jan 24 14:03:45.438 2013 (UTC + 1:00)
System Uptime: 0 days 0:00:25.111
*********************************************************************
* 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 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 3B, {c0000005, fffff880055b382e, fffff8800645b760, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+91982e )
Followup: MachineOwner
---------
ktoś coś z niego rozumie bo mi nic to nie mówi 
chodzi o sterowniki do karty graficznej ?