Blue screen :(


(Tomekdkm) #1

Witam. Od jakiegoś czasu pojawia mi się blue screen ( raz na 3 dni ) a ja nie mam pojęcia czym jest to spowodowane. Jeśli wiecie w czym jest problem to prosiłbym o poradę co mam robić. Oto szczegóły:

Blue screen 1: Sygnatura problemu

Nazwa zdarzenia problemu: BlueScreen

Wersja systemu operacyjnego: 6.0.6001.2.1.0.768.3

Identyfikator ustawień regionalnych: 1045

Dodatkowe informacje o problemie

BCCode: 7f

BCP1: 0000000000000008

BCP2: 0000000080050031

BCP3: 00000000000006F8

BCP4: FFFFF80001B72D4E

OS Version: 6_0_6001

Service Pack: 1_0

Product: 768_1

Blue screen 2: Sygnatura taka sama

Dodatkowe informacje o problemie

BCCode: 3b

BCP1: 00000000C0000005

BCP2: FFFFF9600007AF89

BCP3: FFFFFA600709AF30

BCP4: 0000000000000000

OS Version: 6_0_6001

Service Pack: 1_0

Product: 768_1

Dane mojego komputera:

Komputer:

Komputer z procesorem x64 obsługujący interfejs ACPI

System operacyjny Microsoft Windows Vista Home Premium z Service pack 1 64 bit

Płyta główna:

Typ procesora Intel Celeron D 352, 3200 MHz (24 x 133) (64bit)

Nazwa płyty głównej Asus P5VD2-VM (2 PCI, 1 PCI-E x1, 1 PCI-E x16, 2 DDR2 DIMM, Audio, Video, Gigabit LAN)

Karta graficzna:

NVIDIA GeForce 7300 GT

Karta dźwiękowa Creative Audigy SE (SB0570) Sound Card

Moduły pamięci : 1024 MB 667MHz oraz 2024 MB 667 MHz razem 3Gb ( dodam że każdy moduł jest innej firmy )

Zasilacz: 300W

Jeżeli dodałem mało informacji to piszcie jakie jeszcze mam dane podać:

Z góry Bardzo dziękuję, pozdrawiam:)


(Cosik Ktosik) #2

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

Daj raport na forum wg tych zasad :arrow: viewtopic.php?f=16&t=253052

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

Ogólnie:

0x0000007F - UNEXPECTED_KERNEL_MODE_TRAP - błędy sprzętowe lub programowe jądra systemu: http://support.microsoft.com/kb/137539/pl

0x3B - SYSTEM_SERVICE_EXCEPTION - błąd programowy. Może dotyczyć błędów spowodowanych sterownikami do karty graficznej.

Podaj koniecznie całe raporty z plików DMP.


(Tomekdkm) #3

Nie wiem która część jest ważna, ale wkleję cały tekst z pliku :frowning: A co do wysyłania raportu według zasad ( nie wiem czemu, ale ta strona mi się nie otwiera i nie wiem czemu ). Sorki za długość :frowning:

Microsoft ® Windows Debugger Version 6.9.0003.113 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 \SystemRoot\system32\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 Server 2008 Kernel Version 6001 (Service Pack 1) UP Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0xfffff80001a5b000 PsLoadedModuleList = 0xfffff80001c20db0

Debug session time: Fri Oct 31 11:20:32.007 2008 (GMT+1)

System Uptime: 0 days 0:12:16.617

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

* 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 \SystemRoot\system32\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 7F, {8, 80050031, 6f8, fffff80001b72d4e}

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

*** ***

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

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

*** ***

*** ***

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

*** ***

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

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

*** ***

*** ***

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

*** ***

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

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

*** ***

*** ***

*** 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 : ntoskrnl.exe ( nt+55350 )

Followup: MachineOwner



(Cosik Ktosik) #4

To jest jeden błąd dotyczący jądra, a jeszcze powinien być drugi 3b.

PS Do wklejania mamy dwie zasadnicze stronki http://wklejto.pl/ oraz http://www.wklej.org/

Jeżeli Masz z nimi problemy to użyj tagów code (są nad oknem pisania postów) i pomiędzy nie wklej drugi raport.


(Tomekdkm) #5

Witam. Jeżeli chodzi o ten drugi ( chyba plik lub część danych danego pliku - nie wiem ) 3b, to w danym katalogu znajdują się same pliki DMP. Innych plików z innymi rozszerzeniami niema. A po otwarciu jednego DMP pokazuje to co wcześniej wkleiłem. Pozdrawiam.


(Cosik Ktosik) #6

Jasne, bo te pliki są podobne. Rodzaj błędu znajdziesz w linijce:

, a przyczynę: