Niebieski ekran (BŁĄD) :(


(Marcinptaszek) #1

Witam

od kilku dni mam problem z moim laptopem, jest to hp 6715s, z xp professionalem, problem polega na tym że wyłącza się co 15-20 min i wyskakuje niebieski ekran, a tam kod błędu BCCode : 1000007f BCP1 : 0000000D BCP2 : 00000000 BCP3 : 00000000 BCP4 : 00000000

OSVer : 5_1_2600 SP : 3_0 Product : 256_1

Czego to jest przyczyna proszę o pomoc

Pozdrawiam


(Cosik Ktosik) #2

Aby dowiedzieć się więcej, czego dotyczył bluescreen, odczytaj plik DMP. Zrób to wg tej instrukcji :arrow: Czytanie DMP

Sprawdź rozwiązanie (także w linkach): kody błędów.(szukaj 0x0000007f)

Jeżeli nie rozwiążesz problemu, to daj raport na forum wg tych zasad :arrow: viewtopic.php?f=16&t=253052

Sprawdź teraz, czy są jakieś pliki DMP.


(Sebos99) #3

Zainstaluj ten program i podaj temperatury poszczególnych podzespołów komputera w zakładce czujnik.

http://dobreprogramy.pl/index.php?dz=2& ... ition+2.20

Przeczyść również kratki wentylacyjne z boku i pod spodem lapka. Możliwe, że się przegrzewa.


(Marcinptaszek) #4

Procesor ma temp 49 C a dysk 43


(Marcinptaszek) #5

Microsoft ® Windows Debugger Version 6.10.0003.233 X86

Copyright © 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 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 3) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Sun Nov 30 12:19:41.843 2008 (GMT+1)

System Uptime: 0 days 0:20:37.458

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

* 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

.............

Unable to load image ati2mtag.sys, Win32 error 0n2

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

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {d, 0, 0, 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. ***

*** ***

*** 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 : ati2mtag.sys ( ati2mtag+105a30 )

Followup: MachineOwner


Wygenerowano w 0.031s, przy pomocy GeSHi 1.0.8


(Cosik Ktosik) #6

Uaktualnij sterowniki od karty graficznej.


(Marcinptaszek) #7

cosik_ktosik ,

Oki dzięki