Share via

BSOD tap0901.sys

Anonymous
2014-04-30T15:13:43+00:00
Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

8 answers

Sort by: Most helpful
  1. Anonymous
    2014-04-30T20:44:07+00:00

    Hi,

    The attached DMP files are of the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) bug check.

    This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

    A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.

    kd> k

    ChildEBP RetAddr  

    WARNING: Stack unwind information not available. Following frames may be wrong.

    a5c25120 8965e4ef tap0901+0x2a30

    a5c2514c 8965dc68 ndis!ndisMSendPacketsXToMiniport+0x129

    a5c251b8 89628c11 ndis!ndisMSendNetBufferListsToPackets+0x76

    a5c25298 8264dc36 ndis!NdisSendNetBufferLists+0x431

    a5c25318 826505f2 tcpip!IppFragmentPackets+0x4ca

    a5c25378 826502a0 tcpip!IppDispatchSendPacketHelper+0x80

    a5c25420 8264f612 tcpip!IppPacketizeDatagrams+0x289

    a5c254b8 8264e227 tcpip!IppSendDatagramsCommon+0x65a

    a5c254d0 8263ffc5 tcpip!IpNlpSendDatagrams+0x57

    a5c25744 82641810 tcpip!UdpSendMessagesOnPathCreation+0x4d4

    a5c258c4 82641b01 tcpip!UdpSendMessages+0x1c2

    a5c258d0 81eacea5 tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x13

    a5c25960 81eacb09 nt!KeExpandKernelStackAndCalloutInternal+0x385

    a5c25978 826469d9 nt!KeExpandKernelStackAndCalloutEx+0x1f

    a5c259b8 8d44254c tcpip!UdpTlProviderSendMessages+0x53

    a5c25a10 8d44227b afd!AfdTLFastDgramSend+0x88

    a5c25ad0 8d430558 afd!AfdFastDatagramSend+0x1fe

    a5c25c40 8209b9a3 afd!AfdFastIoDeviceControl+0x553

    a5c25cf8 8209ab96 nt!IopXxxControlFile+0x1f3

    a5c25d24 81f306c7 nt!NtDeviceIoControlFile+0x2a

    a5c25d24 772ef804 nt!KiSystemServicePostCall

    050ef504 00000000 0x772ef804

    tap0901.sys is the problematic driver which is TAP-Win32 Adapter V9 or OpenVPN driver or COMODO. If you have COMODO installed, uninstall it ASAP! For the VPN, I'd recommend removal as well.

    Regards,

    Patrick

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2014-05-04T15:54:01+00:00

    No, I don't have any software regarding the TAP adapter.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2014-05-04T06:09:58+00:00

    Hm, do you have any software regarding the TAP adapter, or is it only listed in Device Manager?

    Regards,

    Patrick

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2014-05-04T06:03:57+00:00

    Which one of TAP-Win32 Adapter V9 should I uninstall?

    https://onedrive.live.com/redir?resid=34148F7E79725CFF%21921

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2014-05-04T19:41:25+00:00

    Actually, you should.

    The TAP adapters are virtual network connections for Open VPN. Did you uninstall this software? If so, and if the adapters are still there, just uninstall all of them.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments