Solved L1c63x64.sys Atheros LAN driver random blue screen on Win10

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Simplifico

Ralph
Thread Starter
Joined
Dec 15, 2016
Messages
90
Hi,
Apart from the O/S (mine is Win 10 instead of 8) my question is identical to that posted at https://forums.techguy.org/threads/...-sys-random-blue-screen-on-windows-8.1150528/

I have installed WinDbg but am having some trouble identifying what else may be the cause, other than just L1c63x64.sys itself. I don't have either of the two programs suggested in the above thread as being the likely culprits causing random BSODs.

I downgraded my driver to the default v2.1.0.16 (I previously had the latest v2.1.0.21 installed) and things were OK for a while, but now getting random blue screens again even with the default version.

Would it be OK if I upload my last few minidumps for analysis?

Thanks in advance.

Tech Support Guy System Info Utility version 1.0.0.4
OS Version: Microsoft Windows 10 Home, 64 bit
Processor: Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz, Intel64 Family 6 Model 30 Stepping 5
Processor Count: 8
RAM: 8116 Mb
Graphics Card: AMD Mobility Radeon HD 5000, 1024 Mb
Hard Drives: C: 118 GB (46 GB Free); D: 295 GB (127 GB Free); S: 3725 GB (1488 GB Free);
Motherboard: ASUSTeK Computer Inc., N61Jq
Antivirus: Windows Defender, Enabled and Updated
 

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
24,723
It appears to me that you either have defective hardware - your hard drive
OR you have a ram problem
Have you experienced ANY other problems besides the crashes

Have you received ANY error messages

I think this is your ram
Corsair CMSX4GX3M1A1600C9 NB Vengeance Performance 4GB 1600MHz CL DDR3 SO-DIMM Memory Module

and you have two sticks of it. I would take out one and re run and check
Then swop if you still get crashes.
The computer is an Asus notebook is it not, I do not know how accessible that ram is on the computer
 
Last edited:

Simplifico

Ralph
Thread Starter
Joined
Dec 15, 2016
Messages
90
Thank you. A few months ago I was also getting DPC_WATCHDOG_VIOLATION BSODs occasionally. Following some advice, I turned off Win10's Fast Restart option (don't think my BIOS supports it anyway). Restart times were not affected and I haven't had that stop error since.

The other day, quite soon after one of the crashes, the laptop 'died' (sudden power-down) which was unusual. I ran a chkdsk afterwards, which I will include at the end of this post.

You are correct about the laptop, it's an Asus N61JQ-2AJX, but with upgraded RAM and a Samsung SSD.

Also correct about the type of RAM, and it's easy to access, so I'll remove a stick now and see how we go. Let me know if you'd like any other info, and in the meantime kindly keep the thread open as the issue is quite intermittent and may not recur for some time, so it would be a good idea to give it a couple of weeks or so.

Thanks again and here is the chkdsk log:

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
Cleaning up instance tags for file 0x356a0.
434688 file records processed. File verification completed.
13701 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
550224 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 7299 unused index entries from index $SII of file 0x9.
Cleaning up 7299 unused index entries from index $SDH of file 0x9.
Cleaning up 7299 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
57769 data files processed. CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
434672 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
12659252 free clusters processed. Free space verification is complete.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

124565503 KB total disk space.
73230724 KB in 291500 files.
191540 KB in 57772 indexes.
0 KB in bad sectors.
506231 KB in use by the system.
65536 KB occupied by the log file.
50637008 KB available on disk.

4096 bytes in each allocation unit.
31141375 total allocation units on disk.
12659252 allocation units available on disk.

Internal Info:
00 a2 06 00 6d 53 05 00 16 6f 09 00 00 00 00 00 ....mS...o......
d9 05 00 00 2d 00 00 00 00 00 00 00 00 00 00 00 ....-...........

Windows has finished checking your disk.
Please wait while your computer restarts.
 

Simplifico

Ralph
Thread Starter
Joined
Dec 15, 2016
Messages
90
D is a partition of the SSD that contains mainly data (and just a few installed programs, but most of those are on the C partition of the same SSD).
S is an external Seagate Backup Plus USB3 drive that is used for storage, music and videos.
 

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
24,723
IF YOU HAVE NOT yet carried out ram test
1. disconnect the Seagate
2. Run a chkdsk /r on the D partition
3. Check system see if it still crashes - depending of course on chkdsk of D
4. RAM test as previously posted
5. If all OK with one, we can presume defective ram
6. Run WMD memory diagnostic and/or MEMTEST on stick that is presumed faulty. Test in both slots in case we have a DIMM slot problem
3. I am signing off I am in UK back online about 1000hrs but only briefly to check and post if necessary a reply

Are you OK with Windows memory diagnostic and memtest
 

Simplifico

Ralph
Thread Starter
Joined
Dec 15, 2016
Messages
90
Thanks I'll do that - haven't yet removed the RAM. I did actually run a chkdsk on D as well, although S was connected at the time - don't know if that should make any difference though - I will post the result at the end here, and will later re-run it with S disconnected 'just the be sure'. I'm OK with the WMD and MemTest, thanks for your help so far :)

Chkdsk was executed in read/write mode.

Checking file system on D:
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Volume dismounted. All opened handles to this volume are now invalid.
Volume label is DATA.

Stage 1: Examining basic file system structure ...


147968 file records processed. File verification completed.


405 large file records processed.

0 bad file records processed.
Stage 2: Examining file name linkage ...


