Blue Screen

[Spider]

Witam mam pewien problem dzisiaj wyskoczył mi Blue Screen lecz nie zdążyłem go przeczytać więc użyłem programu WinDbg którego kod zamieszczam poniżej. Program wskazuje że problem dotyczy pliku ntoskrnl.exe Dodam także że komputer się nie przegrzewa, pamięci ustawione są na 1,7V tak samo z timingami jak zaleca producent. Błąd ten pokazał się podczas normalnego słuchania muzyki i ściąganiu pliku z internetu. Proszę was o pomoc pozdro.

 

Microsoft (R) Windows Debugger Version 6.10.0003.233 X86Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\092710-27690-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeWindows 7 Kernel Version 7600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7600.16617.amd64fre.win7_gdr.100618-1621Machine Name:Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e9ae50Debug session time: Mon Sep 27 13:38:59.530 2010 (GMT+2)System Uptime: 0 days 0:30:52.874********************************************************************** 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*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeLoading Kernel Symbols..................................................................................................................................................................Loading User SymbolsLoading unloaded module list.....********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 3B, {c0000005, fffff80002cd0905, fffff88006fe1b30, 0}*** WARNING: Unable to verify timestamp for hal.dll*** ERROR: Module load completed but symbols could not be loaded for hal.dll***** 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+                                    **********************************************************************Probably caused by : ntoskrnl.exe ( nt+73905 )Followup: MachineOwner---------3: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SYSTEM_SERVICE_EXCEPTION (3b)An exception happened while executing a system service routine.Arguments:Arg1: 00000000c0000005, Exception code that caused the bugcheckArg2: fffff80002cd0905, Address of the exception record for the exception that caused the bugcheckArg3: fffff88006fe1b30, Address of the context record for the exception that caused the bugcheckArg4: 0000000000000000, zero.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                                     ******                                                                   ************************************************************************************************************************************************** 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+                                    **********************************************************************MODULE_NAME: ntFAULTING_MODULE: fffff80002c5d000 ntDEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwoFAULTING_IP: nt+73905fffff800`02cd0905 498b08          mov     rcx,qword ptr [r8]CONTEXT:  fffff88006fe1b30 -- (.cxr 0xfffff88006fe1b30)rax=0000000022e9ffff rbx=0000000000000008 rcx=fffff880031d3e80rdx=e56c694602150001 rsi=fffff880031d3e80 rdi=0000000000000008rip=fffff80002cd0905 rsp=fffff88006fe2500 rbp=fffff80002e5c880 r8=e56c694602150000  r9=fffff80002c5d000 r10=fffff880031d3e80r11=0000000000000000 r12=000000000000000d r13=0000000000000000r14=0000000000000002 r15=000000006770534eiopl=0         nv up ei ng nz na po nccs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286nt+0x73905:fffff800`02cd0905 498b08          mov     rcx,qword ptr [r8] ds:002b:e56c6946`02150000=????????????????Resetting default scopeCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WRONG_SYMBOLSBUGCHECK_STR:  0x3BCURRENT_IRQL:  0LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002cd0905STACK_TEXT:  fffff880`06fe2500 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x73905FOLLOWUP_IP: nt+73905fffff800`02cd0905 498b08          mov     rcx,qword ptr [r8]SYMBOL_STACK_INDEX:  0SYMBOL_NAME:  nt+73905FOLLOWUP_NAME:  MachineOwnerIMAGE_NAME:  ntoskrnl.exeSTACK_COMMAND:  .cxr 0xfffff88006fe1b30 ; kbBUCKET_ID:  WRONG_SYMBOLSFollowup: MachineOwner---------3: kd> lmvm ntstart             end                 module namefffff800`02c5d000 fffff800`03239000   nt         (no symbols)               Loaded symbol image file: ntoskrnl.exe    Image path: \SystemRoot\system32\ntoskrnl.exe    Image name: ntoskrnl.exe    Timestamp:        Sat Jun 19 06:16:41 2010 (4C1C44A9)    CheckSum:         005489D7    ImageSize:        005DC000    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

[BuMeL]

Awaria Kernela może nastąpić przez awarię dysku lub pamięci. Zobacz czy nie masz badów i sprawdź ramy memtestem, możesz im też podnieść napięcie o pół oczka jeśli mają radiatory. Mógł się też pojawić sprzętowy błąd np. spowodowany systemem zarządzania energią w windowsie przy próbie obniżenia taktowania procka. Jeśli błąd nie pojawia się częściej to nie ma obawy, zaktualizuj Bios płyty.

[Spider]

Zgadza się ten błąd pokazał mi się pierwszy raz inne nigdy nie występowały a system Windows 7 mam na dysku ponad pół roku. Co do Ramu i dysku oczywiście sprawdzę. Jeśli chodzi o systemem zarządzania energią w windowsie przy próbie obniżenia taktowania procka to tą opcje mam wyłączoną w biosie dzięki czemu mój procek ma cały czas 3,2Ghz.

 

Ps. Ile czasu należy testować pamięć ram aby być pewnym że są sprawne 5 godzin? pozdro

[ULLISSES]

Myślę, że 2 przebiegu w GoldMemory powinny starczyć na początek.

[Spider]

Witam ponownie posiedziałem trochę nad testami i oto wyniki:

 

1. Ram wygląda na wporzo przez całe dwie pętle w programie Gold Memory v6.92 nie wykazał żadnych błędów ale na wszelki wypadek daje screeny z ustawieniami w biosie.

 

 

 

 

2. No i druga kwestia jeśli chodzi o dysk twardy nie wygląda chyba najciekawiej zresztą zobaczcie sami.

 

Jak widzicie tutaj ma pewne problemy.

 

Tutaj znowu nic nie wskazuje na to aby były uszkodzone jakieś sektory cały scan wygląda na czysty.

 

A na koniec ogólna wydajność dysku na wszelki wypadek.

 

Ps. Dodam także że każdy podzespół komputera jest objęty gwarancją i w razie czego jeśli okaże się że coś jest nie tak to proszę śmiało mówić. pozdro. :)

[BuMeL]

Dysk na serwis, zgraj ważne rzeczy póki jeszcze możesz.

[Spider]

Czyli jednak :cry: tak myślałem że coś jest z nim nie tak. Dzięki BuMel za pomoc i tobie ULLISSES także jutro zgram co ważne z dysku i pojadę do serwisu. O wszelkich postępach będę pisać tutaj pozdro.

[BuMeL]

Wyślij do WD, co będziesz zapracowanym ludziom głowę zawracał ;)