Recurring BSODs caused by afd.sys. Dump data included

Hi all,
For several months the BSODs were gone but now they're back. They all have the same message: 1000008E, 80000003, 8052a828 and then a changing frame. They have the same address 8052a828 and always the same probable cause suggested by Debugwiz: afd.sys. The crashes are clearly browser-related. I have tested the memory (memtest86 v. 3.4) without any problems.

Any ideas? TIA

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini031708-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: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Mar 17 20:06:27.194 2008 (GMT+1)
System Uptime: 0 days 0:59:30.568
Loading Kernel Symbols
.......................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {80000003, 8052a828, a7230b4c, 0}



Probably caused by : afd.sys ( afd!AfdIssueDeviceControl+134 )

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

0: kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* 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: 80000003, The exception code that was not handled
Arg2: 8052a828, The address that the exception occurred at
Arg3: a7230b4c, Trap Frame
Arg4: 00000000

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




EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Ett eller flera argument r ogiltiga

FAULTING_IP:
nt!DbgBreakPoint+0
8052a828 cc int 3

TRAP_FRAME: a7230b4c -- (.trap 0xffffffffa7230b4c)
.trap 0xffffffffa7230b4c
ErrCode = 00000000
eax=00000001 ebx=86ace008 ecx=8052a95c edx=00000031 esi=00000000 edi=00000000
eip=8052a829 esp=a7230bc0 ebp=a7230bec iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000282
nt!DbgBreakPoint+0x1:
8052a829 c3 ret
.trap
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: iexplore.exe

LAST_CONTROL_TRANSFER: from a9aa5275 to 8052a829

STACK_TEXT:
a7230bbc a9aa5275 86b9ea40 00000000 8595a380 nt!DbgBreakPoint+0x1
a7230bec a9aa1e59 88058408 a7230c0c 0000000c afd!AfdIssueDeviceControl+0x134
a7230c18 a9aab5b5 88058408 00000004 00000000 afd!AfdSetEventHandler+0x2e
a7230c54 a9aab17e 880dbf90 891ea730 a7230ca4 afd!AfdCleanup+0x619
a7230c64 804ef095 8920c710 86b9ea30 86b9ea30 afd!AfdDispatch+0xbb
a7230c74 805826c7 880dbf78 89e27900 00000001 nt!IopfCallDriver+0x31
a7230ca4 805bb459 86d2d020 8920c710 001f01ff nt!IopCloseFile+0x26b
a7230cd4 805badab 86d2d020 010dbf78 89e27900 nt!ObpDecrementHandleCount+0x11b
a7230cfc 805bae49 e23834d8 880dbf90 0000d44c nt!ObpCloseHandleTableEntry+0x14d
a7230d44 805baf81 0000d44c 00000001 00000000 nt!ObpCloseHandle+0x87
a7230d58 8054086c 0000d44c 0cf6e390 7c90eb94 nt!NtClose+0x1d
a7230d58 7c90eb94 0000d44c 0cf6e390 7c90eb94 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0cf6e390 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
afd!AfdIssueDeviceControl+134
a9aa5275 e99ccbffff jmp afd!AfdIssueDeviceControl+0x134 (a9aa1e16)

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: afd!AfdIssueDeviceControl+134

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: afd

IMAGE_NAME: afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107eb5

FAILURE_BUCKET_ID: 0x8E_afd!AfdIssueDeviceControl+134

BUCKET_ID: 0x8E_afd!AfdIssueDeviceControl+134

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

eax=00000001 ebx=86ace008 ecx=8052a95c edx=00000031 esi=00000000 edi=00000000
eip=8052a829 esp=a7230bc0 ebp=a7230bec iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000282
nt!DbgBreakPoint+0x1:
8052a829 c3 ret
ChildEBP RetAddr Args to Child
a7230bbc a9aa5275 86b9ea40 00000000 8595a380 nt!DbgBreakPoint+0x1 (FPO: [0,0,0])
a7230bec a9aa1e59 88058408 a7230c0c 0000000c afd!AfdIssueDeviceControl+0x134 (FPO: [Non-Fpo])
a7230c18 a9aab5b5 88058408 00000004 00000000 afd!AfdSetEventHandler+0x2e (FPO: [Non-Fpo])
a7230c54 a9aab17e 880dbf90 891ea730 a7230ca4 afd!AfdCleanup+0x619 (FPO: [Non-Fpo])
a7230c64 804ef095 8920c710 86b9ea30 86b9ea30 afd!AfdDispatch+0xbb (FPO: [Non-Fpo])
a7230c74 805826c7 880dbf78 89e27900 00000001 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
a7230ca4 805bb459 86d2d020 8920c710 001f01ff nt!IopCloseFile+0x26b (FPO: [Non-Fpo])
a7230cd4 805badab 86d2d020 010dbf78 89e27900 nt!ObpDecrementHandleCount+0x11b (FPO: [Non-Fpo])
a7230cfc 805bae49 e23834d8 880dbf90 0000d44c nt!ObpCloseHandleTableEntry+0x14d (FPO: [Non-Fpo])
a7230d44 805baf81 0000d44c 00000001 00000000 nt!ObpCloseHandle+0x87 (FPO: [Non-Fpo])
a7230d58 8054086c 0000d44c 0cf6e390 7c90eb94 nt!NtClose+0x1d (FPO: [Non-Fpo])
a7230d58 7c90eb94 0000d44c 0cf6e390 7c90eb94 nt!KiFastCallEntry+0xfc (FPO: [0,0] TrapFrame @ a7230d64)
WARNING: Frame IP not in any known module. Following frames may be wrong.
0cf6e390 00000000 00000000 00000000 00000000 0x7c90eb94
start end module name
804d7000 806e2000 nt ntkrpamp.exe Wed Feb 28 09:38:53 2007 (45E53F9D)
806e2000 80702d00 hal halmacpi.dll Wed Aug 04 07:59:09 2004 (41107B2D)
a6599000 a659c0c0 HTTPFILT HTTPFILT.DLL Thu Apr 05 14:57:10 2007 (4614F226)
a67b5000 a67b7200 FTPFILT FTPFILT.DLL Thu Apr 05 14:57:38 2007 (4614F242)
a67c1000 a67c4780 MAILFILT MAILFILT.DLL Thu Apr 05 14:57:24 2007 (4614F234)
a67c5000 a67c7520 POP3FILT POP3FILT.DLL Thu Apr 05 14:57:20 2007 (4614F230)
a67c9000 a67cc640 DNSCACHE DNSCACHE.DLL Thu Apr 05 14:57:05 2007 (4614F221)
a67cd000 a67cfaa0 HTMLFILT HTMLFILT.DLL Thu Apr 05 14:57:13 2007 (4614F229)
a6895000 a68987e0 PROTECT PROTECT.DLL Thu Apr 05 14:57:41 2007 (4614F245)
a689d000 a689fee0 SECRET SECRET.DLL Thu Apr 05 14:57:50 2007 (4614F24E)
a68e9000 a693a480 srv srv.sys Mon Aug 14 12:34:39 2006 (44E051BF)
a6c33000 a6c73280 HTTP HTTP.sys Fri Mar 17 01:33:09 2006 (441A03C5)
a6ebc000 a6edf000 Fastfat Fastfat.SYS Wed Aug 04 08:14:15 2004 (41107EB7)
a6edf000 a6f598c0 amon amon.sys Fri Feb 09 10:39:09 2007 (45CC413D)
a704a000 a7075d80 mrxdav mrxdav.sys Tue Dec 18 10:51:33 2007 (47679825)
a7164000 a7178400 wdmaud wdmaud.sys Wed Jun 14 11:00:44 2006 (448FD03C)
a72b9000 a72e0c00 netbt netbt.sys Wed Aug 04 08:14:36 2004 (41107ECC)
a7331000 a733fd80 sysaudio sysaudio.sys Wed Aug 04 08:15:54 2004 (41107F1A)
a9801000 a982a380 atinavt2 atinavt2.sys Wed Aug 02 03:52:59 2006 (44D0057B)
a982b000 a9842480 dump_atapi dump_atapi.sys Wed Aug 04 07:59:41 2004 (41107B4D)
a98a7000 a98a9e00 BdaSup BdaSup.SYS Wed Aug 04 08:10:11 2004 (41107DC3)
a98af000 a98b1900 Dxapi Dxapi.sys Fri Aug 17 22:53:19 2001 (3B7D843F)
a999b000 a99a4340 tifsfilt tifsfilt.sys Wed Aug 29 14:37:17 2007 (46D5687D)
a99ab000 a9a19a00 mrxsmb mrxsmb.sys Fri May 05 11:41:42 2006 (445B1DD6)
a9a1a000 a9a73500 ndasfat ndasfat.sys Fri Feb 23 03:02:49 2007 (45DE4B49)
a9a74000 a9a9ea00 rdbss rdbss.sys Fri May 05 11:47:55 2006 (445B1F4B)
a9a9f000 a9ac0d00 afd afd.sys Wed Aug 04 08:14:13 2004 (41107EB5)
a9ac1000 a9b3c000 Wdf01000 Wdf01000.sys Thu Nov 02 09:54:18 2006 (4549B23A)
a9b3c000 a9b40a40 AegisP AegisP.sys Fri Jun 10 16:29:52 2005 (42A9A3E0)
a9b8c000 a9bacf00 ipnat ipnat.sys Thu Sep 30 00:28:36 2004 (415B3714)
a9bd5000 a9c02000 FILTNT FILTNT.SYS Thu Apr 05 14:56:14 2007 (4614F1EE)
a9c02000 a9c59e80 tcpip tcpip.sys Tue Oct 30 18:20:52 2007 (472767F4)
a9c5a000 a9c6c400 ipsec ipsec.sys Wed Aug 04 08:14:27 2004 (41107EC3)
a9c6d000 a9c85e80 InCDfs InCDfs.SYS Thu Mar 23 17:00:18 2006 (4422C612)
b9d7e000 b9d81b00 usbscan usbscan.sys Wed Aug 04 07:58:44 2004 (41107B14)
b9d86000 b9d88f80 mouhid mouhid.sys Fri Aug 17 22:47:57 2001 (3B7D82FD)
b9d8e000 b9d9ee80 ndasbus ndasbus.sys Fri Feb 23 03:01:17 2007 (45DE4AED)
b9d9f000 b9dd2200 update update.sys Wed Aug 04 07:58:32 2004 (41107B08)
b9de7000 b9de9580 hidusb hidusb.sys Fri Aug 17 23:02:16 2001 (3B7D8658)
b9def000 b9df1f00 ws2ifsl ws2ifsl.sys Fri Aug 17 22:55:58 2001 (3B7D84DE)
b9dfb000 b9e2b100 rdpdr rdpdr.sys Wed Aug 04 08:01:10 2004 (41107BA6)
b9e2c000 b9e3ce00 psched psched.sys Wed Aug 04 08:04:16 2004 (41107C60)
b9e3d000 b9e53680 ndiswan ndiswan.sys Wed Aug 04 08:14:30 2004 (41107EC6)
b9ea4000 b9eb3900 Cdfs Cdfs.SYS Wed Aug 04 08:14:09 2004 (41107EB1)
b9ee4000 b9eec880 Fips Fips.SYS Sat Aug 18 03:31:49 2001 (3B7DC585)
b9ef4000 b9f47000 NVSNPU NVSNPU.SYS Wed May 17 04:24:18 2006 (446A8952)
b9f47000 ba04d880 NVNRM NVNRM.SYS Wed May 17 04:24:41 2006 (446A8969)
ba04e000 ba0b0a00 dmxsens dmxsens.sys Tue Jul 22 13:12:51 2003 (3F1D1C33)
ba0b1000 ba0d4980 portcls portcls.sys Wed Aug 04 08:15:47 2004 (41107F13)
ba0d5000 ba0ea180 dmx6fire dmx6fire.sys Fri Aug 29 09:30:15 2003 (3F4F0107)
ba0eb000 ba10d680 ks ks.sys Wed Aug 04 08:15:20 2004 (41107EF8)
ba10e000 ba130e80 USBPORT USBPORT.SYS Wed Aug 04 08:08:34 2004 (41107D62)
ba131000 ba144980 parport parport.sys Wed Aug 04 07:59:04 2004 (41107B28)
ba145000 ba158780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 08:07:04 2004 (41107D08)
ba159000 ba36d000 ati2mtag ati2mtag.sys Fri Feb 02 21:03:24 2007 (45C3990C)
ba36d000 ba36f280 rasacd rasacd.sys Fri Aug 17 22:55:39 2001 (3B7D84CB)
ba375000 ba377200 InCDrec InCDrec.SYS Thu Mar 23 17:00:29 2006 (4422C61D)
ba379000 ba37ca00 kbdhid kbdhid.sys Wed Aug 04 07:58:33 2004 (41107B09)
ba3ad000 ba3b0c80 mssmbios mssmbios.sys Wed Aug 04 08:07:47 2004 (41107D33)
ba3cd000 ba3cf580 ndistapi ndistapi.sys Fri Aug 17 22:55:29 2001 (3B7D84C1)
ba3ed000 ba3f0c80 serenum serenum.sys Wed Aug 04 07:59:06 2004 (41107B2A)
ba4a5000 ba4e1680 lfsfilt lfsfilt.sys Fri Feb 23 03:02:42 2007 (45DE4B42)
ba4e2000 ba4fc580 Mup Mup.sys Wed Aug 04 08:15:20 2004 (41107EF8)
ba4fd000 ba51aec0 snapman snapman.sys Fri Jul 13 12:03:56 2007 (46974E0C)
ba51b000 ba573580 tdrpman tdrpman.sys Mon Oct 29 13:29:10 2007 (4725D216)
ba574000 ba5de380 timntr timntr.sys Wed Aug 29 14:13:12 2007 (46D562D8)
ba5df000 ba60ba80 NDIS NDIS.sys Wed Aug 04 08:14:27 2004 (41107EC3)
ba60c000 ba698400 Ntfs Ntfs.sys Fri Feb 09 12:10:31 2007 (45CC56A7)
ba699000 ba6af780 KSecDD KSecDD.sys Wed Aug 04 07:59:45 2004 (41107B51)
ba6b0000 ba6c1e80 sr sr.sys Wed Aug 04 08:06:22 2004 (41107CDE)
ba6c2000 ba6e1780 fltMgr fltMgr.sys Mon Aug 21 11:14:57 2006 (44E97991)
ba6e2000 ba6f2680 SI3132 SI3132.sys Wed Jan 19 23:30:51 2005 (41EEDF9B)
ba6f3000 ba70a800 SCSIPORT SCSIPORT.SYS Wed Aug 04 07:59:39 2004 (41107B4B)
ba70b000 ba722480 atapi atapi.sys Wed Aug 04 07:59:41 2004 (41107B4D)
ba723000 ba748900 dmio dmio.sys Wed Aug 04 08:07:13 2004 (41107D11)
ba749000 ba767b00 ftdisk ftdisk.sys Fri Aug 17 22:52:41 2001 (3B7D8419)
ba768000 ba778a00 pci pci.sys Wed Aug 04 08:07:45 2004 (41107D31)
ba779000 ba7a6d80 ACPI ACPI.sys Wed Aug 04 08:07:35 2004 (41107D27)
ba8a8000 ba8b0d00 isapnp isapnp.sys Fri Aug 17 22:58:01 2001 (3B7D8559)
ba8b8000 ba8c6e80 ohci1394 ohci1394.sys Wed Aug 04 08:10:05 2004 (41107DBD)
ba8c8000 ba8d5000 1394BUS 1394BUS.SYS Wed Aug 04 08:10:03 2004 (41107DBB)
ba8d8000 ba8e2500 MountMgr MountMgr.sys Wed Aug 04 07:58:29 2004 (41107B05)
ba8e8000 ba8f4e80 VolSnap VolSnap.sys Wed Aug 04 08:00:14 2004 (41107B6E)
ba8f8000 ba900e00 disk disk.sys Wed Aug 04 07:59:53 2004 (41107B59)
ba908000 ba914200 CLASSPNP CLASSPNP.SYS Wed Aug 04 08:14:26 2004 (41107EC2)
ba918000 ba925500 lpx lpx.sys Fri Feb 23 03:01:21 2007 (45DE4AF1)
ba958000 ba961980 processr processr.sys Wed Aug 04 07:59:14 2004 (41107B32)
ba968000 ba977e80 serial serial.sys Wed Aug 04 08:15:51 2004 (41107F17)
ba978000 ba982380 imapi imapi.sys Wed Aug 04 08:00:12 2004 (41107B6C)
ba988000 ba994180 cdrom cdrom.sys Wed Aug 04 07:59:52 2004 (41107B58)
ba998000 ba9a6300 redbook redbook.sys Wed Aug 04 07:59:34 2004 (41107B46)
ba9a8000 ba9b0300 incdrm incdrm.SYS Thu Mar 23 16:59:58 2006 (4422C5FE)
ba9b8000 ba9c6b80 drmk drmk.sys Wed Aug 04 08:07:54 2004 (41107D3A)
ba9c8000 ba9d7180 nic1394 nic1394.sys Wed Aug 04 07:58:28 2004 (41107B04)
ba9d8000 ba9e1000 nvnetbus nvnetbus.sys Wed May 17 04:25:01 2006 (446A897D)
ba9e8000 ba9f4880 rasl2tp rasl2tp.sys Wed Aug 04 08:14:21 2004 (41107EBD)
ba9f8000 baa02200 raspppoe raspppoe.sys Wed Aug 04 08:05:06 2004 (41107C92)
baa08000 baa13d00 raspptp raspptp.sys Wed Aug 04 08:14:26 2004 (41107EC2)
baa18000 baa20900 msgpc msgpc.sys Wed Aug 04 08:04:11 2004 (41107C5B)
baa28000 baa31f00 termdd termdd.sys Wed Aug 04 07:58:52 2004 (41107B1C)
baa38000 baa44e00 NVENETFD NVENETFD.sys Wed May 17 04:24:58 2006 (446A897A)
baa48000 baa51480 NDProxy NDProxy.SYS Fri Aug 17 22:55:30 2001 (3B7D84C2)
baa88000 baa96100 usbhub usbhub.sys Wed Aug 04 08:08:40 2004 (41107D68)
baac8000 baad0700 wanarp wanarp.sys Wed Aug 04 08:04:57 2004 (41107C89)
baad8000 baae0080 ipfltdrv ipfltdrv.sys Fri Aug 17 22:55:07 2001 (3B7D84AB)
baae8000 baaf6d80 arp1394 arp1394.sys Wed Aug 04 07:58:28 2004 (41107B04)
baaf8000 bab05000 WDFLDR WDFLDR.SYS Thu Nov 02 09:54:05 2006 (4549B22D)
bab08000 bab10d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 08:08:18 2004 (41107D52)
bab18000 bab20700 netbios netbios.sys Wed Aug 04 08:03:19 2004 (41107C27)
bab28000 bab2e200 PCIIDEX PCIIDEX.SYS Wed Aug 04 07:59:40 2004 (41107B4C)
bab30000 bab34900 PartMgr PartMgr.sys Sat Aug 18 03:32:23 2001 (3B7DC5A7)
bab38000 bab3e5c0 ultra ultra.sys Fri May 16 08:11:00 2003 (3EC480F4)
bab40000 bab44880 TDI TDI.SYS Wed Aug 04 08:07:47 2004 (41107D33)
baba0000 baba7880 Npfs Npfs.SYS Wed Aug 04 08:00:38 2004 (41107B86)
baba8000 baba9000 fdc fdc.sys unavailable (00000000)
babc0000 babc4280 usbohci usbohci.sys Wed Aug 04 08:08:34 2004 (41107D62)
babc8000 babce800 usbehci usbehci.sys Wed Aug 04 08:08:34 2004 (41107D62)
babd0000 babd7b80 usbccgp usbccgp.sys Wed Aug 04 08:08:45 2004 (41107D6D)
babe8000 babef300 InCDPass InCDPass.sys Thu Mar 23 17:00:02 2006 (4422C602)
babf0000 babf5500 LUsbFilt LUsbFilt.Sys Fri Sep 21 13:05:27 2007 (46F3A577)
bac10000 bac17ec0 ADBLOCK ADBLOCK.DLL Thu Apr 05 14:57:16 2007 (4614F22C)
bac18000 bac1e780 USBSTOR USBSTOR.SYS Wed Aug 04 08:08:44 2004 (41107D6C)
bac20000 bac26f00 LHidFilt LHidFilt.Sys Fri Sep 21 13:05:22 2007 (46F3A572)
bac28000 bac2c580 ptilink ptilink.sys Fri Aug 17 22:49:53 2001 (3B7D8371)
bac30000 bac37380 LMouFilt LMouFilt.Sys Fri Sep 21 13:05:25 2007 (46F3A575)
bac38000 bac3c080 raspti raspti.sys Fri Aug 17 22:55:32 2001 (3B7D84C4)
bac48000 bac4e100 kbdclass kbdclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
bac50000 bac56500 usbprint usbprint.sys Wed Aug 04 08:01:23 2004 (41107BB3)
bac58000 bac5db00 mouclass mouclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
bac60000 bac65000 flpydisk flpydisk.sys Wed Aug 04 07:59:24 2004 (41107B3C)
bac80000 bac840a0 ARP ARP.DLL Thu Apr 05 14:57:47 2007 (4614F24B)
bac98000 bac9e180 HIDPARSE HIDPARSE.SYS Wed Aug 04 08:08:15 2004 (41107D4F)
baca0000 baca5200 vga vga.sys Wed Aug 04 08:07:06 2004 (41107D0A)
baca8000 bacac500 watchdog watchdog.sys Wed Aug 04 08:07:32 2004 (41107D24)
bacb0000 bacb4a80 Msfs Msfs.SYS Wed Aug 04 08:00:37 2004 (41107B85)
bacb8000 bacbb000 BOOTVID BOOTVID.dll Fri Aug 17 22:49:09 2001 (3B7D8345)
bacbc000 bacbe880 SiWinAcc SiWinAcc.sys Mon Nov 01 20:21:31 2004 (41868CBB)
bada8000 bada9b80 kdcom kdcom.dll Fri Aug 17 22:49:10 2001 (3B7D8346)
badaa000 badab100 WMILIB WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B)
badac000 badad700 dmload dmload.sys Fri Aug 17 22:58:15 2001 (3B7D8567)
badae000 badaf480 speedfan speedfan.sys Sun Sep 24 15:28:47 2006 (4516880F)
badb4000 badb5420 ASACPI ASACPI.sys Fri Aug 13 04:52:52 2004 (411C2D04)
badba000 badbb100 swenum swenum.sys Wed Aug 04 07:58:41 2004 (41107B11)
badc0000 badc1280 USBD USBD.SYS Fri Aug 17 23:02:58 2001 (3B7D8682)
badc4000 badc5f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 22:49:37 2001 (3B7D8361)
badc8000 badc9080 Beep Beep.SYS Fri Aug 17 22:47:33 2001 (3B7D82E5)
badcc000 badcd080 mnmdd mnmdd.SYS Fri Aug 17 22:57:28 2001 (3B7D8538)
badce000 badcf140 CONTENT CONTENT.DLL Thu Apr 05 14:57:27 2007 (4614F237)
badd0000 badd1080 RDPCDD RDPCDD.sys Fri Aug 17 22:46:56 2001 (3B7D82C0)
badd2000 badd3a20 IMAPFILT IMAPFILT.DLL Thu Apr 05 14:57:35 2007 (4614F23F)
badd4000 badd5860 NNTPFILT NNTPFILT.DLL Thu Apr 05 14:57:31 2007 (4614F23B)
badd6000 badd7de0 nod32drv nod32drv.sys Fri Feb 09 10:39:19 2007 (45CC4147)
badda000 baddb440 AsIO AsIO.sys Wed Dec 21 09:55:21 2005 (43A91879)
badde000 baddf780 fixustor fixustor.sys Mon Jan 05 03:23:15 2004 (3FF8CA93)
bade2000 bade3100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B)
bade6000 bade7b00 ParVdm ParVdm.SYS Fri Aug 17 22:49:49 2001 (3B7D836D)
bae70000 bae70d00 pciide pciide.sys Fri Aug 17 22:51:49 2001 (3B7D83E5)
bae71000 bae71680 giveio giveio.sys Thu Apr 04 04:33:25 1996 (316334F5)
baed7000 baed7b80 Null Null.SYS Fri Aug 17 22:47:39 2001 (3B7D82EB)
baf2d000 baf2dd00 dxgthk dxgthk.sys Fri Aug 17 22:53:12 2001 (3B7D8438)
baffa000 baffac00 audstub audstub.sys Fri Aug 17 22:59:40 2001 (3B7D85BC)
bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 14:47:34 2007 (45F013F6)
bf9c3000 bf9d4580 dxg dxg.sys Wed Aug 04 08:00:51 2004 (41107B93)
bf9d5000 bfa19000 ati2dvag ati2dvag.dll Fri Feb 02 21:03:43 2007 (45C3991F)
bfa19000 bfa6e000 ati2cqag ati2cqag.dll Fri Feb 02 20:20:27 2007 (45C38EFB)
bfa6e000 bfaba000 atikvmag atikvmag.dll Fri Feb 02 20:27:17 2007 (45C39095)
bfaba000 bfd6c6c0 ati3duag ati3duag.dll Fri Feb 02 20:46:43 2007 (45C39523)
bfd6d000 bfea3c80 ativvaxx ativvaxx.dll Fri Feb 02 20:40:29 2007 (45C393AD)

