Seeming random BSOD, with: IRQL NOT LESS OR EQUAL

[TombaNL]

Hi readers,

I have recently tried to clean up an old laptop, I re-installed windows and a bunch of software. But ever since I have been experiencing BSOD screens every other day. I do not have any experience in solving this. Any advice is much appreciated.

 

[Golden]

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

 

[TombaNL]

My apologies, you probably get this a lot . I was under the presumption the dump files were all that were necessary. Anyhow here is the other information.

 

[Golden]

I'll take a look at this shortly.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 8, 0}

*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : [B][COLOR="Red"]athrx.sys[/COLOR][/B] ( athrx+a0581 )

Followup: MachineOwner
---------

0: kd> lmvm athrx
start             end                 module name
fffff880`04491000 fffff880`045e9000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Fri [B][COLOR="red"]Oct 09[/COLOR][/B] 13:10:55 [B][COLOR="red"]2009[/COLOR][/B] (4ACEA2B7)
    CheckSum:         0015580F
    ImageSize:        00158000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Product Type	[B][COLOR="red"]Atheros AR9285[/COLOR][/B] Wireless Network Adapter

The Atheros network driver is outdated. Update it and monitor for further BSOD.

Scroll down list and select AR9285 for Windows 7 64 bit:
https://www.atheros.cz/atheros-wireless-drivers.html

 

[TombaNL]

My laptop just got an BSOD again. Which is twice in an hour and seems somewhat troubling. Anyhow, I've managed to update the network drives as you suggested, so I hope this does the trick. Thank you gain, I really appreciate you taking your time to help me!

 

[Golden]

If you re-run the tool again, I'll check the latest .dmp file - I assume that BSOD happened prior to updating the Atheros driver?

 

[TombaNL]

Yes the BSOD happened before I did the Atheros driver update. Here's the report you asked. And thanks again.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {44, 2, 0, fffff8800429f8c1}

*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+5c8c1 )

Followup: MachineOwner
---------

1: kd> lmvm athrx
start             end                 module name
fffff880`04243000 fffff880`0439b000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Fri Oct 09 13:10:55 2009 (4ACEA2B7)
    CheckSum:         0015580F
    ImageSize:        00158000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Confirmed - it was also the Atheros driver. After updating, it should be OK now.