Problem niewiadomo z czym , komputer sie restartuje


(Koks497) #1

Witam !

Od wczoraj mam dziwny problem z komputerem , mialem go juz kiedys wczesniej po zainstalowaniu programu SmartDoctor.

Teraz jest tak , ze jak wlacze jakis film lub np. jakas gre to moze wyskoczyc taki oto obrazek :

Po czym komputer sie restartuje... .

Prosze o pomoc, pozdrawiam.


(eyeti) #2

Instalowałeś ostatnio jakieś nowe sterowniki gdyż błąd wygląda na to że sterowniki są wadliwe.


(matfeusz) #3

jaki system?

zobacz:

http://support.microsoft.com/default.as ... :stuck_out_tongue_winking_eye:L;311564


(Cosik Ktosik) #4

Zwykły problem ze sterownikiem.

Aby odczytać problem, którego dotyczy BSOD użyj tego: Klik

Daj raport.


(Koks497) #5

Microsoft ® Windows Debugger Version 6.9.0003.113 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [G]

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 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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700

Debug session time: Sun Aug 3 01:18:26.656 2008 (GMT+2)

System Uptime: 0 days 0:10:59.294

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

* 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 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 1000000A, {16, 1c, 0, 80502392}

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

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

*** ERROR: Module load completed but symbols could not be loaded for atkosdmini.dll

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

*** ERROR: Module load completed but symbols could not be loaded for atkdisp.dll

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

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

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

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

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

*** ***

*** ***

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

* using .sympath and .sympath+ *

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

Probably caused by : atkosdmini.dll ( atkosdmini+1370 )

Followup: MachineOwner

Tak to wyglada :frowning:

ps. moze pomoze ponowana instalacja sterownika od grafiki ?


(Kormak) #6

o, mam identyczny problem i taki sam rezultat debuggera mi wyskoczył, ten sam plik dll pokazuje...


(Cosik Ktosik) #7

Macie jakieś sterowniki ASUSa, a dokładnie Enhanced Display Driver Helper Service w ASUS Other Devices.

Przeinstalujcie sterowniki tak, jak tutaj: http://www.searchengines.pl/index.php?s ... 1357&st=45


(Koks497) #8

Dzieki , dziala :wink:

ps. przeinstalowalem tez jeszcze sterowniki od grafiki :slight_smile:

Pozdrawiam.