Unloaded modules:
bae88000 bae89000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a7116000 a7141000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a7141000 a7164000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a7311000 a731e000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a7321000 a732f000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bae58000 bae5a000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a9a8a000 a9a9f000 wdmaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba379000 ba37d000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
baab8000 baac5000 i8042prt.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
bac88000 bac8d000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ba37d000 ba380000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

afd.sys is mentioned twice:

http://www.file.net/process/afd.sys.html

mickzer.

 

Thanks for the link. I have updated my vga driver and upgraded the bios too. That might help. If not, I guess repairing the Windows installation is the best option.
/RednulB

 

Hi, RednulB.

NOTE:

I found a post of yours in another forum related to this issue with a similar crash dump log (but different time-stamp) where you stated,

Is there a newer version of Outpost available? If so, then perhaps updating/upgrading Outpost will resolve your BSOD issue.

I'm guessing the modules listed above in ALL CAPS are related to Outpost Firewall. Since those are near the top of your module list, I wonder whether one or more of them might be related to your BSODs or not.

I'd be inclined to disconnect from the Internet, uninstall Outpost Firewall, and then enable another firewall (such as Windows XP's built-in firewall) before connecting to the Internet. I'd also be inclined to restart the computer after uninstalling Outpost and then restart again after installing and/or enabling another another firewall.

