Random BSOD, multiple times a week, started recently

[M3rcNate]

So I just had two bluescreen crashes this morning, right after booting up my PC and using a chrome. I turned it on, Windows booted, I started using Chrome and it crashed. After it rebooted I started using chrome again and the same thing happened. This has just started in the past two or so weeks (can't think of anything that has changed since then) and I'm really tired of it. Any help you could provide would be great.

I've included the BSOD log file in this post.

 

[axe0]

Hi M3rcNate,

Sorry for the delay.
Are you still in need of help?

 

[M3rcNate]

Hi M3rcNate,

Sorry for the delay.
Are you still in need of help?

No problem, yes. I haven't used the PC much since I posted this, though I haven't encountered a BSOD again, I suspect whatever the issue is, I still have it. Knowing why I am getting the BSOD would be nice.

 

[axe0]

The Atheros ethernet driver looks to be causing the issue, its quite dated.

1: kd> lmvm L1E62x64
Browse full module list
start             end                 module name
fffff880`02de2000 fffff880`02df4000   L1E62x64 T (no symbols)           
    Loaded symbol image file: L1E62x64.sys
    Image path: L1E62x64.sys
    Image name: L1E62x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Sun Aug 23 07:08:09 2009 (4A90CEB9)
    CheckSum:         0001697B
    ImageSize:        00012000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[M3rcNate]

The Atheros ethernet driver looks to be causing the issue, its quite dated.

1: kd> lmvm L1E62x64
Browse full module list
start             end                 module name
fffff880`02de2000 fffff880`02df4000   L1E62x64 T (no symbols)           
    Loaded symbol image file: L1E62x64.sys
    Image path: L1E62x64.sys
    Image name: L1E62x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Sun Aug 23 07:08:09 2009 (4A90CEB9)
    CheckSum:         0001697B
    ImageSize:        00012000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That's really interesting, thank you. I wonder why it would start BSOD now? I've been using the driver likely since I built the PC. Maybe something in Windows updated that is clashing with it.

Here's my question though, that driver is likely the most recent driver my motherboard supports. So you say it is really old, how would I go about finding a newer driver for it?

edit: Never mind. My motherboards website has a beta driver that is newer and I found some others online that are newer. I installed to a 3-29-2010 driver (1.0.0.49 - Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller Drivers Download for Windows 10, 8.1, 7, Vista, XP) and so far my internet is working just fine so we'll see if the BSOD stops happening.

 

[axe0]

There are various reasons why something starts acting up after years of use, example:
- drivers corruption
- drivers not compatible with updates from Windows Update
- device malfunctioning
- port where the device is connected on is malfunctioning