Announcement

Announcement Module
Collapse
No announcement yet.

tolong dong ini error gara2 apa ya...

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • tolong dong ini error gara2 apa ya...

    guys... tolong dong... artiin error dari debugging dibawah... kalo browsing... ntkrnlpa.exe sepertinya ada hubungannya ama modul memori... tapi yg ( nt+1eacd3 ) ngak nemu... notebooknya toshiba seri m300... t8100... 3G... os... vista business basic...


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


    Loading Dump File [C:\Users\-\Documents\backup registry\Mini081209-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 = 0x8223a000 PsLoadedModuleList = 0x82351c70
    Debug session time: Wed Aug 12 11:35:52.998 2009 (GMT+7)
    System Uptime: 0 days 3:01:32.737
    ************************************************** *******************
    * 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 1000007E, {c0000005, 82424cd3, 8b563c34, 8b563930}

    ***** 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 ***
    *** ***
    ************************************************** ***********************
    ************************************************** *******************
    * 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 : ntkrnlpa.exe ( nt+1eacd3 )

    Followup: MachineOwner

  • #2
    Re: tolong dong ini error gara2 apa ya...

    itu symbols-nya koq invalid. coba download dulu symbols-nya, download yang sesuai dengan service pack level-nya.

    Comment


    • #3
      Re: tolong dong ini error gara2 apa ya...

      betul kata bro tri_zet symbolnya invalid tuch... jadi kudu download symbolnya dulu...

      Comment


      • #4
        Re: tolong dong ini error gara2 apa ya...

        symbol apa ya bro... nyari nya dimana ya... thanks a lot before...

        Comment


        • #5
          Re: tolong dong ini error gara2 apa ya...

          symbols debugger-nya.
          download disini
          download yang sama serice pack level-nya. (pakai yang SP1 RTM x86)

          btw, itu sempat BSOD ya? kalau BSOD-nya baru sekali sih bisa di cuekin dulu, tapi kalau sudah berulang-ulang baru di troubleshoot.
          kemungkinan-nya ya bisa memory/hardware atau vistanya sendiri.
          Last edited by tri_zet; 18-08-2009, 15:54.

          Comment


          • #6
            Re: tolong dong ini error gara2 apa ya...

            thanks tri_zet... gue lagi dwnld nih... udh sering juga bsod nya... tapi jarang2 sih... kadang sebulan ngak se kali... kadang 2x...

            Comment


            • #7
              Re: tolong dong ini error gara2 apa ya...

              bro tri_zet atau bro yusni... gue udh 2 hari cobain debugging... tapi ngak bisa... selalu symbols invalid... ini gue udh attached dump filenya... siapa tau bisa tolongin... thanks a lot ya...

              Comment


              • #8
                Re: tolong dong ini error gara2 apa ya...

                waduh sorry bro, ane ga punya symbols vista, belum download, jadi belum bisa bantu lihat dump filenya. (punyanya xp sp2 dan sp3)

                bro running debuggernya dari f8 ya?
                coba gini nih:
                -install (extract) dulu symbols-nya, file pathnya bisa di mana saja tapi defaultnya di c:\windows.
                -download debugger versi terbaru lalu install dan run jangan dari f8. (link download sama dengan symbols)
                -run debugger, lalu pilih "symbols file path" dulu
                -lalu open crash dump, browse ke lokasi dump filenya.

                Comment


                • #9
                  Re: tolong dong ini error gara2 apa ya...

                  bro tri_zet... ini dia akhirnya bisa...

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


                  Loading Dump File [C:\Users\nita\Documents\backup registry\Mini081209-01.dmp]
                  Mini Kernel Dump File: Only registers and stack trace are available

                  Symbol search path is: SRV*D:\websymbols*http://msdl.microsoft.com/download/symbols
                  Executable search path is:
                  Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
                  Product: WinNt, suite: TerminalServer SingleUserTS
                  Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
                  Machine Name:
                  Kernel base = 0x8223a000 PsLoadedModuleList = 0x82351c70
                  Debug session time: Wed Aug 12 11:35:52.998 2009 (GMT+7)
                  System Uptime: 0 days 3:01:32.737
                  Loading Kernel Symbols
                  .................................................. .............
                  .................................................. ..............
                  ..........................................
                  Loading User Symbols
                  Loading unloaded module list
                  ............
                  ************************************************** *****************************
                  * *
                  * Bugcheck Analysis *
                  * *
                  ************************************************** *****************************

                  Use !analyze -v to get detailed debugging information.

                  BugCheck 1000007E, {c0000005, 82424cd3, 8b563c34, 8b563930}

                  Probably caused by : ntkrpamp.exe ( nt!CmpCleanUpKcbValueCache+23 )

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

                  ************************************************** *****************************
                  * *
                  * Bugcheck Analysis *
                  * *
                  ************************************************** *****************************

                  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
                  This is a very common bugcheck. Usually the exception address pinpoints
                  the driver/function that caused the problem. Always note this address
                  as well as the link date of the driver/image that contains this address.
                  Some common problems are exception code 0x80000003. This means a hard
                  coded breakpoint or assertion was hit, but this system was booted
                  /NODEBUG. This is not supposed to happen as developers should never have
                  hardcoded breakpoints in retail code, but ...
                  If this happens, make sure a debugger gets connected, and the
                  system is booted /DEBUG. This will let us see why this breakpoint is
                  happening.
                  Arguments:
                  Arg1: c0000005, The exception code that was not handled
                  Arg2: 82424cd3, The address that the exception occurred at
                  Arg3: 8b563c34, Exception Record Address
                  Arg4: 8b563930, Context Record Address

                  Debugging Details:
                  ------------------


                  EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

                  FAULTING_IP:
                  nt!CmpCleanUpKcbValueCache+23
                  82424cd3 8b04bb mov eax,dword ptr [ebx+edi*4]

                  EXCEPTION_RECORD: 8b563c34 -- (.exr 0xffffffff8b563c34)
                  ExceptionAddress: 82424cd3 (nt!CmpCleanUpKcbValueCache+0x00000023)
                  ExceptionCode: c0000005 (Access violation)
                  ExceptionFlags: 00000000
                  NumberParameters: 2
                  Parameter[0]: 00000000
                  Parameter[1]: 50ed26c6
                  Attempt to read from address 50ed26c6

                  CONTEXT: 8b563930 -- (.cxr 0xffffffff8b563930)
                  eax=50ed26c6 ebx=50ed26c6 ecx=84980828 edx=00000000 esi=b1a57b28 edi=00000000
                  eip=82424cd3 esp=8b563cfc ebp=8b563d14 iopl=0 nv up ei pl nz na pe nc
                  cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
                  nt!CmpCleanUpKcbValueCache+0x23:
                  82424cd3 8b04bb mov eax,dword ptr [ebx+edi*4] ds:0023:50ed26c6=????????
                  Resetting default scope

                  CUSTOMER_CRASH_COUNT: 1

                  DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

                  PROCESS_NAME: System

                  CURRENT_IRQL: 0

                  ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

                  EXCEPTION_PARAMETER1: 00000000

                  EXCEPTION_PARAMETER2: 50ed26c6

                  READ_ADDRESS: GetPointerFromAddress: unable to read from 82371868
                  Unable to read MiSystemVaType memory at 82351420
                  50ed26c6

                  FOLLOWUP_IP:
                  nt!CmpCleanUpKcbValueCache+23
                  82424cd3 8b04bb mov eax,dword ptr [ebx+edi*4]

                  BUGCHECK_STR: 0x7E

                  LAST_CONTROL_TRANSFER: from 82425053 to 82424cd3

                  STACK_TEXT:


                  SYMBOL_STACK_INDEX: 0

                  SYMBOL_NAME: nt!CmpCleanUpKcbValueCache+23

                  FOLLOWUP_NAME: MachineOwner

                  MODULE_NAME: nt

                  IMAGE_NAME: ntkrpamp.exe

                  DEBUG_FLR_IMAGE_TIMESTAMP: 49ac8fb4

                  STACK_COMMAND: .cxr 0xffffffff8b563930 ; kb

                  FAILURE_BUCKET_ID: 0x7E_nt!CmpCleanUpKcbValueCache+23

                  BUCKET_ID: 0x7E_nt!CmpCleanUpKcbValueCache+23

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

                  tolongin dong bro...thanks a lot before...

                  Comment


                  • #10
                    Re: tolong dong ini error gara2 apa ya...

                    BugCheck 1000007E
                    coba buka dump file yang lain apa hasilnya sama?
                    kalau semua dump file hasilnya sama coba lihat DISINI dan DISINI.
                    kalau isi dump filenya lain2 bisa cari stop codenya DISINI

                    kalau tidak ada yang cocok mungkin bisa dibantu dengan melihat event viewer, untuk melihat aplikasi yang error/running dengan jam yang sama atau beberapa saat sebelum BSOD

                    Comment

                    Working...
                    X