If your BSODs stop occurring after uninstalling Outpost, then perhaps we have narrowed down the culprit to an Outpost component.

If you want to try another reputable 3rd-party firewall, then I suggest you download COMODO Firewall Pro (free) ahead of time if possible (before disconnecting from the Internet and uninstalling Outpost). I recently started using COMODO Firewall Pro with my laptop and I like it so much, I will probably replace the ZoneAlarm Pro firewall I have in my desktop computer when my ZoneAlarm Pro subscription runs out in the next couple weeks or so.

Keep in Mind: One should have only ONE software firewall active at any time. Having more than one firewall active can produce conflicts.

 

Thanks Mailman for thoroughly cheking my case. The code is certainly difficult and I'm grateful for all the help I get. It's interesting, I think, that the address is the same for every crash.

Yes, my fw might be involved since the afd.sys is part of the winsock kernel and controls connections/open channels -- or something like that. The problems actually started when I installed a new version of Spybot S&D which didn't work at all with my fw Outpost. I have removed every trace of Spybot 1.52 but... There's a newer version of Outpost available, but that's a complete security suite with fewer user otions so Comodo or Online Armour are probably better options. If the BSODs continue, I will certainly move on from OP to another fw or try to repair the Windows installation. But my computer's has been BSOD-free since the yesterday...
Thanks for the good advice/RednulB

 

