各位大虾，我的电脑蓝屏了！好像是小A的问题～

xiaoyv2

  今天电脑蓝屏了！下面是我的内存转储分析，大家帮我看看是不是一定要离开小A呀？！真的舍不得！！！


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

Loading Dump File [C:\WINDOWS\Minidump\Mini120608-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.080814-1242
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Dec  6 14:27:12.921 2008 (GMT+8)
System Uptime: 0 days 3:02:54.623
Loading Kernel Symbols
........................................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, aa2f9438, a8a747f4, 0}
*** WARNING: Unable to verify timestamp for aswTdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
Probably caused by : aswTdi.SYS ( aswTdi+449 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: aa2f9438, The address that the exception occurred at
Arg3: a8a747f4, Trap Frame
Arg4: 00000000
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"
FAULTING_IP:
tcpip!TcpipBufferVirtualAddress+8
aa2f9438 f6400605        test    byte ptr [eax+6],5
TRAP_FRAME:  a8a747f4 -- (.trap 0xffffffffa8a747f4)
ErrCode = 00000000
eax=0000005c ebx=00004a2d ecx=00000000 edx=0000001f esi=0000005c edi=00000000
eip=aa2f9438 esp=a8a74868 ebp=a8a74868 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
tcpip!TcpipBufferVirtualAddress+0x8:
aa2f9438 f6400605        test    byte ptr [eax+6],5         ds:0023:00000062=??
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  Thunder5.exe
LAST_CONTROL_TRANSFER:  from aa2fc0c0 to aa2f9438
STACK_TEXT:  
a8a74868 aa2fc0c0 0000005c 00000010 85db0025 tcpip!TcpipBufferVirtualAddress+0x8
a8a74888 aa2fd973 00024689 85dba07c 86624eb8 tcpip!XsumSendChain+0x44
a8a74908 aa2fd78b 865cda48 86624eb8 85ffd0c0 tcpip!UDPSend+0x3ca
a8a7492c aa2fd7f1 00a74950 85ffd008 85dba0bc tcpip!TdiSendDatagram+0xd5
a8a74964 aa2fc149 85ffd0c0 85ffd130 85ffd0c0 tcpip!UDPSendDatagram+0x4f
a8a74980 804f0199 8680b5f8 85ffd0c0 8675d890 tcpip!TCPDispatchInternalDeviceControl+0xff
a8a74990 f7760449 85ffd178 00000000 8675d860 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
a8a749f4 f77607e2 8675d860 85ffd0c0 85ffd154 aswTdi+0x449
a8a74a54 804f0199 8675d7a8 85ffd0c0 85ffd19c aswTdi+0x7e2
a8a74aa8 804f0199 867517d8 85ffd0c0 86237778 nt!IopfCallDriver+0x31
a8a74ab8 aa233787 a8a74ba8 00000008 a8a74b1c nt!IopfCallDriver+0x31
a8a74b10 aa22ab5e 80562134 023ff83c aa22ab5e afd!AfdFastDatagramSend+0x2fd
a8a74c5c 80580325 862623b8 00000001 023ff70c afd!AfdFastIoDeviceControl+0x2a7
a8a74d00 8057917e 00000200 00000bc4 00000000 nt!IopXxxControlFile+0x255
a8a74d34 805423fc 00000200 00000bc4 00000000 nt!NtDeviceIoControlFile+0x2a
a8a74d34 7c92eb94 00000200 00000bc4 00000000 nt!KiFastCallEntry+0xfc
023ff7fc 00000000 00000000 00000000 00000000 0x7c92eb94

STACK_COMMAND:  kb
FOLLOWUP_IP:
aswTdi+449
f7760449 ??              ???
SYMBOL_STACK_INDEX:  7
SYMBOL_NAME:  aswTdi+449
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: aswTdi
IMAGE_NAME:  aswTdi.SYS
DEBUG_FLR_IMAGE_TIMESTAMP:  492d8475
FAILURE_BUCKET_ID:  0x8E_aswTdi+449
BUCKET_ID:  0x8E_aswTdi+449
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: aa2f9438, The address that the exception occurred at
Arg3: a8a747f4, Trap Frame
Arg4: 00000000
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"
FAULTING_IP:
tcpip!TcpipBufferVirtualAddress+8
aa2f9438 f6400605        test    byte ptr [eax+6],5
TRAP_FRAME:  a8a747f4 -- (.trap 0xffffffffa8a747f4)
ErrCode = 00000000
eax=0000005c ebx=00004a2d ecx=00000000 edx=0000001f esi=0000005c edi=00000000
eip=aa2f9438 esp=a8a74868 ebp=a8a74868 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
tcpip!TcpipBufferVirtualAddress+0x8:
aa2f9438 f6400605        test    byte ptr [eax+6],5         ds:0023:00000062=??
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  Thunder5.exe
LAST_CONTROL_TRANSFER:  from aa2fc0c0 to aa2f9438
STACK_TEXT:  
a8a74868 aa2fc0c0 0000005c 00000010 85db0025 tcpip!TcpipBufferVirtualAddress+0x8
a8a74888 aa2fd973 00024689 85dba07c 86624eb8 tcpip!XsumSendChain+0x44
a8a74908 aa2fd78b 865cda48 86624eb8 85ffd0c0 tcpip!UDPSend+0x3ca
a8a7492c aa2fd7f1 00a74950 85ffd008 85dba0bc tcpip!TdiSendDatagram+0xd5
a8a74964 aa2fc149 85ffd0c0 85ffd130 85ffd0c0 tcpip!UDPSendDatagram+0x4f
a8a74980 804f0199 8680b5f8 85ffd0c0 8675d890 tcpip!TCPDispatchInternalDeviceControl+0xff
a8a74990 f7760449 85ffd178 00000000 8675d860 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
a8a749f4 f77607e2 8675d860 85ffd0c0 85ffd154 aswTdi+0x449
a8a74a54 804f0199 8675d7a8 85ffd0c0 85ffd19c aswTdi+0x7e2
a8a74aa8 804f0199 867517d8 85ffd0c0 86237778 nt!IopfCallDriver+0x31
a8a74ab8 aa233787 a8a74ba8 00000008 a8a74b1c nt!IopfCallDriver+0x31
a8a74b10 aa22ab5e 80562134 023ff83c aa22ab5e afd!AfdFastDatagramSend+0x2fd
a8a74c5c 80580325 862623b8 00000001 023ff70c afd!AfdFastIoDeviceControl+0x2a7
a8a74d00 8057917e 00000200 00000bc4 00000000 nt!IopXxxControlFile+0x255
a8a74d34 805423fc 00000200 00000bc4 00000000 nt!NtDeviceIoControlFile+0x2a
a8a74d34 7c92eb94 00000200 00000bc4 00000000 nt!KiFastCallEntry+0xfc
023ff7fc 00000000 00000000 00000000 00000000 0x7c92eb94

STACK_COMMAND:  kb
FOLLOWUP_IP:
aswTdi+449
f7760449 ??              ???
SYMBOL_STACK_INDEX:  7
SYMBOL_NAME:  aswTdi+449
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: aswTdi
IMAGE_NAME:  aswTdi.SYS
DEBUG_FLR_IMAGE_TIMESTAMP:  492d8475
FAILURE_BUCKET_ID:  0x8E_aswTdi+449
BUCKET_ID:  0x8E_aswTdi+449
Followup: MachineOwner
---------

xiaoyv2

我去网上查了一下，好像因为aswTdi.sys而引发的BSOD现象还是很多的，公司也就此问题做了好几次修正，我觉得似乎应该再加一次修正了！
Version 4.6.739
December 3, 2005
added a workaround to a small bug in NetBios (might have even

caused blue screens in aswTdi.sys)

Version 4.6.665
May 22, 2005
fixed a minor problem in aswTdi.sys (that could theoretically

lead even to the "BSOD")

Version 4.5.549
December 2, 2004
fixed rare crashes in aswTdi.sys

xiaoyv2

决定了，去官方论坛整一帖子！！！

月影花痕

支持一下！希望在官方论坛能得到权威的解答！

禅师归来

反正我至今没有因为avast蓝屏过O(∩_∩)O哈哈~运气好

关9军

没遇见过

得巴

用它也没出现过蓝屏

xiaoyv2

崩溃了！又死掉一次！！！！！！！！！！！！！！！！！！！1111

hjs

俺蓝过一次，是和某知名软件冲突引起的……

ashe_vaan

可能是软件冲突导致的