Problem z BSDOD Restarty co 10min

Witam

Mam problem z komputerem mianowicie przy korzystaniu z komputera co 10 min mam reset lub myszka/klawiatura mi nie działa /czarny ekran

robiłem co się dało format na xp viste nawet 98 i za każdym razem to samo a po resecie wyświetla mi błąd zmieniłem wszystkie sterowniki na nowe i nic

OTO ZAPIS Z DZIENNIKA SYSTEMU znaczy z debuggera :slight_smile:

Microsoft ® Windows Debugger Version 6.11.0001.404 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) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0

Debug session time: Tue Nov 29 12:08:08.125 2011 (GMT+1)

System Uptime: 0 days 0:35:38.719

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

* 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 win32k.sys, Win32 error 0n2

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

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf80257d, b7444c20, 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 : hardware ( win32k+257d )

Followup: MachineOwner


CO MAM ZROBIĆ JUŻ 5 LAT Z TYM WALCZĘ I NIC NA INNYCH FORACH COŚ PISZE ALE NIC Z TEGO NIE WYNIKA BŁAGAM O POMOC

MOJA KONFIGURACJA PECETA TO

Nazwa systemu operacyjnego Microsoft Windows XP Professional

Wersja 5.1.2600 Dodatek Service Pack 3 Kompilacja 2600

Producent systemu VIA

Model systemu K7VT2

Typ systemu Komputer z procesorem x86

Procesor x86 Family 6 Model 8 Stepping 1 AuthenticAMD ~1665 Mhz

Wersja/data systemu BIOS American Megatrends Inc. P1.30, 2003-03-07

Wersja SMBIOS 2.3

Ustawienia regionalne Polska

Warstwa abstrakcji sprzętu Wersja = “5.1.2600.5512 (xpsp.080413-2111)”

Całkowita pamięć fizyczna 512,00 MB

Dostępna pamięć fizyczna 119,39 MB

Całkowity rozmiar pamięci wirtualnej 2,00 GB

Dostępna pamięć wirtualna 1,95 GB

Obszar pliku strony 1,22 GB

DYSK 320GB

Pamięci masz jakie?? DDR czy SDRAM?? Ale na twoim miejscu to bym już wymienił tego staruszka. Tym bardziej że juz 5 lat sie tak męczysz. Ja bym dawno już tą historie wywalił.

Bardzo prawdopodobne że przyczyną jest płyta główna w połączeniu z ramem. A jeszcze jak ma się SDRAM.

http://support.microsoft.com/kb/903251/pl

http://forum.centrumxp.pl/Default.aspx?g=posts&t=103452

do poczytania