locked
KB961373 & KB959426 Hotfix Cause BlueScreen RRS feed

  • 問題

  • client電腦的環境都是Windows XP SP3,最近透過Windows Update後,安裝了KB961373 & KB959426這兩支Hotfix後,就陸續開始出現BlueScreen,已經將近3,40台都有同樣的情形,雖然有的重開機1,2次就好了,但有的電腦會重複發生。看MiniDump的結果又都不盡相同,所以判斷並不是硬體造成的,想請教一下否有解決的方法?

    • 已變更類型 Vincent Lin 2009年5月13日 上午 05:56
    • 已變更類型 Vincent Lin 2009年7月27日 上午 03:19
    2009年5月7日 上午 03:47

解答

  • 已經解決了,非常謝謝各位的幫忙。
    最後的結果是整批電腦BIOS需要更新,所以只有影響該批電腦而以!

    • 已標示為解答 Vincent Lin 2009年7月27日 上午 03:20
    2009年7月27日 上午 03:16

所有回覆

  • HI:
    藍色畫面上應該會有錯誤代碼和錯誤訊息
    請貼出來一下

    謝謝

    2009年5月7日 上午 04:50
  • 其實每一台的結果都不一樣。

    其中一台,Minidump debug:
    Probably caused by : rdbss.sys ( rdbss!RxTableLookupName+7f )
    BugCheck 1000007E, {c0000005, 8050fce3, ba4eba98, ba4eb794}
    Probably caused by : memory_corruption ( nt!MiFlushSectionInternal+59 )

    另一台
    BugCheck 100000C5, {60, 2, 1, 8054c10d}
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+107 )

    再另一台
    BugCheck C2, {7, cd4, 530053, 891b5528}
    Probably caused by : SYMTDI.SYS ( SYMTDI+256bc )


    其中一台藍色畫面上的代碼:
    STOP:0X00000019(0X00000020,0X00C3B340,0X00C3B350,0X0A20203)

    2009年5月7日 上午 06:31
  • HI:
    0X00000019那台,請先從驅動程式開始檢查或更新
    再來RAM和硬碟
    所有電腦配備都相同嗎
    SYMTDI.SYS這應該是Symantec的產品所使用的,可以向它們詢問

    謝謝

    • 已編輯 IronMouse 2009年5月7日 上午 09:23
    2009年5月7日 上午 07:06
  • 所有的配備都相同,
    在安裝更新前都沒有問題,
    可是安裝更新完這兩個星期內就陸續發生了這3,40台的BlueScreen,
    所以我們並不認為是驅動程式or硬體的問題,
    因為其他同型上百台的電腦也並沒有問題。

    其實國外也有同樣的反應,
    而且並不是單一型號或品牌的電腦,
    似乎都有同樣的問題。
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windowsxp.security_admin&tid=6bd8ca0b-d8e4-4f9f-a849-58460ceacc8f&cat=en_US_649a30ca-5c6a-454c-995f-663a9bdbd12f&lang=en&cr=US&sloc=&p=1

    不過還是非常感謝提供相關的建議!

    2009年5月7日 上午 07:40
  • 你先挑一台有問題的電腦..把兩個更新都解除安裝
    解除安裝後在該台電腦上執行下面動作

    1.開始->執行->msconfig
    2.服務->勾選"隱藏所有Microsoft服務"->全部停用
    3.啟動->全部停用
    4.套用->重新開機
    5.重新開機後在去把兩個更新安裝上去.安裝完後重新開機測試看看是不是還會有此問題

    可能是安裝完更新後跟已安裝的軟體有衝突才會這樣

    2009年5月7日 上午 08:45
  • 這個是很實在的一個方法,但卻有點難以執行。
    因為公司內安裝的軟體很多,似乎很難這樣來進行測試。
    更難的在於有些電腦發生BlueScreen重開後就沒事了,
    有些電腦會重複的發生,
    但同樣一台電腦每次的錯誤又都不一樣,
    也沒辦法預期什麼時候會再發生。
    以同一台電腦為例,所發生的四次(4/30 2次,5/4&5/18各一次),
    所debug的詳細資訊如下,
    沒辦法歸納出究竟是哪裡出現問題,
    而且就算做了什麼樣的修改也沒辦法知道有沒有效,
    除了下一次的BSOD再發生。
    像這一台電腦已經移除了這兩個hotfix可是還是會發生BlueScreen,
    可是大規模的BSOD確實是在這兩個hotfix安裝以後才開始的,
    已經不知該如何處理了。


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


    Loading Dump File [z:\windows\minidump\Mini043009-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*c:\symbols*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.090206-1234
    Machine Name:
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
    Debug session time: Thu Apr 30 11:17:39.953 2009 (GMT+8)
    System Uptime: 0 days 18:08:02.641
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000C5, {5, 2, 1, 8054c10f}

    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+109 )

    Followup: Pool_corruption
    ---------

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

    DRIVER_CORRUPTED_EXPOOL (c5)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is
    caused by drivers that have corrupted the system pool.  Run the driver
    verifier against any new (or suspect) drivers, and if that doesn't turn up
    the culprit, then use gflags to enable special pool.
    Arguments:
    Arg1: 00000005, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 8054c10f, address which referenced memory

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


    BUGCHECK_STR:  0xC5_2

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!ExDeferredFreePool+109
    8054c10f 895f04          mov     dword ptr [edi+4],ebx

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    PROCESS_NAME:  KillVirus.exe

    LAST_CONTROL_TRANSFER:  from 8054c75f to 8054c10f

    STACK_TEXT: 
    94a4d884 8054c75f 00000001 877a5d18 c0000034 nt!ExDeferredFreePool+0x109
    94a4d8c4 b9d3e8f2 87f8f9a0 00000000 94a4d8f8 nt!ExFreePoolWithTag+0x47f
    94a4d8d4 b9d36431 8936a618 87f8f9a0 87803918 Mup!DfsDeleteFcb_Real+0x10
    94a4d8f8 b9d3678f 87803818 8936a618 87f8f9a0 Mup!DfsPostProcessRelativeOpen+0x4c
    94a4d928 b9d33c44 87803818 8936a618 88c0ea20 Mup!DfsPassThroughRelativeOpen+0x1a0
    94a4d998 b9d31fd6 8936a618 88feb680 87803818 Mup!DfsCommonCreate+0x116
    94a4d9e0 b9d32076 88feb680 87803818 87803828 Mup!DfsFsdCreate+0xe0
    94a4da38 804f019f 88feb680 87803818 87803818 Mup!MupCreate+0xbc
    94a4da48 805841fa 88f69b50 8734d378 94a4dc18 nt!IopfCallDriver+0x31
    94a4db28 8058461c 88feb680 00000000 892484d0 nt!IopParseDevice+0xa12
    94a4db60 805c002d 88f69b50 00000000 892484d0 nt!IopParseFile+0x46
    94a4dbd8 805bc9dc 0000000c 94a4dc18 00000040 nt!ObpLookupObjectName+0x119
    94a4dc2c 80577033 00000000 00000000 00000101 nt!ObOpenObjectByName+0xea
    94a4dca8 805779aa 0012ef1c 00100001 0012eec0 nt!IopCreateFile+0x407
    94a4dd04 8057b1a9 0012ef1c 00100001 0012eec0 nt!IoCreateFile+0x8e
    94a4dd44 8054262c 0012ef1c 00100001 0012eec0 nt!NtOpenFile+0x27
    94a4dd44 7c92e514 0012ef1c 00100001 0012eec0 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012f18c 00000000 00000000 00000000 00000000 0x7c92e514


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!ExDeferredFreePool+109
    8054c10f 895f04          mov     dword ptr [edi+4],ebx

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!ExDeferredFreePool+109

    FOLLOWUP_NAME:  Pool_corruption

    IMAGE_NAME:  Pool_Corruption

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    MODULE_NAME: Pool_Corruption

    FAILURE_BUCKET_ID:  0xC5_2_nt!ExDeferredFreePool+109

    BUCKET_ID:  0xC5_2_nt!ExDeferredFreePool+109

    Followup: Pool_corruption
    ---------


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


    Loading Dump File [z:\windows\minidump\Mini043009-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*c:\symbols*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.090206-1234
    Machine Name:
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
    Debug session time: Thu Apr 30 11:38:29.419 2009 (GMT+8)
    System Uptime: 0 days 0:19:27.030
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    .............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000C5, {60, 2, 1, 8054c10d}

    Unable to load image wpsdrvnt.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for wpsdrvnt.sys
    *** ERROR: Module load completed but symbols could not be loaded for wpsdrvnt.sys
    Unable to load image SYMEVENT.SYS, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SYMEVENT.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+107 )

    Followup: Pool_corruption
    ---------

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

    DRIVER_CORRUPTED_EXPOOL (c5)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is
    caused by drivers that have corrupted the system pool.  Run the driver
    verifier against any new (or suspect) drivers, and if that doesn't turn up
    the culprit, then use gflags to enable special pool.
    Arguments:
    Arg1: 00000060, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 8054c10d, address which referenced memory

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


    BUGCHECK_STR:  0xC5_2

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!ExDeferredFreePool+107
    8054c10d 893b            mov     dword ptr [ebx],edi

    CUSTOMER_CRASH_COUNT:  2

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    PROCESS_NAME:  Iap.exe

    LAST_CONTROL_TRANSFER:  from 8054c75f to 8054c10d

    STACK_TEXT: 
    941d7ab0 8054c75f 00000001 000028f8 87af4be8 nt!ExDeferredFreePool+0x107
    941d7af0 8054c95f 87af4be8 00000000 941d7b1c nt!ExFreePoolWithTag+0x47f
    941d7b00 b670f65b 87af4be8 805649e4 e199fab8 nt!ExFreePool+0xf
    WARNING: Stack unwind information not available. Following frames may be wrong.
    941d7b1c 805d10bc 89c46a50 000001c8 941d7b5c wpsdrvnt+0x465b
    941d7b3c 805b2421 89c46a50 000001c8 941d7b5c nt!PsCallImageNotifyRoutines+0x36
    941d7b84 805b2efe 893da240 007d0000 941d7c54 nt!MiMapViewOfImageSection+0x4c1
    941d7be0 805b32c3 00000004 8911c788 941d7c54 nt!MmMapViewOfSection+0x13c
    941d7c70 956d72e9 000001cc ffffffff 0153e964 nt!NtMapViewOfSection+0x2bd
    941d7d34 8054262c 000001cc ffffffff 0153e964 SYMEVENT+0x142e9
    941d7d34 00000023 000001cc ffffffff 0153e964 nt!KiFastCallEntry+0xfc
    941d7da4 00000000 00000001 ffffffff 0000003b 0x23


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!ExDeferredFreePool+107
    8054c10d 893b            mov     dword ptr [ebx],edi

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!ExDeferredFreePool+107

    FOLLOWUP_NAME:  Pool_corruption

    IMAGE_NAME:  Pool_Corruption

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    MODULE_NAME: Pool_Corruption

    FAILURE_BUCKET_ID:  0xC5_2_nt!ExDeferredFreePool+107

    BUCKET_ID:  0xC5_2_nt!ExDeferredFreePool+107

    Followup: Pool_corruption
    ---------

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


    Loading Dump File [z:\windows\minidump\Mini050409-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*c:\symbols*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
    Built by: 2600.xpsp_sp3_gdr.090206-1234
    Machine Name:
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
    Debug session time: Thu Apr 30 19:08:52.967 2009 (GMT+8)
    System Uptime: 0 days 2:43:52.095
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    ...................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {6df9e4, 1c, 0, 80538bf1}

    *** WARNING: Unable to verify timestamp for teefer2.sys
    *** ERROR: Module load completed but symbols could not be loaded for teefer2.sys
    Probably caused by : teefer2.sys ( teefer2+61d9 )

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

    1: 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: 006df9e4, memory referenced
    Arg2: 0000001c, 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: 80538bf1, address which referenced memory

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


    READ_ADDRESS:  006df9e4

    CURRENT_IRQL:  1c

    FAULTING_IP:
    nt!ExpCopyThreadInfo+d
    80538bf1 8b8744010000    mov     eax,dword ptr [edi+144h]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0xA

    TRAP_FRAME:  b719991c -- (.trap 0xffffffffb719991c)
    ErrCode = 00000000
    eax=00000000 ebx=a5cfc138 ecx=ba340538 edx=80554882 esi=a5cfd8f0 edi=006df8a0
    eip=80538bf1 esp=b7199990 ebp=b7199998 iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
    nt!ExpCopyThreadInfo+0xd:
    80538bf1 8b8744010000    mov     eax,dword ptr [edi+144h] ds:0023:006df9e4=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 80538bf1 to 805456f0

    STACK_TEXT: 
    b719991c 80538bf1 badb0d00 80554882 c052e860 nt!KiTrap0E+0x238
    b7199998 805390e5 a5cfd8f0 006df8a0 806eda00 nt!ExpCopyThreadInfo+0xd
    b7199a30 8061286c 87f08000 00010000 b7199c5c nt!ExpGetProcessInformation+0x169
    b7199c78 8054262c 00000005 87f08000 00010000 nt!NtQuerySystemInformation+0x7b6
    b7199c78 80501ad1 00000005 87f08000 00010000 nt!KiFastCallEntry+0xfc
    b7199d00 b6a7e1d9 00000005 87f08000 00010000 nt!ZwQuerySystemInformation+0x11
    WARNING: Stack unwind information not available. Following frames may be wrong.
    00000000 00000000 00000000 00000000 00000000 teefer2+0x61d9


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    teefer2+61d9
    b6a7e1d9 ??              ???

    SYMBOL_STACK_INDEX:  6

    SYMBOL_NAME:  teefer2+61d9

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: teefer2

    IMAGE_NAME:  teefer2.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  48f4f1d4

    FAILURE_BUCKET_ID:  0xA_teefer2+61d9

    BUCKET_ID:  0xA_teefer2+61d9

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

     

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


    Loading Dump File [z:\windows\minidump\Mini051909-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*c:\symbols*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
    Built by: 2600.xpsp_sp3_gdr.090206-1234
    Machine Name:
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
    Debug session time: Mon May 18 18:19:45.896 2009 (GMT+8)
    System Uptime: 0 days 3:11:06.153
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    ...................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {cbd9c0, 2, 1, 805276aa}

    Probably caused by : afd.sys ( afd!AfdFreePollInfo+3a )

    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: 00cbd9c0, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 805276aa, address which referenced memory

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


    WRITE_ADDRESS:  00cbd9c0

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!ObfDereferenceObject+1c
    805276aa f00fc13e        lock xadd dword ptr [esi],edi

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0xA

    TRAP_FRAME:  80552230 -- (.trap 0xffffffff80552230)
    ErrCode = 00000002
    eax=87fa1f10 ebx=00cbd9d8 ecx=00cbd9d8 edx=00000002 esi=00cbd9c0 edi=ffffffff
    eip=805276aa esp=805522a4 ebp=805522c0 iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
    nt!ObfDereferenceObject+0x1c:
    805276aa f00fc13e        lock xadd dword ptr [esi],edi ds:0023:00cbd9c0=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 805276aa to 805456f0

    STACK_TEXT: 
    80552230 805276aa badb0d00 00000002 ffdff120 nt!KiTrap0E+0x238
    805522ac 97c4b87f 878ebd98 89be54c0 00000000 nt!ObfDereferenceObject+0x1c
    805522c0 97c508ce 89be54c0 97c5085a 80552308 afd!AfdFreePollInfo+0x3a
    805522e0 8050320f 89be54d0 89be54c0 2ac48853 afd!AfdTimeoutPoll+0xbd
    805523fc 8050332b 8055d0c0 ffdff9c0 ffdff000 nt!KiTimerListExpire+0x14b
    80552428 80546e7f 8055d4c0 00000000 000b3289 nt!KiTimerExpiration+0xb1
    80552440 8055ce60 ffdffc50 00000000 8055ce60 nt!KiRetireDpcList+0x61
    80552450 80546d64 00000000 0000000e 00000000 nt!KiIdleThread0
    80552454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    afd!AfdFreePollInfo+3a
    97c4b87f 83c610          add     esi,10h

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  afd!AfdFreePollInfo+3a

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: afd

    IMAGE_NAME:  afd.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  48a40333

    FAILURE_BUCKET_ID:  0xA_afd!AfdFreePollInfo+3a

    BUCKET_ID:  0xA_afd!AfdFreePollInfo+3a

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

    2009年5月19日 上午 08:25
  • 前兩個dmp(Mini043009-01.dmp & Mini043009-02.dmp)藍色畫面是DRIVER_CORRUPTED_EXPOOL (c5)
    試試看更新網卡Driver看看


    後兩個dmp(Mini050409-01.dmp & Mini051909-01.dmp)藍色畫面是IRQL_NOT_LESS_OR_EQUAL (a)
    公司防毒軟體是OfficeScan嗎?有安裝他的防火牆(OfficeScan Firewall )嗎?有的話上官方網站去安裝一些更新檔看看有沒有改善
    如果是其他的防毒,建議都先更新或是移除測試看看

    以上是我的一些建議,希望可以改善你的問題

    2009年5月19日 上午 09:14
  • 已經解決了,非常謝謝各位的幫忙。
    最後的結果是整批電腦BIOS需要更新,所以只有影響該批電腦而以!

    • 已標示為解答 Vincent Lin 2009年7月27日 上午 03:20
    2009年7月27日 上午 03:16
  • 方便分享一下機型跟BIOS版本嗎?
    也方便之後的人瞭解相關資訊。 :)
    蘇老碎碎念
    資訊無涯,回頭已不見岸
    2009年7月27日 上午 03:18