Since the BSODs started only yesterday, perhaps you can use System Restore to revert your computer to a stable state it was in prior to the BSODs.

• Click Start > All Programs > Accessories > System Tools > System Restore

Also, from your dump log,

Perhaps you should consider starting Windows with the /DEBUG switch to see if that identifies a potential culprit. I'm not familiar with its use though.

The "debugger" referred to might be the Debugging Tools for Windows which I suspect you have already installed.

 

I did a little research about the /DEBUG switch. If I understand correctly, "make sure a debugger gets connected" means one would need to connect another Windows XP computer (that has a kernel debugger) via a COM port, null modem cable, or FireWire (IEEE 1394 port).

• Microsoft KB833721: Available switch options for the Windows XP and the Windows Server 2003 Boot.ini files

The /DEBUG switch might not be useful for you as an intermediate experience end-user.

• Microsoft KB314081: The purpose of the Boot.ini file in Windows XP
  

I'd be inclined to try System Restore first anyway.

 

Thanks Mailman for the updates.
I thought about the debug switch mentioned in the log file but never knew what it meant. Now I do, and I'm sure that option is way too advanced for me. A System Restore might do it, but the crashes have been occuring for a few weeks now so it might be too late. Right now, everything works fine with zero new BSODs to report.
Happy easter/RednulB

 

