BSOD 0x000000d1 usually watching video


  1. Posts : 1
    Windows 7 Ultimate x64
       #1

    BSOD 0x000000d1 usually watching video


    Hi,

    I started getting a new BSOD on Monday. It crashed 2 or 3 times Monday, and 2 or 3 times Tuesday. I tried Dell tech support, and we tried a system restore to Friday. The most recent program installed was Spotify. After the system restore Spotify was not working so I uninstalled it. After coming back up, I had additional crashes today.

    Most of the crashes happen when I am watching a video, like on Yahoo! Finance. I'm not sure if they are Flash videos or otherwise. I am using IE 9. However, some of the BSOD's happend when I was not watching a video.

    It says it is 0x000000d1, DRIVER_IRQL_NOT_LESS_OR_EQUAL, and the file is ELK62x64.sys, I'm not sure what that file is; I can't seem to find it on my hard drive or get any good search results.

    I've attached the SF_Diagnostic_Tool data.

    Thanks so much for any assistance!

    -Tom
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome to Seven Forums.

    Please update this driver Intel 82577LM Gigabit NIC

    Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program:


    Driver Reference Table - e1k62x64.sys
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {90, 2, 1, fffff88004685353}
    
    *** WARNING: Unable to verify timestamp for e1k62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1k62x64.sys
    Probably caused by : e1k62x64.sys ( e1k62x64+1b353 )
    
    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: 0000000000000090, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff88004685353, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c30e0
    GetUlongFromAddress: unable to read from fffff800030c3198
     0000000000000090 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    e1k62x64+1b353
    fffff880`04685353 48899090000000  mov     qword ptr [rax+90h],rdx
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff88002b24850 -- (.trap 0xfffff88002b24850)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8006b23750
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88004685353 rsp=fffff88002b249e0 rbp=0000000000000159
     r8=fffffa80081ce270  r9=0000000000000000 r10=fffffa80067e08c0
    r11=000000000000fffb r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    e1k62x64+0x1b353:
    fffff880`04685353 48899090000000  mov     qword ptr [rax+90h],rdx ds:00000000`00000090=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002e8ab69 to fffff80002e8b600
    
    STACK_TEXT:  
    fffff880`02b24708 fffff800`02e8ab69 : 00000000`0000000a 00000000`00000090 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`02b24710 fffff800`02e897e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`02b24850 fffff880`04685353 : fffffa80`06bf7550 fffffa80`06f0b140 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`02b249e0 fffffa80`06bf7550 : fffffa80`06f0b140 00000000`00000000 00000000`00000000 00000000`00000000 : e1k62x64+0x1b353
    fffff880`02b249e8 fffffa80`06f0b140 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0468d445 : 0xfffffa80`06bf7550
    fffff880`02b249f0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`0468d445 fffffa80`00000000 : 0xfffffa80`06f0b140
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    e1k62x64+1b353
    fffff880`04685353 48899090000000  mov     qword ptr [rax+90h],rdx
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  e1k62x64+1b353
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: e1k62x64
    
    IMAGE_NAME:  e1k62x64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bbae4c3
    
    FAILURE_BUCKET_ID:  X64_0xD1_e1k62x64+1b353
    
    BUCKET_ID:  X64_0xD1_e1k62x64+1b353
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm e1k62x64
    start             end                 module name
    fffff880`0466a000 fffff880`046b6000   e1k62x64 T (no symbols)           
        Loaded symbol image file: e1k62x64.sys
        Image path: \SystemRoot\system32\DRIVERS\e1k62x64.sys
        Image name: e1k62x64.sys
        Timestamp:        Tue Apr 06 13:37:39 2010 (4BBAE4C3)
        CheckSum:         0004DF61
        ImageSize:        0004C000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Install all updates including Service Pack 1

    Learn how to install Windows 7 Service Pack 1 (SP1)

    Perform a System File Check to check the integrity of all protected Windows 7:
    1. Click on the start
    2. Type CMD on Search
    3. Left click and Run as Administrator
    4. Type
      Code:
      SFC /scannow

    Full tutorial here:

    Check your hard drive(s) for errors by running chkdsk

    Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.

    Good luck.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:20.
Find Us