Elektroda.pl
Elektroda.pl
X

Search our partners

Find the latest content on electronic components. Datasheets.com
Elektroda.pl
Please add exception to AdBlock for elektroda.pl.
If you watch the ads, you support portal and users.

problem BSOD-y Windows 7 Sony Vaio VPCEB1S1E

vinga 20 Jul 2010 10:54 2318 4
  • #1
    vinga
    Level 9  
    Witam serdecznie,
    mam taki problem: od wczoraj na moim laptopie pojawiają się Blue Screeny, i zaraz reset komputera. Na początku działo się to tylko przy grze Avatar, teraz przy każdej pracy. Może ktoś potrafiłby mi pomóc? Błąd wygląda tak:


    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\072010-18751-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 (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`0301e000 PsLoadedModuleList = 0xfffff800`0325be50
    Debug session time: Tue Jul 20 09:53:45.561 2010 (UTC + 2:00)
    System Uptime: 0 days 0:03:58.121
    *********************************************************************
    * 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
    ...
    *** WARNING: Unable to verify timestamp for hal.dll
    *** ERROR: Module load completed but symbols could not be loaded for hal.dll
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.



    BugCheck 124, {0, fffffa800647a028, b2000000, 30005}

    ***** 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!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for PSHED.dll
    *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 : hardware

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





    Dodam, że sterowniki są aktualne, temperatury chyba też, procesor ok 35%, grafika - 55%.

    Będę wdzięczna za każdą pomoc.
    [28-30.06.2022, targi] PowerUP EXPO 2022 - zasilanie w elektronice. Zarejestruj się za darmo
  • #2
    lpm11
    Level 22  
    Niestety w tym logu nie ma żadnych konkretnych informacji.

    Napisz może po prostu kod błędu jaki się wyświetla przy blue-screenie.
    Jeżeli system się natychmiast resetuje włącz opcję "wyłącz automatyczne uruchamianie po awarii..." przy uruchamianiu systemu wciskając F8.
  • #3
    vinga
    Level 9  
    wracam do tematu, gdyż problem, po miesiącu spokoju, znów wrócił. poprzednim razem wydaje mi się, że pomogła aktualizacja systemu, albo nowy antywirus. teraz to też nie pomaga. kody błędów wyglądają tak:

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

    Dodatkowe informacje o problemie:
    BCCode: 124
    BCP1: 0000000000000000
    BCP2: FFFFFA800646D028
    BCP3: 00000000B2000000
    BCP4: 0000000000030005
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    Pliki pomagające opisać problem:
    C:\Windows\Minidump\082210-23228-01.dmp
    C:\Users\vinga\AppData\Local\Temp\WER-73367-0.sysdata.xml

    Przeczytaj w trybie online nasze zasady zachowania poufności informacji:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0415

    Jeśli zasady zachowania poufności informacji w trybie online nie są dostępne, przeczytaj nasze zasady zachowania poufności informacji w trybie offline:
    C:\Windows\system32\pl-PL\erofflps.txt



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

    Dodatkowe informacje o problemie:
    BCCode: 124
    BCP1: 0000000000000000
    BCP2: FFFFFA800652E028
    BCP3: 00000000B2000000
    BCP4: 0000000000030005
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    Pliki pomagające opisać problem:
    C:\Windows\Minidump\082810-20389-01.dmp
    C:\Users\vinga\AppData\Local\Temp\WER-74412-0.sysdata.xml

    Przeczytaj w trybie online nasze zasady zachowania poufności informacji:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0415

    Jeśli zasady zachowania poufności informacji w trybie online nie są dostępne, przeczytaj nasze zasady zachowania poufności informacji w trybie offline:
    C:\Windows\system32\pl-PL\erofflps.txt



    czy ktoś potrafiłby mi pomóc?


    a to kolejne podpisy:

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

    Dodatkowe informacje o problemie:
    BCCode: 124
    BCP1: 0000000000000000
    BCP2: FFFFFA8006580028
    BCP3: 00000000B2000000
    BCP4: 0000000000030005
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    Pliki pomagające opisać problem:
    C:\Windows\Minidump\082810-27924-01.dmp
    C:\Users\vinga\AppData\Local\Temp\WER-538250-0.sysdata.xml


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

    Dodatkowe informacje o problemie:
    BCCode: 124
    BCP1: 0000000000000000
    BCP2: FFFFFA80065C3028
    BCP3: 00000000B2000000
    BCP4: 0000000000030005
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    Pliki pomagające opisać problem:
    C:\Windows\Minidump\082810-26270-01.dmp
    C:\Users\vinga\AppData\Local\Temp\WER-227184-0.sysdata.xml



    Jeszcze jedna rzecz: sprawdziłam programem BlueScreenView, który każdy z minidumpów pokazywał jako przyczynę:
    Spowodowane przez sterownik: hal.dll
    Spowodowane przez adres: hal.dll+12903

    co to jest? szukam w googlach, ale nie potrafię znaleźć rozwiązania podobnego problemu....
  • #4
    User removed account
    User removed account  
  • #5
    vinga
    Level 9  
    niestety nic nie rozwiązało problemu, laptop pojechał na gwarancję. został wymieniony dysk twardy i procesor. temat można zamknąć.