locked
Windows 7 - BSOD when transfering data over VPN RRS feed

  • Question

  • I am running Windows 7 Professional. I connect to my work VPN using the standard windows vpn client using L2TP/IPSec using a certificate and no encryption.

    Often when transferring data my machine will BSOD.  The reason I say " transferring data" is because I can remain connected to my VPN over the week-ends or evenings doing other things (non VPN related) and the machine remains stable.

    Scenarios during which my machine has BSDO'ed include :
    - publishing from Visual Studio
    - copy and paste a file from one of the machines on the remote network
    - using remote desktop into a machine on the remote network 

    I have the mini dump files available (3 of them in the last 6 days) if that will help narrow things down.

    I've searched around for a lot for solutions to this - but most seem o point to a Cisco driver? (my company has no Cisco hardware installed that I know of) - or say to replace the Cisco client with ShrewSoft's VPN client?

    Any insights, troubleshooting tips will be greatly appreciated.

    Thanks - Hayward G.

    ps. Apologies for the clinical tone - but as a programmer I know the more clearer the issue is presented, the easier it is to track down.

     

    Edit: Was not sure if this should go under the Performance forum or the Networking forum. - Apologies if incorrectly posted.

    Tuesday, February 8, 2011 1:58 PM

Answers

  • Hi Hayward ,

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000005 - access violation

    STACK_TEXT: 
    nt!KeBugCheckEx
    nt!KipFatalFilter+0x1b
    nt! ?? ::FNODOBFM::`string'+0x95d
    nt!_C_specific_handler+0x8c
    nt!RtlpExecuteHandlerForException+0xd
    nt!RtlDispatchException+0x410
    nt!KiDispatchException+0x16f
    nt!KiExceptionDispatch+0xc2
    nt!KiGeneralProtectionFault+0x10a
    hal!HalpAllocateAdapterCallback+0xef
    hal!HalAllocateAdapterChannel+0x101
    hal!HalBuildScatterGatherList+0x2f3
    ndis!NdisMAllocateNetBufferSGList+0x181
    L1E62x64 +0x6a10

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.

    nt!KeBugCheckEx
    nt!KiBugCheckDispatch+0x69
    nt!KiPageFault+0x260
    ndis! ?? ::FNODOBFM::`string'+0x14dd
    L1E62x64 +0x6a10

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high .

    CURRENT_IRQL:  2

    Child-SP          RetAddr           Call Site
    fffff880`07759088 fffff800`0306eae9 nt!KeBugCheckEx
    fffff880`07759090 fffff800`0306d760 nt!KiBugCheckDispatch+0x69
    fffff880`077591d0 fffff800`03071640 nt!KiPageFault+0x260
    fffff880`07759368 fffff800`035dee08 nt!RtlCopyMemoryNonTemporal+0x40
    fffff880`07759370 fffff800`035de593 hal!HalpDmaSyncMapBuffers+0x1b0
    fffff880`07759420 fffff800`035e14fb hal!HalpDmaMapScatterTransfer+0xa3
    fffff880`07759470 fffff800`035e1472 hal!HalpMapTransfer+0x7b
    fffff880`07759500 fffff800`035e094f hal!IoMapTransfer+0x8e
    fffff880`07759540 fffff800`035e113d hal!HalpAllocateAdapterCallback+0xc7
    fffff880`077595e0 fffff800`035e071f hal!HalAllocateAdapterChannel+0x101
    fffff880`07759620 fffff880`01418831 hal!HalBuildScatterGatherList+0x2f3
    fffff880`07759690 fffff880`03c06a10 ndis!NdisMAllocateNetBufferSGList+0x181
    fffff880`07759730 fffffa80`081d01a0 L1E62x64 +0x6a10

        Image path: \SystemRoot\system32\DRIVERS\L1E62x64.sys
        Image name: L1E62x64.sys
        Timestamp:        Thu Jun 11 08:45:22 2009

    This is the Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller driver. So update the driver, please!

    Also update some older drivers, which may cause issues in the future:

    ASACPI.sys   Mon Mar 28 04:30:36 2005
    adfs.SYS     Thu Jun 26 22:52:37 2008
    ElbyCDIO.sys Tue Feb 17 18:11:23 2009
    GEARAspiWDM.sys Mon May 18 14:17:04 2009
    mrdd.sys     Wed Nov 12 07:44:48 2008
    PxHlpa64.sys Wed Oct 17 20:25:02 2007
    RTKVHD64.sys Fri May 22 20:04:20 2009

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Juke Chou Tuesday, February 22, 2011 9:10 AM
    Tuesday, February 8, 2011 3:17 PM

