Błąd blue screen podczas gry

[danielg202]

Mój komputer to:
płyta główna:MSI MS-7502 / s775
procesor core 2 duo e6750
karta graficzna radeon x600 pro
zasilacz atx fortron 400w
pamięć ram ddr2 4gb
dysk twardy WD / 80/ 7200 rpm / sata

Proszę o powiedzenie jak można naprawić ten problem,czyli całkiem go wyeliminować.
Gram se w grę Wiedźmin i nagle wyłącza się komputer i pojawia się niebieskie tło i jest coś tam napisane,a póżniej się włącza komputer i windows pokazuje jaki to może być problem,o to i on:

Podpis problemu:

Nazwa zdarzenia problemu: BlueScreen
Wersja systemu operacyjnego: 6.1.7601.2.1.0.768.3
Identyfikator ustawień regionalnych: 1045

Dodatkowe informacje o problemie:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA8005B6FB30
BCP3: FFFFFA8005B6FE10
BCP4: FFFFF80002BE6DB0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Pliki pomagające opisać problem: C:\Windows\Minidump\062212-23540-01.dmp C:\Users\oem\AppData\Local\Temp\WER-34632-0.sysdata.xm


Również przy instalacji windows xp wyskakuje niebieskie tło i nie można podjąć próby zainstalowania systemu,tylko pisze tam coś o tym że może uszkodzić to dysk i trzeba sprawdzić wszystko w programie CHKDSK/F

Proszę o pomoc jakokolwiek.

[Wszechstronny]

Uruchom [b]Start - wiersz poleceń - chkdsk /f. [/b]
Wykonaj [url="http://www.forumpc.pl/index.php?showtopic=16074"]http://www.forumpc.pl/index.php?showtopic=16074[/url] , wklej raport.

[danielg202]

Wpisałem i pokazuje takie coś,co trzeba zrobić żeby to włączyć.

Odmowa dostępu z powodu niewystarczających uprawnień.
Musisz wywołać to narzędzie przy uruchomionym trybie podniesionych uprawnień.

Uruchomiłem to jako adminstrator.zaraz sprawdze.

Za dużo z tego nie na piszę,bo szybko te czarne okienko znika co skanuje dysk(ale chyba żadnych uszkodzeń nie ma , prawda?czy się myle??)
to mi się udało spisać:
NTFS Typ systemu plików
Skanowane pliki

przetworzone rekordy dużych plików - 69
przetworzone rekordy uszkodzonych plików - 0
przetworzone rekordy atrybótów rozszerzonych - 0
przetworzone rekordy ponownej analizy - 67

Skanowane indeksy:
Przetworzone wpisy indeksu 116316
P. plik nieinkasowanych - 0 ? - nie wiem jak w tym wyrazie to pisało,(dalej już nie zdążyłem)

[Wszechstronny]

Ok, kolego nie warto pisać, bo się zapiszesz, ważne, że przeskanował. Wykonaj ten link i wklej raport.( Patrz pierwszy post )

[danielg202]

to jest ten błąd wyczytany za pomocą programu debugging tools for windows
Chce jeszcze powiedzieć że skanowałem dzisiaj antywirusem avast komputer i nie wykrył zagrożenia
Proszę powiedzieć co to jest i jak to zniszczyć,mógł bym nawet zainstalować odnowa windowsa,ale nie stety nie chce się instalować,bo wyskakuje że można uszkodzić dysk.Jeśli chodzi o te 3 raporty to w każdym przedostatni tekst się powtarzał więc wyciołem i zostawiłem jeden
Proszę o pomoc.


[spoiler]Microsoft ® Windows Debugger Version 6.2.8400.0 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\062212-23540-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 \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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02863000 PsLoadedModuleList = 0xfffff800`02aa8e90
Debug session time: Fri Jun 22 22:46:42.226 2012 (UTC + 2:00)
System Uptime: 0 days 0:05:54.067
*********************************************************************
* 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 \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 F4, {3, fffffa8005b6fb30, fffffa8005b6fe10, fffff80002be6db0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

----- ETW minidump data unavailable-----
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
Probably caused by : wininit.exe

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
















A TO JEST DRUGI:





Microsoft ® Windows Debugger Version 6.2.8400.0 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\062212-24148-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 \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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02865000 PsLoadedModuleList = 0xfffff800`02aaae90
Debug session time: Fri Jun 22 22:40:05.475 2012 (UTC + 2:00)
System Uptime: 0 days 4:23:47.624
*********************************************************************
* 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 \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 F4, {3, fffffa80051ebb30, fffffa80051ebe10, fffff80002be8db0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

----- ETW minidump data unavailable-----
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
Probably caused by : wininit.exe

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

0: kd> g
^ No runnable debuggees error in 'g'









A TO JEST 3




Microsoft ® Windows Debugger Version 6.2.8400.0 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\062312-26629-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 \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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0285e000 PsLoadedModuleList = 0xfffff800`02aa3e90
Debug session time: Sat Jun 23 18:23:01.485 2012 (UTC + 2:00)
System Uptime: 0 days 1:15:41.327
*********************************************************************
* 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 \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 F4, {3, fffffa8005b36b30, fffffa8005b36e10, fffff80002be1db0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

----- ETW minidump data unavailable-----
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
************************************************************************
Probably caused by : csrss.exe

Followup: MachineOwner
---------[/spoiler]

PROSZĘ O POMOC JAK TO NAPRAWIĆ.
Mógł bym nawet sformatować komputer ale gdy się on nie chcę przez te błedy,więc musze się pozbyć tych błedów.

[Wszechstronny]

Wszystko fajnie, tylko nie śpiesz się tak. Wystarczył jeden najnowszy raport a poza tym musisz pobrać symbole, ponieważ raport jest niekompletny. [b]Kernel symbols are WRONG. Please fix symbols to do analysis [/b]na to wskazuje. Odpal ten link [url="http://www.forumpc.pl/index.php?showtopic=16074"]http://www.forumpc.pl/index.php?showtopic=16074[/url] i wykonaj drugą część zaczynającą się od słowa uwaga. Wklej [b]jeden [/b]raport.

[danielg202]

Tamte 3 pliki znikneły ale pojawił się dzisiaj blue screen podczas gry,jest wklejony zaraz po tych symbolach od tego co dzisiaj mindumpu.
A symbole co są w tym pliku tak wyglądają,nic więcej się nie wyświetliłą tylko to co widać:

TO SĄ SYMBOLE Z DZISIEJSZEGO BLUE SCREENA

[spoiler]Microsoft ® Windows Debugger Version 6.2.8400.0 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\062412-18798-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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02850000 PsLoadedModuleList = 0xfffff800`02a95e90
Debug session time: Sun Jun 24 11:22:44.963 2012 (UTC + 2:00)
System Uptime: 0 days 1:31:10.805
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8005493a20, fffffa8005493d00, fffff80002bd3db0}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

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

















A TO JEST TEN DZISIEJSZY MINI DUMP
------------------------------------------------------------------------------------------------------------------------------------
Microsoft ® Windows Debugger Version 6.2.8400.0 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\062412-18798-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 \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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02850000 PsLoadedModuleList = 0xfffff800`02a95e90
Debug session time: Sun Jun 24 11:22:44.963 2012 (UTC + 2:00)
System Uptime: 0 days 1:31:10.805
*********************************************************************
* 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 \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 F4, {3, fffffa8005493a20, fffffa8005493d00, fffff80002bd3db0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

----- ETW minidump data unavailable-----
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
Probably caused by : csrss.exe

Followup: MachineOwner
---------[/spoiler]

[Wszechstronny]

Na razie przeskanuj komputer [b]Malwarebytes Anti-Malware[/b], oczyść rejestr [b]Ccleaner, [/b]sterowniki do karty graficznej wgrywałeś może ostatnio ? Możliwe, że temperatury są zbyt wysokie i nie są w stanie wytrzymać obciążenia. Trudno bez tego pliku podać dokładną przyczynę.

[danielg202]

Z programu SpeedFan mój komputer:

[spoiler]Fan1:930 RPM
Fan2:0 RPM
Fan3:0 RPM
Fan4:0 RPM

(strzałka niebieska w dół)Temp1: 28
(strzałka niebieska w dół)Temp2: 31
(strzałka niebieska w dół)Temp3: -128
(zielony ptaszek)HD0: 41
(strzałka niebieska w dół)Temp1: 22
(strzałka niebieska w dół)Temp0: 27
(strzałka niebieska w dół)Temp1:24

Pwm1 39%
Pwm2 75%
Pwm3 75%
Pwm4 75%

VCC3V: 3.36V
Vcore: 1.05V
VRAM 1.73V
Vchipset 0.95V
+5V 5.09V
+12V 12.32V
VCC1.5V: 0.91V
VSB3V: 3.34V
Vbat 3.25V



A PROGRAMEM [b]Malwarebytes Anti-Malware nic nie wykryło.[/b]
Oczyśćiłem też rejestr [b]Ccleaner[/b]
[b]I za aktualizowałem sterownik do karty graficznej[/b]

A teraz normalnie podczas przeglądania internetu zacieło się i wyłączyło komputer i pojawił się blue screen.Oto spis z minidump:
Microsoft ® Windows Debugger Version 6.2.8400.0 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\062412-14445-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 \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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02849000 PsLoadedModuleList = 0xfffff800`02a8ee90
Debug session time: Sun Jun 24 13:57:38.461 2012 (UTC + 2:00)
System Uptime: 0 days 0:05:57.303
*********************************************************************
* 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 \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 F4, {3, fffffa80053c4910, fffffa80053c4bf0, fffff80002bccdb0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

----- ETW minidump data unavailable-----
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
Probably caused by : wininit.exe

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

I do tego chyba symbole:

Microsoft ® Windows Debugger Version 6.2.8400.0 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\062412-14445-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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02849000 PsLoadedModuleList = 0xfffff800`02a8ee90
Debug session time: Sun Jun 24 13:57:38.461 2012 (UTC + 2:00)
System Uptime: 0 days 0:05:57.303
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80053c4910, fffffa80053c4bf0, fffff80002bccdb0}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

Followup: MachineOwner
---------[/spoiler]

[Gość]

wykonaj skan pamięci ram programem memtest x86

jesli nic nie wykryje to jeszcze wykonaj skan programem goldenmemory

[danielg202]

Mem testem wyszło że nie ma błędu.
Na końcu napisało: Pass complete,no errors,press Esc to exit.

Tam tym programem nie testowałem,bo by chyba nic nowego nie wykrył,a kolejna pusta płyta była by potrzebna.

Więc co to może być za błąd i jak go usunąć?

[Gość]

uruchom cmd jako administrator i wykonaj " sfc /scannow " - jesli nic nie wykryje to wykonaj logi otl
niewykluczona infekcja, obstaje przy dodatkowym skanie goldenmemory, memtest nie zawsze wykrywa błędy

znaczy sie wykonaj logi otl i wklej na www.wklej.org , oraz wykonaj komende sfc /scannow w cmd

[danielg202]

W sfc/scannow nic nie wykryło.
A to link do logów: http://www.wklej.eu/index.php?id=fba57cd11c
No i jak wiesz już jak można się pozbyć tego blue screena???

[Gość]

do logów musi spec zajrzeć - powtarzam prośbę abyś wykonał skan pamięci programem goldenmemory - w niektorych przypadkach memtest nie wykrywa błędu

takowego bluscreena m.in powoduje uszkodzona kość pamięci

w jakim celu zainstalowałes HDD Regenerator?? sprawdź dysk programem HD Tune (zakładka error scan) nie używaj więcej hdd regeneratora i napisz czy dotychczas go uzywales

[danielg202]

Ngidy jeszcze nie używałem hdd regenerator.Niestety ale program gold memory chyba nie obsługuje windows 7.

HD tune wykrywa błedy(czerwone kwadraciki),ale nie kontrolowałem i mi się zresetował sam,przez te błędy i nie wiem ile było,i przy włączeniu komputera pokazało się jak chcę włączyć komputer po błedzie(takie typowe:czyli awaryjnie lub normalnie),ale wcześniej rządało płyte jakąś w botowaniu,coś tam pisało o systemie.Więc prawdopodobnie problemem jest dysk twardy.
Możesz mi podać jak mogę sprawdzić jaki mam dysk twardy i czy spełnia wymogi do programu MHDD,gdyż będzię chyba trzeba spróbować naprawić błędy tym programem.Jak myślisz czy tak zrobić,i jak sprawdzić to co napisałem???
I np. jakby sformatował dysk i zainstalował windows 7 to by przeszła bez problemu instalacja,czy by dysk uniemożliwił instalację???aktualnie też posiadam windows 7(wersje testową),ale jak chciałem instalować windows xp to mi wyskakiwał blue screen z błędem stop 0x0000007b.
Podaj odpowiedzi do każdego pytania.

[Gość]

przepraszam ze nie odpisywałem - pracowałem od rana do wieczora.
juz odpowiadam - z całą pewnością masz uszkodzony dysk i nalezy go wymienić - czerwone kwadraciki są to badsektory

jak najbardziej uszkodzony dysk uniemowżliwił instalację windows xp - mhdd raczej tu nie pomoże, mhdd pomaga przy pojedynczych bad sektorach i kiepskich odczytach s.m.a.r.t. - gdy z powodu bad sektorów są już bsody a u ciebie są to już dysk kwalfikuje sie do wymiany

[danielg202]

Po kilku dniach odpoczęciu od komputera,sprawdziłem tym razem dysk programem Ashampoo HDD Control 2 Guard i nie wykryło żadnego bada sektorów,a tamten program którym testowałem przedtem i co wykrył bady sektorów nie był dla dysku sata,a ja taki posiadam.Jeszcze powiem jak tak piszę normalnie to mam temperature dysku 45 stopni(ptaszek zielony),a resztę podzespołów strzałkę w dół.I niekiedy prawdopodobnie dysk twardy, zapiszczy kilka sekund.
I też z 6 sekund ładuje się komputer jak pokaże się pulpit przy włączeniu komputera.
Nie raz się przy normalnej pracy tak jakby przytnie komputer,a potem działa,a w innym razie blue screen się pojawi,ostatnio z błędem F4.

[Gość]

mimo to zostaje przy tezie że dysk jest padnięty i nadaje się do wymiany

[danielg202]

Pomyliłem się, około 20 sekund się ładuję pulpit przy włączeniu komputera i też nie raz komputer działa tak jak by ramu jej było zamało czyli wolono myszka chodzi i przy tym ciche zgrzytania od komputera.
Czyli podtrzymujesz tą teze,czy nie? i czemu tak myślisz.? Chce przypomnieć że nie wykryło żadnego bada sektoru.
Możesz zasugerować jeszcze jakieś programy diagnostyczne na windows 7.

[Gość]

programem goldenmemory sprawdz pamięci ram

wykonaj ponownie test programem hd tune (normalne powolne skanowanie bez szybkiego)

[danielg202]

Chyba nie ma programu goldenmemory,znalazłem gold memory 6.92,niestety nie wiem jak wypalić na płyte cd,bo jest tam kilka plików.
HD tune nie obsługuje dysku sata,a taki ja posiadam.Możesz mi podać program taki który obsługuje dysk sata.

[Gość]

[quote name='danielg202' timestamp='1340822987' post='1527500']
Ngidy jeszcze nie używałem hdd regenerator.Niestety ale program gold memory chyba nie obsługuje windows 7.

HD tune wykrywa błedy(czerwone kwadraciki),ale nie kontrolowałem i mi się zresetował sam,przez te błędy i nie wiem ile było,i przy włączeniu komputera pokazało się jak chcę włączyć komputer po błedzie(takie typowe:czyli awaryjnie lub normalnie),ale wcześniej rządało płyte jakąś w botowaniu,coś tam pisało o systemie.Więc prawdopodobnie problemem jest dysk twardy.[/quote] sprawdziłeś już raz dysk programem hd tune więc zrób to ponownie, w czym problem?

[danielg202]

No ale piszę dokładnie że nie obsługuje moje go dysku.A jak przed tem używałem to nie doszło do końca tylko do 1/5 i się zacieło i blue screen się pojawił.
Zasugeruj mi inny program na dysk sata.
Na to chwilę pojawiają się bluescreeny z kodem F4.
I błąd jest powiązany z plikiem wininit.exe

[Gość]

więc ściągnij mhdd - do testu dysku

[danielg202]

Możesz mi powiedzieć jak sprawdzić czy mam dysk ustawiony w trybie master.
I jak sprawdzić czy dysk jest jedynym urządzeniem podpiętym pod kanał SATA.
Bo program MHDD 4.6 te czynności wymaga.