BSOD watching movie using VLC


  1. Posts : 9
    Windows 7 Ultimate 32bit
       #1

    BSOD watching movie using VLC


    I have not had this problem for a long time. Recently, I was just watching a movie using VLC media player and PC will suddenly have a blue screen and shut down, I am not aware of the reason. Any help in identifying the issue would be greatly appreciated.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Download and install Drivers for Atheros L1E and Windows 7.

    Report us for any further BSOD.
    ______________________________________________
    Code:
    BugCheck D1, {14, 2, 0, 8b07a6fa}
    
    Unable to load image \SystemRoot\system32\DRIVERS\L1E60x86.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for L1E60x86.sys
    *** ERROR: Module load completed but symbols could not be loaded for L1E60x86.sys
    Probably caused by : L1E60x86.sys ( L1E60x86+5a09 )
    
    Followup: MachineOwner
    ---------
    
    1: 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: 00000014, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8b07a6fa, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82d7f84c
    Unable to read MiSystemVaType memory at 82d5ee20
     00000014 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    ndis!NdisMAllocateNetBufferSGList+40
    8b07a6fa 8b4b14          mov     ecx,dword ptr [ebx+14h]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  PING.EXE
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    TRAP_FRAME:  abdad4c0 -- (.trap 0xffffffffabdad4c0)
    ErrCode = 00000000
    eax=0000002c ebx=00000000 ecx=00000020 edx=85616e30 esi=86524590 edi=85616e30
    eip=8b07a6fa esp=abdad534 ebp=abdad548 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    ndis!NdisMAllocateNetBufferSGList+0x40:
    8b07a6fa 8b4b14          mov     ecx,dword ptr [ebx+14h] ds:0023:00000014=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 8b07a6fa to 82c56b7f
    
    STACK_TEXT:  
    abdad4c0 8b07a6fa badb0d00 85616e30 00000000 nt!KiTrap0E+0x1b3
    abdad548 8ff6fa09 86524590 85616e30 868ae730 ndis!NdisMAllocateNetBufferSGList+0x40
    WARNING: Stack unwind information not available. Following frames may be wrong.
    abdad5bc 8ff6b34a 000003fe 85616e30 00000000 L1E60x86+0x5a09
    abdad5e0 8b0deda1 025371b8 00000000 00000000 L1E60x86+0x134a
    abdad614 8b07a4d8 864020e0 857ce678 00000000 ndis!ndisMSendNBLToMiniport+0x11a
    abdad634 8b07a448 857ce678 857ce678 00000000 ndis!ndisFilterSendNetBufferLists+0x87
    abdad64c 8f745c20 8655d660 857ce678 00000000 ndis!NdisFSendNetBufferLists+0x38
    abdad6c8 8b07a618 8690b0b0 857ce678 00000000 pacer!PcFilterSendNetBufferLists+0x256
    abdad6f4 8b0debad 864020e0 857ce678 00000000 ndis!ndisSendNBLToFilter+0xf2
    abdad724 8b298953 867fe740 857ce678 00000000 ndis!NdisSendNetBufferLists+0x162
    abdad770 8b2bb164 867fe008 00000000 00000000 tcpip!FlSendPackets+0x416
    abdad7c4 8b2ba1ea 8b31cda0 00000000 00000000 tcpip!IppFragmentPackets+0x2e2
    abdad7fc 8b297a2b 8b31cda0 860acd54 860acdf0 tcpip!IppDispatchSendPacketHelper+0x266
    abdad89c 8b298516 000acd54 8b31cda0 00000000 tcpip!IppPacketizeDatagrams+0x8d6
    abdad91c 8b299dc7 00000000 857ce600 8b31cda0 tcpip!IppSendDatagramsCommon+0x67f
    abdad93c 8b263b5c 8b31cda0 abdad988 87d4c288 tcpip!IppSendDatagrams+0x2a
    abdad964 8b259612 00000000 00000000 857ce678 tcpip!IppSendControl+0x100
    abdadaec 8b259769 00000000 000020c1 8b318d1c tcpip!Ipv4SetEchoRequestCreate+0x72a
    abdadb34 8b135e62 abdadb4c 00000000 8792e278 tcpip!Ipv4SetAllEchoRequestParameters+0xf6
    abdadb74 8f7e508f 00000006 86f8bac4 00000000 NETIO!NsiSetAllParametersEx+0xc0
    abdadbc0 8f7e5f0c 00000000 855fda88 855fdac0 nsiproxy!NsippSetAllParameters+0x1b1
    abdadbe4 8f7e5fe5 86f8ba01 00000000 855d0f80 nsiproxy!NsippDispatchDeviceControl+0x88
    abdadbfc 82c4cc1e 8639cae0 86f8baa8 86f8baa8 nsiproxy!NsippDispatch+0x33
    abdadc14 82e40bf9 855d0f80 86f8baa8 86f8bb18 nt!IofCallDriver+0x63
    abdadc34 82e43de2 8639cae0 855d0f80 00000000 nt!IopSynchronousServiceTail+0x1f8
    abdadcd0 82e8a779 8639cae0 86f8baa8 00000000 nt!IopXxxControlFile+0x6aa
    abdadd04 82c538c6 0000006c 000000bc 00000000 nt!NtDeviceIoControlFile+0x2a
    abdadd04 778770f4 0000006c 000000bc 00000000 nt!KiSystemServicePostCall
    001ef354 00000000 00000000 00000000 00000000 0x778770f4
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    L1E60x86+5a09
    8ff6fa09 ??              ???
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  L1E60x86+5a09
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: L1E60x86
    
    IMAGE_NAME:  L1E60x86.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  48d9e8f4
    
    FAILURE_BUCKET_ID:  0xD1_L1E60x86+5a09
    
    BUCKET_ID:  0xD1_L1E60x86+5a09
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xd1_l1e60x86+5a09
    
    FAILURE_ID_HASH:  {9305afff-9930-2294-0bba-6399b26b7fd2}
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmvm L1E60x86
    start    end        module name
    8ff6a000 8ff7a000   L1E60x86 T (no symbols)           
        Loaded symbol image file: L1E60x86.sys
        Image path: \SystemRoot\system32\DRIVERS\L1E60x86.sys
        Image name: L1E60x86.sys
        Timestamp:        Wed Sep 24 12:45:00 2008 (48D9E8F4)
        CheckSum:         00011115
        ImageSize:        00010000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 9
    Windows 7 Ultimate 32bit
    Thread Starter
       #3

    Didn't expect an immediate response, but thanks. I just have one question (and forgive me about this), the zip file I downloaded from the website you mentioned doesn't have an .exe file that I can use to install the drivers. Tried the method I found on Google but it gives me an error saying the drivers are not compatible, so I had to roll back.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Driver Install - Device Manager

    If it still say that the drivers are not compatible, that is not true, because

    Your network is ....
    Code:
    Name    [00000009] Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller
    Driver    c:\windows\system32\drivers\l1e60x86.sys (1.0.0.38, 47.00 KB (48,128 bytes), 12/22/2014 1:42 PM)
    And the driver is meant for ....
    I think it is clear to you now.
      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 13:14.
Find Us