win7 32bit 蓝屏 RRS feed

  • 问题

  • - <Event xmlns="">
    - <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck"
    <TimeCreated SystemTime="2012-04-15T15:04:27.000000000Z" />
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Security />
    - <EventData>
    <Data Name="param1">0x0000007f (0x00000008, 0x801eb000,
    0x00000000, 0x00000000)
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">041512-44975-01</Data>
    dmb文件已经上传到 希望帮忙解决!

    2012年4月15日 15:18


  • BUGCHECK_STR:  0x7f_8



    PROCESS_NAME:  QQMusic.exe


    LAST_CONTROL_TRANSFER:  from 94d3eefd to 94d58e98

    WARNING: Stack unwind information not available. Following frames may be wrong.
    c2469008 94d3eefd 84080000 00000001 08000000 igdpmd32+0x14ee98
    c2469284 94d41d05 8a6395e8 c24692a8 c24692c0 igdpmd32+0x134efd
    c2469294 94c1430b 898ff000 c24692a8 00000001 igdpmd32+0x137d05
    c24692c0 94c581a6 898ff000 c24692e0 94c16400 igdpmd32+0xa30b
    c2469334 94c58224 898ff000 94c16400 c2469300 igdpmd32+0x4e1a6
    c246936c 94c1b4b8 898ff000 86e61490 94c16400 igdpmd32+0x4e224
    c246940c 94c4f87e 86e61490 89902c6c 00000000 igdpmd32+0x114b8
    c24697f0 94c239e6 898ff000 00000000 8bbb4b38 igdpmd32+0x4587e
    c2469820 93392331 898ff000 c2469840 c0000001 igdpmd32+0x199e6
    c2469964 93379a4a 00000000 c24699b8 00000000 atikmpag+0x1c331
    c246997c 9410c783 00000000 00000102 c2469998 atikmpag+0x3a4a
    c24699b8 93e4e779 000c45c3 8ba37ff0 8ba20000 atikmdag+0x2d9783
    c24699d8 93e4d43a 00000004 c24699f4 93e5a75d atikmdag+0x1b779
    c24699e4 93e5a75d 841f7000 c2469ac0 c2469a44 atikmdag+0x1a43a
    c24699f4 93ec32de 8977a000 c2469a04 00000040 atikmdag+0x2775d
    c2469a44 93ec83f3 8ba20000 93e4d41b 841f7000 atikmdag+0x902de
    c2469af4 93ec8573 8ba20000 8ba2e5f8 00000000 atikmdag+0x953f3
    c2469b40 93ec8a0f 00000000 8ba2e5f8 8ba20000 atikmdag+0x95573
    c2469ba4 93ec8b5b 8ba20000 8ba2e5f8 00000000 atikmdag+0x95a0f
    c2469c0c 93ecd6c9 8ba20000 8ba2e5f8 00000000 atikmdag+0x95b5b
    c2469c78 93ec23b9 8ba20000 8998f940 89217410 atikmdag+0x9a6c9
    c2469c90 93e4d319 8ba20000 c2469cb4 9337ad34 atikmdag+0x8f3b9
    c2469c9c 9337ad34 8998f940 00000000 841c1c80 atikmdag+0x1a319
    c2469cb4 956e4b14 8998f940 00000000 c2469cd8 atikmpag+0x4d34
    c2469cc4 848a4b30 841c1c80 8977c920 00000000 dxgkrnl!DpiFdoMessageInterruptRoutine+0x17
    c2469cd8 848547cd 841c1c80 8977c920 c2469d04 nt!KiInterruptMessageDispatch+0x12
    c2469cd8 9931b6b1 841c1c80 8977c920 c2469d04 nt!KiInterruptDispatch+0x6d
    c2469d74 89d8e020 89ff81bc 89d424f0 89d424f0 athr+0xf76b1
    c2469d8c 99348a35 89d8e020 0000402c 89d8e020 0x89d8e020
    c2469db0 992c64d2 89d8e020 00000000 00000000 athr+0x124a35
    c2469dd4 992c5eed 89d8a020 00000001 89d8a020 athr+0xa24d2
    c2469df4 9924637e 89d8a020 c2469e4f c2469e1c athr+0xa1eed
    c2469e04 99225267 89d3e020 c2469e4f 89d7e020 athr+0x2237e
    c2469e1c 8aa6f317 89d7e020 c2469e4f c2469e44 athr+0x1267
    c2469e50 8485455c 877d4000 8a074880 0000007f ndis!ndisMiniportIsr+0x67
    c2469e7c 848544a9 00000002 00000051 c2469f20 nt!KiChainedDispatch2ndLvl+0x60
    c2469e7c 8489c57a 00000002 00000051 c2469f20 nt!KiChainedDispatch+0x29
    c2469f20 8489c520 c246a1c0 9ee41084 00000000 nt!RtlSidHashLookup+0x25
    c2469f34 8489c4d6 00000000 00000000 00000000 nt!SepSidInTokenSidHash+0x40
    c2469f50 8489c2d9 00000000 00000000 00000000 nt!SepSidInToken+0x29
    c2469f7c 8489bf1a 00000000 c246a0f8 c246a0f8 nt!SepNormalAccessCheck+0x6c
    c2469f80 00000000 c246a0f8 c246a0f8 00000000 nt!SepAccessCheck+0x1f9


    Juke Chou

    TechNet Community Support

    2012年4月18日 3:35
  • 我的笔记本的,装驱动的时候我应该选择品牌驱动还是有WHQL认证的驱动好?

    2012年4月18日 5:38
  • WHQL 驱动。

    Juke Chou

    TechNet Community Support

    2012年4月18日 7:25
  • 更新了WQHL驱动以后还是没用,用Debug分析还是igdpmd32.sys这个文件出错

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

    Loading Dump File [C:\Users\hp\Desktop\042312-30076-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\sytemp*
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17790.x86fre.win7sp1_gdr.120305-1505
    Machine Name:
    Kernel base = 0x84840000 PsLoadedModuleList = 0x849894d0
    Debug session time: Mon Apr 23 11:53:43.692 2012 (GMT+8)
    System Uptime: 0 days 1:53:58.129
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    Unable to load image \SystemRoot\system32\DRIVERS\igdpmd32.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for igdpmd32.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdpmd32.sys
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007F, {8, 801eb000, 0, 0}

    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : igdpmd32.sys ( igdpmd32+4db79 )

    Followup: MachineOwner

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

    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
            .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)
    kb will then show the corrected stack.
    Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 801eb000
    Arg3: 00000000
    Arg4: 00000000

    Debugging Details:

    BUGCHECK_STR:  0x7f_8



    PROCESS_NAME:  SearchIndexer.


    LAST_CONTROL_TRANSFER:  from 94db1a06 to 94c83b79

    WARNING: Stack unwind information not available. Following frames may be wrong.
    bf449014 94db1a06 89955000 00070180 89955000 igdpmd32+0x4db79
    bf449028 94e559fa 8a18bd78 00070180 8a18bd78 igdpmd32+0x17ba06
    bf44903c 94e85228 86e635e8 0000007f bf449064 igdpmd32+0x21f9fa
    bf449050 94dda23e 86e635e8 86e635e8 c0000001 igdpmd32+0x24f228
    bf449064 94db46b7 8a1b8000 00000001 00001580 igdpmd32+0x1a423e
    bf449204 94db81b7 89ab2340 bf44923c 8a18bd78 igdpmd32+0x17e6b7
    bf44921c 94c71506 89955000 bf44923c 00000000 igdpmd32+0x1821b7
    bf44924c 94cf1049 89955000 bf449264 00000001 igdpmd32+0x3b506
    bf449274 94c7dfd2 89955000 86e77618 00000000 igdpmd32+0xbb049
    bf44931c 94c8836c 89955000 89958a90 00000000 igdpmd32+0x47fd2
    bf4493fc 94c3e5ce 89955000 00000000 895af4f8 igdpmd32+0x5236c
    bf449448 93a1cdcf 89955000 bf449468 c0000001 igdpmd32+0x85ce
    bf449588 93a068ce 00000001 bf4495dc 00000001 atikmpag+0x19dcf
    bf4495a0 9411634c 00000000 00000102 bf4495bc atikmpag+0x38ce
    bf4495dc 93e44847 0008d2d1 834c95c0 834ae000 atikmdag+0x2eb34c
    bf4495fc 93e436ac 00000004 bf449618 93e4fe96 atikmdag+0x19847
    bf449608 93e4fe96 83433008 bf4496e4 bf449668 atikmdag+0x186ac
    bf449618 93ead7cf 89942000 bf449628 00000040 atikmdag+0x24e96
    bf449668 93eb243b 834ae000 93e4368d 83433008 atikmdag+0x827cf
    bf44972c 93eb2585 834ae000 834bcfb0 00000000 atikmdag+0x8743b
    bf449774 93eb2a36 00000000 834bcfb0 834ae000 atikmdag+0x87585
    bf4497d8 93eb2c07 834ae000 834bcfb0 00000000 atikmdag+0x87a36
    bf449840 93eb7a33 834ae000 834bcfb0 00000000 atikmdag+0x87c07
    bf4498a4 93eac8df 834ae000 8993f8c0 89225410 atikmdag+0x8ca33
    bf4498bc 93e4358b 834ae000 bf4498e0 93a0766a atikmdag+0x818df
    bf4498c8 93a0766a 8993f8c0 00000000 8a120c80 atikmdag+0x1858b
    bf4498e0 956c5b14 8993f8c0 00000000 bf449904 atikmpag+0x466a
    bf4498f0 848cab30 8a120c80 89914800 00000000 dxgkrnl!DpiFdoMessageInterruptRoutine+0x17
    bf449904 8487a7cd 8a120c80 89914800 bf449930 nt!KiInterruptMessageDispatch+0x12
    bf449904 848e9408 8a120c80 89914800 bf449930 nt!KiInterruptDispatch+0x6d
    bf449e04 84872e49 bf449e28 8557561c 00000000 nt!_woutput_l+0xc5
    bf449e48 848e9d62 bf449eb0 00000063 855755fc nt!_vsnwprintf_l+0x7b
    bf449e64 8556b160 bf449eb0 00000063 855755fc nt!_vsnwprintf+0x18
    bf449e88 85571fac bf449eb0 000000c8 855755fc volmgr!RtlStringCbPrintfW+0x3a
    bf449f7c 8556b8ab 8929f9e0 86f02408 00004000 volmgr!VmpQueryDeviceName+0x46
    bf449fa0 8487758e 8929f928 86f02574 892a10d8 volmgr!VmDeviceControl+0x2f1
    bf449fb8 8ab4e854 bf44a000 8ab4f74d 892a1020 nt!IofCallDriver+0x63
    bf449fc0 8ab4f74d 892a1020 86f02408 8929e388 fvevol!FveFilterSkip+0x1e
    bf449ff0 9f3ff778 bf44a010 bf44a02c 00000000 fvevol!FveFilterDeviceControl+0x16f
    ffffffff 00000000 00000000 00000000 00000000 0x9f3ff778


    94c83b79 e872e70600      call    igdpmd32+0xbc2f0 (94cf22f0)


    SYMBOL_NAME:  igdpmd32+4db79

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: igdpmd32

    IMAGE_NAME:  igdpmd32.sys


    FAILURE_BUCKET_ID:  0x7f_8_igdpmd32+4db79

    BUCKET_ID:  0x7f_8_igdpmd32+4db79

    Followup: MachineOwner

    2012年4月23日 4:12
  • 你看下这个文件的版本,更新一个比较新的版本试一下。

    Juke Chou

    TechNet Community Support

    2012年4月23日 5:14
  • 我试过换了几个不同版本的驱动,但是这个文件的版本都没有变,只是显示修改日期改变。你是指换一个比较新版本的驱动还是只换这个文件?如果只换文件又应该怎么换?
    2012年4月23日 10:26
  • Hi,

    错误是由此文件引起的,还是建议换一个不同版本的文件试一下,如果有其他版本,直接替换在safemode 下。

    Juke Chou

    TechNet Community Support

    2012年4月24日 2:31