none
I3 2100机器运行一段时间自动关机 求故障分析 RRS feed

  • 问题

  • 201105月配置的电脑,

    酷睿i3 2100 原包原盒  微星 H61MU-E35 B3步进 威刚 2G DDR3 1333 万紫千红版 WD5000AAKX SATA3.0蓝盘

    机器外接了4路摄像头+APC&UPS一台。电脑日常应用作为监控电脑使用  ,最近每天运行一段时间自动关机,然后重启又正常 。截止到目前发现此类故障记录18次。上传了062411-10951-01.dmp 求分析  

    http://u.115.com/file/clgxzf2m

    2011年7月11日 2:44

答案

  • 这个问题经过分析是 Encode.exe 程序在调用 dxgmms1.sys 文件时发生的,这可能和您使用的监控软件有关。

    可以尝试安装监控程序的最新版本或更新摄像头或相关驱动程序。

     

    以下是分析出来的详细信息:

    Debugging Details:

    ------------------

     

     

    READ_ADDRESS: GetPointerFromAddress: unable to read from 84378718

    Unable to read MiSystemVaType memory at 843581a0

     fffffffc 

     

    CURRENT_IRQL:  2

     

    FAULTING_IP: 

    nt!KiProcessThreadWaitList+1c

    8428b638 ff7670          push    dword ptr [esi+70h]

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

     

    BUGCHECK_STR:  0xA

     

    PROCESS_NAME:  Encode.exe

     

    TRAP_FRAME:  b040f55c -- (.trap 0xffffffffb040f55c)

    ErrCode = 00000000

    eax=8433cf14 ebx=00000001 ecx=84339d20 edx=00000001 esi=ffffff8c edi=00000000

    eip=8428b638 esp=b040f5d0 ebp=b040f5e0 iopl=0         nv up ei pl zr na pe nc

    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246

    nt!KiProcessThreadWaitList+0x1c:

    8428b638 ff7670          push    dword ptr [esi+70h]  ds:0023:fffffffc=????????

    Resetting default scope

     

    LAST_CONTROL_TRANSFER:  from 8428b638 to 8424f5cb

     

    STACK_TEXT:  

    b040f55c 8428b638 badb0d00 00000001 000000a2 nt!KiTrap0E+0x2cf

    b040f5e0 842855b1 00000000 00000001 00000000 nt!KiProcessThreadWaitList+0x1c

    b040f61c 84285577 84339d20 00000000 00000001 nt!KiExitDispatcher+0x2a

    b040f650 923a13ac 87af6aa8 00000000 00000000 nt!KeSetEvent+0xb2

    b040f67c 9239c4c5 010a4338 00000000 b2d18008 dxgmms1!VidSchiSubmitCommandPacketToQueue+0x1fe

    b040f6a0 922d4caf 88510278 b040f8f8 00008000 dxgmms1!VidSchSubmitCommand+0x38b

    b040fa44 922d6477 875d2620 b040fbb8 226ddd84 dxgkrnl!DXGCONTEXT::Render+0x5bd

    b040fc28 8424c1ea 0be5fa04 0be5fb58 76e370b4 dxgkrnl!DxgkRender+0x328

    b040fc28 76e370b4 0be5fa04 0be5fb58 76e370b4 nt!KiFastCallEntry+0x12a

    WARNING: Frame IP not in any known module. Following frames may be wrong.

    0be5fb58 00000000 00000000 00000000 00000000 0x76e370b4

     

     

    STACK_COMMAND:  kb

     

    FOLLOWUP_IP: 

    dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

    923a13ac 5f              pop     edi

     

    SYMBOL_STACK_INDEX:  4

     

    SYMBOL_NAME:  dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: dxgmms1

     

    IMAGE_NAME:  dxgmms1.sys

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d4a24c1

     

    FAILURE_BUCKET_ID:  0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

     

    BUCKET_ID:  0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

     

    Followup: MachineOwner

    ---------

     

    0: 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: fffffffc, memory referenced

    Arg2: 00000002, IRQL

    Arg3: 00000000, 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: 8428b638, address which referenced memory

     

    Debugging Details:

    ------------------

     

     

    READ_ADDRESS: GetPointerFromAddress: unable to read from 84378718

    Unable to read MiSystemVaType memory at 843581a0

     fffffffc 

     

    CURRENT_IRQL:  2

     

    FAULTING_IP: 

    nt!KiProcessThreadWaitList+1c

    8428b638 ff7670          push    dword ptr [esi+70h]

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

     

    BUGCHECK_STR:  0xA

     

    PROCESS_NAME:  Encode.exe

     

    TRAP_FRAME:  b040f55c -- (.trap 0xffffffffb040f55c)

    ErrCode = 00000000

    eax=8433cf14 ebx=00000001 ecx=84339d20 edx=00000001 esi=ffffff8c edi=00000000

    eip=8428b638 esp=b040f5d0 ebp=b040f5e0 iopl=0         nv up ei pl zr na pe nc

    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246

    nt!KiProcessThreadWaitList+0x1c:

    8428b638 ff7670          push    dword ptr [esi+70h]  ds:0023:fffffffc=????????

    Resetting default scope

     

    LAST_CONTROL_TRANSFER:  from 8428b638 to 8424f5cb

     

    STACK_TEXT:  

    b040f55c 8428b638 badb0d00 00000001 000000a2 nt!KiTrap0E+0x2cf

    b040f5e0 842855b1 00000000 00000001 00000000 nt!KiProcessThreadWaitList+0x1c

    b040f61c 84285577 84339d20 00000000 00000001 nt!KiExitDispatcher+0x2a

    b040f650 923a13ac 87af6aa8 00000000 00000000 nt!KeSetEvent+0xb2

    b040f67c 9239c4c5 010a4338 00000000 b2d18008 dxgmms1!VidSchiSubmitCommandPacketToQueue+0x1fe

    b040f6a0 922d4caf 88510278 b040f8f8 00008000 dxgmms1!VidSchSubmitCommand+0x38b

    b040fa44 922d6477 875d2620 b040fbb8 226ddd84 dxgkrnl!DXGCONTEXT::Render+0x5bd

    b040fc28 8424c1ea 0be5fa04 0be5fb58 76e370b4 dxgkrnl!DxgkRender+0x328

    b040fc28 76e370b4 0be5fa04 0be5fb58 76e370b4 nt!KiFastCallEntry+0x12a

    WARNING: Frame IP not in any known module. Following frames may be wrong.

    0be5fb58 00000000 00000000 00000000 00000000 0x76e370b4

     

     

    STACK_COMMAND:  kb

     

    FOLLOWUP_IP: 

    dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

    923a13ac 5f              pop     edi

     

    SYMBOL_STACK_INDEX:  4

     

    SYMBOL_NAME:  dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: dxgmms1

     

    IMAGE_NAME:  dxgmms1.sys

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d4a24c1

     

    FAILURE_BUCKET_ID:  0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

     

    BUCKET_ID:  0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

     

    Followup: MachineOwner

    ---------

     


    黄俊伟(wbpluto) MSN: hjw@live.cn Blogs: http://blog.wbpluto.com http://blogs.itecn.net/blogs/wbpluto
    2011年7月11日 5:51

