none
蓝屏 求助! RRS feed

  • 问题

  •       VISTA系统已经重新安装了,系统启动过程中还是不定时蓝屏出错。进系统后使用正常,未发现蓝屏的问题。很是让人郁闷!那位前辈可以指点一二,不胜感激!

          以下是DMP文件。

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


    Loading Dump File [C:\Windows\Minidump\Mini012809-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: F:\WINDOWS\Symbols
    Executable search path is:
    Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
    Machine Name:
    Kernel base = 0x8184e000 PsLoadedModuleList = 0x81965c70
    Debug session time: Wed Jan 28 19:58:44.658 2009 (GMT+8)
    System Uptime: 0 days 0:00:08.330
    Loading Kernel Symbols
    ...............................................................
    ........................................
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {c0000005, 0, 80599530, 8059922c}

    Probably caused by : ntkrpamp.exe ( nt!ObpGetObjectSecurity+86 )

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

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: 00000000, The address that the exception occurred at
    Arg3: 80599530, Exception Record Address
    Arg4: 8059922c, Context Record Address

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx

    FAULTING_IP:
    +0
    00000000 ??              ???

    EXCEPTION_RECORD:  80599530 -- (.exr 0xffffffff80599530)
    ExceptionAddress: 00000000
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 00000008
       Parameter[1]: 00000000
    Attempt to execute non-executable address 00000000

    CONTEXT:  8059922c -- (.cxr 0xffffffff8059922c)
    eax=8059962c ebx=80599654 ecx=85724034 edx=00000020 esi=85724000 edi=80599658
    eip=00000000 esp=805995f8 ebp=80599634 iopl=0         nv up ei ng nz ac po cy
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210293
    00000000 ??              ???
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx

    EXCEPTION_PARAMETER1:  00000008

    EXCEPTION_PARAMETER2:  00000000

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81985868
    Unable to read MiSystemVaType memory at 81965420
     00000000

    FOLLOWUP_IP:
    nt!ObpGetObjectSecurity+86
    81a96b5f 3d230000c0      cmp     eax,0C0000023h

    FAILED_INSTRUCTION_ADDRESS:
    +0
    00000000 ??              ???

    BUGCHECK_STR:  0x7E

    LAST_CONTROL_TRANSFER:  from 81a96b5f to 00000000

    STACK_TEXT: 
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    805995f4 81a96b5f 853e79c8 00000001 8059962c 0x0
    80599634 81a3986c 853e79c8 00000100 00000000 nt!ObpGetObjectSecurity+0x86
    80599664 81a397f5 853e79c8 00000000 80599688 nt!ObpCheckObjectReference+0x28
    80599760 819f5b5e 805997b0 00000240 00000000 nt!ObReferenceObjectByName+0x1b3
    805997d4 819f5524 805997f8 8195bdcc 80599850 nt!IopGetLegacyVetoListDrivers+0x13b
    80599808 819f55fd 805998f8 805998fc 00000000 nt!IoGetLegacyVetoList+0x4a
    80599834 819aa715 00599850 805998f8 80599940 nt!PopFilterCapabilities+0x26
    805998a8 819aa862 80599bec 00000000 88015c7c nt!PopVerifyPowerActionPolicy+0x49
    805998c8 819aaae7 00000000 80599c84 00000000 nt!PopVerifySystemPowerPolicy+0xcb
    80599ad0 819a0f85 00000000 000000e8 00000001 nt!PopApplyPolicy+0x72
    80599bf8 81baac0a 80847880 80849580 00000000 nt!PopResetCurrentPolicies+0xa0
    80599c90 81badd37 00000001 80849580 83654c90 nt!PoInitSystem+0x627
    80599d74 819a6af1 80599dc0 81a23a1c 80849580 nt!Phase1InitializationDiscard+0xc0a
    80599d7c 81a23a1c 80849580 a2b2e3f4 00000000 nt!Phase1Initialization+0xd
    80599dc0 8187ca3e 819a6ae4 80849580 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!ObpGetObjectSecurity+86

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  47918b12

    STACK_COMMAND:  .cxr 0xffffffff8059922c ; kb

    FAILURE_BUCKET_ID:  0x7E_NULL_IP_nt!ObpGetObjectSecurity+86

    BUCKET_ID:  0x7E_NULL_IP_nt!ObpGetObjectSecurity+86

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

     

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


    Loading Dump File [C:\Windows\Minidump\Mini012909-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: F:\WINDOWS\Symbols
    Executable search path is:
    Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
    Machine Name:
    Kernel base = 0x81846000 PsLoadedModuleList = 0x8195dc70
    Debug session time: Thu Jan 29 02:00:59.566 2009 (GMT+8)
    System Uptime: 0 days 0:00:07.254
    Loading Kernel Symbols
    ...............................................................
    ........................................
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {c0000005, 0, 80599530, 8059922c}

    Probably caused by : ntkrpamp.exe ( nt!ObpGetObjectSecurity+86 )

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

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: 00000000, The address that the exception occurred at
    Arg3: 80599530, Exception Record Address
    Arg4: 8059922c, Context Record Address

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx

    FAULTING_IP:
    +0
    00000000 ??              ???

    EXCEPTION_RECORD:  80599530 -- (.exr 0xffffffff80599530)
    ExceptionAddress: 00000000
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 00000008
       Parameter[1]: 00000000
    Attempt to execute non-executable address 00000000

    CONTEXT:  8059922c -- (.cxr 0xffffffff8059922c)
    eax=8059962c ebx=80599654 ecx=85369034 edx=00000026 esi=85369000 edi=80599658
    eip=00000000 esp=805995f8 ebp=80599634 iopl=0         nv up ei ng nz na pe cy
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210287
    00000000 ??              ???
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx

    EXCEPTION_PARAMETER1:  00000008

    EXCEPTION_PARAMETER2:  00000000

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8197d868
    Unable to read MiSystemVaType memory at 8195d420
     00000000

    FOLLOWUP_IP:
    nt!ObpGetObjectSecurity+86
    81a8eb5f 3d230000c0      cmp     eax,0C0000023h

    FAILED_INSTRUCTION_ADDRESS:
    +0
    00000000 ??              ???

    BUGCHECK_STR:  0x7E

    LAST_CONTROL_TRANSFER:  from 81a8eb5f to 00000000

    STACK_TEXT: 
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    805995f4 81a8eb5f 8521a9b0 00000001 8059962c 0x0
    80599634 81a3186c 8521a9b0 00000100 00000000 nt!ObpGetObjectSecurity+0x86
    80599664 81a317f5 8521a9b0 00000000 80599688 nt!ObpCheckObjectReference+0x28
    80599760 819edb5e 805997b0 00000240 00000000 nt!ObReferenceObjectByName+0x1b3
    805997d4 819ed524 805997f8 81953dcc 80599850 nt!IopGetLegacyVetoListDrivers+0x13b
    80599808 819ed5fd 805998f8 805998fc 00000000 nt!IoGetLegacyVetoList+0x4a
    80599834 819a2715 00599850 805998f8 80599940 nt!PopFilterCapabilities+0x26
    805998a8 819a2862 80599bec 00000000 88015c7c nt!PopVerifyPowerActionPolicy+0x49
    805998c8 819a2ae7 00000000 80599c84 00000000 nt!PopVerifySystemPowerPolicy+0xcb
    80599ad0 81998f85 00000000 000000e8 00000001 nt!PopApplyPolicy+0x72
    80599bf8 81ba2c0a 80847880 80849580 00000000 nt!PopResetCurrentPolicies+0xa0
    80599c90 81ba5d37 00000001 80849580 83654c90 nt!PoInitSystem+0x627
    80599d74 8199eaf1 80599dc0 81a1ba1c 80849580 nt!Phase1InitializationDiscard+0xc0a
    80599d7c 81a1ba1c 80849580 ae9786f4 00000000 nt!Phase1Initialization+0xd
    80599dc0 81874a3e 8199eae4 80849580 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!ObpGetObjectSecurity+86

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  47918b12

    STACK_COMMAND:  .cxr 0xffffffff8059922c ; kb

    FAILURE_BUCKET_ID:  0x7E_NULL_IP_nt!ObpGetObjectSecurity+86

    BUCKET_ID:  0x7E_NULL_IP_nt!ObpGetObjectSecurity+86

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

     

          看似是硬件的问题,但该机器使用XP SP3时都正常,而且进入VISTA系统后各项测试没有发现任何问题,蓝屏问题只是不定时出现在系统启动过程中。

          硬件配置:E2160--万紫千红1G×2--ST3500320AS--GeForce 7800 GT--G31T-LM。

    2009年1月28日 18:28

答案

  •  是ntkrpamp.exe这个文件导致的蓝屏,这是windows的保护性进程,在计算机反复启动失败时出现,在正常情况下不会出现该进程,如果在正常情况下出现了该进程,也有可能是W32.Bolzano病毒。

    建议对计算机系统修复安装,并在安全模式下全盘查杀病毒。
    夜鹰
    2009年2月5日 3:06

全部回复

  • 你有没有破解过TCPIP.SYS文件,恢复默认文件。如果没有备份的话,运行SFC /SCANNOW来修复出错的系统文件。

    2009年1月29日 10:16
    版主
  • 您好

    我觉得和硬件。。或者是可能是系统破解有关,因为我的电脑原来也有过这样的问题。。

    后来用公司的正版就没问题了。。


    tomato.net
    2009年1月29日 17:41
  •  是ntkrpamp.exe这个文件导致的蓝屏,这是windows的保护性进程,在计算机反复启动失败时出现,在正常情况下不会出现该进程,如果在正常情况下出现了该进程,也有可能是W32.Bolzano病毒。

    建议对计算机系统修复安装,并在安全模式下全盘查杀病毒。
    夜鹰
    2009年2月5日 3:06
  • 对上面的‘答案’心存怀疑。

    我使用正版windows 7 也遇到了此问题。未破解任何windows文件。之前同一pc安装windows 2008 sp1 X64, 非常稳定。(现在的win7 是32位)。

    做的最蠢的事情莫过于安装了acronis disk director suite 10,出错后去acronis网站才看到人家明确指出此版本不支持win7。(蓝屏原因时snapman.sys).卸载之后启动失败,用修复盘启动后恢复正常,稳定运行了一天出现了此蓝屏。

    希望这是一次偶然的蓝屏。看看以后怎么样。


    altair
    • 已建议为答案 gavin.zhao 2012年4月1日 15:57
    2010年7月10日 11:34