x-kom hosting

Ogromny problem z Windows XP

Keepsake
utworzono
utworzono

Ostatnio z racji padającej Visty zrobiłem formata i zainstalowałem Windowsa XP SP2. Myślałem ,że w ten sposób pozbęde się BSOD'ów jednak myliłem się. Problem w tym ,że "niebieski ekran śmierci" atakuje z nienacka kiedy wciskam np. ctrl + c lub włączam jakiś program który powoduje wzrost zużycia pamięci RAM. Na początek moja konfiguracja

Intel Core 2 Duo E6750 2.66GHz

Nvidia GeForce 8600GTS 512MB

Geil Dual Ultra 2x1024MB DDR2 800MHz

Seagate 250GB

A oto co przeczytałem na stronie Micro$oftu :

"(....)Microsoft is unable to determine the exact cause of this error. However, this problem was most likely caused by an error in your computer’s random access memory (RAM)(....)"

"During the crash analysis, we noticed the basic input/output system (BIOS) version on this computer does not match the specifications for the central processing unit (CPU), also known as a processor, that is installed on your computer. This can occur when a newer processor is installed on an older system board or older BIOS. Using a BIOS that does not support the installed processor can result in Windows system crashes. Contact your computer manufacturer or motherboard manufacturer for an updated version of BIOS for your computer's processor."

A oto mój bios Phoenix Award Bios 6.00. Przez dwa lata nic w komputerze nie zmieniałem, o co chodzi ?

To z debuggera Windowsa

Microsoft ® Windows Debugger Version 6.6.0003.5

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini061309-02.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 2

*** 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: Sat Jun 13 21:27:33.265 2009 (GMT+2)

System Uptime: 0 days 0:04:02.980

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

* 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 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 User Symbols

Loading unloaded module list

...........

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck E3, {89afaa30, 88eca448, 0, 2}

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

*** ***

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

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

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

Followup: MachineOwner

---------

oraz

Microsoft ® Windows Debugger Version 6.6.0003.5

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini061309-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 2

*** 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: Sat Jun 13 21:22:25.015 2009 (GMT+2)

System Uptime: 0 days 0:00:21.593

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

* 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 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 User Symbols

Loading unloaded module list

....

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 80042000, 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 ***

*** ***

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

Followup: MachineOwner

---------

Da sie to jakoś naprawić :( ?

//Zmien nazwe tematu, sprecyzuj ja, podaj problem...

//Inaczej temat do kosza trafi

//Ebol

ZooMpl
komentarz
komentarz

Stestuj pamięc MemTestem

Sprawdź , czy nie ma wersji BIOS'a dla Windows XP, MSI ostatnio robi osobny BIOS na którym nie działa XP

Keepsake
komentarz
komentarz
Stestuj pamięc MemTestem

Jutro sprawdze ;] Jeśli pamięć jest uszkodzona to będzie świetna okazja do zakupu 2x2GB.... i do wrócenia na Viste.

Sprawdź , czy nie ma wersji BIOS'a dla Windows XP, MSI ostatnio robi osobny BIOS na którym nie działa XP

Zapomniałbym, moja płyta - Abit IP-35E

Keepsake
komentarz
komentarz

Wielkie dzięki, Memtest pokazał ,że jedna z kości jest uszkodzona ,wystarczyło ja wyjąć i wszystko dobrze działa. Btw da się ją jakoś naprawić ? I jeśli kupie te same kości Geil Dual Ultra ale 2x2GB to będą dobrze działały z tą "samotną" :D ?

ZooMpl
komentarz
komentarz

Kości uszkodzonej nie naprawisz

Jeśli kupisz ten sam rodzaj RAM'u (SDRAM,DDR itp) , napięcie , szyna będą pasować to jak najbardziej będzie działać :) (i jeśli Twoja płyta głowna obsłuży tyle ramu)

Keepsake
komentarz
komentarz

Wiesz, na opakowaniu pisze ,że obsłuży 16GB :D Te kości są takie same tylko ,że nowe będą po 2GB a ta jest po 1GB. Rozumiem ,że system w pełni będzie obsługiwał te 5GB ? Bo teraz na 1GB ścina jak cholera.

ZooMpl
komentarz
komentarz

Tak, tylko musisz pobrać system 64bitowy bo 32 obsłuży ci tylko do 3gb

Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!

Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.

×
×
  • Dodaj nową pozycję...

Powiadomienie o plikach cookie

Strona wykorzystuje pliki cookies w celu prawidłowego świadczenia usług i wygody użytkowników. Warunki przechowywania i dostępu do plików cookies możesz zmienić w ustawieniach przeglądarki.