Sterownik do karty - Laptop się nie wyłącza


(Murawskixx) #1

Witam.

Mam laptopa Acer aspire v3 771G z kartą graficzną Nvidia Geforce 650M 2GB

przy instalacji sterowników zauważyłem, że po zainstalowaniu najnowszych sterowników do karty graficznej gdy klikam zamknij, komputer się nie wyłącza, lecz uruchamia ponownie, odznaczyłem restart po błędzie i po zamknij siedzi z czarnym ekranie. chyba był bsod, (wklejam go niżej) próbowałem instalacji poprzednich sterowników, lecz to samo. proszę o pomoc.

Microsoft (R) Windows Debugger Version 6.2.0013.1

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 Longhorn Kernel Version 9200 MP (8 procs) Free AMD x86-64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 9200.16384.amd64fre.win8_rtm.120725-1247

Kernel base = 0xfffff802`38410000 PsLoadedModuleList = 0xfffff802`386daa60

Debug session time: Tue Jan 01 17:07:21 2013

System Uptime: 0 days 0:01:59.192

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

* 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 unloaded module list

.......

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 50, {fffff88019412000, 1, fffff880018f1baf, 0}


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

******

******

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

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

Probably caused by : Unknown_Image ( ndis+7baf )


Followup: MachineOwner

---------

Probably caused by : Unknown_Image ( ndis+7baf ) - Wujek google tego nie ma, to coś istnieje?


(Neon1992) #2

ndis.sys chyba jest od karty sieciowej, spróbuj odinstalować ten sterownik i zobacz co się będzie działo.