No announcement yet.

Vista BSOD problems - driver related?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Vista BSOD problems - driver related?

    I've had intermittent BSOD errors on my HP A6152N since 9/8 (13 so far). The computer reboots automatically and I get a message saying that Windows recovered from a problem, with the following information if I click show details:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.0.6001.
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 1000007e
    BCP1: 80000003
    BCP2: 81E89954
    BCP3: 8B1BFBD0
    BCP4: 8B1BF8CC
    OS Version: 6_0_6001
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    C:\Users\David\AppData\Local\Temp\WER4B18.tmp.vers ion.txt

    I've done obvious things such as updating the video drivers. I also downloaded the Microsoft Debugging Tools and the Symbol Package to try to track down the cause of the error.

    It looks like some sort of driver error related to afd.sys. I've added the mini dump file renamed as a txt file (instead of dmp). Here is what I get from the debugging tools with the !analyze -v command:

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

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

    Symbol search path is: c:\windows\symbols
    Executable search path is:
    Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
    Kernel base = 0x81e38000 PsLoadedModuleList = 0x81f4fc70
    Debug session time: Sun Sep 28 01:45:51.584 2008 (GMT-4)
    System Uptime: 0 days 7:16:09.799
    Loading Kernel Symbols
    .................................................. .................................................. .................................................. ...........................
    Loading User Symbols
    Loading unloaded module list
    2: kd> !analyze -v
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    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
    Arg1: 80000003, The exception code that was not handled
    Arg2: 81e89954, The address that the exception occurred at
    Arg3: 8b1bfbd0, Exception Record Address
    Arg4: 8b1bf8cc, Context Record Address

    Debugging Details:

    EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

    81e89954 cc int 3

    EXCEPTION_RECORD: 8b1bfbd0 -- (.exr 0xffffffff8b1bfbd0)
    ExceptionAddress: 81e89954 (nt!DbgBreakPoint)
    ExceptionCode: 80000003 (Break instruction exception)
    ExceptionFlags: 00000000
    NumberParameters: 3
    Parameter[0]: 00000000
    Parameter[1]: 843902d8
    Parameter[2]: 00000065

    CONTEXT: 8b1bf8cc -- (.cxr 0xffffffff8b1bf8cc)
    eax=00000000 ebx=00000000 ecx=81ef616e edx=00000065 esi=8508aa08 edi=00000000
    eip=81e89954 esp=8b1bfc98 ebp=8b1bfcc4 iopl=0 nv up ei ng nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
    81e89954 cc int 3
    Resetting default scope




    PROCESS_NAME: System


    ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

    LAST_CONTROL_TRANSFER: from 9218e7d0 to 81e89954

    8b1bfcc4 9218e7d0 85074458 00000000 00000000 nt!DbgBreakPoint
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8b1bfcf0 9216e0a7 84a80780 84a807f8 9217f268 afd+0x227d0
    8b1bfd08 9218482b 84a80780 8b1bfd30 9216dc86 afd+0x20a7
    8b1bfd14 9216dc86 84a807f8 81f3a13c 872fd7a0 afd+0x1882b
    8b1bfd30 8205431b 872fd7a0 00000000 843902d8 afd+0x1c86
    8b1bfd44 81e7041d 872fd130 00000000 843902d8 nt!IopProcessWorkItem+0x23
    8b1bfd7c 8200db18 872fd130 e87d49c8 00000000 nt!ExpWorkerThread+0xfd
    8b1bfdc0 81e66a3e 81e70320 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

    9218e7d0 ?? ???


    SYMBOL_NAME: afd+227d0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: afd

    IMAGE_NAME: afd.sys


    STACK_COMMAND: .cxr 0xffffffff8b1bf8cc ; kb

    FAILURE_BUCKET_ID: 0x7E_afd+227d0

    BUCKET_ID: 0x7E_afd+227d0

    Followup: MachineOwner

    I'm not sure what afd.sys does. These problems seem to have started about the time I trying installing the Kerio Personal Firewall by Sunbelt Software. The installation did not complete and I had to use spfclean.exe from Sunbelt Software to clean up the mess. There were a few leftovers in in the device manager under network adapters (and registy) for "Sunbelt Software Firewall NDIS IM Filter Miniport". I was able to delete these network adapters after dleting some SPF-related registry keys.

    Thanks for your help.


  • #2
    Re: Vista BSOD problems - driver related?

    Does this help at all???


    • #3
      Re: Vista BSOD problems - driver related?


      Thanks for the suggestion. It's on the right track, but the hotfix is only for Windows Server 2003. I've been searching for a similar hotfix for Windows Vista without success (yet).



      • #4
        Re: Vista BSOD problems - driver related?

        Whoops sorry about that.

        I've done some digging and it would seem that afd.sys is something to do with Winsock.

        Try reading this to reset winsock

        and this to reset TCP/IP


        • #5
          Re: Vista BSOD problems - driver related?


          Thanks for the suggestions, I'll give them a try over the weekend. Do you know if the Winsock reset reinstalls the LSPs that it clears out or will I need to do something to reinstall them?




          • #6
            Re: Vista BSOD problems - driver related?

            Originally posted by DavidFMitchell View Post

            Thanks for the suggestions, I'll give them a try over the weekend. Do you know if the Winsock reset reinstalls the LSPs that it clears out or will I need to do something to reinstall them?


            As far as i'm aware it resets everything back to the factory install. No other reinstallation needs to be done.


            • #7
              Re: Vista BSOD problems - driver related?

              I reverted back to Windows Live OneCare on my home computer after trying several other anti-virus/firewall combinations, including Kaspersky, AVG and Sunbelt. I've got my fingers crossed, but it seems that the BSOD's have stopped.

              I tried MS tech support via email but the suggestion I got was to repair Vista from the DVD. This would be difficult because the DVD I have is pre-SP1 and I have SP1 installed.

              The whole thing has been really odd. I have about 50 computers at work running AVG v7.5 and have never had these kinds of problems.