locked
BSOD's on Dell E6510 Laptop Windows 7 Enterprise 32bit RRS feed

  • Question

  • This is a new computer I got from work.  Since I got it with Windows 7 I have had 7 BSOD's total, most of them with 0xD1 codes, one with a 0xA code.  I have updated the video and network drives to the latest from Dell to no avail.  The driver listed in the 0xD1 BSOD's is the Intel network drive, and the 0xA BSOD indicated ntkrnlpa.exe which looks to be part of the OS.  Here is the link to the last 2 minidump files.  

    http://cid-51644cf6699d8779.skydrive.live.com/redir.aspx?resid=51644CF6699D8779!123&Bpub=SDX.Docs&Bsrc=GetSharingLink

    Most recent one was the same 0xD1 code I have recieved before, the one prior to that was the 0xA code.  I have 5 more older ones that all had the 0xD1 codes if you need them just let me know and i'll upload them.  

    It does seem to happen when I have a decent amount of network traffic going on, such as downloading a large file from MSDN or moving files to a file share. Though I believe in one occasion I was just working on emails and it crashed right after I got the little popup in the lower right showing that I had gotten a new email.  Any help is appreciated.  

     

    Thursday, July 29, 2010 4:16 PM

Answers

  • I contacted Dell again and Per Hunter's suggestion requested the driver version 11.5.10.0 installed it and I was able to capture the image to a server.

    The Dell Tech refered me to a driver page for this download. What was interesting was Intel and Dell had 3 versions of this driver and each was labeled critical. :( 

    I emailed my results to the Dell Tech who took ownership of the problem. I don't know if this will get the ball rolling with Intel on this?

    The laptop's OS is Windows 7 Enterprise 32-bit.

    Regards to All!

    • Marked as answer by RustyZ Friday, August 6, 2010 3:54 PM
    Friday, August 6, 2010 10:38 AM
  • Hi,

    I've got blue screens and after I read this, I remembered that I had installed a optional download: Intel - Network - Intel(R) 82577LM Gigabit Network Connection (164 KB) from Microsoft WIndows Update.

    Now I've got installed the driver from HP again, and delete the e1k6232.sys. I think DELL and HP are using the same network card so they get the same optional updates.

    Hopefully now, I don't get the blue secreens anymore.


    --------------------- Frank
    • Marked as answer by Magon Liu Friday, August 6, 2010 10:36 AM
    Friday, August 6, 2010 6:33 AM

All replies

  • The errors in the two minidumps are below. The error appears to be
    caused by e1k6232.sys. Looking on the net, it appears that this is a
    network card driver, but you can get more info from the Software
    Environment\System Drivers node of the msinfo32.exe utility and then
    look at the drivers in use under the Components node.
     
    Overall, I'd check with the computer/hardware manufacturers to ensure
    that your drivers, BIOS, and any applicable firmware are up to the
    latest versions.
     
    *******************************************************************************
    *
          *
    *                        Bugcheck Analysis
          *
    *
          *
    *******************************************************************************
     
    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.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only
    on chips which support this level of status)
    Arg4: 82e950ac, address which referenced memory
     
    Debugging Details:
    ------------------
     WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82fb6718
    Unable to read MiSystemVaType memory at 82f96160
     00000000
     
    CURRENT_IRQL:  2
     
    FAULTING_IP:
    nt!InterlockedPushEntrySList+c
    82e950ac 8903            mov     dword ptr [ebx],eax
     
    CUSTOMER_CRASH_COUNT:  1
     
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
     
    BUGCHECK_STR:  0xA
     
    PROCESS_NAME:  System
     
    TRAP_FRAME:  b0fe0af0 -- (.trap 0xffffffffb0fe0af0)
    ErrCode = 00000002
    eax=85f31008 ebx=00000000 ecx=871f5788 edx=00010004 esi=85f25f10
    edi=87450ef0
    eip=82e950ac esp=b0fe0b64 ebp=871f5788 iopl=0         nv up ei ng nz ac
    po cy
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000
    efl=00010293
    nt!InterlockedPushEntrySList+0xc:
    82e950ac 8903            mov     dword ptr [ebx],eax
    ds:0023:00000000=????????
    Resetting default scope
     
    LAST_CONTROL_TRANSFER:  from 82e950ac to 82e9482b
     
    STACK_TEXT:
    b0fe0af0 82e950ac badb0d00 00010004 00000000 nt!KiTrap0E+0x2cf
    b0fe0b68 8c0323bd b0fe0b88 8c00c674 871f5788
    nt!InterlockedPushEntrySList+0xc
    b0fe0b70 8c00c674 871f5788 00000000 00000000
    ndis!ExFreeToNPagedLookasideList+0x29
    b0fe0b88 957a8159 87450ef0 85f31008 85f25f10
    ndis!NdisMFreeNetBufferSGList+0x48
    WARNING: Stack unwind information not available. Following frames may be
    wrong.
    b0fe0be8 957a4a0e 877ae000 877b7280 00000002 e1k6232+0x16159
    b0fe0c58 957a3093 877ae000 00000000 b0fe0ca0 e1k6232+0x12a0e
    b0fe0c74 8c05e309 877ae000 00000000 b0fe0ca0 e1k6232+0x11093
    b0fe0cb0 8c03f6b2 8745dc6c 0045dc58 00000000 ndis!ndisMiniportDpc+0xe2
    b0fe0d10 8c026976 8745ddf0 00000000 85bfd690
    ndis!ndisQueuedMiniportDpcWorkItem+0xd0
    b0fe0d50 8305c6bb 00000003 95e818b1 00000000
    ndis!ndisReceiveWorkerThread+0xeb
    b0fe0d90 82f0e0f9 8c02688b 00000003 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
     STACK_COMMAND:  kb
     
    FOLLOWUP_IP:
    e1k6232+16159
    957a8159 ??              ???
     
    SYMBOL_STACK_INDEX:  4
     
    SYMBOL_NAME:  e1k6232+16159
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: e1k6232
     
    IMAGE_NAME:  e1k6232.sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bbae470
     
    FAILURE_BUCKET_ID:  0xA_e1k6232+16159
     
    BUCKET_ID:  0xA_e1k6232+16159
     
    Followup: MachineOwner
    ---------
     
    3: kd> lmvm e1k6232
    start    end        module name
    95792000 957cb000   e1k6232  T (no symbols)
        Loaded symbol image file: e1k6232.sys
        Image path: \SystemRoot\system32\DRIVERS\e1k6232.sys
        Image name: e1k6232.sys
        Timestamp:        Tue Apr 06 01:36:16 2010 (4BBAE470)
        CheckSum:         0003C923
        ImageSize:        00039000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
     *******************************************************************************
    *
          *
    *                        Bugcheck Analysis
          *
    *
          *
    *******************************************************************************
     
    Use !analyze -v to get detailed debugging information.
     
    BugCheck D1, {34, 2, 1, 93da1171}
     
    Unable to load image \SystemRoot\system32\DRIVERS\e1k6232.sys, Win32
    error 0n2
    *** WARNING: Unable to verify timestamp for e1k6232.sys
    *** ERROR: Module load completed but symbols could not be loaded for
    e1k6232.sys
    Probably caused by : e1k6232.sys ( e1k6232+16171 )
     
    Followup: MachineOwner
    ---------
     
    2: kd> !analyze -v
    ERROR: FindPlugIns 80070005
    *******************************************************************************
    *
          *
    *                        Bugcheck Analysis
          *
    *
          *
    *******************************************************************************
     
    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.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000034, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 93da1171, address which referenced memory
     
    Debugging Details:
    ------------------
     WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82fbb718
    Unable to read MiSystemVaType memory at 82f9b160
     00000034
     
    CURRENT_IRQL:  2
     
    FAULTING_IP:
    e1k6232+16171
    93da1171 f00fc111        lock xadd dword ptr [ecx],edx
     
    CUSTOMER_CRASH_COUNT:  1
     
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
     
    BUGCHECK_STR:  0xD1
     
    PROCESS_NAME:  System
     
    TRAP_FRAME:  a610bb28 -- (.trap 0xffffffffa610bb28)
    ErrCode = 00000002
    eax=0000fffb ebx=87961280 ecx=00000034 edx=ffffffff esi=8797dcb0
    edi=00000000
    eip=93da1171 esp=a610bb9c ebp=a610bbe8 iopl=0         nv up ei ng nz na
    pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000
    efl=00010286
    e1k6232+0x16171:
    93da1171 f00fc111        lock xadd dword ptr [ecx],edx
    ds:0023:00000034=????????
    Resetting default scope
     
    LAST_CONTROL_TRANSFER:  from 93da1171 to 82e9982b
     
    STACK_TEXT:
    a610bb28 93da1171 badb0d00 ffffffff a610bcb4 nt!KiTrap0E+0x2cf
    WARNING: Stack unwind information not available. Following frames may be
    wrong.
    a610bbe8 93d9da0e 87958000 87961280 00000003 e1k6232+0x16171
    a610bc58 93d9c093 87958000 00000000 a610bca0 e1k6232+0x12a0e
    a610bc74 8bf8b309 87958000 00000000 a610bca0 e1k6232+0x11093
    a610bcb0 8bf6c6b2 8757cc44 0057cc30 00000000 ndis!ndisMiniportDpc+0xe2
    a610bd10 8bf53976 8757cd9c 00000000 881137b8
    ndis!ndisQueuedMiniportDpcWorkItem+0xd0
    a610bd50 830616bb 00000002 82fc3bb3 00000000
    ndis!ndisReceiveWorkerThread+0xeb
    a610bd90 82f130f9 8bf5388b 00000002 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
     STACK_COMMAND:  kb
     
    FOLLOWUP_IP:
    e1k6232+16171
    93da1171 f00fc111        lock xadd dword ptr [ecx],edx
     
    SYMBOL_STACK_INDEX:  1
     
    SYMBOL_NAME:  e1k6232+16171
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: e1k6232
     
    IMAGE_NAME:  e1k6232.sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bbae470
     
    FAILURE_BUCKET_ID:  0xD1_e1k6232+16171
     
    BUCKET_ID:  0xD1_e1k6232+16171
     
    Followup: MachineOwner
     
     

    -- Mike Burr
    Thursday, July 29, 2010 4:42 PM
  • Also, err a and d1 refer to similar errors (both are usually caused by
    errors in device drivers),
     
    # for hex 0xa / decimal 10 :
      IRQL_NOT_LESS_OR_EQUAL                                     bugcodes.h
     
    # for hex 0xd1 / decimal 209 :
      DRIVER_IRQL_NOT_LESS_OR_EQUAL                              bugcodes.h
     

    -- Mike Burr
    Thursday, July 29, 2010 4:45 PM
  • Well I have checked and the drivers, all of them, are up to date.  I will check again today though.  
    Thursday, July 29, 2010 5:05 PM
  • You might want to contact the vendor, if this is a new issue for them they might ask for a memory dump to help troubleshoot the issue and may have something available that is not posted on their site yet.
    -- Mike Burr
    Thursday, July 29, 2010 5:16 PM
  • Also, when you are getting the drivers, are you looking on the computer
    manufacturer site or the manufacturer for the network card?
     

    -- Mike Burr
    Thursday, July 29, 2010 5:35 PM
  • I typically get them from the computer manufactures site, in this case support.dell.com.  I am checking to see if i can contact Dell tech support directly, or if it has to go through our companies helpdesk to get addressed.  
    Thursday, July 29, 2010 7:03 PM
  • In the meantime, what model of system do you have and what information does the Components node of the msinfo32 utility describe for your network card(s)? I might be able to find newer drivers than the Dell support site has...
    -- Mike Burr
    Thursday, July 29, 2010 7:57 PM
  • Dell Latitude E6510.  

     

    Odly enough when I look for e1k6232.sys in the System Drivers note of msinfo, its not listed.  the closest one listed is e1kexpress which has a description of Intel(R) PRO/1000 PCI Express Network Connection Driver K.

    However under Components, Network then Adapter The network adapter is listed as Intel(R) 82577LM Gigabit Network Connection and has the driver listed as e1k6232.sys, and the Service name listed  of e1kexpress.  Looks like the version is 11.6.92.0 for the driver. 

    Thursday, July 29, 2010 8:36 PM
  • As long as Dell didn't do any major customization when they incorporated the network card, the generic driver listed here might work, but Dell might not provide support for them since they did not provide this driver. You could always take a backup and test the driver, and then try uninstalling the driver and reinstalling Dell's or restoring from backup if you encounter any major problems.

    http://www.intel.com/support/ethernetcomponents/controllers/82577/sb/CS-031229.htm

    http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Ethernet+Components&ProductLine=Ethernet+Controllers&ProductProduct=Intel%c2%ae+82577+Gigabit+Ethernet+PHY


    -- Mike Burr
    Thursday, July 29, 2010 9:09 PM
  • I'm having the exact same issue with an Latitude E6510 running Windows 7 Enterprise 32 bit. The problem for me seems to be copying large amounts of data, at least in excess of 1GB+. I was able to copy a 522MB zip file containing Symantec Endpoint Protection 11.0.5 (MR5) with no problem while I was setting it up.

     

    However, I am able to boot into safe mode and copy 3.5GB with no problem. A boot back into normal mode and disabling Symantec with an attempt to copy an 8.10GB PST yielded to the machine locking up completely but no BSOD this time.

     

    Any word if the Intel drivers were a success? Are you able to perform the same tasks as I am with the same results? ...just trying to narrow things down here.

     

    ~J.

    Friday, July 30, 2010 3:46 PM
  • Well I did install the one you linked from Intel.  It appears to contain the same exact version of the driver as the one from the Dell website, though it did give me all the other nice PROset features.  The driver still shows as being version 11.6.92.0 dated 4/12/2010. I'm not sure what the date was on the Dell issued driver, but the version number was the same.  

    I can also concur that transferring large amounts of data does fit with when I get the BSOD's most of the time.  I had not tried booting into safe mode though.  

    I am contacting Dell tech support via the website now so we will see what they say.  

    Friday, July 30, 2010 4:13 PM
  • I just got off the phone with Dell myself. I tried a selective startup disabling all startup items as well as non-Microsoft services. I was then able to transfer the 8.10GB PST as well 3.5GB of misc items from a My Documents folder from a file share on to the system successfully. Now it appears to be a matter of which service/startup item is causing the trip-up. Something seems to have a conflict of some sorts.

    ....I will post the results of my trial and error.

     

    ~J.

    Friday, July 30, 2010 4:43 PM
  • EDIT: Just Kidding... it eventually did it, just not as quick this time. Back to the drawing board.

     

    "So far it appears to be something with Symantec Endpoint Protection... are you running this as well?

    If so, try to disable the startup item "Symantec Security Technologies" that points to "C:\Program Files\Common Files\Symantec Shared\ccApp.exe". Let me know if you are able to copy files then."

     

    ~J.

    Friday, July 30, 2010 5:33 PM
  • Well Dell Techsupport was less than helpful.  They suggested I download the Microsoft debugging tools and analyze the minidump files myself.  It seems to be happening when I am doing a lot of multi tasking as well, I had 8 or so differnet programs up including a vMWare client and the console of a couple of VM's.  It just blue screened again a few mins ago, and I'm uploading that minidump fil to the same skydrive link as posted above.  

     

    I am not running Symantecs Endpoint encryption but we do use bitlocker.  At this point i'm putting a ticket in with out local helpdesk and see what they can do.  I imagine they will want to just re-image my laptop.. but I don't see much other choice at the moment.  I'll keep watching this thread and will update if I or they figure anything out.  

    Monday, August 2, 2010 9:13 PM
  • Sorry to hear that you are still having trouble, the latest error still
    seems to be coming from the same wireless driver, e1k6232.sys.
     
    Is there anyone else in your company that has the same system/configuration?
     *******************************************************************************
    *
          *
    *                        Bugcheck Analysis
          *
    *
          *
    *******************************************************************************
     
    Use !analyze -v to get detailed debugging information.
     
    BugCheck D1, {48, 2, 1, 93da41b8}
     
    Unable to load image \SystemRoot\system32\DRIVERS\e1k6232.sys, Win32
    error 0n2
    *** WARNING: Unable to verify timestamp for e1k6232.sys
    *** ERROR: Module load completed but symbols could not be loaded for
    e1k6232.sys
    Probably caused by : e1k6232.sys ( e1k6232+161b8 )
     
    Followup: MachineOwner
    ---------
     
    0: kd> !analyze -v
    *******************************************************************************
    *
          *
    *                        Bugcheck Analysis
          *
    *
          *
    *******************************************************************************
     
    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.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000048, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 93da41b8, address which referenced memory
     
    Debugging Details:
    ------------------
     WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82f6f718
    Unable to read MiSystemVaType memory at 82f4f160
     00000048
     
    CURRENT_IRQL:  2
     
    FAULTING_IP:
    e1k6232+161b8
    93da41b8 c7414800000000  mov     dword ptr [ecx+48h],0
     
    CUSTOMER_CRASH_COUNT:  1
     
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
     
    BUGCHECK_STR:  0xD1
     
    PROCESS_NAME:  System
     
    TRAP_FRAME:  9e42bb28 -- (.trap 0xffffffff9e42bb28)
    ErrCode = 00000002
    eax=0000fffb ebx=879a1280 ecx=00000000 edx=87998000 esi=879b8940
    edi=00000000
    eip=93da41b8 esp=9e42bb9c ebp=9e42bbe8 iopl=0         nv up ei pl nz na
    po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000
    efl=00010202
    e1k6232+0x161b8:
    93da41b8 c7414800000000  mov     dword ptr [ecx+48h],0
    ds:0023:00000048=????????
    Resetting default scope
     
    LAST_CONTROL_TRANSFER:  from 93da41b8 to 82e4d82b
     
    STACK_TEXT:
    9e42bb28 93da41b8 badb0d00 87998000 9e42bcb4 nt!KiTrap0E+0x2cf
    WARNING: Stack unwind information not available. Following frames may be
    wrong.
    9e42bbe8 93da0a0e 87998000 879a1280 00000004 e1k6232+0x161b8
    9e42bc58 93d9f093 87998000 00000000 9e42bca0 e1k6232+0x12a0e
    9e42bc74 8bf9f309 87998000 00000000 9e42bca0 e1k6232+0x11093
    9e42bcb0 8bf806b2 86fa6b94 00fa6b80 00000000 ndis!ndisMiniportDpc+0xe2
    9e42bd10 8bf67976 86fa6c94 00000000 887f9d48
    ndis!ndisQueuedMiniportDpcWorkItem+0xd0
    9e42bd50 830156bb 00000000 baaff024 00000000
    ndis!ndisReceiveWorkerThread+0xeb
    9e42bd90 82ec70f9 8bf6788b 00000000 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
     STACK_COMMAND:  kb
     
    FOLLOWUP_IP:
    e1k6232+161b8
    93da41b8 c7414800000000  mov     dword ptr [ecx+48h],0
     
    SYMBOL_STACK_INDEX:  1
     
    SYMBOL_NAME:  e1k6232+161b8
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: e1k6232
     
    IMAGE_NAME:  e1k6232.sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bbae470
     
    FAILURE_BUCKET_ID:  0xD1_e1k6232+161b8
     
    BUCKET_ID:  0xD1_e1k6232+161b8
     
    Followup: MachineOwner
    ---------
     

    -- Mike Burr
    • Proposed as answer by Andre.Ziegler Tuesday, August 3, 2010 11:58 AM
    Monday, August 2, 2010 10:16 PM
  • I got the same BSOD on the Dell E6410. I was trying to capture a Windows 7 image to our server.
    Tuesday, August 3, 2010 2:27 PM
  • I've been dealing with this for a few weeks myself with a slightly different configuration.

    I'm running a Dell E6410 with Windows 7 64-bit.

    I've updated all of my drivers and the bios.  The helpdesk guys at my company formatted and re-installed the OS thinking it was an issue caused by the disk being in RAID mode.  Nothing has worked and every BSOD now complains about the e1k62x64.sys driver, (the 64-bit version of the same driver.)

    This is yet another reason why I always get the Dell cards, the Intel devices have always caused me trouble.

    --

    Hunter Lewis

    Wednesday, August 4, 2010 6:47 PM
  • I downgraded the driver to the 11.5.10.0 version from Dell.

    Since then I've transferred about a GB and still going strong.

    Hope that helps.

    --

    Hunter Lewis

    Wednesday, August 4, 2010 9:08 PM
  • I contacted Dell Gold Support and they don't understand the problem they suggested installing latest driver. Duh. I upgraded BIOS to A04 and problem still exists. 
    Thursday, August 5, 2010 12:23 PM
  • Hi,

    I've got blue screens and after I read this, I remembered that I had installed a optional download: Intel - Network - Intel(R) 82577LM Gigabit Network Connection (164 KB) from Microsoft WIndows Update.

    Now I've got installed the driver from HP again, and delete the e1k6232.sys. I think DELL and HP are using the same network card so they get the same optional updates.

    Hopefully now, I don't get the blue secreens anymore.


    --------------------- Frank
    • Marked as answer by Magon Liu Friday, August 6, 2010 10:36 AM
    Friday, August 6, 2010 6:33 AM
  • I contacted Dell again and Per Hunter's suggestion requested the driver version 11.5.10.0 installed it and I was able to capture the image to a server.

    The Dell Tech refered me to a driver page for this download. What was interesting was Intel and Dell had 3 versions of this driver and each was labeled critical. :( 

    I emailed my results to the Dell Tech who took ownership of the problem. I don't know if this will get the ball rolling with Intel on this?

    The laptop's OS is Windows 7 Enterprise 32-bit.

    Regards to All!

    • Marked as answer by RustyZ Friday, August 6, 2010 3:54 PM
    Friday, August 6, 2010 10:38 AM
  • By chance do any of you guys have any Cisco VPN products installed or any Cisco products at all?
    Friday, August 6, 2010 3:05 PM
  • Not on this laptop! Windows 7 is still in an evaluation phase in my company.
    Friday, August 6, 2010 3:09 PM
  • Yes, I have the Cisco VPN client installed on my laptop.  

     

    I will try downgrading the network driver and will update in a few days.  Unfortunately I haven't been able to completely reproduce this, it just happens at seemingly random times.  I will keep everyone up to date.  

    Friday, August 6, 2010 3:50 PM
  • Try the latest Intel driver and remove Cisco VPN and see what happens.
    Friday, August 6, 2010 3:58 PM
  • So, my company is experiencing the elk6232.sys BSOD and we're investigating if our Cisco products have anything to do with it.  With those products uninstalled, we don't get BSODs, with them installed we get BSODs.  If we rev bacl to the 11.5 version of the Intel NIC driver, with Cisco products installed all is well.  Update to 11.6.92.0 and BSODs again.

    Here's the steps we use to reproduce the BSOD at will.

    Open IE and go to YouTube.com

    Do a search for High Definition 1080p

    Run the first one in the list which is some video about an IMAX under water Coral Reef movie preview.

    Change the resolution to 1080p (default is 360p)

    Then click the full screen button and run the video at full screen.

    The BSOD should happen pretty quick.  It usually happens for me within 10 secs.

    Give that a shot and see what you get.

    JY

    Friday, August 6, 2010 7:56 PM
  • Thanks to everyone here, especially JY.

    We are experiencing this as well. We have E6410s and are rolling them out with Windows 7. We use the Cisco VPN client as well. I migrated to the E6410 first for testing and ran into the problem. I downgraded the driver to 11.5 and everything is ok. I'll try testing w/out Cisco VPN and see what that does.

    ETA,

    I've reproduced the problem by copying large 2-3.5GB files from our fileserver to the laptop.

    Friday, August 6, 2010 8:22 PM
  • Thanks for the props.  We've been working on this for a couple of weeks now and have still not been able to get a proper fix.  We have MS engaged, Cisco engaged and Intel engaged.  I've tried the large file copy and that didn't seem to give me a BSOD.  I'll keep trying that howveer for sure I get it everytime with the streaming HD video test.

    My gut feeling is that it's an issue with Cisco interfering with the networking stack.  But I think there was someone in this thread that wasn't using Cisco, so obviously can't rule anything out.

     

    To be continued....

    JY

    Friday, August 6, 2010 10:03 PM
  • So has anyone tried the Intel 11.6.92.0 driver without Cisco VPN installed?  Just trying to see if we are going down the right path.

     

    JY

    Monday, August 9, 2010 6:46 PM
  • I tested several ways with driver version 11.6.92.0 and Cisco VPN Client 5.0.07.0290. Using a freshly installed OS, I tested with 11.6.92.0 and no Cisco products. I didn't test very much, but no BSODs. Installed the VPN client, and was able to force BSODs at will. Uninstalled the VPN client w/out a reboot, but still got BSODs. Rebooted, same thing. Downgraded to 11.5.10.0 - no problems. Upgraded again, BSODs. At this point, we need the Cisco VPN and we need to start rolling out laptops, so I downgraded the driver on our deployment server. I'd like the newer driver to be fixed, but don't have time to follow up on it now. I'd still like to test a fresh install without the VPN client, but it almost acted like the stack was tainted even after removing the Cisco VPN.
    Monday, August 9, 2010 7:14 PM
  • Thanks for the reply.  Can you let me know what your proceedure is for creating the BSOD? 
    Monday, August 9, 2010 8:26 PM
  • So far after downgrading to 11.5.10.0 I haven't had any issues.  Unfortunately I can't uninstall the VPN client as I need to use it almost daily.  I will try some of the above methods for reproducing the BSODS and see if I can get it to do anything.
    Tuesday, August 10, 2010 6:52 PM
  • To create the BSODs, I used the methods mentioned already - youtube streaming and large file transfers. The large file transfer seemed to produce them more reliably, but the surefire method I used was to start a file transfer (a folder with ghost images) and play a 1080p video on youtube. This produced BSODs within 10-20 seconds. I don't recall a time that it failed.
    Wednesday, August 11, 2010 12:55 PM
  • I've been fighting this issue for a week now. Win7 64-bit, on Dell E6410 testing with each driver set mentioned above. This machine also has the Cisco VPN client for 64-bit Win installed; ver 5.0.07.0240. I'll start down the path of removing the VPN client to continue testing.

    I'm able to create a BSOD by opening WMPlayer and listening to music shared via UNC. After selecting 10 tracks (MP3s), right click, Play, then pressing the Track Advance button 4 times.

    I'll post back if I discover anything.

    S

    Wednesday, August 11, 2010 3:07 PM
  • Hello everyone,

     

    I have been following this thread and wanted to throw in my 2 cents. I work at the University at Buffalo in an IT node and we just got in a few of the E6410's about a week ago. We created a Windows 7 64-bit image and threw it on all of the machines. Within a couple days one of our users was experiencing the same blue screen issue when streaming audio via Pandora and using the internet normally (however it did take several hours). We were able to reproduce the problem using video streaming via youtube. We did a slightly different technique, and instead of using one large video at 1080p would open up about 4-5 videos simultaneously. This would consistently produce a blue screen after 15-20 seconds using the Intel 82577LM driver (version 11.6.92.0 from Dell's website). We tried all the revisions listed for the 82577LM on Intel's site for this NIC, and the same problem would keep happening. After reading through this thread I thought it would be useful to try uninstalling the Cisco VPN software and that didn't stop the blue screen issue.

     

    What did stop the issue was using version 11.5.10.0 of the Intel 82577 NIC driver. After updating our image with this driver and applying it to 4 machines in the field, we have had no reports of problems. I was able to stream 20 youtube videos at once and it didn't even hiccup. Please note that we also did reinstall the VPN software and there are still no problems with it installed.

     

    Figured it wouldn't hurt to throw out another success story using 11.5.10.0. Best of luck everyone.

     

    John

    Wednesday, August 11, 2010 7:20 PM
  • So far after downgrading to 11.5.10.0 I haven't had any issues.  Unfortunately I can't uninstall the VPN client as I need to use it almost daily.  I will try some of the above methods for reproducing the BSODS and see if I can get it to do anything.


    So Rusty, here's the issues I have with just using the 11.5 driver. 

    1) What happens when a new driver comes out to support a newer NIC or they fix something critical?  I'll be stuck with the BSODs again.

    2) Along the lines of #1, Dell has an Urgent recommendation to upgrade to the 11.6.92.0 driver because it "Fixes intermittent NIC connectivity issues".  So if I go back to the 11.5 driver, I may be introducing some other issue.

    What we are seeing in both our corporate image and a plain vanilla install of Win7 is that when the Cisco VPN or SSC products are not installed, the BSODs don't manifest themselves.  So far, most every one on this thread has replied that they are running a Cisco product which seems a little more than coincidental in my mind.  Just in case of course, we have MS involved, Intel has been pulled in and of course Cisco.  So far no one has told us what's going on really. 

    One other thing I noticed in my testing is that with out the Cisco VPN installed, the streaming of the HD You Tube videos would go much faster than when VPN was installed.  I'm not even using VPN at this point, it's just installed.  With it installed the red bar showing the download progress goes quite fast, with VPN installed the red bar will barely keep ahead of the pace of playing the video and sometimes the video pauses to allow the buffer to catch up.  Odd behavior IMO.

    I'd be really interest to see if someone can do a clean install of the image or the OS itself and do testing with the 11.6.92.0 driver and see if they can get a BSOD.  If not, then install thier VPN client and see if they get it then.

    JY

    Wednesday, August 11, 2010 7:42 PM
  • Hello everyone,

     

    I have been following this thread and wanted to throw in my 2 cents. I work at the University at Buffalo in an IT node and we just got in a few of the E6410's about a week ago. We created a Windows 7 64-bit image and threw it on all of the machines. Within a couple days one of our users was experiencing the same blue screen issue when streaming audio via Pandora and using the internet normally (however it did take several hours). We were able to reproduce the problem using video streaming via youtube. We did a slightly different technique, and instead of using one large video at 1080p would open up about 4-5 videos simultaneously. This would consistently produce a blue screen after 15-20 seconds using the Intel 82577LM driver (version 11.6.92.0 from Dell's website). We tried all the revisions listed for the 82577LM on Intel's site for this NIC, and the same problem would keep happening. After reading through this thread I thought it would be useful to try uninstalling the Cisco VPN software and that didn't stop the blue screen issue.

     

    What did stop the issue was using version 11.5.10.0 of the Intel 82577 NIC driver. After updating our image with this driver and applying it to 4 machines in the field, we have had no reports of problems. I was able to stream 20 youtube videos at once and it didn't even hiccup. Please note that we also did reinstall the VPN software and there are still no problems with it installed.

     

    Figured it wouldn't hurt to throw out another success story using 11.5.10.0. Best of luck everyone.

     

    John


    Again, what's in common is that you had and use Cisco VPN which I find to be more than coincidental.  I found the same thing as you though, uninstalling VPN didn't resolve the issue.  It's only when I didn't have it on there from the beginning that I we'd stop getting BSODs.  I'm just wondering if in fact if you were able to test a scenerio without ever having the VPN client installed.

    JY

    Wednesday, August 11, 2010 8:18 PM
  • And BTW, I'm not trying to point the finger away from Intel and towards Cisco or MS, just trying to see if I can get someone else to see what we are seeing in our testing.  If in fact you get BSODs without ever have installed VPN but using 11.6.92.0 version of the driver, then my theroy needs to be shifted elsewhere.

    JY

    Wednesday, August 11, 2010 8:21 PM
  • And BTW, I'm not trying to point the finger away from Intel and towards Cisco or MS, just trying to see if I can get someone else to see what we are seeing in our testing.  If in fact you get BSODs without ever have installed VPN but using 11.6.92.0 version of the driver, then my theroy needs to be shifted elsewhere.

    JY

    Yeah definitely understand your view on it. Unfortunately we never did have a test scenario where we had a machine where the Cisco VPN client was never installed. I would also be quite interested to see what would happen!

     

    John

    Wednesday, August 11, 2010 9:03 PM
  • Per my plan I removed the Cisco VPN client I mentioned earlier plus removed the NIC driver as well and restarted. Reinstalled the NIC driver 11.6.92.0 and have not been able to generate the BSOD. Next I'll put the Cisco VPN client back and test... But as it stands the BSOD hasn't happened again.

     

    S

    Thursday, August 12, 2010 5:08 PM
  • Added the 64-bit Cisco VPN client and BSOD. I'll install the 32-bit version of the cisco VPN client and see what happens.

    S

    Thursday, August 12, 2010 5:36 PM
  • Uninstalled 64-bit version of Cisco VPN Client and no more BSOD. I'm not suggesting any connection or opinion just events.

    Can't install 32-bit Cisco VPN client on 64-bit system. I can live without the Cisco VPN client for now, and monitor for a more current version than 5.0.07.0290.

    S

    Thursday, August 12, 2010 5:46 PM
  • And BTW, I'm not trying to point the finger away from Intel and towards Cisco or MS, just trying to see if I can get someone else to see what we are seeing in our testing.  If in fact you get BSODs without ever have installed VPN but using 11.6.92.0 version of the driver, then my theroy needs to be shifted elsewhere.

    JY

    I was experiencing the BSOD with the 11.6.92.0 driver and I have never installed a VPN client on this machine.

    I did notice that if you poke around on the Dell driver page, there is a newer version number showing up, but it isn't possible to download it.  I'm not sure if it is a problem with the website or if they really will be posting a 15.x.x.0 version in the near future.  It seems like a pretty huge jump in version numbers, but who knows.

    --

    Hunter

    Thursday, August 12, 2010 6:46 PM
  • And BTW, I'm not trying to point the finger away from Intel and towards Cisco or MS, just trying to see if I can get someone else to see what we are seeing in our testing.  If in fact you get BSODs without ever have installed VPN but using 11.6.92.0 version of the driver, then my theroy needs to be shifted elsewhere.

    JY

    I was experiencing the BSOD with the 11.6.92.0 driver and I have never installed a VPN client on this machine.

    I did notice that if you poke around on the Dell driver page, there is a newer version number showing up, but it isn't possible to download it.  I'm not sure if it is a problem with the website or if they really will be posting a 15.x.x.0 version in the near future.  It seems like a pretty huge jump in version numbers, but who knows.

    --

    Hunter

    I think you may be looking at the NIC diagnostic download. It's version 15.x.x.0 but as far as I could see the actual NIC driver was still 11.6.92.0.

     

    John

    Thursday, August 12, 2010 8:39 PM
  • The Intel version of the suite of Intel NIC drivers for Windows is up to version 15.5, however 15.5 still have version 11.6.92.0 for the driver for the newer Dell and HP systems that use the elk6232.sys driver.

    Thursday, August 12, 2010 9:48 PM
  • I was experiencing the BSOD with the 11.6.92.0 driver and I have never installed a VPN client on this machine.

    I did notice that if you poke around on the Dell driver page, there is a newer version number showing up, but it isn't possible to download it.  I'm not sure if it is a problem with the website or if they really will be posting a 15.x.x.0 version in the near future.  It seems like a pretty huge jump in version numbers, but who knows.

    --

    Hunter

    Interesting Hunter.  By chance are there any other Cisco products installed?  Have you tried a fresh install with nothing on it but the drivers (no extra software added)?  I'm just wondering how some can't produce the BSOD while some can and most of us who can use a Cisco product.

    We use 2 Cisco products in our image and we only get BSODs when either one or both of these products are installed.  Without them, the BSODs go away which is now what Schwinke seems to be seeing.

    We have it in the hands of both Intel and Cisco and whatever we get back I'll report here and maybe it'll help others.

    JY

    Thursday, August 12, 2010 9:53 PM
  • Anyone have any updates?  We're still in the process of getting Cisco and Intel working together to look more closely at this issue.
    Tuesday, August 17, 2010 1:45 PM
  • Just to add my experiences to the mix:

    I've got an E6410 running Windows 7 64-bit.  No Cisco or other VPN products installed.  I get a Stop 0xD1 BSOD intermittently when playing a large AVI file (not HD) that's located on a network share.  Doesn't always happen, so I can't recreate at will, but I can tell it's coming when the video playback starts getting choppy.

    Current NIC driver is 11.6.92.0.

    Saturday, August 21, 2010 3:46 PM
  • Our agency is getting ready to field the E6510 as well and we are getting the same errors with the BSOD, however we CAN recreate the error consistently.  Watching the video clips is fine while streaming, as long as the image has been BUFFERED, but if we skip ahead numerous occasisions to where we are getting ahead of the bufferin that is when we get the BSOD.  We have the Cisco VPN client on our new laptops as well.

     

    Friday, August 27, 2010 5:32 PM
  • aic90

    I am getting this also on my E6410 with Windows 7 64bit and only with Cisco anyconnect client (which is not near as intrusive as the ipsec client).  I think it is a driver problem that really needs some attention.

    Tuesday, August 31, 2010 4:27 AM
  • I'll jump in here to say I am having the same issue, but not on a Dell.  Just rolled out an HP 8540p, but it has the same Intel card.  I can reproduce this at will with the YouTube steps provided above.  Heck, it will often crash just at the YouTube intro screen.

    I, too, have the Cisco VPN client installed.  Uninstalling it has 0 effect.  Here's what I am wondering:  Is it something to do with Symantec Endpoint Protection?  I know some others said they did not have SEP installed, but others said they didn't have the VPN client either.   Looking back at my logs, I see that the update for the network driver was rolled out on Aug 9.  I had 0 instances of the BSOD for 2 weeks and during that time, this laptop was under normal use the same as what triggers it now.  During that time, a new version of SEP was rolled out and, by mistake, the admin that manages that app installed the Network Threat Protection module of SEC.  This was on Aug 13.  It still may not be SEP as the first BSOD was not until Aug 24.  So a full 2 weeks of normal use before the crashes.

    Now that I can reproduce it, I'll start troubleshooting here as well and post back what I find.

    Tuesday, August 31, 2010 3:39 PM
  • Testing this more this morning and the problem *seems* to have gone away.  Here's what I did/found...

    All tests were done using the YouTube steps above

    -Uninstalled Cisco VPN Client, still got BSOD anywhere from 0 to 45 seconds into video

    -Disabled every part of SEP, no change

    -Looked at installed apps to see what was installed in the two week time frame between driver update and first BSOD.  The only two things there were SEP and something called System Requirements Lab.  I have no idea what SRL is nor did I install it.  I suspect it piggy backed in on something.  Anyway, I uninstalled that and the BSODs went away.  I have been trying for and hour to invoke one, but it has not happened yet.

    -I reinstalled the Cisco VPN and have not gotten the BSOD so far.

     

    I will keep monitoring this and report back if I find out anything else useful.  I am tempted to go find the SRL and reinstall it to see if the BSODs come back, but I really don't like doing that.

    Tuesday, August 31, 2010 5:50 PM
  • thanks for the info.  I'm running an E6410 recently install with Windows 7 32bit and Cisco VPN client.  Couldn't figure out why it would keep hanging (as I had it's exact twin with Windows 7 64bit with no issues but running the Cisco AnyConnect.

    I've gone to Dell and installed the Dell Drivers as well as all the Intel chipset updates.   Just an FYI, My bios is even current A04.

    Now mind you, if I was running Direct Access, I'll bet none of this would be happening ;)

    Sean


    Powershell. It's so Easy and it's FREE! Dive in and use it now, It'll take no time. :) http://www.energizedtech.com http://www.itprotoronto.ca
    Thursday, September 2, 2010 7:04 PM
  • Update:

    My Dell E6410 is a personal device, but I happen to be a director in the IT shop of a large company that uses Dell for desktops & laptops.  Getting nowhere with first line Dell support, I approached our desktop area at work asking for a name within Dell support that I could contact directly.  Anyway after a week or so of back & forth with the contact I was given, the representative said today that they are now aware of the STOP 0xD1 BSOD's and have a fix in the form of a beta driver.  I'm going to have to sign a non-disclosure agreement to get the driver.  As of this writing, the non-disclosure form had not made its way to me.

    Cokeman92,

    I also have System Requirements Lab installed.  On my machine it's called "System Requirements Lab for Intel."  I suspect it came along with either the wired or wireless NIC drivers.  Since a new driver is coming, I haven't tried de-installing this software and testing for the BSOD's.

    Thursday, September 2, 2010 11:06 PM
  • UPDATE - -

    Sorry that it's been so long since I've posted.  Here's what we've found out.  We worked with Cisco as far as we could go and we also engaged Intel.  Then Cisco engaged Intel as well and they looked over our dumps and were also able to reproduce with Intel driver 11.6.92 and Cisco VPN.  It then went to Intel engineering and they determined what the fault was. 

    Here's what we were told:

    "The Message Signalled Interrupts, a high-efficiency interrupt method used in PCI Express, was not not enabled for the 82577 devices.  Adding the command to enable these interrupts resolved the issue in our reproduction environment."

    He also told us that Intel had put out 11.6.92 to resolve an issue that one company was having (didn't get the exact details on that) and appearenly that broke the driver so that when various VPN programs were installed (including Cisco) it caused the NIC driver to crash.

    Intel corrected the bug and let us test the fix and it worked just fine.  The fixes are in the .inf and not the .sys (driver) itself. They are now in the midst of getting the driver WHQL certified and will post it as soon as it is.  In the meantime Intel says to use the  11.5.10 driver which also doesn't have the issue.  I asked them about the Dell urgent request to update to 11.6.92 because it "Fixes Intermittent NIC connectivity issues" and he said that  was all about that one company and that chances are we would not experience the same connectivity issues.  So we're moving forward with 11.5.10 and we'll move to the next version in our next update down the road sometime.

    Hope this helps.

    JY

    • Proposed as answer by JYoung1055 Friday, September 3, 2010 1:30 AM
    Friday, September 3, 2010 1:25 AM
  • Thanks to all for posting on this issue.  Its always great to find others suffering just as badly :)   I just got off the phone with Dell regarding this issue on a E6410 with win7 32bit, and the tech is attempting to update their KB with this information so that they can give this fix to other users.  For anyone looking, Dell has the 11.5 drivers posted on their site here:

    http://support.dell.com/support/downloads/download.aspx?c=us&cs=555&l=en&s=biz&releaseid=R267025&SystemID=lat_e6410&servicetag=&os=W764&osl=en&deviceid=11814&devlib=0&typecnt=0&vercnt=3&catid=-1&impid=-1&formatcnt=0&libid=5&typeid=-1&dateid=-1&formatid=-1&source=-1&fileid=392592

    I had additional trouble installing 11.5 - for anyone attempting the downgrade be sure to remove any Intel NIC software in "programs & features" under control panel in addition to removing from device manager.  I also had to uninstall Checkpoint VPN client before installing the downgraded driver, as all my attempts to install resulted in an adapter without IP4/6.  Tests so far with 11.5 seem good, so I'll be re-installing checkpoint soon.  I will be watching for the new driver from Intel.  Thanks again for everyone's input.

    • Proposed as answer by Spaceballone Wednesday, September 29, 2010 9:44 PM
    Friday, September 3, 2010 10:57 PM
  • Refreshing to see that they took the time to identify the problem and suggest a fix.

     

    Just FYI, I have still not had a BSOD since my posting above and I have been occasionally trying to induce it.  I am still using the  11.6.92 version of the Intel driver, but I did notice that when I reinstalled the VPN client, that a newer version had been rolled out.  The previous version I had was 2.3.254 and the current version is 2.5.217.  I am not sure if the new VPN client corrected an issue or what is going on there as the problem was eliminated when I uninstalled the SRL mentioned above and I didn't reinstall the VPN until after I went awhile without crashing.  Since the fix JY mentions is in the .inf and not the .sys, I suspect that the uninstall SRL and VPN/Reinstall newer VPN corrected a problem in the .inf.

     

    Sounds like reverting back to the old driver is the most reliable solution for most, but I am just letting everyone know that I fixed mine without doing that.  But, again, this problem child is an HP and not a Dell so there could be issues with the proprietary software.  I killed the HP stuff.

     

    That's my $0.02.

    Tuesday, September 7, 2010 1:54 AM
  • I have similar issue - using E6410 with 64-bit Windows 7 - Intel 82577 Gigabit - Driver 11.6.92.0 - Works fine most of the time in Docking station. BSOD when watching online streaming video or webinars - shows e1k62x64.sys caused the BSOD.
    Thursday, September 9, 2010 2:31 PM
  • rcusa:  I suggest you contact Dell support and request the beta driver that fixes the issue.  I installed it last Friday (9/3) and have not had a BSOD since.  I had to sign a non-disclosure agreement in order to obtain the driver.  They said the driver would be GA late this month.

    Hope this helps...

    Saturday, September 11, 2010 1:27 AM
  • I am experiencing the exact same BSOD while hard wired to the network.  The box is a DELL E6410 with win7 32bit.  Is there a fix yet from DELL.  It is painfull to wade through their teir 1 support.  If anyone has the beta driver link, pleae post. 

    Thank you.


    Sonders
    Wednesday, September 22, 2010 1:20 PM
  • Hello All,

    Thanks for the collabrative ideas and testing. Figure i'd put my 2 cents in. I too had VPN installed on my machine and got the BSOD to go away after the following:

    -uninstalling Cisco VPN and its driver hidden in the device manager. Make sure you delete this driver for it is the cuase of the OS not totally seeing it as uninstalled.

    -Uninstalling everything that is related to the Itel NIC *this includes hidden drivers and Programs

    -just like everyone suggested - revert back to 11.5.10 from the link above

    -Have no problems so far, have run 1080P streams from youtube and Netflix with no issues. Will try to install the new VPN client and do some more testing.

    Wednesday, September 29, 2010 9:51 PM
  • We are experiencing same issue.  I found the following on the Intel site

    http://communities.intel.com/message/102835;jsessionid=896ED996D9140AB9AF367D501792DCCC.node7COM

    reply 32 if you are running 64bit

    reply 38 if you are running 32bit

    I am running this updated INF on the 11.6.92 driver from the Dell website (so not downloading the Intel driver- still running the Dell driver)  You have to force the update and get thru the warning messges etc.

    Interested in knowing if this assists others as well as I haven't come across a sure fire way of forcing BSOD.  But situations where I did BSOD, no longer occur.  (massive file transfers over LAN, extracting WIMs over LAN to LAN location etc)

     

     

     

     

     

    Tuesday, October 5, 2010 4:00 AM
  • New Dell Network driver:

    1. Fixes blue-screens at high traffic.

    R280807.exe version: 11.6.92.0, A05

    • Proposed as answer by kswags Thursday, November 4, 2010 1:48 PM
    Tuesday, November 2, 2010 9:53 AM
  • New Dell Network driver:

    1. Fixes blue-screens at high traffic.

    R280807.exe version: 11.6.92.0, A05


    We began with 11.6.92.0 which is when we saw crashes during high traffic. Downgrade to 11.5.10.0 resolved it.

    Is there a documentation that says 11.6.92.0 resolves the issue?


    Mayur
    Monday, November 15, 2010 4:19 PM
  • Had the same issue with E6510 with VPN and this has fixed the issue.
    Monday, December 6, 2010 9:06 PM
  • neil,

    Are you saying downgrading to the 11.15.10 driver resolved it or applying the R280807 driver resolved the BSOD.  I also have E6510's with Cisco VPN 64bit 5.07 and have BSOD a couple of times with e1k62x64.sys error.  Thanks.

    Friday, December 10, 2010 4:38 PM
  • Im also confused Neil. Does the 11.5 downgrade fix it, or did the new 11.6.92.0 fix it?
    Thursday, December 16, 2010 10:15 PM