none
求救 各位高手救救我啊 我的Vista系统 最近老是蓝屏 蓝屏代码如下 RRS feed

  • 问题

  • driver_irql_not_less_or_equal

    stop:0x000000D1(0x00000036,0x00000002,0x00000000,0x9430EBF0)

    kll,sys--address 9430EBF0 base at 942E0000,Datestamp 4a361baf.

    特别是在运行大型3D游戏的时候

    很容易蓝屏  是什么原因啊?是显卡问题 还是驱动啊
    2009年9月16日 16:33

全部回复

  • 請參考這個 Microsoft 幫助和支持

    易宝典:Windows常见蓝屏故障分析(MVP 撰稿)
    http://support.microsoft.com/kb/972602/zh-cn

    以下內容完整複製至 謝依村 在帖子 2003 企业版系统意外重起 的回覆

    首先下载 windebug

     

    http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

    说下 debug 方法
    1.
    我的电脑,属性 -> 高级 -> 启动,最下面的内存调试选最后一项的全部,确定后重新启动
    2.
    蓝屏后不要急着重启,系统会保存整个内存内容,然后会自动重启
    3.
    找到 C:\Windows\Minidump\

    4. 下载安装 windwos debug tools, 我这有下载地址,或微软网站
    http://public.hshh.org/SysTools/debug/dbg_x86_6.6.07.5.exe
    5.
    安装后创建一个临时目录,例如 c:\temp
    6.
    启动 windbg
    7. windbg
    界面 : file->symbol file path (ctrl+s) 输入 :
    SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    然后确定
    8. windbg
    界面 : file->open crash dump(ctrl+d) ,打开 9. 打开例如 C:\Windows\Minidump\Mini122208-01.dmp 后,等待提示
    当出现 Use !analyze -v to get detailed debugging information. 字样后,在下面输入框
    !analyze -v
    10.
    等待分析完毕,可以知道什么导致的出错
    11. windbg
    使用中需要网上下载调试内容,这个速度嘛,取决于你的网络了。

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

     

    你把敲完 !analyze -v 后的信息发上来!

    以上內容完整複製至 謝依村 在帖子 2003 企业版系统意外重起 的回覆

    原始連接:
    http://social.microsoft.com/Forums/vistazhchs/windowsserversystemzhchs/thread/48d50269-adb8-43b9-a74d-ccf1914eb72f

    Folding@Home
    2009年9月17日 0:45
  • 以下是windbg 的错误报告

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {4, 2, 0, 95f08f2c}

    Unable to load image \SystemRoot\system32\DRIVERS\kl1.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for kl1.sys
    *** ERROR: Module load completed but symbols could not be loaded for kl1.sys
    Probably caused by : kl1.sys ( kl1+27f2c )

    Followup: MachineOwner

    它也说Probably caused by : kl1.sys  楼上的方法我也找到了  但是我不想卸载卡巴斯基啊 有没有不用卸载的方法啊???
    2009年9月17日 1:38
  • windbg完整的错误报告如下:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


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

    Symbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6000.16830.x86fre.vista_gdr.090302-1506
    Machine Name:
    Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
    Debug session time: Wed Sep 16 22:03:37.411 2009 (GMT+8)
    System Uptime: 0 days 0:51:33.343
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {4, 2, 0, 95f08f2c}

    Unable to load image \SystemRoot\system32\DRIVERS\kl1.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for kl1.sys
    *** ERROR: Module load completed but symbols could not be loaded for kl1.sys
    Probably caused by : kl1.sys ( kl1+27f2c )

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000004, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 95f08f2c, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 821315ac
    Unable to read MiSystemVaType memory at 821117e0
     00000004

    CURRENT_IRQL:  2

    FAULTING_IP:
    kl1+27f2c
    95f08f2c ??              ???

    CUSTOMER_CRASH_COUNT:  2

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    PROCESS_NAME:  TLR.exe

    TRAP_FRAME:  81e04354 -- (.trap 0xffffffff81e04354)
    ErrCode = 00000000
    eax=00000000 ebx=00000000 ecx=853e68f0 edx=95f01cf4 esi=86c4eaf8 edi=86b8efb0
    eip=95f08f2c esp=81e043c8 ebp=86c4eaf8 iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210286
    kl1+0x27f2c:
    95f08f2c ??              ???
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 95f08f2c to 8208fdc4

    STACK_TEXT:  
    81e04354 95f08f2c badb0d00 95f01cf4 81e04386 nt!KiTrap0E+0x2ac
    WARNING: Stack unwind information not available. Following frames may be wrong.
    81e043c4 95f067b8 86c4eb96 95f0701d 8490aae0 kl1+0x27f2c
    81e04428 8aaffae4 86c08b38 00000000 00000000 kl1+0x257b8
    81e04448 8aaffb98 8490aae0 8490aae0 00000000 ndis!ndisFilterSendNetBufferLists+0x8b
    81e04460 95ac4e58 86c86810 8490aae0 00000000 ndis!NdisFSendNetBufferLists+0x18
    81e044dc 8aaffb76 86c84180 8490aae0 00000000 pacer!PcFilterSendNetBufferLists+0x232
    81e044f8 8abc364a 8490aae0 8490aae0 00000000 ndis!ndisSendNBLToFilter+0x87
    81e0451c 95b876eb 86c08788 8490aae0 00000000 ndis!NdisSendNetBufferLists+0x4f
    81e045b4 95b85bcd 86b96908 00000000 81e04738 tcpip!FlSendPackets+0x4b7
    81e045f4 95b87202 95bd2a00 00000000 00000000 tcpip!IppFragmentPackets+0x203
    81e0462c 95b86899 95bd2a00 81e04738 95bd2a00 tcpip!IppDispatchSendPacketHelper+0x259
    81e046c4 95b86099 00e04738 81e04874 85349008 tcpip!IppPacketizeDatagrams+0x7ea
    81e0481c 95b88582 00000000 00000007 95bd2a00 tcpip!IppSendDatagramsCommon+0x4ab
    81e0483c 95b577a2 86a8d468 81e04854 fffffffc tcpip!IpNlpSendDatagrams+0x4b
    81e048c4 95b576fe 86a8d468 81e049ac 875cd3b0 tcpip!IppSlowSendDatagram+0x3e
    81e04914 95b89433 86a8d468 00000001 81e049ac tcpip!IpNlpFastSendDatagram+0x3fd
    81e04a00 95b7c6be 874b2020 00000002 0000f0dd tcpip!TcpTcbSend+0x48b
    81e04a2c 95b887ec 00000004 00000000 81e04b0c tcpip!TcpFlushDelay+0xdb
    81e04a58 95b8d72d 86bf1f80 86be72a0 86be7419 tcpip!TcpPreValidatedReceive+0x23c
    81e04a74 95b8d94f 86bf1f80 86be72a0 81e04ab0 tcpip!TcpReceive+0x2d
    81e04a84 95b7f3c4 81e04a98 c000023e 00000000 tcpip!TcpNlClientReceiveDatagrams+0x12
    81e04ab0 95b7f194 95bd2be4 81e04b0c c000023e tcpip!IppDeliverListToProtocol+0x49
    81e04ad0 95b7f0c3 95bd2a00 00000006 81e04b0c tcpip!IppProcessDeliverList+0x2a
    81e04b24 95b7a72e 95bd2a00 00000006 00000000 tcpip!IppReceiveHeaderBatch+0x1da
    81e04bb4 95b7e9ea 86c0aea8 00000000 6673e801 tcpip!IpFlcReceivePackets+0xc06
    81e04c30 95b7e303 86b96908 867d6838 00000000 tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x6db
    81e04c58 8abc30b0 86b96908 867d6838 00000000 tcpip!FlReceiveNetBufferListChain+0x104
    81e04c8c 8abb58a2 00c08788 867d6838 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0xab
    81e04cb4 8abb5819 00000000 8205421b 85ee10e8 ndis!ndisIndicateSortedNetBufferLists+0x4a
    81e04e30 8ab17fc6 85ee10e8 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x129
    81e04e6c 8ab17df3 e04e9c00 81e04f5c 81e04f38 ndis!ndisDoPeriodicReceivesIndication+0x170
    81e04e90 820a9c92 85177c18 00000000 7c8ecc81 ndis!ndisPeriodicReceivesTimer+0x48
    81e04f88 820a9421 00000000 00000000 00030555 nt!KiTimerExpiration+0x659
    81e04ff4 82090f2d a70cfd10 00905a4d 00000003 nt!KiRetireDpcList+0xba
    81e04ff8 a70cfd10 00905a4d 00000003 00000004 nt!KiDispatchInterrupt+0x3d
    82090f2d e1bb80fb 0000001a 00c1850f bb830000 0xa70cfd10
    82090f31 00000000 00c1850f bb830000 00000128 0xe1bb80fb


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    kl1+27f2c
    95f08f2c ??              ???

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  kl1+27f2c

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: kl1

    IMAGE_NAME:  kl1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  48849e41

    FAILURE_BUCKET_ID:  0xD1_kl1+27f2c

    BUCKET_ID:  0xD1_kl1+27f2c

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000004, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 95f08f2c, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 821315ac
    Unable to read MiSystemVaType memory at 821117e0
     00000004

    CURRENT_IRQL:  2

    FAULTING_IP:
    kl1+27f2c
    95f08f2c ??              ???

    CUSTOMER_CRASH_COUNT:  2

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    PROCESS_NAME:  TLR.exe

    TRAP_FRAME:  81e04354 -- (.trap 0xffffffff81e04354)
    ErrCode = 00000000
    eax=00000000 ebx=00000000 ecx=853e68f0 edx=95f01cf4 esi=86c4eaf8 edi=86b8efb0
    eip=95f08f2c esp=81e043c8 ebp=86c4eaf8 iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210286
    kl1+0x27f2c:
    95f08f2c ??              ???
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 95f08f2c to 8208fdc4

    STACK_TEXT:  
    81e04354 95f08f2c badb0d00 95f01cf4 81e04386 nt!KiTrap0E+0x2ac
    WARNING: Stack unwind information not available. Following frames may be wrong.
    81e043c4 95f067b8 86c4eb96 95f0701d 8490aae0 kl1+0x27f2c
    81e04428 8aaffae4 86c08b38 00000000 00000000 kl1+0x257b8
    81e04448 8aaffb98 8490aae0 8490aae0 00000000 ndis!ndisFilterSendNetBufferLists+0x8b
    81e04460 95ac4e58 86c86810 8490aae0 00000000 ndis!NdisFSendNetBufferLists+0x18
    81e044dc 8aaffb76 86c84180 8490aae0 00000000 pacer!PcFilterSendNetBufferLists+0x232
    81e044f8 8abc364a 8490aae0 8490aae0 00000000 ndis!ndisSendNBLToFilter+0x87
    81e0451c 95b876eb 86c08788 8490aae0 00000000 ndis!NdisSendNetBufferLists+0x4f
    81e045b4 95b85bcd 86b96908 00000000 81e04738 tcpip!FlSendPackets+0x4b7
    81e045f4 95b87202 95bd2a00 00000000 00000000 tcpip!IppFragmentPackets+0x203
    81e0462c 95b86899 95bd2a00 81e04738 95bd2a00 tcpip!IppDispatchSendPacketHelper+0x259
    81e046c4 95b86099 00e04738 81e04874 85349008 tcpip!IppPacketizeDatagrams+0x7ea
    81e0481c 95b88582 00000000 00000007 95bd2a00 tcpip!IppSendDatagramsCommon+0x4ab
    81e0483c 95b577a2 86a8d468 81e04854 fffffffc tcpip!IpNlpSendDatagrams+0x4b
    81e048c4 95b576fe 86a8d468 81e049ac 875cd3b0 tcpip!IppSlowSendDatagram+0x3e
    81e04914 95b89433 86a8d468 00000001 81e049ac tcpip!IpNlpFastSendDatagram+0x3fd
    81e04a00 95b7c6be 874b2020 00000002 0000f0dd tcpip!TcpTcbSend+0x48b
    81e04a2c 95b887ec 00000004 00000000 81e04b0c tcpip!TcpFlushDelay+0xdb
    81e04a58 95b8d72d 86bf1f80 86be72a0 86be7419 tcpip!TcpPreValidatedReceive+0x23c
    81e04a74 95b8d94f 86bf1f80 86be72a0 81e04ab0 tcpip!TcpReceive+0x2d
    81e04a84 95b7f3c4 81e04a98 c000023e 00000000 tcpip!TcpNlClientReceiveDatagrams+0x12
    81e04ab0 95b7f194 95bd2be4 81e04b0c c000023e tcpip!IppDeliverListToProtocol+0x49
    81e04ad0 95b7f0c3 95bd2a00 00000006 81e04b0c tcpip!IppProcessDeliverList+0x2a
    81e04b24 95b7a72e 95bd2a00 00000006 00000000 tcpip!IppReceiveHeaderBatch+0x1da
    81e04bb4 95b7e9ea 86c0aea8 00000000 6673e801 tcpip!IpFlcReceivePackets+0xc06
    81e04c30 95b7e303 86b96908 867d6838 00000000 tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x6db
    81e04c58 8abc30b0 86b96908 867d6838 00000000 tcpip!FlReceiveNetBufferListChain+0x104
    81e04c8c 8abb58a2 00c08788 867d6838 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0xab
    81e04cb4 8abb5819 00000000 8205421b 85ee10e8 ndis!ndisIndicateSortedNetBufferLists+0x4a
    81e04e30 8ab17fc6 85ee10e8 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x129
    81e04e6c 8ab17df3 e04e9c00 81e04f5c 81e04f38 ndis!ndisDoPeriodicReceivesIndication+0x170
    81e04e90 820a9c92 85177c18 00000000 7c8ecc81 ndis!ndisPeriodicReceivesTimer+0x48
    81e04f88 820a9421 00000000 00000000 00030555 nt!KiTimerExpiration+0x659
    81e04ff4 82090f2d a70cfd10 00905a4d 00000003 nt!KiRetireDpcList+0xba
    81e04ff8 a70cfd10 00905a4d 00000003 00000004 nt!KiDispatchInterrupt+0x3d
    82090f2d e1bb80fb 0000001a 00c1850f bb830000 0xa70cfd10
    82090f31 00000000 00c1850f bb830000 00000128 0xe1bb80fb


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    kl1+27f2c
    95f08f2c ??              ???

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  kl1+27f2c

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: kl1

    IMAGE_NAME:  kl1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  48849e41

    FAILURE_BUCKET_ID:  0xD1_kl1+27f2c

    BUCKET_ID:  0xD1_kl1+27f2c

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

    2009年9月17日 1:43
  • 估计你计算机的卡巴斯基软件与游戏The Last Remnant之间有兼容性问题导致蓝屏了,建议卸载其中一方看看。

    2009年9月17日 4:12