none
为什么我的电脑(Windows Vista™ Ultimate Service pack 2 )总蓝屏? RRS feed

  • 问题

  • 只要是有接通宽带就保证会在某个不确定的时刻蓝屏,真的是很可恶!!!
    要怎么解决?请给予协助,谢谢。
    0×000000D1(Ox00000000,Ox00000002,Ox00000008,Ox00000000)
    2009年8月2日 14:01

全部回复

  • 请用windebug分析一下,把结果发上来,以便进一步分析.


    1、首先下载windebug
    http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
    2、 启动 windbg, windbg界面: file->symbol file path (ctrl+s) 输入:
    SRV*c:\temp*http://msdl.microsoft.com/download/symbols,然后确定
    3. windbg界面: file->open crash dump(ctrl+d),打开9. 打开例如C:\Windows\Minidump\Mini122208-01.dmp后,等待提示
    当出现 Use !analyze -v to get detailed debugging information. 字样后,在下面输入框
    !analyze -v
    4. 等待分析完毕,把结果发上来。


    从你描述上来看,是网卡驱动导致的可能性比较大,或者你更换另一版本的VISTA版本的网卡驱动试试。
    2009年8月2日 14:17
  • Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\Mini080209-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (3 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
    Machine Name:
    Kernel base = 0x82c18000 PsLoadedModuleList = 0x82d2fc70
    Debug session time: Sun Aug  2 21:16:08.451 2009 (GMT+8)
    System Uptime: 0 days 9:00:14.423
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {0, 2, 8, 0}

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

    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: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: 00000000, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 82d4f868
    Unable to read MiSystemVaType memory at 82d2f420
     00000000 

    CURRENT_IRQL:  2

    FAULTING_IP: 
    +65ce952f021bdce8
    00000000 ??              ???

    PROCESS_NAME:  System

    CUSTOMER_CRASH_COUNT:  2

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    TRAP_FRAME:  8b9848bc -- (.trap 0xffffffff8b9848bc)
    ErrCode = 00000010
    eax=87d3a510 ebx=00000000 ecx=00000000 edx=00000000 esi=87d3a630 edi=8b984a90
    eip=00000000 esp=8b984930 ebp=8b984aa8 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    00000000 ??              ???
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 00000000 to 82c65fb9

    FAILED_INSTRUCTION_ADDRESS: 
    +65ce952f021bdce8
    00000000 ??              ???

    STACK_TEXT:  
    8b9848bc 00000000 badb0d00 00000000 87c43018 nt!KiTrap0E+0x2e1
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    8b98492c 937d8979 00000000 00000016 8b984b44 0x0
    8b984aa8 936fe426 87d3a510 00000016 8b984b44 HdFwLH+0x5979
    8b984bd0 83478b03 8766e5d0 8b984bf0 85fe2244 tdx!TdxEventReceiveMessagesTransportAddress+0x48e
    8b984c08 83473eb3 00000000 00000001 00000000 tcpip!UdpDeliverDatagrams+0x23b
    8b984c54 83473f00 87203b38 00d83b80 8b984c90 tcpip!UdpReceiveDatagrams+0x112
    8b984c64 834736e3 8b984c78 c000023e 00000000 tcpip!UdpNlClientReceiveDatagrams+0x12
    8b984c90 83473110 834c9008 8b984ce4 c000023e tcpip!IppDeliverListToProtocol+0x49
    8b984cb0 83473560 834c8c90 00000011 8b984ce4 tcpip!IppProcessDeliverList+0x2a
    8b984d08 83457e95 834c8c90 00000011 82d1a13c tcpip!IppReceiveHeaderBatch+0x1eb
    8b984d30 82e25865 8692b4b8 004c8c90 855ab2d8 tcpip!IppLoopbackTransmit+0x52
    8b984d44 82cbde22 872035a0 00000000 855ab2d8 nt!IopProcessWorkItem+0x23
    8b984d7c 82dedc42 872035a0 d7ace31c 00000000 nt!ExpWorkerThread+0xfd
    8b984dc0 82c56efe 82cbdd25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    HdFwLH+5979
    937d8979 ??              ???

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  HdFwLH+5979

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: HdFwLH

    IMAGE_NAME:  HdFwLH.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  480805fe

    FAILURE_BUCKET_ID:  0xD1_CODE_AV_NULL_IP_HdFwLH+5979

    BUCKET_ID:  0xD1_CODE_AV_NULL_IP_HdFwLH+5979

    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: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: 00000000, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 82d4f868
    Unable to read MiSystemVaType memory at 82d2f420
     00000000 

    CURRENT_IRQL:  2

    FAULTING_IP: 
    +65ce952f021bdce8
    00000000 ??              ???

    PROCESS_NAME:  System

    CUSTOMER_CRASH_COUNT:  2

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    TRAP_FRAME:  8b9848bc -- (.trap 0xffffffff8b9848bc)
    ErrCode = 00000010
    eax=87d3a510 ebx=00000000 ecx=00000000 edx=00000000 esi=87d3a630 edi=8b984a90
    eip=00000000 esp=8b984930 ebp=8b984aa8 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    00000000 ??              ???
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 00000000 to 82c65fb9

    FAILED_INSTRUCTION_ADDRESS: 
    +65ce952f021bdce8
    00000000 ??              ???

    STACK_TEXT:  
    8b9848bc 00000000 badb0d00 00000000 87c43018 nt!KiTrap0E+0x2e1
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    8b98492c 937d8979 00000000 00000016 8b984b44 0x0
    8b984aa8 936fe426 87d3a510 00000016 8b984b44 HdFwLH+0x5979
    8b984bd0 83478b03 8766e5d0 8b984bf0 85fe2244 tdx!TdxEventReceiveMessagesTransportAddress+0x48e
    8b984c08 83473eb3 00000000 00000001 00000000 tcpip!UdpDeliverDatagrams+0x23b
    8b984c54 83473f00 87203b38 00d83b80 8b984c90 tcpip!UdpReceiveDatagrams+0x112
    8b984c64 834736e3 8b984c78 c000023e 00000000 tcpip!UdpNlClientReceiveDatagrams+0x12
    8b984c90 83473110 834c9008 8b984ce4 c000023e tcpip!IppDeliverListToProtocol+0x49
    8b984cb0 83473560 834c8c90 00000011 8b984ce4 tcpip!IppProcessDeliverList+0x2a
    8b984d08 83457e95 834c8c90 00000011 82d1a13c tcpip!IppReceiveHeaderBatch+0x1eb
    8b984d30 82e25865 8692b4b8 004c8c90 855ab2d8 tcpip!IppLoopbackTransmit+0x52
    8b984d44 82cbde22 872035a0 00000000 855ab2d8 nt!IopProcessWorkItem+0x23
    8b984d7c 82dedc42 872035a0 d7ace31c 00000000 nt!ExpWorkerThread+0xfd
    8b984dc0 82c56efe 82cbdd25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    HdFwLH+5979
    937d8979 ??              ???

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  HdFwLH+5979

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: HdFwLH

    IMAGE_NAME:  HdFwLH.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  480805fe

    FAILURE_BUCKET_ID:  0xD1_CODE_AV_NULL_IP_HdFwLH+5979

    BUCKET_ID:  0xD1_CODE_AV_NULL_IP_HdFwLH+5979

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

    2009年8月2日 14:25
  • 这是分析结果,谢谢。
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\Mini080209-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (3 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
    Machine Name:
    Kernel base = 0x82c18000 PsLoadedModuleList = 0x82d2fc70
    Debug session time: Sun Aug  2 21:16:08.451 2009 (GMT+8)
    System Uptime: 0 days 9:00:14.423
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {0, 2, 8, 0}

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

    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: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: 00000000, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 82d4f868
    Unable to read MiSystemVaType memory at 82d2f420
     00000000 

    CURRENT_IRQL:  2

    FAULTING_IP: 
    +65ce952f021bdce8
    00000000 ??              ???

    PROCESS_NAME:  System

    CUSTOMER_CRASH_COUNT:  2

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    TRAP_FRAME:  8b9848bc -- (.trap 0xffffffff8b9848bc)
    ErrCode = 00000010
    eax=87d3a510 ebx=00000000 ecx=00000000 edx=00000000 esi=87d3a630 edi=8b984a90
    eip=00000000 esp=8b984930 ebp=8b984aa8 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    00000000 ??              ???
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 00000000 to 82c65fb9

    FAILED_INSTRUCTION_ADDRESS: 
    +65ce952f021bdce8
    00000000 ??              ???

    STACK_TEXT:  
    8b9848bc 00000000 badb0d00 00000000 87c43018 nt!KiTrap0E+0x2e1
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    8b98492c 937d8979 00000000 00000016 8b984b44 0x0
    8b984aa8 936fe426 87d3a510 00000016 8b984b44 HdFwLH+0x5979
    8b984bd0 83478b03 8766e5d0 8b984bf0 85fe2244 tdx!TdxEventReceiveMessagesTransportAddress+0x48e
    8b984c08 83473eb3 00000000 00000001 00000000 tcpip!UdpDeliverDatagrams+0x23b
    8b984c54 83473f00 87203b38 00d83b80 8b984c90 tcpip!UdpReceiveDatagrams+0x112
    8b984c64 834736e3 8b984c78 c000023e 00000000 tcpip!UdpNlClientReceiveDatagrams+0x12
    8b984c90 83473110 834c9008 8b984ce4 c000023e tcpip!IppDeliverListToProtocol+0x49
    8b984cb0 83473560 834c8c90 00000011 8b984ce4 tcpip!IppProcessDeliverList+0x2a
    8b984d08 83457e95 834c8c90 00000011 82d1a13c tcpip!IppReceiveHeaderBatch+0x1eb
    8b984d30 82e25865 8692b4b8 004c8c90 855ab2d8 tcpip!IppLoopbackTransmit+0x52
    8b984d44 82cbde22 872035a0 00000000 855ab2d8 nt!IopProcessWorkItem+0x23
    8b984d7c 82dedc42 872035a0 d7ace31c 00000000 nt!ExpWorkerThread+0xfd
    8b984dc0 82c56efe 82cbdd25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    HdFwLH+5979
    937d8979 ??              ???

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  HdFwLH+5979

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: HdFwLH

    IMAGE_NAME:  HdFwLH.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  480805fe

    FAILURE_BUCKET_ID:  0xD1_CODE_AV_NULL_IP_HdFwLH+5979

    BUCKET_ID:  0xD1_CODE_AV_NULL_IP_HdFwLH+5979

    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: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: 00000000, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 82d4f868
    Unable to read MiSystemVaType memory at 82d2f420
     00000000 

    CURRENT_IRQL:  2

    FAULTING_IP: 
    +65ce952f021bdce8
    00000000 ??              ???

    PROCESS_NAME:  System

    CUSTOMER_CRASH_COUNT:  2

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    TRAP_FRAME:  8b9848bc -- (.trap 0xffffffff8b9848bc)
    ErrCode = 00000010
    eax=87d3a510 ebx=00000000 ecx=00000000 edx=00000000 esi=87d3a630 edi=8b984a90
    eip=00000000 esp=8b984930 ebp=8b984aa8 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    00000000 ??              ???
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 00000000 to 82c65fb9

    FAILED_INSTRUCTION_ADDRESS: 
    +65ce952f021bdce8
    00000000 ??              ???

    STACK_TEXT:  
    8b9848bc 00000000 badb0d00 00000000 87c43018 nt!KiTrap0E+0x2e1
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    8b98492c 937d8979 00000000 00000016 8b984b44 0x0
    8b984aa8 936fe426 87d3a510 00000016 8b984b44 HdFwLH+0x5979
    8b984bd0 83478b03 8766e5d0 8b984bf0 85fe2244 tdx!TdxEventReceiveMessagesTransportAddress+0x48e
    8b984c08 83473eb3 00000000 00000001 00000000 tcpip!UdpDeliverDatagrams+0x23b
    8b984c54 83473f00 87203b38 00d83b80 8b984c90 tcpip!UdpReceiveDatagrams+0x112
    8b984c64 834736e3 8b984c78 c000023e 00000000 tcpip!UdpNlClientReceiveDatagrams+0x12
    8b984c90 83473110 834c9008 8b984ce4 c000023e tcpip!IppDeliverListToProtocol+0x49
    8b984cb0 83473560 834c8c90 00000011 8b984ce4 tcpip!IppProcessDeliverList+0x2a
    8b984d08 83457e95 834c8c90 00000011 82d1a13c tcpip!IppReceiveHeaderBatch+0x1eb
    8b984d30 82e25865 8692b4b8 004c8c90 855ab2d8 tcpip!IppLoopbackTransmit+0x52
    8b984d44 82cbde22 872035a0 00000000 855ab2d8 nt!IopProcessWorkItem+0x23
    8b984d7c 82dedc42 872035a0 d7ace31c 00000000 nt!ExpWorkerThread+0xfd
    8b984dc0 82c56efe 82cbdd25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    HdFwLH+5979
    937d8979 ??              ???

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  HdFwLH+5979

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: HdFwLH

    IMAGE_NAME:  HdFwLH.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  480805fe

    FAILURE_BUCKET_ID:  0xD1_CODE_AV_NULL_IP_HdFwLH+5979

    BUCKET_ID:  0xD1_CODE_AV_NULL_IP_HdFwLH+5979

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


    肥嘟嘟左卫门
    2009年8月2日 14:28
  • 一個相關幫助:

    电脑蓝屏。HdFwLH.sys错误,请问高手HdFwLH.sys是什么东西?
    http://zhidao.baidu.com/question/63186306.html
    Folding@Home
    2009年8月2日 14:56
  • 谢谢回复。不过问题尚未解决。
    我的网卡是:NVIDIA nForce 10/100 Mbps Ethernet

    肥嘟嘟左卫门
    2009年8月2日 15:03
  • 請問你的意思是在卸載該軟件後, 上網依舊不定時藍屏嗎?
    Folding@Home
    2009年8月2日 15:04
  • 不是,
    我的意思是“相關幫助“里的内容对我没有帮助

    顺便提供自己的网卡型号

    肥嘟嘟左卫门
    2009年8月2日 15:08
  • 补充:仔细一想,自己确实有江民防火墙,卸载一下试一试
    肥嘟嘟左卫门
    2009年8月2日 15:11
  • 因為從你的 BSOD 診斷分析報告中看到, 導致你此次藍屏與一個文件名為 Hdfwlh.sys 的驅動程序有關.

    透過網路檢索, 我找到了上述帖子和下面一個相關文章.

    Hdfwlh.sys driver .sys information
    http://dllinfo.dll-free-download.org/h/41778-hdfwlh.sys.html

    另外, 如果你要卸載該軟件, 建議在卸載前手動創建一個系統還原點, 已被不時之需. 同時卸載工作, 如果當前用戶不是管理員帳戶的話, 請先注銷, 然後以管理員用戶身份登錄桌面, 并斷開網路後, 進行卸載.


    Folding@Home
    2009年8月2日 15:14
  • 谢谢你的帮助,目前已卸载完毕,观察情况中。
    肥嘟嘟左卫门
    2009年8月2日 15:18
  • 如之後在上網時沒有發生不定時藍屏, 建議就此問題向軟件廠商進行反饋.


    新佑衛門敬上 - Folding@Home
    2009年8月2日 15:21
  • 再補充一個 Microsoft 幫助和支持, 可以在以後發生 BSOD 時, 作為第一手參考資料.

    易宝典:Windows常见蓝屏故障分析(MVP 撰稿)
    http://support.microsoft.com/kb/972602/zh-cn
    小葉子敬上 - Folding@Home
    2009年8月2日 15:27
  • 恩,谢谢。


    肥嘟嘟左卫门
    2009年8月2日 15:27
  • 把江民防火墙先卸载掉,然后开启系统自带的防火墙,观察一些日子看会否再发生蓝屏现象。
    2009年8月2日 23:13
  • 你好

    错误名称 0x000000D1:DRIVER_IRQL_NOT_LESS_OR_EQUAL
    故障分析 0x000000D1错误表示硬件设备的驱动程序遇到了问题。这个错误一般是因为硬件设备驱动程序存在BUG或安装不正确引起的。如果遇到0x000000D1错误,建议检查一下完整的蓝屏故障提示,看看有没有提到引起错误的具体是哪个文件,如果在蓝屏故障提示中看到某驱动程序的文件名,则表示相应的驱动程序存在BUG或安装不正确。例如,假设引起0x000000D1蓝屏故障的文件名为NV4.SYS,则可能是nVIDIA Geforce显卡驱动程序引起的问题;假设引起0x000000D1蓝屏故障的文件名为ACPI.SYS,则可能是ACPI高级电源选项驱动程序引起的问题,等等。


    Smile service,common progress!
    2011年1月2日 15:12