Duży problem z laptopem, pomocy

[majkelkokos]

Witam, dostałem od kolegi laptopa (kupił nowego ten mu niepotrzebny) jak stwierdził nie sprzedaje go bo coś się zawieszał, więc zacząłem od dysku, potem pamięć memtestem86+, ona też była ok, laptop zawiesza się co jakiś czas (jakby się zamrażał) nie reaguje jak coś nacisnę wydaje pojedyncze piknięcie, trzeba go wyłączyć guzikiem. A ostatnio zrobił mi podczas pracy bluescreena, oto co było w pliku minidump:

 

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [i:\Mini090210-01.dmp]

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 <symbol_path> 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) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0

Debug session time: Thu Sep 2 09:10:22.484 2010 (GMT+2)

System Uptime: 0 days 0:00:36.062

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

* 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 <symbol_path> 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 1000008E, {c0000005, 82462b38, 82462aa8, 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 <symbol_path> 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 <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

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

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

 

Followup: MachineOwner

---------

 

 

może mi ktoś wytłumaczyć co jest grane? procesor?

 

z góry dzięki

[ULLISSES]

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Robak albo uszkodzony system.

 

Postaw od nowa system. Przy okazji zresetuj ustawienia bios i przeczyść kompa - może chłodzenie jest zakurzone i nie działa wydajnie. Pomocne okaże się sprężone powietrze.

[majkelkokos]

Witam ponownie, temperatury Ok, wyczyszczony laptop, zmieniona pasta na procku i chipsecie (taki model ze do wiatraka idzie miedziany radiator z procka i chipsetu), sprawdzone ramy sa ok, dysk tez sprawdzony zero bad sectorów itp, format zrobiony 3 razy!! na nowszych i starszych sterownikach problem ten sam, wrzucam dwa powtarzające się blue screeny, z góry dzięki

 

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Documents and Settings\kokos\Moje dokumenty\Pobieranie\Mini090610-02.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

 

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 2600.xpsp.080413-2111

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0

Debug session time: Mon Sep 6 18:08:08.218 2010 (GMT+2)

System Uptime: 0 days 0:00:24.796

Loading Kernel Symbols

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

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

...

Loading User Symbols

Loading unloaded module list

.....

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 1000008E, {c000001d, 8063a182, a75e9c7c, 0}

 

Probably caused by : hardware ( nt!DbgkCreateThread+1d0 )

 

Followup: MachineOwner

---------

 

 

i drugi blue screen

 

 

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Documents and Settings\kokos\Moje dokumenty\Pobieranie\Mini090610-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

 

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 2600.xpsp.080413-2111

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0

Debug session time: Mon Sep 6 14:24:04.781 2010 (GMT+2)

System Uptime: 0 days 0:00:38.359

Loading Kernel Symbols

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

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

.......

Loading User Symbols

Loading unloaded module list

.......

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 1000008E, {c0000005, 8063a8af, bad4bc6c, 0}

 

Probably caused by : ntkrnlpa.exe ( nt!PiGetInterfaceDeviceList+53 )

 

Followup: MachineOwner

---------

[ULLISSES]

No tutaj już jesteśmy bliżej:

Probably caused by : hardware ( nt!DbgkCreateThread+1d0 )

(..)

 

Probably caused by : ntkrnlpa.exe ( nt!PiGetInterfaceDeviceList+53 )

Mam małe doświadczenie w lapkach, ale może to być kwestia ustawień bios (trudno powiedzieć jakich), uszkodzenia płyty głównej (tudzież problemy z zasilaniem) lub ostatecznie systemu (jeśli wcześniej był tam inny system).

 

Gwarancji (jak rozumiem) już nie ma? Można spróbować postawić WinXP SP2 i nie wrzucać SP3 - jest mała szansa, że coś w SP3 nie jest zgodne ze sprzętem.

Jeśli nie, to pozostaje próba innych systemów - nawet jakiś Linux. Jak inne systemy też będą robić problemy, to pewnie sprzęt jest uszkodzony.