none
Microsoft ISATAP Adapter This Device Is Not Working Error (Code 10)

    Question

  • Ok. So i been hunting around on how to fix this and all threads say that you should be able to leave it alone and such much. well i can leave it alone and all that but eventually i geen the blue screen of death system dump crash in which case i says there is an error with TCPIP.sys. which is also something i cannot find how to fix. plz help im crashing every 5 hours or so.
    Thursday, September 25, 2008 6:49 PM

Answers

  • Hi,

     

    Regarding the Microsoft ISATAP Adapter error, you can ignore it safely. Please refer to the following link:

     

    On a Windows Vista-based computer or on a Windows Server 2008-based computer, the Microsoft ISATAP adapter appears with a yellow exclamation mark next to it in Device Manager, and you also receive an error message

    http://support.microsoft.com/kb/932520/en-us

     

    Regarding the TCPIP.sys leading BSOD problem. This issue mostly can be caused by the file are corrupted or cracked. To solid troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump and analyze the related source code if needed. Unfortunately, debugging is beyond what we can do in the forum. I'd like to recommend that you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

     

    If you are outside the US please see http://support.microsoft.com for regional support phone numbers.

     

    Hope it helps.

     

    Friday, September 26, 2008 9:40 AM

All replies

  • Hi,

     

    Regarding the Microsoft ISATAP Adapter error, you can ignore it safely. Please refer to the following link:

     

    On a Windows Vista-based computer or on a Windows Server 2008-based computer, the Microsoft ISATAP adapter appears with a yellow exclamation mark next to it in Device Manager, and you also receive an error message

    http://support.microsoft.com/kb/932520/en-us

     

    Regarding the TCPIP.sys leading BSOD problem. This issue mostly can be caused by the file are corrupted or cracked. To solid troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump and analyze the related source code if needed. Unfortunately, debugging is beyond what we can do in the forum. I'd like to recommend that you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

     

    If you are outside the US please see http://support.microsoft.com for regional support phone numbers.

     

    Hope it helps.

     

    Friday, September 26, 2008 9:40 AM
  • This might have helped:
    Open command prompt as an administrator and then run this command:

    netsh winsock reset catalog

    "This command resets the Winsock catalog to the default configuration. This can be useful if a malformed LSP is installed that results in loss of network connectivity. While use of this command can restore network connectivity, it should be used with care because any previously-installed LSPs will need to be re-installed."

    Tuesday, November 17, 2009 1:44 PM