LandsberG utworzono 4 kwietnia 2010 utworzono 4 kwietnia 2010 (edytowane) Witam Gdy gram w jakieś gry, lub czasem surfuję po internecie wyświetla mi się blue screen. Jest raczej przy grach, bez żadnych oznak po prostu gra się zacina, a po chwili pojawia się blue screen. Blue screeny : - Internet ( rzadko) - Counter Strike 1.6 (rzadko) -Garry's Mod ( Bardzo często ) -Battlefield 2 Bad Company ( dość często ) Nie wiem od czego to zależy. Skanowałem całego kompa i usuwałem rejestry przez CCleaner oraz EasyCleaner. Mój sprzęt : Ms Windows Vista Ultimate SP1 AMD Athlon 7850 Dual-Core Processor 2,0 GB Ram Nvidia GeForce 9600GT Wiem, że format jest odpowiedzią na wiele pytań, ale czy da się go ominąć, czy mam iść z tym do serwisu bo komp jest na gwarancji ... Dodam, że bardzo częśto użycie procesora jest 100 % ... Przed wystąpieniami tych blue screenów pisało coś o BIOSIE. Trzeba go update'ować czy jak ? Zdjęcie : [img]http://iv.pl/images/35229130227259183681.jpg[/img]
raazor90 komentarz 4 kwietnia 2010 komentarz 4 kwietnia 2010 Wykonaj to: http://www.forumpc.pl/index.php?showtopic=16074 a będziemy wiedzieć co jest przyczyną BSOD-ów
LandsberG komentarz 4 kwietnia 2010 Autor komentarz 4 kwietnia 2010 (edytowane) [spoiler]Microsoft ® Windows Debugger Version 6.11.0001.404 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini040310-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\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x81e40000 PsLoadedModuleList = 0x81f57c70 Debug session time: Sat Apr 3 02:19:13.833 2010 (GMT+2) System Uptime: 0 days 4:16:34.784 ********************************************************************* * 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\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols ............................................................... ................................................................ ........................................ Loading User Symbols Loading unloaded module list ................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {81d2e6e0, 8, 81d2e6e0, 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 *** *** *** ************************************************************************* ********************************************************************* * 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+ * ********************************************************************* [color="#FF00FF"]Probably caused by : ntkrnlpa.exe ( nt+a5195 )[/color] Followup: MachineOwner[/spoiler] --------- Zaznaczyłem na różowo Sciągnąć ten program i wsadzić do folderu windowsa ?
raazor90 komentarz 4 kwietnia 2010 komentarz 4 kwietnia 2010 Wykonaj: [quote][b]Kernel symbols are WRONG. Please fix symbols to do analysis.[/b] 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.[/quote]
LandsberG komentarz 4 kwietnia 2010 Autor komentarz 4 kwietnia 2010 (edytowane) Tylko coś takiego było, postępowałem zgodnie z instrukcją [log]Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini040410-03.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: Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x81e36000 PsLoadedModuleList = 0x81f4dc70 Debug session time: Sun Apr 4 10:30:44.253 2010 (GMT+2) System Uptime: 0 days 1:55:52.048 Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols ............................................................... ................................................................ ........................................ Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffffffe, 8, fffffffe, 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 *** *** *** ************************************************************************* Probably caused by : watchdog.sys ( watchdog!WdLogEvent5+57 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffffffe, memory referenced. Arg2: 00000008, value 0 = read operation, 1 = write operation. Arg3: fffffffe, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved) Debugging Details: ------------------ ***** 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 *** *** *** ************************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. FAULTING_MODULE: 81e36000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 47918c21 WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd fffffffe FAULTING_IP: +69ce952f0322dc90 fffffffe ?? ??? MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 3 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 81e90bf4 to 81edb195 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. c4ba76a0 81e90bf4 00000008 fffffffe 00000000 nt+0xa5195 c4ba76c8 8d5bb157 8d5bb100 00000000 97f4a008 nt+0x5abf4 c4ba7d50 81e8da9a bee25748 00000000 00000000 watchdog!WdLogEvent5+0x57 c4ba7d64 77229a94 badb0d00 0ffefe88 00000000 nt+0x57a9a c4ba7d68 badb0d00 0ffefe88 00000000 00000000 0x77229a94 c4ba7d6c 0ffefe88 00000000 00000000 00000000 0xbadb0d00 c4ba7d70 00000000 00000000 00000000 00000000 0xffefe88 STACK_COMMAND: kb FOLLOWUP_IP: watchdog!WdLogEvent5+57 8d5bb157 894604 mov dword ptr [esi+4],eax SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: watchdog!WdLogEvent5+57 FOLLOWUP_NAME: MachineOwner MODULE_NAME: watchdog IMAGE_NAME: watchdog.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------[/log]
raazor90 komentarz 4 kwietnia 2010 komentarz 4 kwietnia 2010 Zrób reinstalkę sterowników płyty głównej itp. Dodatkowo zainstaluj Service packa 2
LandsberG komentarz 4 kwietnia 2010 Autor komentarz 4 kwietnia 2010 http://www.microsoft.com/downloads/details.aspx?FamilyID=891ab806-2431-4d00-afa3-99ff6f22448d&displaylang=pl Nie chce mi sie zainstalowac serwice pack. Instaluje si wszystko a potem, że nie udana instalacja i że wszystkie podjęte decyzje będą cofnięta i tak zatacza błędne koło. Co do sterowników to nie moge znależć do plyty glownej asusa. Może lepiej zrobić formata ?
bartek86 komentarz 4 kwietnia 2010 komentarz 4 kwietnia 2010 jak zrobisz formata to i tak trzeba będzie znaleźć i zainstalować odpowiednie sterowniki podaj model swojej płyty głównej
raazor90 komentarz 4 kwietnia 2010 komentarz 4 kwietnia 2010 Przed instalacją SP2 zrób aktualizację wstępną: http://support.microsoft.com/?kbid=955430
LandsberG komentarz 4 kwietnia 2010 Autor komentarz 4 kwietnia 2010 Service Pack 2 nic nie dał Informacja z BIOS'u Award ASUS M2N-SLI DELUXE ACPI BIOS Revision 1701
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.