03-30-2011 04:31 PM - edited 03-31-2011 04:10 PM
by giona87 » Thu Apr 15, 2010 7:38 am
03-30-2011 04:33 PM
by Mike L » Thu Apr 15, 2010 11:02 am
03-30-2011 04:34 PM
by giona87 » Fri Apr 16, 2010 8:44 am
03-30-2011 04:36 PM
by giona87 » Fri Apr 23, 2010 5:43 am
03-30-2011 04:36 PM - edited 03-31-2011 04:14 PM
by giona87 » Wed Apr 28, 2010 8:43 am
03-30-2011 04:38 PM
by Mike L » Wed Apr 28, 2010 10:26 am
03-06-2012 07:38 PM
After reading up from users who got rid of the BSOD for AGNFILT.SYS by changing routers, I did the same myself and it resolved the issue.
I was using the internal wireless of an ACTIONTEC Q1000 from Qwest/CenturyLink that is also a DSL modem. I blue screened whenever connected with AT&T active. I updated to the latest version of net client from ATTNETCLIENT.COM to no avail. My girlfriend's 2 computers (WinXP and Windows7) also blue screened when connected via the client. It was a consistent problem that would hit multiple times a day during the work day.
I converted the Action Q1000 DSL modem/router to just bridge mode and turned off the wireless feature. I plugged in my old D-Link DIR-655 to be the wireless router and the BSOD events have disappeared on all 3 computers for over a week now. I highly recommend making the change in your router if you regularly get the BSOD while using AT&T Net Client as they don't appear interested in resolving the issue.
03-21-2012 04:43 AM
I get the BSOD in agnfilt.sys a varying hotels around the world and also at home -- practically always AFTER waking up from sleep-gone-into-automatic-hibernate mode, and always on the wireless. It happens immediately when I click the CONNECT button quite quickly after opening the laptop lid.
My experience is that when I wait longer, the chance of ti coccurring is less.
But in most cases I did wait until the wireless icon of W7 said it had established internet connectivity,
My hypothesis would be it has something to do with some pointer being remembered for a wireless connection, and that pointer not being there or at another place if the PC has slept or hibernated in the mean time.
My ATT cleint version is 188.8.131.5203
03-21-2012 09:51 AM
I got a BSOD this morning under similar circumstances. My system is a desktop, not a laptop (connected to gigabit backbone using an Intel 82579V NIC); It is Win7 x64 SP1 (plus latest fixes); agnc is v184.108.40.20604. This trap occurred when I tried to restore the client window (was minimized to taskbar) after the system had been asleep. The particular error on the BSOD was IRQL_NOT_LOWER (iirc). I've noticed that AGNC has definitely had problems for at least a few months after the system was asleep. Other (presumably related) symptoms include leaking win32 handles and the client just hanging. Obviously a ring 0 trap is the most annoying. I have a memory.dmp if you want it. Email me instructions on where to put it,if so.
03-29-2012 12:26 PM
Same issue on Lenovo W510.
Windows 7 x64
Blue screen after returning from standby.
At first I thought it was wireless related as well, but this morning I got the same blue screen with all wireless radios turned off (with the hardware disable switch on the side of the laptop).
I have also disabled the Windows Device for Microsoft Virtual WiFi Miniport Adapter, since I have read that this has also correcte the issue for some.
NetClient.exe version 220.127.116.1103