BSOD L1C62x64.sys

You could also attempt this driver, it's slightly older, but it's worth trying - Driver Details | Dell US

Anak said:

sygnus21 said:

Britton30 said:

User malfunctionality. It may be they should look for Qualcom?

I don't know, I see a lot of these popping up - Search Results for Atheros

Try this site: Qualcomm, Atheros, Zidas, Attansic, Intellion drivers, firmwares, specifically at the bottom of this page: Qualcomm, Atheros, Zidas, Attansic, Intellion drivers, firmwares Yes, I know they look the same but will take you to two different pages.

When I was helping regularly with BSOD's we ran into the same problem and usually could only come up with the czech site but it wasn't as complete.

I'd have to look back, but here's the gist of it, if memory serves.
The problem with Atheros started a little after I joined 7F in 2010. Atheros was a small business bought out by Qualcom (Q) and Q was busy acquiring other companies and left Atheros on its own. It's another "rags to riches (Atheros)" - "the rich get richer (Q)", management changes at Atheros story.
Wouldn't you agree to new management if you received a share of 3billion?

The result?
Anything Q touches becomes proprietary and we all know what that means, Your shite out of luck until the patent or copyright runs out. You will find information about Q's technology on their site. But, you will not find any real support like drivers.

Was gone for few days, came back today got new bsod with some newer driver, maybe its a hardware problem.

Code:

BugCheck D1, {fffff98090b6ee60, 2, 0, fffff880045ba0e9}

*** 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+70e9 )

Code:

0: kd> lmvm L1C62x64
start             end                 module name
fffff880`045b3000 fffff880`045d5000   L1C62x64 T (no symbols)           
    Loaded symbol image file: L1C62x64.sys
    Image path: L1C62x64.sys
    Image name: L1C62x64.sys
    Timestamp:        Wed May 29 08:15:30 2013 (51A5AB12)
    CheckSum:         000214C1
    ImageSize:        00022000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It's the same driver and the same problem as before, have you tried the Dell driver?

Update your System Specifications with Speccy, and then copy this information into your System Specifications: Go to your UserCP, and then select Edit System Spec in the left pane. Copy the information from Speccy into the required fields. These System Specifications will then follow your every post.

It wasnt the same driver, it was something i found by following the links in your quote, after i got that one i installed the dell one and just got another bsod

Code:

0: kd> .time
Debug session time: Mon Aug  5 23:55:52.110 2013 (UTC + 1:00)
System Uptime: 0 days 8:00:22.015

Code:

0: kd> .time
Debug session time: Mon Aug  5 23:55:52.110 2013 (UTC + 1:00)
System Uptime: 0 days 8:00:22.015

Both of the dump files are exactly the same, when have latest the crashes happened?

Something, we haven't tried yet is Driver Verifier, I would like to see if there is any problems with another drivers, and if these drivers are causing problems, are they causing any problems with the present driver?

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

x BlueRobot said:

Code:

0: kd> .time
Debug session time: Mon Aug  5 23:55:52.110 2013 (UTC + 1:00)
System Uptime: 0 days 8:00:22.015

Code:

0: kd> .time
Debug session time: Mon Aug  5 23:55:52.110 2013 (UTC + 1:00)
System Uptime: 0 days 8:00:22.015

Both of the dump files are exactly the same, when have latest the crashes happened?

Something, we haven't tried yet is Driver Verifier, I would like to see if there is any problems with another drivers, and if these drivers are causing problems, are they causing any problems with the present driver?

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

This is the last diagnostic file i just got, also got another bsod, it seems to happen when i watching video streams, at least the last few i can remember happened while i was doing that. Im using SopCast for that, maybe this gives you something, i dunno, im trying everything. Also i did the driver verifier test the first day i join this forum but ill do it again.

As for the drivers, iv uninstall them from the device manager and installed others that i got from other place then gigabyte website.

one from here - Qualcomm, Atheros, Zidas, Attansic, Intellion drivers, firmwares
and one from here (witch is currently installed) Driver Details | Dell US

Code:

BugCheck D1, {fffff9805c76ce80, 2, 0, fffff8800425d0e9}

*** 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+70e9 )

The bugcheck is the same, but the dump file is different :)

Code:

0: kd> lmvm L1C62x64
start             end                 module name
fffff880`04256000 fffff880`04278000   L1C62x64 T (no symbols)           
    Loaded symbol image file: L1C62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\L1C62x64.sys
    Image name: L1C62x64.sys
    Timestamp:        Wed May 29 08:15:30 2013 (51A5AB12)
    CheckSum:         000214C1
    ImageSize:        00022000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I wonder actually if the network adapter is faulty, we've tried multiple different driver versions, and it hasn't had any effect.

Have you changed any of the Windows Firewall settings?

Is the network adapter a physical card or a chip on the motherboard?

Still getting the dsod's posting the last diagnostinc tool files here. The network adapter is part of the motherboard and i still have warranty for it in case is a hardware fault, but first i need to be sure about this.

Also gona make a clean install of the windows today and gona see if that helps.

Personally, I would use the motherboard warranty and get a replacement, I know it may be inconvenient but the driver seems to causing problems regardless of version and date.

Code:

BugCheck 3B, {c0000005, fffff88002c5cae2, fffff88009f50030, 0}

*** 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+6ae2 )

Code:

2: kd> lmvm L1C62x64
start             end                 module name
fffff880`02c56000 fffff880`02c78000   L1C62x64 T (no symbols)           
    Loaded symbol image file: L1C62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\L1C62x64.sys
    Image name: L1C62x64.sys
    Timestamp:        Wed May 29 08:15:30 2013 (51A5AB12)
    CheckSum:         000214C1
    ImageSize:        00022000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4