155216 index entries processed. Index verification completed.


0 unindexed files scanned.

0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 441 unused index entries from index $SII of file 0x9.
Cleaning up 441 unused index entries from index $SDH of file 0x9.
Cleaning up 441 unused security descriptors.
Security descriptor verification completed.


3625 data files processed. CHKDSK is verifying Usn Journal...


40532736 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...


147952 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...


33553844 free clusters processed. Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

309807720 KB total disk space.
175267360 KB in 109552 files.
61720 KB in 3626 indexes.
0 KB in bad sectors.
263260 KB in use by the system.
65536 KB occupied by the log file.
134215380 KB available on disk.

4096 bytes in each allocation unit.
77451930 total allocation units on disk.
33553845 allocation units available on disk.
 

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
24,723
ok
a little advice if you do not mind
NEVER unless you are forced into it force a dismount
Answer N to that question and the next reply should be do you wish to run at boot.
It is unusual that forcing dismount will cause a problem, but the risk is not worthwhile

I am signing off Goodnight
You have a 5 hour time difference I think so it is 0200 for me and 2100 for you
 

Simplifico

Ralph
Thread Starter
Joined
Dec 15, 2016
Messages
90
Ah thanks - I appreciate the advice and will bear it in mind
Actually I'm in Australia, so 2am for you, 1pm over here - cheerio for now and thanks for all the help at this late hour!
 

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
24,723
Was there in February
Perth and Dunsborough
4 days of 35 - glad the relatives had a pool, but it was in - out and back to aircon in house

Will reply when I resume good to work with you

THAT processor runs
DDR3 1066/1333 these ram speeds on default setting
If you are using the 1600 ram it runs at 1333 SPD serial presence detect
on standard settings
Are you using those or have you set in BIOS to run at 1600
 

Simplifico

Ralph
Thread Starter
Joined
Dec 15, 2016
Messages
90
Temps have been like that here in Sydney over the last few days too...
I will check on the speed - I don't think I changed anything in BIOS but it was some years ago I installed the RAM so will need to re-check.
But for now - I really do give you permission to retire for the night - you've gone above and beyond the call of duty for the day already :)
 

Simplifico

Ralph
Thread Starter
Joined
Dec 15, 2016
Messages
90
OK, so I've re-run chkdsk /r on the D drive, but without the external drive plugged in, and did it on reboot this time rather than force dismount - all looks good to me (though I'll post results below anyway).

I looked in the BIOS for anywhere I could change speed settings but couldn't find anywhere. If there is a way to access hidden settings in that Aptio BIOS I don't know it. Alt+F1, Ctrl+F1, Shift+F1 all did nothing. (I can post screenshots of the 5 menus if you like - they are Main, Advanced, Boot, Security, Save&Exit.)

Remember I mentioned the PC once died suddenly recently? It hasn't done this again (yet) while in Windows, but curiously it did do it several times while I was in the BIOS. I found that rather odd.

The next thing I will do is remove one stick of RAM as you advised, and we'll see what happens...

Here is the chkdsk log:

Checking file system on D:
The type of the file system is NTFS.
Volume label is DATA.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
147968 file records processed. File verification completed.
405 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
155220 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 1 unused index entries from index $SII of file 0x9.
Cleaning up 1 unused index entries from index $SDH of file 0x9.
Cleaning up 1 unused security descriptors.
Security descriptor verification completed.
3627 data files processed. CHKDSK is verifying Usn Journal...
40826352 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
147952 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
33545292 free clusters processed. Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

309807720 KB total disk space.
175301036 KB in 109585 files.
61744 KB in 3628 indexes.
0 KB in bad sectors.
263772 KB in use by the system.
65536 KB occupied by the log file.
134181168 KB available on disk.

4096 bytes in each allocation unit.
77451930 total allocation units on disk.
33545292 allocation units available on disk.

Internal Info:
00 42 02 00 48 ba 01 00 c8 94 02 00 00 00 00 00 .B..H...........
87 35 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .5..............
 

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
24,723
1. Re the ram - I would not concern yourself with the settings at this time
It is not the speed you change it is the settings in the BIOS for timings, to achieve that speed or enable XMP - if your processor had that
See this
http://www.howtogeek.com/257766/how...o-make-your-ram-run-at-its-advertised-speeds/

2. The crash in BIOS is concerning, but it tends to confirm that it cannot be a Windows or other software driver issue and therefore supports my opinion that you have a ram fault or other hardware fault

3. Unfortunately this could be the CPU, or indeed the motherboard. However lets continue to start with the easiest and check the ram
Try the one stick test first and see if it crashes in BIOS
If it does change that stick for the other one and see if it still crashes
PLEASE ensure power disconnected and of course battery out and power button held down for 20 seconds to discharge all current BEFORE removing ram and only handle by edges of stick - do not touch chips. Take anti-static precautions by grounding yourself first

4. It would be unusual for both sticks to be faulty but if crashes do still occur on both run memtest on boot. IF they do NOT occur with just one stick - start with memtest on the apparently faulty stick.
http://www.memtest.org/

Use version 5.01 pre complied bootable ISO
RUN two passes on each stick - each pass consisting of 8 to 10 tests
see this

https://forums.techguy.org/threads/bsod.1161969/#post-9177446
the attached image on post 7.

5. Depending on what if anything we find from the ram test we may need to continue to check temps, voltages etc.
 
Last edited:
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Top