none
win7蓝屏,求助 RRS feed

  • 问题

  • 蓝屏会出现在看视频,玩游戏中

    我看这出现 svchost.exe   但不知道具体是哪个程序问题

    请大家帮助,谢谢


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


    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Complete Dump File: Full address space is available

    Symbol search path is: SRV*c:\sytemp*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
    Machine Name:
    Kernel base = 0x8483d000 PsLoadedModuleList = 0x8497d230
    Debug session time: Wed Jun 22 16:48:18.764 2011 (UTC + 8:00)
    System Uptime: 0 days 0:30:47.387
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................
    Loading User Symbols
    ....................................................
    Loading unloaded module list
    ...................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {85bfe940, 2, 1, 848b4d8b}

    Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+bf )

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

    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 85bfe940, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, bitfield :
     bit 0 : value 0 = read operation, 1 = write operation
     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 848b4d8b, address which referenced memory

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


    WRITE_ADDRESS:  85bfe940

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!MiRemoveAnyPage+bf
    848b4d8b f00fba2800      lock bts dword ptr [eax],0

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  svchost.exe

    TRAP_FRAME:  b796bc4c -- (.trap 0xffffffffb796bc4c)
    ErrCode = 00000002
    eax=00000000 ebx=00000000 ecx=00000800 edx=00000000 esi=00008000 edi=b6453000
    eip=8486e505 esp=b796bcc0 ebp=b796bcf0 iopl=0         nv up ei pl nz ac pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010216
    nt!memset+0x45:
    8486e505 f3ab            rep stos dword ptr es:[edi]
    Resetting default scope

    LOCK_ADDRESS:  84999f20 -- (!locks 84999f20)

    Resource @ nt!PiEngineLock (0x84999f20)    Available
        Contention Count = 4
    1 total locks

    PNP_TRIAGE:
     Lock address  : 0x84999f20
     Thread Count  : 0
     Thread address: 0x00000000
     Thread wait   : 0x0

    LAST_CONTROL_TRANSFER:  from 848b4d8b to 84875c9b

    STACK_TEXT: 
    b796ba34 848b4d8b badb0d00 000000ff 84a4ee98 nt!KiTrap0E+0x2cf
    b796bae8 848aec35 00000023 00000000 8499d240 nt!MiRemoveAnyPage+0xbf
    b796bb10 848a9522 00000000 00000000 c02d914c nt!MiGetPage+0x287
    b796bb48 8489f0cd 00000001 b6453000 b796bc4c nt!MiResolveDemandZeroFault+0xc9
    b796bbbc 8489cf34 b6453000 00000000 00000000 nt!MiDispatchFault+0x580
    b796bc34 84875aa8 00000001 b6453000 00000000 nt!MmAccessFault+0x128f
    b796bc34 8486e505 00000001 b6453000 00000000 nt!KiTrap0E+0xdc
    b796bcc0 84a10e59 b644d000 00000000 00008000 nt!memset+0x45
    b796bcf0 84a118b5 00000009 b644d000 00000018 nt!PiControlGetInterfaceDeviceList+0x9f
    b796bd20 848728ba 00000009 0148f450 00000018 nt!NtPlugPlayControl+0xbe
    b796bd20 775f70b4 00000009 0148f450 00000018 nt!KiFastCallEntry+0x12a
    0148f428 775f5e74 74ce3b7e 00000009 0148f450 ntdll!KiFastSystemCallRet
    0148f42c 74ce3b7e 00000009 0148f450 00000018 ntdll!NtPlugPlayControl+0xc
    0148f488 74ce3d21 002fbe38 00000000 0119a7c8 umpnpmgr!PnpGetInterfaceDeviceList+0xb4
    0148f4d8 762004e8 00000000 002fbe38 00000000 umpnpmgr!PNP_GetInterfaceDeviceList+0x71
    0148f504 76265311 74ce3cc1 0148f6f0 00000006 RPCRT4!Invoke+0x2a
    0148f90c 7626431d 00000000 00000000 003b21c0 RPCRT4!NdrStubCall2+0x2d6
    0148f928 7620063c 003b21c0 e0d63c02 003167e0 RPCRT4!NdrServerCall2+0x19
    0148f964 762007ca 74ce29c1 003b21c0 0148fa14 RPCRT4!DispatchToStubInCNoAvrf+0x4a
    0148f9bc 762006b6 003167e0 00000000 00000000 RPCRT4!RPC_INTERFACE::DispatchToStubWorker+0x16c
    0148f9e4 761f76db 00000000 00000000 0148fa14 RPCRT4!RPC_INTERFACE::DispatchToStub+0x8b
    0148fa30 76200ac6 003b2108 0148fa4c 003b4460 RPCRT4!LRPC_SCALL::DispatchRequest+0x257
    0148fa50 76200a85 003b2108 002fbdf8 003b4460 RPCRT4!LRPC_SCALL::QueueOrDispatchCall+0xbd
    0148fa6c 76200921 00000000 002fbde0 003167e0 RPCRT4!LRPC_SCALL::HandleRequest+0x34f
    0148faa0 76200895 00000000 002fbde0 002ee078 RPCRT4!LRPC_SASSOCIATION::HandleRequest+0x144
    0148fad8 761ffe85 00314128 00000000 002ee078 RPCRT4!LRPC_ADDRESS::HandleRequest+0xbd
    0148fb54 761ffd1d 00000000 0148fb70 761ffc6a RPCRT4!LRPC_ADDRESS::ProcessIO+0x50a
    0148fb60 761ffc6a 003141c4 00000000 0148fb98 RPCRT4!LrpcServerIoHandler+0x16
    0148fb70 775e1d55 0148fbdc 003141c4 00316758 RPCRT4!LrpcIoComplete+0x16
    0148fb98 775e15ac 0148fbdc 00000000 00000000 ntdll!TppAlpcpExecuteCallback+0x1c5
    0148fd00 76013c45 002e92e8 0148fd4c 776137f5 ntdll!TppWorkerThread+0x5a4
    0148fd0c 776137f5 002e92e8 7620d44c 00000000 kernel32!BaseThreadInitThunk+0xe
    0148fd4c 776137c8 775e03e7 002e92e8 00000000 ntdll!__RtlUserThreadStart+0x70
    0148fd64 00000000 775e03e7 002e92e8 00000000 ntdll!_RtlUserThreadStart+0x1b


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!MiRemoveAnyPage+bf
    848b4d8b f00fba2800      lock bts dword ptr [eax],0

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!MiRemoveAnyPage+bf

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fd76c

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  0xA_nt!MiRemoveAnyPage+bf

    BUCKET_ID:  0xA_nt!MiRemoveAnyPage+bf

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

     

    2011年6月22日 10:23

答案

  • 你可以用Process Explorer 对当前svchost.ese 进行查看。这是一个驱动错误,它准备调用一个pageable 地址空间。

    我同样建议你联系微软客户支持服务(CSS)寻求帮助,这样的问题是可以有效的解决。你可以通过以下网站,获取微软的客服信息:
    http://support.microsoft.com/contactus

    希望可以有助于你解决此问题。


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    2011年6月25日 8:25
    版主

全部回复

  • 太复杂了 建议 改一下 硬盘 接口 可以试试 很多时候 是程序窜改了 硬盘的接入方式
    lijiang
    2011年6月23日 17:03
  • 你可以用Process Explorer 对当前svchost.ese 进行查看。这是一个驱动错误,它准备调用一个pageable 地址空间。

    我同样建议你联系微软客户支持服务(CSS)寻求帮助,这样的问题是可以有效的解决。你可以通过以下网站,获取微软的客服信息:
    http://support.microsoft.com/contactus

    希望可以有助于你解决此问题。


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    2011年6月25日 8:25
    版主