BSoD: athr.sys 0x0000001D IRQL NOT LESS OR EQUAL
Good day, I've recently moved to Win7 Ultimate 32-bit. Clean install, not upgrade. Worked good for 4 days, now having stability problems. Two BOsDs now, pointing at athr.sys which I've found is related to wifi. Running an Atheros AR5007 802.11 b/g. After 2 reboots after BSoD, was able to reconnect to my wifi. Ping testing shows massive latency, average ping time to google.com is aprox 1200ms, with peaks at 5000+ms. Confirmed it was PC and not router. Pings from router diagnostics shows 30ms average to google.com. Rolled back the wifi driver. Ping tested again, same latency. Forced an update of the driver via device manager's update driver button, it completed. Did ping test again, latency lasted for about 1~2 min, then it started working correctly, ping times dropped to 30ms. Doing aninfinite ping test now, after 10 min, still running strong and getting 30ms. Driver Files (After updating the driver) athr.sys Version 2.0.0.75 built by WinDDK xwfibus.sys Version 6.1.7600.16385 (win7_rtm.090713-1255) Question: I do not believe I have this problem fixed even though now my system is running correctly. Should this issue occur again, what other aspects should I look at?
November 12th, 2009 6:31am

Hello IDrake, According to your problem description, I suppose that the issue is most likely caused by the incompatibility of the networking driver,installingthe latestdevice driver via Windows update should solve the problem.If you still get the BSOD error in the future, remove all unnecessary hardware devices from the computer, try entering Windows safe mode to test whether it is a third-party software/hardware compatibility issue.And then download and run Windows 7 Upgrade Advisor to check the reason for the issue. Please understand that Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a hardware device, third-party drivers, backup software or anti-virus services (buggy services). The system goes to a blue screen because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are). To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS If you are outside the US please see http://support.microsoft.com for regional support phone numbers. I hope the problem will be resolved soon. Thanks! Andy
Free Windows Admin Tool Kit Click here and download it now
November 12th, 2009 10:37am

Thank you for the further ideas. I'm at hour 24 since doing a driver update which seems to have resolved the issue. I dospecifically remember on the second BSoD that I had attached to the box, a WD External hard drive. However, it was not attached during the first BSoD. The Windows 7 Upgrade Advisor is a good idea,I've downloaded and installed it and will use it in troubleshooting issues such as this in the future. I've also taken the added steps of installing software into the system, bit by bit, and testing the stability of it, rather than just installing everything at once. So far Windows 7 is working about... 400x better than Vista did for me, this is the only hiccup so far, and I believe now after through testing that it is now resolved. Thank you for your suggestions Andy, and for now it looks like a simple update of the driver for the wifiadapter has fixed my problem. iDrake
November 13th, 2009 6:29am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics