none
系统蓝屏 RRS feed

  • 问题

  • 今天早上系统自动更新完毕提示更新以后,系统重新启动后就出现蓝屏,下面是debug分析的信息

    * 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 : igxpmp32.sys ( igxpmp32+44124 )

    2011年2月17日 3:53

全部回复

  • 应该是楼主的显卡驱动(Intel Graphics Miniport Driver)问题,建议重新安装驱动。
    在IT的路上,You'll never walk alone
    2011年2月17日 6:13
  • 如果是显卡驱动的问题,我重新安装驱动,再次更新后会不会还会出现 ?无法知道是与哪个补丁冲突么?

     

    2011年2月17日 8:30
  • 你的 WinDebug 符号路径设置不正确,从结果只能看出是 igxpmp32.sys 驱动引起的问题。
     
    驱动问题并不一定是与系统更新存在冲突有关,除非你可以确定卸载某更新后就可以立即解决,这种问题出现的概率很低。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "Michael-ming"
     
    今天早上系统自动更新完毕提示更新以后,系统重新启动后就出现蓝屏,下面是debug分析的信息
    * Symbols can not be loaded because symbol path is not initialized. *
     
     
    2011年2月17日 9:14
    版主
  • Symbols path设置好了,现在是分析的情况,谁知道是什么原因?
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [D:\Documents and Settings\origina\Desktop\Mini021811-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*D:\Tool\WinDbg\Symbols\Win XP sp3*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_gdr.101209-1647
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Fri Feb 18 08:24:37.828 2011 (GMT+8)
    System Uptime: 0 days 0:00:11.484
    Loading Kernel Symbols
    ...............................................................
    ..........................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007F, {8, 80042000, 0, 0}

    Unable to load image igxpmp32.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for igxpmp32.sys
    *** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys
    Unable to load image igxpdx32.DLL, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for igxpdx32.DLL
    *** ERROR: Module load completed but symbols could not be loaded for igxpdx32.DLL
    Probably caused by : igxpmp32.sys ( igxpmp32+44124 )

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

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

    UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 80042000
    Arg3: 00000000
    Arg4: 00000000

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


    BUGCHECK_STR:  0x7f_8

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    PROCESS_NAME:  csrss.exe

    LAST_CONTROL_TRANSFER:  from 80636ac7 to 805f8947

    STACK_TEXT: 
    a96d6060 80636ac7 a96d60fc e1a68d20 a96d6100 nt!SeQuerySecurityDescriptorInfo+0x193
    a96d6078 806379d6 e1024544 a96d60fc e1a68d20 nt!CmpQuerySecurityDescriptorInfo+0x23
    a96d60c4 805bfe5b e1657e18 00000001 a96d60fc nt!CmpSecurityMethod+0xce
    a96d6104 805c01c8 e1657e18 a96d6130 e1657e14 nt!ObpGetObjectSecurity+0x99
    a96d6134 8062f28f e1657e18 8a731f30 00000001 nt!ObCheckObjectAccess+0x2c
    a96d6180 8062ff30 e1036758 004c3390 e1504394 nt!CmpDoOpen+0x2d5
    a96d6380 805bf488 004c3390 004c3390 8a731f30 nt!CmpParseKey+0x5a6
    a96d63f8 805bba14 00000000 a96d6438 00000240 nt!ObpLookupObjectName+0x53c
    a96d644c 80625696 00000000 8a855238 00000000 nt!ObOpenObjectByName+0xea
    a96d6548 8054167c a96d6868 82000000 a96d65ec nt!NtOpenKey+0x1c8
    a96d6548 80500699 a96d6868 82000000 a96d65ec nt!KiFastCallEntry+0xfc
    a96d65cc 805e701e a96d6868 82000000 a96d65ec nt!ZwOpenKey+0x11
    a96d683c 805e712a 00000002 805e70a0 00000000 nt!RtlpGetRegistryHandleAndPath+0x27a
    a96d6884 805e73e3 a96d68a4 00000014 a96d6bf8 nt!RtlpQueryRegistryGetBlockPolicy+0x2e
    a96d68ac 805e79eb 00000003 e166eb24 00000014 nt!RtlpQueryRegistryDirect+0x4b
    a96d68fc 805e7f10 e166eb24 00000003 a96d6988 nt!RtlpCallQueryRegistryRoutine+0x369
    a96d6b98 b9bc4124 00000005 e1d5f138 a96d6bf8 nt!RtlQueryRegistryValues+0x482
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a96d6c40 b9b8985b 00000005 8a416364 8a416464 igxpmp32+0x44124
    a96d72b8 b9b85a7b 8a74a358 a96d72e8 00000000 igxpmp32+0x985b
    a96d72cc b9b7a729 8a74a358 a96d72e8 00000a0c igxpmp32+0x5a7b
    a96d7390 804ef19f 8a74a040 8a5c45e8 0000080c VIDEOPRT!pVideoPortDispatch+0xabf
    a96d73a0 bf85e8c2 a96d7668 bf6e5cdc 00000014 nt!IopfCallDriver+0x31
    a96d73d0 bf85e93c 8a74a040 00232150 a96d7450 win32k!GreDeviceIoControl+0x93
    a96d73f4 bf375769 8a74a040 00232150 a96d7450 win32k!EngDeviceIoControl+0x1f
    a96d867c bf3b8e89 8a74a040 bf6a493c bf6a4960 igxpdx32+0x8769
    a96d86d8 8054b6ed bb40e64e bf3ab546 bf6e5cc8 igxpdx32+0x4be89
    a96d878c 805c10a3 e166ec60 a079654b 8a855238 nt!ExFreePoolWithTag+0x40d
    a96d87ac 805bb4b2 00000000 e166ec60 e166ec78 nt!ObpFreeObject+0x18d
    a96d87c4 805266fa e166ec78 00000000 000003dc nt!ObpRemoveObjectRoutine+0xe8
    a96d8804 805361db a96d881c bf3aa84b 00000000 nt!ObfDereferenceObject+0x4c
    a96d8820 bf6ef998 a96d8834 bf3a7e1e 00000000 nt!ExAcquireResourceExclusiveLite+0x67
    a96d885c 804fff41 badb0d00 a96d88d4 a96d88ac igxpdx32+0x382998
    a96d8880 bf804882 a96d8898 bf853cd5 8a36ba68 nt!ZwClose+0x11
    a96d8938 a96d89dc e1bbab90 e1bbbd10 e1bba714 win32k!GreReleaseFastMutex+0x14
    a96d895c bf86196f bf0031fa a96d8980 00000000 0xa96d89dc
    a96d89b0 bf003cfa e1bba008 a96d89e0 bf00889d win32k!WatchdogDdGetDriverInfo+0x300
    a96d89c0 e1bba008 00000008 e1bbab90 e1bbbd10 dxg!PDEVOBJ::ppfn+0x14
    a96d89e0 bf008c4d e1bf3280 00000000 e1bba714 0xe1bba008
    a96d8a14 bf009033 00000001 e165b008 a96d8a9c dxg!vDdEnableDriver+0x1e5
    a96d8a30 bf874bd5 e1bba008 00000001 e1ad5008 dxg!DxDdEnableDirectDraw+0xbf
    a96d8a50 bf88f454 a96d8bf0 e1a374c8 00000000 win32k!PDEVOBJ::bMakeSurface+0xe2
    a96d8a7c bf88fe54 e1a374c8 e1a60800 e1a88800 win32k!hCreateHDEV+0x3a9
    a96d8bf4 bf89607f 00000000 00000000 00000001 win32k!DrvCreateMDEV+0x4dc
    a96d8ce8 bf892b2c 00000000 00000000 00000000 win32k!DrvChangeDisplaySettings+0x2e5
    a96d8d28 bf892a9a 00000001 a96d8d64 0015fd98 win32k!InitVideo+0x3e
    a96d8d48 bf893e59 a96d8d64 8054167c 00050000 win32k!UserInitialize+0x14d
    a96d8d50 8054167c 00050000 0000006c 00000070 win32k!NtUserInitialize+0x87
    a96d8d50 7c90e514 00050000 0000006c 00000070 nt!KiFastCallEntry+0xfc
    0015fdb0 00000000 00000000 00000000 00000000 0x7c90e514


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    igxpmp32+44124
    b9bc4124 ??              ???

    SYMBOL_STACK_INDEX:  11

    SYMBOL_NAME:  igxpmp32+44124

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: igxpmp32

    IMAGE_NAME:  igxpmp32.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4af86b5b

    FAILURE_BUCKET_ID:  0x7f_8_igxpmp32+44124

    BUCKET_ID:  0x7f_8_igxpmp32+44124

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

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

    UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 80042000
    Arg3: 00000000
    Arg4: 00000000

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


    BUGCHECK_STR:  0x7f_8

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    PROCESS_NAME:  csrss.exe

    LAST_CONTROL_TRANSFER:  from 80636ac7 to 805f8947

    STACK_TEXT: 
    a96d6060 80636ac7 a96d60fc e1a68d20 a96d6100 nt!SeQuerySecurityDescriptorInfo+0x193
    a96d6078 806379d6 e1024544 a96d60fc e1a68d20 nt!CmpQuerySecurityDescriptorInfo+0x23
    a96d60c4 805bfe5b e1657e18 00000001 a96d60fc nt!CmpSecurityMethod+0xce
    a96d6104 805c01c8 e1657e18 a96d6130 e1657e14 nt!ObpGetObjectSecurity+0x99
    a96d6134 8062f28f e1657e18 8a731f30 00000001 nt!ObCheckObjectAccess+0x2c
    a96d6180 8062ff30 e1036758 004c3390 e1504394 nt!CmpDoOpen+0x2d5
    a96d6380 805bf488 004c3390 004c3390 8a731f30 nt!CmpParseKey+0x5a6
    a96d63f8 805bba14 00000000 a96d6438 00000240 nt!ObpLookupObjectName+0x53c
    a96d644c 80625696 00000000 8a855238 00000000 nt!ObOpenObjectByName+0xea
    a96d6548 8054167c a96d6868 82000000 a96d65ec nt!NtOpenKey+0x1c8
    a96d6548 80500699 a96d6868 82000000 a96d65ec nt!KiFastCallEntry+0xfc
    a96d65cc 805e701e a96d6868 82000000 a96d65ec nt!ZwOpenKey+0x11
    a96d683c 805e712a 00000002 805e70a0 00000000 nt!RtlpGetRegistryHandleAndPath+0x27a
    a96d6884 805e73e3 a96d68a4 00000014 a96d6bf8 nt!RtlpQueryRegistryGetBlockPolicy+0x2e
    a96d68ac 805e79eb 00000003 e166eb24 00000014 nt!RtlpQueryRegistryDirect+0x4b
    a96d68fc 805e7f10 e166eb24 00000003 a96d6988 nt!RtlpCallQueryRegistryRoutine+0x369
    a96d6b98 b9bc4124 00000005 e1d5f138 a96d6bf8 nt!RtlQueryRegistryValues+0x482
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a96d6c40 b9b8985b 00000005 8a416364 8a416464 igxpmp32+0x44124
    a96d72b8 b9b85a7b 8a74a358 a96d72e8 00000000 igxpmp32+0x985b
    a96d72cc b9b7a729 8a74a358 a96d72e8 00000a0c igxpmp32+0x5a7b
    a96d7390 804ef19f 8a74a040 8a5c45e8 0000080c VIDEOPRT!pVideoPortDispatch+0xabf
    a96d73a0 bf85e8c2 a96d7668 bf6e5cdc 00000014 nt!IopfCallDriver+0x31
    a96d73d0 bf85e93c 8a74a040 00232150 a96d7450 win32k!GreDeviceIoControl+0x93
    a96d73f4 bf375769 8a74a040 00232150 a96d7450 win32k!EngDeviceIoControl+0x1f
    a96d867c bf3b8e89 8a74a040 bf6a493c bf6a4960 igxpdx32+0x8769
    a96d86d8 8054b6ed bb40e64e bf3ab546 bf6e5cc8 igxpdx32+0x4be89
    a96d878c 805c10a3 e166ec60 a079654b 8a855238 nt!ExFreePoolWithTag+0x40d
    a96d87ac 805bb4b2 00000000 e166ec60 e166ec78 nt!ObpFreeObject+0x18d
    a96d87c4 805266fa e166ec78 00000000 000003dc nt!ObpRemoveObjectRoutine+0xe8
    a96d8804 805361db a96d881c bf3aa84b 00000000 nt!ObfDereferenceObject+0x4c
    a96d8820 bf6ef998 a96d8834 bf3a7e1e 00000000 nt!ExAcquireResourceExclusiveLite+0x67
    a96d885c 804fff41 badb0d00 a96d88d4 a96d88ac igxpdx32+0x382998
    a96d8880 bf804882 a96d8898 bf853cd5 8a36ba68 nt!ZwClose+0x11
    a96d8938 a96d89dc e1bbab90 e1bbbd10 e1bba714 win32k!GreReleaseFastMutex+0x14
    a96d895c bf86196f bf0031fa a96d8980 00000000 0xa96d89dc
    a96d89b0 bf003cfa e1bba008 a96d89e0 bf00889d win32k!WatchdogDdGetDriverInfo+0x300
    a96d89c0 e1bba008 00000008 e1bbab90 e1bbbd10 dxg!PDEVOBJ::ppfn+0x14
    a96d89e0 bf008c4d e1bf3280 00000000 e1bba714 0xe1bba008
    a96d8a14 bf009033 00000001 e165b008 a96d8a9c dxg!vDdEnableDriver+0x1e5
    a96d8a30 bf874bd5 e1bba008 00000001 e1ad5008 dxg!DxDdEnableDirectDraw+0xbf
    a96d8a50 bf88f454 a96d8bf0 e1a374c8 00000000 win32k!PDEVOBJ::bMakeSurface+0xe2
    a96d8a7c bf88fe54 e1a374c8 e1a60800 e1a88800 win32k!hCreateHDEV+0x3a9
    a96d8bf4 bf89607f 00000000 00000000 00000001 win32k!DrvCreateMDEV+0x4dc
    a96d8ce8 bf892b2c 00000000 00000000 00000000 win32k!DrvChangeDisplaySettings+0x2e5
    a96d8d28 bf892a9a 00000001 a96d8d64 0015fd98 win32k!InitVideo+0x3e
    a96d8d48 bf893e59 a96d8d64 8054167c 00050000 win32k!UserInitialize+0x14d
    a96d8d50 8054167c 00050000 0000006c 00000070 win32k!NtUserInitialize+0x87
    a96d8d50 7c90e514 00050000 0000006c 00000070 nt!KiFastCallEntry+0xfc
    0015fdb0 00000000 00000000 00000000 00000000 0x7c90e514


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    igxpmp32+44124
    b9bc4124 ??              ???

    SYMBOL_STACK_INDEX:  11

    SYMBOL_NAME:  igxpmp32+44124

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: igxpmp32

    IMAGE_NAME:  igxpmp32.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4af86b5b

    FAILURE_BUCKET_ID:  0x7f_8_igxpmp32+44124

    BUCKET_ID:  0x7f_8_igxpmp32+44124

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

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

    UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 80042000
    Arg3: 00000000
    Arg4: 00000000

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


    BUGCHECK_STR:  0x7f_8

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    PROCESS_NAME:  csrss.exe

    LAST_CONTROL_TRANSFER:  from 80636ac7 to 805f8947

    STACK_TEXT: 
    a96d6060 80636ac7 a96d60fc e1a68d20 a96d6100 nt!SeQuerySecurityDescriptorInfo+0x193
    a96d6078 806379d6 e1024544 a96d60fc e1a68d20 nt!CmpQuerySecurityDescriptorInfo+0x23
    a96d60c4 805bfe5b e1657e18 00000001 a96d60fc nt!CmpSecurityMethod+0xce
    a96d6104 805c01c8 e1657e18 a96d6130 e1657e14 nt!ObpGetObjectSecurity+0x99
    a96d6134 8062f28f e1657e18 8a731f30 00000001 nt!ObCheckObjectAccess+0x2c
    a96d6180 8062ff30 e1036758 004c3390 e1504394 nt!CmpDoOpen+0x2d5
    a96d6380 805bf488 004c3390 004c3390 8a731f30 nt!CmpParseKey+0x5a6
    a96d63f8 805bba14 00000000 a96d6438 00000240 nt!ObpLookupObjectName+0x53c
    a96d644c 80625696 00000000 8a855238 00000000 nt!ObOpenObjectByName+0xea
    a96d6548 8054167c a96d6868 82000000 a96d65ec nt!NtOpenKey+0x1c8
    a96d6548 80500699 a96d6868 82000000 a96d65ec nt!KiFastCallEntry+0xfc
    a96d65cc 805e701e a96d6868 82000000 a96d65ec nt!ZwOpenKey+0x11
    a96d683c 805e712a 00000002 805e70a0 00000000 nt!RtlpGetRegistryHandleAndPath+0x27a
    a96d6884 805e73e3 a96d68a4 00000014 a96d6bf8 nt!RtlpQueryRegistryGetBlockPolicy+0x2e
    a96d68ac 805e79eb 00000003 e166eb24 00000014 nt!RtlpQueryRegistryDirect+0x4b
    a96d68fc 805e7f10 e166eb24 00000003 a96d6988 nt!RtlpCallQueryRegistryRoutine+0x369
    a96d6b98 b9bc4124 00000005 e1d5f138 a96d6bf8 nt!RtlQueryRegistryValues+0x482
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a96d6c40 b9b8985b 00000005 8a416364 8a416464 igxpmp32+0x44124
    a96d72b8 b9b85a7b 8a74a358 a96d72e8 00000000 igxpmp32+0x985b
    a96d72cc b9b7a729 8a74a358 a96d72e8 00000a0c igxpmp32+0x5a7b
    a96d7390 804ef19f 8a74a040 8a5c45e8 0000080c VIDEOPRT!pVideoPortDispatch+0xabf
    a96d73a0 bf85e8c2 a96d7668 bf6e5cdc 00000014 nt!IopfCallDriver+0x31
    a96d73d0 bf85e93c 8a74a040 00232150 a96d7450 win32k!GreDeviceIoControl+0x93
    a96d73f4 bf375769 8a74a040 00232150 a96d7450 win32k!EngDeviceIoControl+0x1f
    a96d867c bf3b8e89 8a74a040 bf6a493c bf6a4960 igxpdx32+0x8769
    a96d86d8 8054b6ed bb40e64e bf3ab546 bf6e5cc8 igxpdx32+0x4be89
    a96d878c 805c10a3 e166ec60 a079654b 8a855238 nt!ExFreePoolWithTag+0x40d
    a96d87ac 805bb4b2 00000000 e166ec60 e166ec78 nt!ObpFreeObject+0x18d
    a96d87c4 805266fa e166ec78 00000000 000003dc nt!ObpRemoveObjectRoutine+0xe8
    a96d8804 805361db a96d881c bf3aa84b 00000000 nt!ObfDereferenceObject+0x4c
    a96d8820 bf6ef998 a96d8834 bf3a7e1e 00000000 nt!ExAcquireResourceExclusiveLite+0x67
    a96d885c 804fff41 badb0d00 a96d88d4 a96d88ac igxpdx32+0x382998
    a96d8880 bf804882 a96d8898 bf853cd5 8a36ba68 nt!ZwClose+0x11
    a96d8938 a96d89dc e1bbab90 e1bbbd10 e1bba714 win32k!GreReleaseFastMutex+0x14
    a96d895c bf86196f bf0031fa a96d8980 00000000 0xa96d89dc
    a96d89b0 bf003cfa e1bba008 a96d89e0 bf00889d win32k!WatchdogDdGetDriverInfo+0x300
    a96d89c0 e1bba008 00000008 e1bbab90 e1bbbd10 dxg!PDEVOBJ::ppfn+0x14
    a96d89e0 bf008c4d e1bf3280 00000000 e1bba714 0xe1bba008
    a96d8a14 bf009033 00000001 e165b008 a96d8a9c dxg!vDdEnableDriver+0x1e5
    a96d8a30 bf874bd5 e1bba008 00000001 e1ad5008 dxg!DxDdEnableDirectDraw+0xbf
    a96d8a50 bf88f454 a96d8bf0 e1a374c8 00000000 win32k!PDEVOBJ::bMakeSurface+0xe2
    a96d8a7c bf88fe54 e1a374c8 e1a60800 e1a88800 win32k!hCreateHDEV+0x3a9
    a96d8bf4 bf89607f 00000000 00000000 00000001 win32k!DrvCreateMDEV+0x4dc
    a96d8ce8 bf892b2c 00000000 00000000 00000000 win32k!DrvChangeDisplaySettings+0x2e5
    a96d8d28 bf892a9a 00000001 a96d8d64 0015fd98 win32k!InitVideo+0x3e
    a96d8d48 bf893e59 a96d8d64 8054167c 00050000 win32k!UserInitialize+0x14d
    a96d8d50 8054167c 00050000 0000006c 00000070 win32k!NtUserInitialize+0x87
    a96d8d50 7c90e514 00050000 0000006c 00000070 nt!KiFastCallEntry+0xfc
    0015fdb0 00000000 00000000 00000000 00000000 0x7c90e514


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    igxpmp32+44124
    b9bc4124 ??              ???

    SYMBOL_STACK_INDEX:  11

    SYMBOL_NAME:  igxpmp32+44124

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: igxpmp32

    IMAGE_NAME:  igxpmp32.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4af86b5b

    FAILURE_BUCKET_ID:  0x7f_8_igxpmp32+44124

    BUCKET_ID:  0x7f_8_igxpmp32+44124

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

     

     

    !analyze -v  该命令运行后的结果如下

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

    UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 80042000
    Arg3: 00000000
    Arg4: 00000000

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


    BUGCHECK_STR:  0x7f_8

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    PROCESS_NAME:  csrss.exe

    LAST_CONTROL_TRANSFER:  from 80636ac7 to 805f8947

    STACK_TEXT: 


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    igxpmp32+44124
    b9bc4124 ??              ???

    SYMBOL_STACK_INDEX:  11

    SYMBOL_NAME:  igxpmp32+44124

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: igxpmp32

    IMAGE_NAME:  igxpmp32.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4af86b5b

    FAILURE_BUCKET_ID:  0x7f_8_igxpmp32+44124

    BUCKET_ID:  0x7f_8_igxpmp32+44124

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

     

    2011年2月18日 2:30
  • 还是驱动程序错误,建议重新安装或升级 Intel 集成显示驱动。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "Michael-ming"
     
    Symbols path设置好了,现在是分析的情况,谁知道是什么原因?
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
     
     
    2011年2月18日 8:38
    版主