全部回复

  • 这个问题经过分析是 Encode.exe 程序在调用 dxgmms1.sys 文件时发生的,这可能和您使用的监控软件有关。

    可以尝试安装监控程序的最新版本或更新摄像头或相关驱动程序。

     

    以下是分析出来的详细信息:

    Debugging Details:

    ------------------

     

     

    READ_ADDRESS: GetPointerFromAddress: unable to read from 84378718

    Unable to read MiSystemVaType memory at 843581a0

     fffffffc 

     

    CURRENT_IRQL:  2

     

    FAULTING_IP: 

    nt!KiProcessThreadWaitList+1c

    8428b638 ff7670          push    dword ptr [esi+70h]

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

     

    BUGCHECK_STR:  0xA

     

    PROCESS_NAME:  Encode.exe

     

    TRAP_FRAME:  b040f55c -- (.trap 0xffffffffb040f55c)

    ErrCode = 00000000

    eax=8433cf14 ebx=00000001 ecx=84339d20 edx=00000001 esi=ffffff8c edi=00000000

    eip=8428b638 esp=b040f5d0 ebp=b040f5e0 iopl=0         nv up ei pl zr na pe nc

    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246

    nt!KiProcessThreadWaitList+0x1c:

    8428b638 ff7670          push    dword ptr [esi+70h]  ds:0023:fffffffc=????????

    Resetting default scope

     

    LAST_CONTROL_TRANSFER:  from 8428b638 to 8424f5cb

     

    STACK_TEXT:  

    b040f55c 8428b638 badb0d00 00000001 000000a2 nt!KiTrap0E+0x2cf

    b040f5e0 842855b1 00000000 00000001 00000000 nt!KiProcessThreadWaitList+0x1c

    b040f61c 84285577 84339d20 00000000 00000001 nt!KiExitDispatcher+0x2a

    b040f650 923a13ac 87af6aa8 00000000 00000000 nt!KeSetEvent+0xb2

    b040f67c 9239c4c5 010a4338 00000000 b2d18008 dxgmms1!VidSchiSubmitCommandPacketToQueue+0x1fe

    b040f6a0 922d4caf 88510278 b040f8f8 00008000 dxgmms1!VidSchSubmitCommand+0x38b

    b040fa44 922d6477 875d2620 b040fbb8 226ddd84 dxgkrnl!DXGCONTEXT::Render+0x5bd

    b040fc28 8424c1ea 0be5fa04 0be5fb58 76e370b4 dxgkrnl!DxgkRender+0x328

    b040fc28 76e370b4 0be5fa04 0be5fb58 76e370b4 nt!KiFastCallEntry+0x12a

    WARNING: Frame IP not in any known module. Following frames may be wrong.

    0be5fb58 00000000 00000000 00000000 00000000 0x76e370b4

     

     

    STACK_COMMAND:  kb

     

    FOLLOWUP_IP: 

    dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

    923a13ac 5f              pop     edi

     

    SYMBOL_STACK_INDEX:  4

     

    SYMBOL_NAME:  dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: dxgmms1

     

    IMAGE_NAME:  dxgmms1.sys

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d4a24c1

     

    FAILURE_BUCKET_ID:  0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

     

    BUCKET_ID:  0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

     

    Followup: MachineOwner

    ---------

     

    0: 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: fffffffc, memory referenced

    Arg2: 00000002, IRQL

    Arg3: 00000000, 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: 8428b638, address which referenced memory

     

    Debugging Details:

    ------------------

     

     

    READ_ADDRESS: GetPointerFromAddress: unable to read from 84378718

    Unable to read MiSystemVaType memory at 843581a0

     fffffffc 

     

    CURRENT_IRQL:  2

     

    FAULTING_IP: 

    nt!KiProcessThreadWaitList+1c

    8428b638 ff7670          push    dword ptr [esi+70h]

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

     

    BUGCHECK_STR:  0xA

     

    PROCESS_NAME:  Encode.exe

     

    TRAP_FRAME:  b040f55c -- (.trap 0xffffffffb040f55c)

    ErrCode = 00000000

    eax=8433cf14 ebx=00000001 ecx=84339d20 edx=00000001 esi=ffffff8c edi=00000000

    eip=8428b638 esp=b040f5d0 ebp=b040f5e0 iopl=0         nv up ei pl zr na pe nc

    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246

    nt!KiProcessThreadWaitList+0x1c:

    8428b638 ff7670          push    dword ptr [esi+70h]  ds:0023:fffffffc=????????

    Resetting default scope

     

    LAST_CONTROL_TRANSFER:  from 8428b638 to 8424f5cb

     

    STACK_TEXT:  

    b040f55c 8428b638 badb0d00 00000001 000000a2 nt!KiTrap0E+0x2cf

    b040f5e0 842855b1 00000000 00000001 00000000 nt!KiProcessThreadWaitList+0x1c

    b040f61c 84285577 84339d20 00000000 00000001 nt!KiExitDispatcher+0x2a

    b040f650 923a13ac 87af6aa8 00000000 00000000 nt!KeSetEvent+0xb2

    b040f67c 9239c4c5 010a4338 00000000 b2d18008 dxgmms1!VidSchiSubmitCommandPacketToQueue+0x1fe

    b040f6a0 922d4caf 88510278 b040f8f8 00008000 dxgmms1!VidSchSubmitCommand+0x38b

    b040fa44 922d6477 875d2620 b040fbb8 226ddd84 dxgkrnl!DXGCONTEXT::Render+0x5bd

    b040fc28 8424c1ea 0be5fa04 0be5fb58 76e370b4 dxgkrnl!DxgkRender+0x328

    b040fc28 76e370b4 0be5fa04 0be5fb58 76e370b4 nt!KiFastCallEntry+0x12a

    WARNING: Frame IP not in any known module. Following frames may be wrong.

    0be5fb58 00000000 00000000 00000000 00000000 0x76e370b4

     

     

    STACK_COMMAND:  kb

     

    FOLLOWUP_IP: 

    dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

    923a13ac 5f              pop     edi

     

    SYMBOL_STACK_INDEX:  4

     

    SYMBOL_NAME:  dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: dxgmms1

     

    IMAGE_NAME:  dxgmms1.sys

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d4a24c1

     

    FAILURE_BUCKET_ID:  0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

     

    BUCKET_ID:  0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1fe

     

    Followup: MachineOwner

    ---------

     


    黄俊伟(wbpluto) MSN: hjw@live.cn Blogs: http://blog.wbpluto.com http://blogs.itecn.net/blogs/wbpluto
    2011年7月11日 5:51
  • 摄像头驱动就是小光盘带的软件,估计不能更新吧,换成XP系统是不是好点,现在是W7 32位
    2011年7月11日 9:06