Random BSOD, l1c62x64 file mentioned before restart

[jarnaez]

I've had two bsods in the past three days which is rather unusual. It didn't happen until recently. Not really sure what might be doing this. Ran DM log collector and attached the file.

 

[Arc]

Hi.

Can you download and install the last one (as marked in the attached image) of this list form Driver Downloads | Qualcomm Atheros, Inc.

View attachment 330185
​

Let us know.
____________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff880071e54be}

*** WARNING: Unable to verify timestamp for L1C62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1C62x64.sys
Probably caused by : L1C62x64.sys ( L1C62x64+64be )

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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880071e54be, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ae100
GetUlongFromAddress: unable to read from fffff800030ae1c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
L1C62x64+64be
fffff880`071e54be 488b08          mov     rcx,qword ptr [rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  LMS.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE:  FFFFF80004AA7FB0

TRAP_FRAME:  fffff80004aa62d0 -- (.trap 0xfffff80004aa62d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000000015f2
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880071e54be rsp=fffff80004aa6460 rbp=fffffa800dd54c58
 r8=00000000000002a1  r9=fffffa800d363000 r10=9bb8140000000060
r11=fffff80004aa6480 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
L1C62x64+0x64be:
fffff880`071e54be 488b08          mov     rcx,qword ptr [rax] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e76169 to fffff80002e76bc0

STACK_TEXT:  
fffff800`04aa6188 fffff800`02e76169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`04aa6190 fffff800`02e74de0 : 00000000`00000002 00000000`00000074 fffffa80`072ef000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff800`04aa62d0 fffff880`071e54be : fffffa80`0dbbbe80 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff800`04aa6460 fffffa80`0dbbbe80 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0dbbbe80 : L1C62x64+0x64be
fffff800`04aa6468 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0dbbbe80 fffffa80`0dd0f070 : 0xfffffa80`0dbbbe80


STACK_COMMAND:  kb

FOLLOWUP_IP: 
L1C62x64+64be
fffff880`071e54be 488b08          mov     rcx,qword ptr [rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  L1C62x64+64be

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: L1C62x64

IMAGE_NAME:  L1C62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50077726

FAILURE_BUCKET_ID:  X64_0xD1_L1C62x64+64be

BUCKET_ID:  X64_0xD1_L1C62x64+64be

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_l1c62x64+64be

FAILURE_ID_HASH:  {988d9035-c693-869c-8559-08edd06bdb0a}

Followup: MachineOwner
---------

0: kd> lmvm L1C62x64
start             end                 module name
fffff880`071df000 fffff880`071fd000   L1C62x64 T (no symbols)           
    Loaded symbol image file: L1C62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\L1C62x64.sys
    Image name: L1C62x64.sys
    Timestamp:        Thu Jul 19 08:25:34 2012 (50077726)
    CheckSum:         0001FE91
    ImageSize:        0001E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4