All replies

  • A bugcheck (BSOD) is a mechanism to protect your PC from damage.

    To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

    Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

    In the meantime make sure all network related drivers are up to date.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, February 8, 2011 2:44 PM
  • Hi Andrè

     

    Here is the link : http://cid-7db33b6994d67b4e.office.live.com/browse.aspx/.Public?uc=1

     

    *holds.thumbs*

    Tuesday, February 8, 2011 2:52 PM
  • Hi Hayward ,

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000005 - access violation

    STACK_TEXT: 
    nt!KeBugCheckEx
    nt!KipFatalFilter+0x1b
    nt! ?? ::FNODOBFM::`string'+0x95d
    nt!_C_specific_handler+0x8c
    nt!RtlpExecuteHandlerForException+0xd
    nt!RtlDispatchException+0x410
    nt!KiDispatchException+0x16f
    nt!KiExceptionDispatch+0xc2
    nt!KiGeneralProtectionFault+0x10a
    hal!HalpAllocateAdapterCallback+0xef
    hal!HalAllocateAdapterChannel+0x101
    hal!HalBuildScatterGatherList+0x2f3
    ndis!NdisMAllocateNetBufferSGList+0x181
    L1E62x64 +0x6a10

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.

    nt!KeBugCheckEx
    nt!KiBugCheckDispatch+0x69
    nt!KiPageFault+0x260
    ndis! ?? ::FNODOBFM::`string'+0x14dd
    L1E62x64 +0x6a10

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high .

    CURRENT_IRQL:  2

    Child-SP          RetAddr           Call Site
    fffff880`07759088 fffff800`0306eae9 nt!KeBugCheckEx
    fffff880`07759090 fffff800`0306d760 nt!KiBugCheckDispatch+0x69
    fffff880`077591d0 fffff800`03071640 nt!KiPageFault+0x260
    fffff880`07759368 fffff800`035dee08 nt!RtlCopyMemoryNonTemporal+0x40
    fffff880`07759370 fffff800`035de593 hal!HalpDmaSyncMapBuffers+0x1b0
    fffff880`07759420 fffff800`035e14fb hal!HalpDmaMapScatterTransfer+0xa3
    fffff880`07759470 fffff800`035e1472 hal!HalpMapTransfer+0x7b
    fffff880`07759500 fffff800`035e094f hal!IoMapTransfer+0x8e
    fffff880`07759540 fffff800`035e113d hal!HalpAllocateAdapterCallback+0xc7
    fffff880`077595e0 fffff800`035e071f hal!HalAllocateAdapterChannel+0x101
    fffff880`07759620 fffff880`01418831 hal!HalBuildScatterGatherList+0x2f3
    fffff880`07759690 fffff880`03c06a10 ndis!NdisMAllocateNetBufferSGList+0x181
    fffff880`07759730 fffffa80`081d01a0 L1E62x64 +0x6a10

        Image path: \SystemRoot\system32\DRIVERS\L1E62x64.sys
        Image name: L1E62x64.sys
        Timestamp:        Thu Jun 11 08:45:22 2009

    This is the Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller driver. So update the driver, please!

    Also update some older drivers, which may cause issues in the future:

    ASACPI.sys   Mon Mar 28 04:30:36 2005
    adfs.SYS     Thu Jun 26 22:52:37 2008
    ElbyCDIO.sys Tue Feb 17 18:11:23 2009
    GEARAspiWDM.sys Mon May 18 14:17:04 2009
    mrdd.sys     Wed Nov 12 07:44:48 2008
    PxHlpa64.sys Wed Oct 17 20:25:02 2007
    RTKVHD64.sys Fri May 22 20:04:20 2009

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Juke Chou Tuesday, February 22, 2011 9:10 AM
    Tuesday, February 8, 2011 3:17 PM