BSOD caused by Athrx.sys

[haraldzigic]

Hi,
The last 5-6 days I've been having a lot of BSOD on my PC.
I downloaded and tried to update and use other compatible drivers from atheros.cz
But then my computer freeze when used in about 2-3 minutes.
I also tried to just uninstall the driver, and force the driver to not reinstall when starting Windows, but anyway it keeps installing itself.
Please help, my exam is in 1 ½ week, and more BSOD’s may be fatal...:huh:


Crash Dump Analysis

On Mon 03.10.2011 09:43:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athrx.sys (athrx+0x5C8C1)
Bugcheck code: 0xD1 (0x44, 0x2, 0x0, 0xFFFFF88002EA58C1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athrx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device 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.
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: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: athrx.sys Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Mon 03.10.2011 09:43:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100311-25677-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0x44, 0x2, 0x0, 0xFFFFF88002EA58C1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


My PC:
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU T2370 @ 1.73GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2137014272 total
VM: 2147352576, free: 1897914368
Network Driver: Atheros AR5007

 

[zigzag3143]

Hi,
The last 5-6 days I've been having a lot of BSOD on my PC.
I downloaded and tried to update and use other compatible drivers from atheros.cz
But then my computer freeze when used in about 2-3 minutes.
I also tried to just uninstall the driver, and force the driver to not reinstall when starting Windows, but anyway it keeps installing itself.
Please help, my exam is in 1 ½ week, and more BSOD’s may be fatal...:huh:


Crash Dump Analysis

On Mon 03.10.2011 09:43:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athrx.sys (athrx+0x5C8C1)
Bugcheck code: 0xD1 (0x44, 0x2, 0x0, 0xFFFFF88002EA58C1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athrx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device 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.
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: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: athrx.sys Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Mon 03.10.2011 09:43:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100311-25677-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0x44, 0x2, 0x0, 0xFFFFF88002EA58C1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


My PC:
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU T2370 @ 1.73GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2137014272 total
VM: 2147352576, free: 1897914368
Network Driver: Atheros AR5007

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[haraldzigic]

Hi,
I now changed the "small memory dump (256kB)" in the dropdown box
The file (after ziping) is way to big (60 00kb)
Does a new file, smaller then 256kb, shows when the next BSOD appears?

 

[zigzag3143]

Hi,
I now changed the "small memory dump (256kB)" in the dropdown box
The file (after ziping) is way to big (60 00kb)
Does a new file, smaller then 256kb, shows when the next BSOD appears?

You can upload the file to a file sharing service like rapidshare, but the zip file should be around 1 MB only.

 

[haraldzigic]

Mindump attachment

View attachment 177867

 

[zigzag3143]

View attachment 177867

A few problems but most importanly is these were Related to athrx.sys Extensible Wireless LAN device driver from Atheros Communications, Inc. I would re-install newest.

Your AgileVpn.sys is causing memory issues. I would update it

Old drivers needing updating

Apfiltr.sys    9/29/2007 7:32:33 AM        fffff880`02c2d000    fffff300`02c60000    0xfffffa8000033000    0x46fe37d1                        
CHDRT64.sys    2/27/2008 6:26:53 PM        fffff880`06e6f000    fffff880`06eae000    0x0003f000    0x47c5e3ad                        
Rtnic64.sys    3/31/2008 1:39:38 AM        fffff880`075e0000    002ff8f4`075f4000    0x0030007400014000    0x47f0791a                        
VSTCNXT6.SYS    10/15/2008 8:52:22 PM        fffff880`07227000    644d65f3`072f2000    0x644d6d73000cb000    0x48f69046                        
VSTAZL6.SYS    10/15/2008 8:53:42 PM        fffff880`078ef000    fffff080`07941000    0xfffff80000052000    0x48f69096                        
VSTDPV6.SYS    10/15/2008 8:57:45 PM        fffff880`07645000    fffff880`077b9000    0x00174000    0x48f69189

How To Find Drivers:

- search Google for the name of the driver
- 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 this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads