Kamilkadze utworzono 6 stycznia 2013 utworzono 6 stycznia 2013 Witam, od kilku dni znowu mam problem z bluescreenem, po dość długiej przerwie. Dzieje się to tylko i wyłącznie jak komp jest zimny, po włączeniu tak maksymalnie 5-6 bluescreenów i problem ustaje, potem komp może już chodzić i chodzić. Na bsodzie napisane jest Page fault in nonpaged area. Sprawdziłem plik dmp i problem powoduje plik ntoskrnl.exe. Czytałem trochę na necie, ale w sumie to nie wiele się dowiedziałem. Komputer jest calutki świeżo wyczyszczony, wydmuchany. Pomoże ktoś?
raazor90 komentarz 7 stycznia 2013 komentarz 7 stycznia 2013 Witam, Pokaż mi cały raport z dumpa. Pozdrawiam 1
Kamilkadze komentarz 7 stycznia 2013 Autor komentarz 7 stycznia 2013 (edytowane) Dzięki za odzew, jak wrócę z pracy to wrzucę wieczorkiem. Pozdro. Nie mogę ogarnąć załącznika więc wrzucam treść błędu tu: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\010413-14383-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 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`0284b000 PsLoadedModuleList = 0xfffff800`02a88e50 Debug session time: Fri Jan 4 16:19:51.279 2013 (UTC + 1:00) System Uptime: 0 days 0:06:25.152 ********************************************************************* * 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 50, {fffff8a006f66000, 0, fffff80002b81079, 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* Probably caused by : ntoskrnl.exe ( nt+336079 ) Followup: MachineOwner --------- Przed chwilą po raz pierwszy pojawił się bsod po dłuższym działaniu kompa, wcześniej tak nie miałem i to akurat w momencie gdy na youtubie wpisywałem tytuł kawałka. Czy Chrome może być w to zamieszany? :) Jednak wykluczam raczej chroma, bo teraz dwa razy sam z siebie się wysypał. Oj tracę cierpliwość.
raazor90 komentarz 8 stycznia 2013 komentarz 8 stycznia 2013 [quote name='Kamilkadze' timestamp='1357590572' post='1666938'] ***** Kernel symbols are WRONG. Please fix symbols to do analysis. [/quote] brakuje symboli UWAGA: Jeśli na ekranie pojawi się komunikat: Quote ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Oznacza to, że musimy pobrać symbole do swojego systemu dzięki którym odczytamy w całości plik minidump - na tym etapie jest on niekompletny i może wskazywać nie ten plik co trzeba. Zamykamy Debuggera. Po ponownym jego uruchomieniu klikamy File -> Symbol File Path -> wpisujemy:SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Następnie wciskamy [ctrl] + [D] i wskazujemy znów nasz plik minidump. Trzeba poczekać aż Debugger ściągnie sobie wszystkie symbole i przeanalizuje cały plik. Należy pamiętać że ten proces może nieco potrwać - symbole mogą ważyć nawet ponad 10MB, także trzeba uzbroić się w cierpliwość. 6. Wklejamy część minidumpa, o której mowa, na forum. 1
Kamilkadze komentarz 8 stycznia 2013 Autor komentarz 8 stycznia 2013 (edytowane) Ok dzięki, to dzisiaj wieczorną porą wrzucę kompletną treść. Pomału zaczynam odinstalowywać programy i tu szukać przyczyny i mam nadzieję, że to nic ze sprzetęm, bo najgorszy czas na wydatki teraz. Pełna treść z symbolami: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\010813-18267-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsof...ownload/symbols Executable search path is: SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store 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 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`0280b000 PsLoadedModuleList = 0xfffff800`02a48e50 Debug session time: Tue Jan 8 18:26:40.460 2013 (UTC + 1:00) System Uptime: 0 days 0:03:13.333 SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store 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 . SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store . SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store ............................................................. ................................................................ ............ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff8a003366000, 0, fffff80002b41079, 0} SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store ***** Kernel symbols are WRONG. Please fix symbols to do analysis. SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store SYMSRV: c:\symbols*http://msdl.microsof...ownload/symbols needs a downstream store ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* Probably caused by : ntoskrnl.exe ( nt+336079 ) Followup: MachineOwner ---------
raazor90 komentarz 10 stycznia 2013 komentarz 10 stycznia 2013 Stop 0x00000050 lub PAGE_FAULT_IN_NONPAGED_AREAPrzyczyna: może być to uszkodzona pamięć RAM lub niekompatybilne oprogramowanie, szczególnie jeśli chodzi o programy antywirusoweRozwiązanie: Jeśli błąd nastąpił zaraz po instalacji programu/sterownika należy odinstalować go z poziomu trybu awaryjnego Przetestuj pamięć RAM memtestem 86+ 1
Kamilkadze komentarz 11 stycznia 2013 Autor komentarz 11 stycznia 2013 Przeszedłem Max Payne'a i zrobiłem format, bo takie było moje założenie, włączam kompa rano i zero bluescreenów i tak sobie teraz uświadomiłem, że te bsody zaczęły się jak jego zainstalowałem... Jeśli problem znowu wystąpi to odpalę memtesta, a za dotychczasową pomoc stokrotne dzięki. :)
Gość komentarz 11 stycznia 2013 komentarz 11 stycznia 2013 ja tylko od siebie dodam że jeśli memtest nic nie wykryje to odpal dla pewnosci na paregodzinek goldmemory 1
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.