Glad to know you haven't had any recent BSODs. Perhaps Windows XP did its own repairs with its journaling file system (if you're using Windows XP's NTFS instead of FAT32 as your file system).

BSOD issues have cleared themselves up for me in the past. (At least I don't know whether anything I did solved some of those issues or not.)

BTW, I mis-read your post when I stated your BSODs started "yesterday ". I'm sorry about that. My attention to detail apparently lacks in the early morning.

EDIT:

You might be surprised. You can check it out without following through with a restore. If you open System Restore and select "Restore my computer to an earlier time" and then click "Next > ", you can see what dates are available (shown as bold dates on the calendar). You can look at previous months on the calendar as well.

If you ever do decide to perform a System Restore, then you will likely have to reinstall applications and updates that were applied since that date.

 

Uninstalled my old fw last evening after two BSODs of the familiar kind in a row just after booting -- both afd-reladed with the same magic numbers 1000008E, {80000003, 8052a828, XXXXXXXX} involved. I skipped the system restore you recommended and settled for Comodo FW instead of Outpost 4. No crashes since then (8 hours ago). Now I hope that my system stays stable until XP SP3 arrives...

Thanks for all your useful replies Mailman. The help was appreciated.

 

You're welcome.

I hope your BSODs have stopped. (fingers crossed)

Please let us know after a week or two if you don't have any crashes. That information would help others who run into similar issues and discover this thread.

 

Hi all,
This an update to the thread "Recurring BSODs caused by afd.sys. Dump data included" started by myself on March 18 and now too old for new replies. Mailman's last post on March 24 requested an update after a week or two... Well, several weeks have now passed and the BSODs are gone. So, if you have Outpost fw installed and experience frequent BSODs with the error code 1000008E, 80000003, 8052a828 and then a changing frame, then it's pretty likely that they have something to do with Outpost. I removed OP completely and installed Comodo FW instead, et voila, no BSODs (yet...)
cheers/RB