malo pamieci wirtualnej i takie rozne i logi ... Dodaj do ulubionych

  • drzewko
  • od najstarszego
  • od najnowszego
  • drzewko odwrotne
  • Czesc, nie bede oryginalna - licze na pomoc:)
    Komputer zwolnił, krzyczy, że ma za mało pamięci wirtualnej, choc malo co na
    nim robie. W menedżerze zada podwajaj sie procesy, np svchost mam 3 razy:(.
    Nod nie wykrywa nic, mks tez, adware juz uzylam teraz czas na logi.
    Moze ktos pomoze, prosze...
    Logfile of HijackThis v1.99.1
    Scan saved at 01:09:40, on 2006-12-30
    Platform: Windows 2000 SP4 (WinNT 5.00.2195)
    MSIE: Internet Explorer v6.00 SP1 (6.00.2800.1106)

    Running processes:
    C:\WINNT\System32\smss.exe
    C:\WINNT\system32\winlogon.exe
    C:\WINNT\system32\services.exe
    C:\WINNT\system32\lsass.exe
    C:\WINNT\system32\svchost.exe
    C:\WINNT\system32\spoolsv.exe
    C:\Program Files\Grisoft\AVG Anti-Spyware 7.5\guard.exe
    C:\WINNT\System32\svchost.exe
    C:\Program Files\Eset\nod32krn.exe
    C:\WINNT\system32\nvsvc32.exe
    C:\WINNT\system32\regsvc.exe
    C:\WINNT\system32\MSTask.exe
    C:\WINNT\system32\stisvc.exe
    C:\WINNT\System32\WBEM\WinMgmt.exe
    C:\WINNT\system32\svchost.exe
    C:\WINNT\Explorer.EXE
    C:\WINNT\Mixer.exe
    C:\Program Files\Java\jre1.5.0_09\bin\jusched.exe
    C:\WINNT\system32\spool\drivers\w32x86\3\hpztsb05.exe
    C:\Program Files\Eset\nod32kui.exe
    C:\Program Files\Gadu-Gadu\gg.exe
    C:\Program Files\Mozilla Firefox\firefox.exe
    C:\WINNT\system32\wuauclt.exe
    C:\DOCUME~1\ADMINI~1\USTAWI~1\Temp\HijackThis.exe

    R0 - HKCU\Software\Microsoft\Internet Explorer\Toolbar,LinksFolderName = Łącza
    O2 - BHO: AcroIEHlprObj Class - {06849E9F-C8D7-4D59-B87D-784B7D6BE0B3} -
    C:\Program Files\Adobe\Acrobat 7.0\ActiveX\AcroIEHelper.dll
    O2 - BHO: SSVHelper Class - {761497BB-D6F0-462C-B6EB-D4DAF1D92D43} -
    C:\Program Files\Java\jre1.5.0_09\bin\ssv.dll
    O3 - Toolbar: @msdxmLC.dll,-1@1033,&Radio -
    {8E718888-423F-11D2-876E-00A0C9082467} - C:\WINNT\system32\msdxm.ocx
    O4 - HKLM\..\Run: [Synchronization Manager] mobsync.exe /logon
    O4 - HKLM\..\Run: [C-Media Mixer] Mixer.exe /startup
    O4 - HKLM\..\Run: [NvCplDaemon] RUNDLL32.EXE C:\WINNT\system32\NvCpl.dll,NvStartup
    O4 - HKLM\..\Run: [nwiz] nwiz.exe /install
    O4 - HKLM\..\Run: [NvMediaCenter] RUNDLL32.EXE
    C:\WINNT\system32\NvMcTray.dll,NvTaskbarInit
    O4 - HKLM\..\Run: [SunJavaUpdateSched] "C:\Program
    Files\Java\jre1.5.0_09\bin\jusched.exe"
    O4 - HKLM\..\Run: [HPDJ Taskbar Utility]
    C:\WINNT\system32\spool\drivers\w32x86\3\hpztsb05.exe
    O4 - HKLM\..\Run: [Resume copy] copyfstq.exe /startup
    O4 - HKLM\..\Run: [nod32kui] "C:\Program Files\Eset\nod32kui.exe" /WAITSERVICE
    O4 - Global Startup: Microsoft Office.lnk = C:\Program Files\Microsoft
    Office\Office\OSA9.EXE
    O4 - Global Startup: Adobe Gamma Loader.exe.lnk = C:\Program Files\Common
    Files\Adobe\Calibration\Adobe Gamma Loader.exe
    O4 - Global Startup: Adobe Reader Speed Launch.lnk = C:\Program
    Files\Adobe\Acrobat 7.0\Reader\reader_sl.exe
    O9 - Extra button: (no name) - {08B0E5C0-4FCB-11CF-AAA5-00401C608501} -
    C:\Program Files\Java\jre1.5.0_09\bin\ssv.dll
    O9 - Extra 'Tools' menuitem: Sun Java Console -
    {08B0E5C0-4FCB-11CF-AAA5-00401C608501} - C:\Program
    Files\Java\jre1.5.0_09\bin\ssv.dll
    O16 - DPF: {17492023-C23A-453E-A040-C7C580BBF700} (Windows Genuine Advantage
    Validation Tool) - go.microsoft.com/fwlink/?linkid=39204
    O16 - DPF: {6414512B-B978-451D-A0D8-FCFDF33E833C} (WUWebControl Class) -
    update.microsoft.com/windowsupdate/v6/V5Controls/en/x86/client/wuweb_site.cab?1165089438610
    O16 - DPF: {68282C51-9459-467B-95BF-3C0E89627E55} (MainControl Class) -
    www.mks.com.pl/skaner/SkanerOnline.cab
    O17 -
    HKLM\System\CCS\Services\Tcpip\..\{2F75E075-C782-4EB6-AD0A-99923B62E8ED}:
    NameServer = 212.191.132.126,194.204.152.34
    O17 -
    HKLM\System\CS1\Services\Tcpip\..\{2F75E075-C782-4EB6-AD0A-99923B62E8ED}:
    NameServer = 212.191.132.126,194.204.152.34
    O17 -
    HKLM\System\CS2\Services\Tcpip\..\{2F75E075-C782-4EB6-AD0A-99923B62E8ED}:
    NameServer = 212.191.132.126,194.204.152.34
    O23 - Service: AVG Anti-Spyware Guard - Anti-Malware Development a.s. -
    C:\Program Files\Grisoft\AVG Anti-Spyware 7.5\guard.exe
    O23 - Service: Usługa administracyjna Menedżera dysków logicznych (dmadmin) -
    VERITAS Software Corp. - C:\WINNT\System32\dmadmin.exe
    O23 - Service: NOD32 Kernel Service (NOD32krn) - Eset - C:\Program
    Files\Eset\nod32krn.exe
    O23 - Service: NVIDIA Display Driver Service (NVSvc) - NVIDIA Corporation -
    C:\WINNT\system32\nvsvc32.exe

    • Gość: Kolobos IP: *.crowley.pl 30.12.06, 02:41
      > komputer zwolnił, krzyczy, że ma za mało pamięci wirtualnej

      Ile masz wolnego miejsca na dysku C?
      Ktory program w menadzerze zadan zajmuje najwiecej pamieci?

      > W menedżerze zada podwajaj sie procesy, np svchost mam 3 razy:(.

      To normalne.
      • Gość: iza IP: *.internetdsl.tpnet.pl 30.12.06, 10:06
        Na dysku C mam 900 MB wolnego, firefox - 41.920, potem gg - 16, potem exlorer i
        guard.
        Mam komputer sprzed 6 lat - z parametrami raczej slabymi;) - np ram 128. Ale
        komputer wczesniej sie tak nie zachowywal. Czasami tez w najmniej oczekiwanym
        momencie zrzuca mi pamiec fizyczna - ten niebieski ekran sie pojawia i
        restartuje sam.
        • Gość: Kolobos IP: *.crowley.pl 30.12.06, 12:09
          Na ile masz ustawiony rozmiar pamieci wirtualnej? (panel sterowania -> system)
          Skoro masz zrzut pamieci to zrob z nim to:
          forum.purepc.pl/index.php?showtopic=104416
          Wynik wklej na forum.
          • Gość: iza IP: *.internetdsl.tpnet.pl 30.12.06, 13:16
            Rozmiar początkowy - 192, rozmiar maksymalny - 384

            Oto wyniki analizy poszczegolnych plikow minidump - daje narazie 3 zanalizowane
            pliki, wiecej chyba sie nie zmiesci tutaj:

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


            Loading Dump File [C:\WINNT\Minidump\Mini120306-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 ntoskrnl.exe, Win32 error 2
            *** WARNING: Unable to verify timestamp for ntoskrnl.exe
            *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
            Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
            Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
            Debug session time: Sun Dec 3 00:10:34.522 2006 (GMT+1)
            System Uptime: not available
            *********************************************************************
            * 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+ *
            *********************************************************************
            *******************************************************************************
            * *
            * Bugcheck Analysis *
            * *
            *******************************************************************************
            Bugcheck code 0000001A
            Arguments 00041284 79604000 00000000 c0501000

            ChildEBP RetAddr Args to Child
            WARNING: Stack unwind information not available. Following frames may be wrong.
            fc5d5a04 00000000 00041284 79604000 00000000 nt+0x4c666

            WaitForEvent failed


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


            Loading Dump File [C:\WINNT\Minidump\Mini120406-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 ntoskrnl.exe, Win32 error 2
            *** WARNING: Unable to verify timestamp for ntoskrnl.exe
            *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
            Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
            Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
            Debug session time: Mon Dec 4 23:02:37.660 2006 (GMT+1)
            System Uptime: not available
            *********************************************************************
            * 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+ *
            *********************************************************************
            *******************************************************************************
            * *
            * Bugcheck Analysis *
            * *
            *******************************************************************************
            Bugcheck code 0000001A
            Arguments 00041284 79604000 00000000 c0501000

            ChildEBP RetAddr Args to Child
            WARNING: Stack unwind information not available. Following frames may be wrong.
            f93a9a04 00000000 00041284 79604000 00000000 nt+0x4c666

            WaitForEvent failed



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


            Loading Dump File [C:\WINNT\Minidump\Mini120906-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 ntoskrnl.exe, Win32 error 2
            *** WARNING: Unable to verify timestamp for ntoskrnl.exe
            *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
            Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
            Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
            Debug session time: Sat Dec 9 10:36:01.567 2006 (GMT+1)
            System Uptime: not available
            *********************************************************************
            * Symbols can not be loaded because symbol path is not initialized. *
            * *
            * The
            • Gość: iza IP: *.internetdsl.tpnet.pl 30.12.06, 13:24
              Microsoft (R) Windows Debugger Version 6.6.0007.5
              Copyright (c) Microsoft Corporation. All rights reserved.


              Loading Dump File [C:\WINNT\Minidump\Mini121006-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 ntoskrnl.exe, Win32 error 2
              *** WARNING: Unable to verify timestamp for ntoskrnl.exe
              *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
              Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
              Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
              Debug session time: Sun Dec 10 20:03:17.596 2006 (GMT+1)
              System Uptime: not available
              *********************************************************************
              * 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+ *
              *********************************************************************
              *******************************************************************************
              * *
              * Bugcheck Analysis *
              * *
              *******************************************************************************
              Bugcheck code 0000000A
              Arguments ff99f610 00000002 00000000 8044636f

              ChildEBP RetAddr Args to Child
              WARNING: Stack unwind information not available. Following frames may be wrong.
              f9c918f0 00000000 ff99f610 00000002 00000000 nt+0x67df7

              WaitForEvent failed


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


              Loading Dump File [C:\WINNT\Minidump\Mini121206-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 ntoskrnl.exe, Win32 error 2
              *** WARNING: Unable to verify timestamp for ntoskrnl.exe
              *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
              Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
              Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
              Debug session time: Tue Dec 12 23:16:05.201 2006 (GMT+1)
              System Uptime: not available
              *********************************************************************
              * 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+ *
              *********************************************************************
              *******************************************************************************
              * *
              * Bugcheck Analysis *
              * *
              *******************************************************************************
              Bugcheck code 0000004E
              Arguments 00000099 00003bde 00000003 00000000

              ChildEBP RetAddr Args to Child
              WARNING: Stack unwind information not available. Following frames may be wrong.
              fa0e5b34 00000000 00000099 00003bde 00000003 nt+0x4c2f8

              WaitForEvent failed


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


              Loading Dump File [C:\WINNT\Minidump\Mini121806-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 ntoskrnl.exe, Win32 error 2
              *** WARNING: Unable to verify timestamp for ntoskrnl.exe
              *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
              Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
              Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
              Debug session time: Mon Dec 18 15:43:04.793 2006 (GMT+1)
              System Uptime: not available
              *********************************************************************
              * 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> argumen
              • Gość: iza IP: *.internetdsl.tpnet.pl 30.12.06, 13:35

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


                Loading Dump File [C:\WINNT\Minidump\Mini122206-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 ntoskrnl.exe, Win32 error 2
                *** WARNING: Unable to verify timestamp for ntoskrnl.exe
                *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
                Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
                Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
                Debug session time: Fri Dec 22 18:50:57.079 2006 (GMT+1)
                System Uptime: not available
                *********************************************************************
                * 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+ *
                *********************************************************************
                *******************************************************************************
                * *
                * Bugcheck Analysis *
                * *
                *******************************************************************************
                Bugcheck code 0000000A
                Arguments 00000000 00000002 00000001 80068415

                ChildEBP RetAddr Args to Child
                WARNING: Stack unwind information not available. Following frames may be wrong.
                80471884 00000000 00000000 00000002 00000001 nt+0x67df7

                WaitForEvent failed


                icrosoft (R) Windows Debugger Version 6.6.0007.5
                Copyright (c) Microsoft Corporation. All rights reserved.


                Loading Dump File [C:\WINNT\Minidump\Mini122406-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 ntoskrnl.exe, Win32 error 2
                *** WARNING: Unable to verify timestamp for ntoskrnl.exe
                *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
                Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
                Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
                Debug session time: Sun Dec 24 21:56:13.491 2006 (GMT+1)
                System Uptime: not available
                *********************************************************************
                * 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+ *
                *********************************************************************
                *******************************************************************************
                * *
                * Bugcheck Analysis *
                * *
                *******************************************************************************
                Bugcheck code 0000000A
                Arguments 00000000 00000002 00000001 80068415

                ChildEBP RetAddr Args to Child
                WARNING: Stack unwind information not available. Following frames may be wrong.
                80471884 00000000 00000000 00000002 00000001 nt+0x67df7

                WaitForEvent failed




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


                Loading Dump File [C:\WINNT\Minidump\Mini122906-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 ntoskrnl.exe, Win32 error 2
                *** WARNING: Unable to verify timestamp for ntoskrnl.exe
                *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
                Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
                Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
                Debug session time: Fri Dec 29 22:50:49.528 2006 (GMT+1)
                System Uptime: not available
                *********************************************************************
                * 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> ar
                • Gość: Kolobos IP: *.crowley.pl 30.12.06, 14:08
                  Ustaw minimalna wartosc na 256, a max na 512MB. Pomysl tez o kupnie ramu np. 256MB (koszt okolo 60zł na allegro).

                  Co do bledu to powodow wystepowania moze byc wiele.
                  Kiedy dokladnie blad zaczal wystepowac i co wtedy bylo zmieniane w komputerze (czesci lub sterowniki) ?

                  Sprawdz tez ram -> www.memtest.org - sciagnij obraz dyskietki lub plyty, po nagraniu uruchom z niej komputer i testuj 2-3 godziny, jezeli nie wykryje bledow to ram jest ok.
                  • Gość: iza IP: *.internetdsl.tpnet.pl 30.12.06, 14:12
                    śliczne dziękuję za pomoc.

                    Nie zmieniałam części ani sterowników wcale, więc nie wiem, co może być źródłem
                    "niebieskiej smierci". Ram zaraz sprawdzę i zmieniam ustawienia. Ramu nie kupuję
                    narazie - w planach mam zakup nowego komputera, jakoś jeszcze te kilkanaście
                    miesięcy pocierpię z tymi 128.

                    Dziękuję i pozdrawiam.

Wysyłaj powiadomienia o nowych wpisach na forum na e-mail:

Aby uprościć zarządzanie powiadomieniami zaloguj się lub zarejestruj się.

lub anuluj

Zaloguj się

Nie pamiętasz hasła lub loginu ?

Nie masz jeszcze konta? Zarejestruj się

Zadaj pytanie na Forum

Za darmo

Na każdy temat

Tysiącom użytkowników

Zapytaj

Bestsellery

Agora S.A. - wydawca portalu Gazeta.pl nie ponosi odpowiedzialności za treść wypowiedzi zamieszczanych przez użytkowników Forum. Osoby zamieszczające wypowiedzi naruszające prawo lub prawem chronione dobra osób trzecich mogą ponieść z tego tytułu odpowiedzialność karną lub cywilną. Regulamin.