x-kom hosting

[Rozwiązany] Zawieszanie się komputera i ciągłe restarty

Qboj
utworzono
utworzono

Witam.

Problem pojawił się nagle. W pewnym momencie podczas użytkowania PC zawiesza się, monitor przechodzi w "tryb oszczędny", po czym restaruje się. Podczas uruchamiania wyskakuje błąd na niebieskim tle jednak tylko miga także nie mogę zdążyć aby przeczytać. Następnie restartuje się ponownie i wtedy wszystkie litery są do połowy różowe, mogę uruchomić komputer tylko w trybie awaryjnym. Kiedy wyłączę komputer przez 'START' i uruchomię wszystko wraca do normy. Nawet format nie usunął problemu. Proszę o pomoc. Korzystam z Windowsa XP.

Psycholandia
komentarz
komentarz

Wykonaj:
http://www.forumpc.pl/index.php?showtopic=68409 + to: http://www.forumpc.pl/index.php?showtopic=16074

Qboj
komentarz
komentarz

[quote name='Andziorka' date='21 listopad 2009 - 17:23 ' timestamp='1258820600' post='906221']
Wykonaj:
http://www.forumpc.pl/index.php?showtopic=68409 + to: http://www.forumpc.pl/index.php?showtopic=16074
[/quote]



Właśnie zrobiłem zdjęcie błędowi jaki mi sie ukazuje i dołączam też "różowe litery"

problem

[IMG]http://i50.tinypic.com/2b5wld.jpg[/IMG]

"różowe litery"

[IMG]http://i50.tinypic.com/35j9w0j.jpg[/IMG]

Psycholandia
komentarz
komentarz

Jeszcze potrzebujemy tego: http://www.forumpc.pl/index.php?showtopic=16074

Qboj
komentarz
komentarz

przeszukałem komputer ale nigdzie nie znajduje folderu 'minidump'

Psycholandia
komentarz
komentarz

Do poczytania + wykonania:
http://support.microsoft.com/kb/903251/pl
http://support.microsoft.com/kb/329293/pl
http://www.idg.pl/porada/89197/Blad.0x00000050.Page_Fault_In_Non.Paged_Area.w.Windows.XP.html

Zainstaluj inne sterowniki do karty graficznej, a te które masz teraz odinstaluj programem Drive Cleaner 3.

Qboj
komentarz
komentarz (edytowane)

po zainstalowaniu sterowników na nowe problem nie zniknął, dodatkowo pojawił się nowy z włączaniem PC'ta.
kiedy próbuje włączyć, komp pracuje, jednak monitor jest czarny :blink:
restart niewiele pomaga....czasami zadziała i się włączy....

PO FORMACIE WYSKOCZYŁY 2 PLIKI OTO PIERWSZY Z NICH >>>



[code]Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\Mini112109-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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sat Nov 21 23:19:46.546 2009 (GMT+1)
System Uptime: 0 days 0:11:55.125
*********************************************************************
* 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
.............
Unable to load image nv4_mini.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {86600004, 0, f05fca44, 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 : nv4_mini.sys ( nv4_mini+e9a44 )

Followup: MachineOwner
---------

DRUGI Z NICH >>>


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\Mini112109-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 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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sat Nov 21 23:22:56.858 2009 (GMT+1)
System Uptime: 0 days 0:02:43.421
*********************************************************************
* 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
.............
Unable to load image nv4_mini.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {86600030, 0, f1773a44, 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 : nv4_mini.sys ( nv4_mini+e9a44 )

Followup: MachineOwner
---------
[/code]

MAM NADZIEJE ZE TO COS POMOŻE BO JA NIE MAM POJECIA O CO CHODZI ....

Psycholandia
komentarz
komentarz

[quote]Probably caused by : nv4_mini.sys ( nv4_mini+e9a44 [/quote]
inne sterowniki od karty graficznej zainstaluj, stare odinstaluj programem Drive cleaner 3 i zainstaluj najnowsze, a jeśli je masz to jakieś inne

piootr200
komentarz
komentarz

sprawdz na innej karcie graficznej czy bedzie taki sam problem. ja mialem to samo tylko ze pomaranczowe litery -to karta graficzna na 100%, przelaczal sie w stan czuwania ,i czarny ekran i dalej nic moglem resetowac i to samo. jak podepniesz inna sprawna na 100% karte to bedziesz musial sformatowac c i wtedy wgrac sterowniki od tej nowej kart i sie okaze . ja tak zrobilem i bylo ok. co sie stalo z karta nie wiem - cos sie przepalilo, cewka, opornik, itp.

Qboj
komentarz
komentarz

dzieki za pomoc ;)
jednak grafa zrobiła 'bye bye' dzisiaj przyszła nowa ;)
przełaczylismy grafe moja do kompa kumpla i niestety to ona ;/
ale juz wsio ok ;)
dzieki wielkie i Pozdrawiam ^^

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.