L1c63x64 sys синий экран ошибка

Ответы

• Related to L1C63x64.sys Qualcomm Atheros Ar81xx series PCI-E Gigabit Ethernet Controller from Qualcomm Atheros Co., Ltd.

  Completely remove the current driver (or software) and install the newest driver available.  For instructions on how to do that Read all about updating drivers by my partner JMH3143 here http://answers.microsoft.com/en-us/windows/wiki/windows_other-hardware/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1?tm=1436753520149

  Other old drivers needing updating

  Sentinel64.sys    6/2/2008 2:14:55 AM                          
  
  jnprvamgr.sys    11/18/2009 1:39:04 PM                     
  
  LhdX64.sys    1/11/2010 11:06:58 AM                             
  
  ElcMouLFlt.sys    10/4/2010 7:30:57 PM                       
  
  ElcMouUFlt.sys    11/30/2010 1:42:46 AM                            
  
  t_mouse.sys    12/3/2012 2:19:30 AM                        
  
  excfs.sys    1/8/2013 12:00:53 PM                              
  
  excsd.sys    1/8/2013 12:00:57 PM                        
  
  AcpiVpc.sys    2/16/2013 9:52:02 PM                            
  
  trufos.sys    3/6/2013 7:47:58 AM                          
  
  avc3.sys    4/11/2013 4:31:58 AM                            
  
  gzflt.sys    4/22/2013 6:21:00 AM  
  TeeDriverx64.sys    7/2/2013 2:38:08 PM                       
  
  L1C63x64.sys    7/16/2013 2:56:31 AM                      
  
  rtsuvc.sys    7/19/2013 3:58:16 AM                         
  
  dump_iaStorA.sys    8/1/2013 9:39:52 PM                        
  
  iaStorA.sys    8/1/2013 9:39:52 PM                         
  
  RTKVHD64.sys    8/30/2013 8:59:57 AM  

     

  How To Find Drivers:

  Do not use device manager it may tell you the device is up to date but will not tell you if it is corrupt 

  Search Google for the name of the driver, or go to the computer makers site.

  
  Compare the Google results with what’s installed on your system to figure out which device/program it belongs to
  Visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON’T use Windows Update or the Update driver function of Device Manager).
  If there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program

  The most common drivers are listed on these pages: 
  http://www.carrona.org/dvrref.php
  http://sysnative.com/drivers/

  Driver manufacturer links are on this page: http://www.carrona.org

  Microsoft (R) Windows Debugger Version 10.0.14318.1022 AMD64
  Copyright (c) Microsoft Corporation. All rights reserved.
  
  
  Loading Dump File [C:UsersZigzag3143Desktop52316-46500-01.dmp]
  Mini Kernel Dump File: Only registers and stack trace are available
  
  
  ************* Symbol Path validation summary **************
  Response                         Time (ms)     Location
  Deferred                                       SRV*D:symbols*http://msdl.microsoft.com/download/symbols
  Symbol search path is: SRV*D:symbols*http://msdl.microsoft.com/download/symbols
  Executable search path is: 
  Windows 10 Kernel Version 10586 MP (8 procs) Free x64
  Product: WinNt, suite: TerminalServer SingleUserTS Personal
  Built by: 10586.306.amd64fre.th2_release_sec.160422-1850
  Machine Name:
  Kernel base = 0xfffff802`10892000 PsLoadedModuleList = 0xfffff802`10b70cd0
  Debug session time: Mon May 23 23:46:36.408 2016 (UTC - 4:00)
  System Uptime: 7 days 21:45:24.332
  Loading Kernel Symbols
  ...............................................................
  ................................................................
  ...........................................................
  Loading User Symbols
  Loading unloaded module list
  ..................................................
  *******************************************************************************
  *                                                                             *
  *                        Bugcheck Analysis                                    *
  *                                                                             *
  *******************************************************************************
  
  Use !analyze -v to get detailed debugging information.
  
  BugCheck D1, {0, 2, 0, fffff80146aa6cb3}
  
  *** WARNING: Unable to verify timestamp for L1C63x64.sys
  *** ERROR: Module load completed but symbols could not be loaded for L1C63x64.sys
  Probably caused by : L1C63x64.sys ( L1C63x64+6cb3 )
  
  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: 0000000000000000, memory referenced
  Arg2: 0000000000000002, IRQL
  Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
  Arg4: fffff80146aa6cb3, address which referenced memory
  
  Debugging Details:
  ------------------
  
  
  DUMP_CLASS: 1
  
  DUMP_QUALIFIER: 400
  
  BUILD_VERSION_STRING:  10.0.10586.306 (th2_release_sec.160422-1850)
  
  SYSTEM_MANUFACTURER:  LENOVO
  
  SYSTEM_SKU:  LENOVO_BI_IDEAPAD  
  
  SYSTEM_VERSION:  IdeaPad Y510P
  
  BIOS_VENDOR:  LENOVO
  
  BIOS_VERSION:  74CN44WW(V3.05)
  
  BIOS_DATE:  09/18/2013
  
  BASEBOARD_MANUFACTURER:  LENOVO
  
  BASEBOARD_PRODUCT:  VIQY0Y1
  
  BASEBOARD_VERSION:  31900006WIN8 STD MBR IPG
  
  DUMP_TYPE:  2
  
  BUGCHECK_P1: 0
  
  BUGCHECK_P2: 2
  
  BUGCHECK_P3: 0
  
  BUGCHECK_P4: fffff80146aa6cb3
  
  READ_ADDRESS: fffff80210c10520: Unable to get MiVisibleState
   0000000000000000 
  
  CURRENT_IRQL:  2
  
  FAULTING_IP: 
  L1C63x64+6cb3
  fffff801`46aa6cb3 488b08          mov     rcx,qword ptr [rax]
  
  CPU_COUNT: 8
  
  CPU_MHZ: 95a
  
  CPU_VENDOR:  GenuineIntel
  
  CPU_FAMILY: 6
  
  CPU_MODEL: 3c
  
  CPU_STEPPING: 3
  
  CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1E'00000000 (cache) 1E'00000000 (init)
  
  CUSTOMER_CRASH_COUNT:  1
  
  DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
  
  BUGCHECK_STR:  AV
  
  PROCESS_NAME:  Overwatch.exe
  
  ANALYSIS_SESSION_HOST:  DESKTOP-6TOHK78
  
  ANALYSIS_SESSION_TIME:  05-24-2016 23:04:45.0261
  
  ANALYSIS_VERSION: 10.0.14318.1022 amd64fre
  
  TRAP_FRAME:  ffffd0002b894af0 -- (.trap 0xffffd0002b894af0)
  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=fffff80146aa6cb3 rsp=ffffd0002b894c80 rbp=ffffe000d63fa628
   r8=000000000000014a  r9=ffffe000d5fbc000 r10=000000000000008a
  r11=ffffd0002b894c40 r12=0000000000000000 r13=0000000000000000
  r14=0000000000000000 r15=0000000000000000
  iopl=0         nv up ei pl nz na pe nc
  L1C63x64+0x6cb3:
  fffff801`46aa6cb3 488b08          mov     rcx,qword ptr [rax] ds:00000000`00000000=????????????????
  Resetting default scope
  
  LAST_CONTROL_TRANSFER:  from fffff802109df2e9 to fffff802109d4780
  
  STACK_TEXT:  
  ffffd000`2b8949a8 fffff802`109df2e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
  ffffd000`2b8949b0 fffff802`109ddac7 : ffffe000`d6213110 fffff802`108250d8 ffffd000`00000740 00000000`00000001 : nt!KiBugCheckDispatch+0x69
  ffffd000`2b894af0 fffff801`46aa6cb3 : ffffe000`d9196cc0 00001f80`00000200 00000000`7b133d00 ffffe000`d5fbfd01 : nt!KiPageFault+0x247
  ffffd000`2b894c80 ffffe000`d9196cc0 : 00001f80`00000200 00000000`7b133d00 ffffe000`d5fbfd01 00000000`00000018 : L1C63x64+0x6cb3
  ffffd000`2b894c88 00001f80`00000200 : 00000000`7b133d00 ffffe000`d5fbfd01 00000000`00000018 ffffe000`d9196d8a : 0xffffe000`d9196cc0
  ffffd000`2b894c90 00000000`7b133d00 : ffffe000`d5fbfd01 00000000`00000018 ffffe000`d9196d8a ffffe000`cf0f8b80 : 0x00001f80`00000200
  ffffd000`2b894c98 ffffe000`d5fbfd01 : 00000000`00000018 ffffe000`d9196d8a ffffe000`cf0f8b80 ffffe000`d69c7bf0 : 0x7b133d00
  ffffd000`2b894ca0 00000000`00000018 : ffffe000`d9196d8a ffffe000`cf0f8b80 ffffe000`d69c7bf0 ffffe000`d63fa628 : 0xffffe000`d5fbfd01
  ffffd000`2b894ca8 ffffe000`d9196d8a : ffffe000`cf0f8b80 ffffe000`d69c7bf0 ffffe000`d63fa628 00000000`00000000 : 0x18
  ffffd000`2b894cb0 ffffe000`cf0f8b80 : ffffe000`d69c7bf0 ffffe000`d63fa628 00000000`00000000 ffffe000`d5fbca20 : 0xffffe000`d9196d8a
  ffffd000`2b894cb8 ffffe000`d69c7bf0 : ffffe000`d63fa628 00000000`00000000 ffffe000`d5fbca20 fffff801`46aa6edb : 0xffffe000`cf0f8b80
  ffffd000`2b894cc0 ffffe000`d63fa628 : 00000000`00000000 ffffe000`d5fbca20 fffff801`46aa6edb ffffe000`00000064 : 0xffffe000`d69c7bf0
  ffffd000`2b894cc8 00000000`00000000 : ffffe000`d5fbca20 fffff801`46aa6edb ffffe000`00000064 00000000`00000000 : 0xffffe000`d63fa628
  
  
  STACK_COMMAND:  kb
  
  THREAD_SHA1_HASH_MOD_FUNC:  6848407ae33d8b824e44a663bf3b11779613f277
  
  THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  c80863aa88b03eae30cc377f2fdfbe2d3f947016
  
  THREAD_SHA1_HASH_MOD:  6a0b43a94793034e39a5e317480a3872f9f5cf50
  
  FOLLOWUP_IP: 
  L1C63x64+6cb3
  fffff801`46aa6cb3 488b08          mov     rcx,qword ptr [rax]
  
  FAULT_INSTR_CODE:  48088b48
  
  SYMBOL_STACK_INDEX:  3
  
  SYMBOL_NAME:  L1C63x64+6cb3
  
  FOLLOWUP_NAME:  MachineOwner
  
  MODULE_NAME: L1C63x64
  
  IMAGE_NAME:  L1C63x64.sys
  
  DEBUG_FLR_IMAGE_TIMESTAMP:  51e4ee9f
  
  BUCKET_ID_FUNC_OFFSET:  6cb3
  
  FAILURE_BUCKET_ID:  AV_L1C63x64!unknown_function
  
  BUCKET_ID:  AV_L1C63x64!unknown_function
  
  PRIMARY_PROBLEM_CLASS:  AV_L1C63x64!unknown_function
  
  TARGET_TIME:  2016-05-24T03:46:36.000Z
  
  OSBUILD:  10586
  
  OSSERVICEPACK:  306
  
  SERVICEPACK_NUMBER: 0
  
  OS_REVISION: 0
  
  SUITE_MASK:  784
  
  PRODUCT_TYPE:  1
  
  OSPLATFORM_TYPE:  x64
  
  OSNAME:  Windows 10
  
  OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal
  
  OS_LOCALE:  
  
  USER_LCID:  0
  
  OSBUILD_TIMESTAMP:  2016-04-23 00:04:21
  
  BUILDDATESTAMP_STR:  160422-1850
  
  BUILDLAB_STR:  th2_release_sec
  
  BUILDOSVER_STR:  10.0.10586.306
  
  ANALYSIS_SESSION_ELAPSED_TIME: 10db7
  
  ANALYSIS_SOURCE:  KM
  
  FAILURE_ID_HASH_STRING:  km:av_l1c63x64!unknown_function
  
  FAILURE_ID_HASH:  {1c745e23-731f-42c8-af3a-346943adb42b}
  
  Followup:     MachineOwner
  ---------
  
  

  ---

  Wanikiya and Dyami—Team Zigzag Windows IT-PRO (MS-MVP)

  • Предложено в качестве ответа

    25 мая 2016 г. 7:06

  • Помечено в качестве ответа
    MeipoXuMicrosoft contingent staff
    10 июня 2016 г. 7:36