I am posting the crash dump log created by whocrashed in hopes someone may be able to help me out on why this PC, from time to time, will apparently BSOD and reboot. It seems to happen when the PC is asleep and possibly comes out of sleep for a WHS2011 client backup.
I have driver 1.0.0.45 installed for the Atheros NIC, which is more current than I can google, except for a wiki driver I found that claims to be 1.0.0.49 (but I'm not sure I trust this download link). My driver is newer than what shows on Atheros.cz, and QUALCOMM/Atheros doesn't list this chipset.
System Information (local)
--------------------------------------------------------------------------------
computer name: ASUS-P5Q-PRO
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core2 Duo CPU E8400 @ 3.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 6441447424 total
VM: 2147352576, free: 1928462336
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 9/12/2013 5:48:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091213-8236-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF880016836BA)
Bugcheck code: 0xD1 (0x32, 0x2, 0x0, 0xFFFFF880016836BA)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 9/12/2013 5:48:59 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: l1e62x64.sys (L1E62x64+0x6C2D)
Bugcheck code: 0xD1 (0x32, 0x2, 0x0, 0xFFFFF880016836BA)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\l1e62x64.sys
product: Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)
company: Atheros Communications, Inc.
description: Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: l1e62x64.sys (Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20), Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 8/27/2013 6:30:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082713-8829-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8005735A10, 0xFFFFF80004CC24D8, 0xFFFFFA80076DC3C0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 8/25/2013 9:19:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082513-8938-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF8800150E6BA)
Bugcheck code: 0xD1 (0x32, 0x2, 0x0, 0xFFFFF8800150E6BA)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
l1e62x64.sys (Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20), Atheros Communications, Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.