Random BSOD - NDIS.sys "driver_irql_not_less_or_equal"

Hey guys,

Lately some odd things have been happening with my computer. A couple of days ago my computer refused to POST when I started it up and sat on a blank screen indefinitely. So I force shut it down and restarted it and it started right up. I have no idea if this is related to my problem or not, but I thought I'd say it.

Anyways, tonight I was browsing the internet and my computer BSOD'd for the first time since I've had it. I restarted and thought I'd see if it would happen again. Within 30 minutes it BSOD'd again with the exact same error that is in my title. Any idea why all of a sudden this is happening and why its so random (I've been on it for 45 minutes now since the last BSOD)? If it matters, both times I was playing Runescape. Since then I haven't been playing it and no BSOD.

Basic specs:
- Windows 7 x64
- Original OS was Vista x64 for 6 months. In October of 2009 I upgraded it with Windows 7.
- Vista was full retail, 7 is an upgrade.
- I build this computer in May of 2009, so it's about 3 years old now.
- OS was installed in March or April of 2010 after having an audio issue for a few weeks.

Code:

ASACPI.sys Sun Mar 27 20:30:36 2005 (42476C4C)

Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:

1. Going to the Asus motherboard support site
   When you reach the website:
2. Scroll down the page and click Utilities
3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
4. Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
5. Download and install the driver.
6. After installation is complete, verify that it installed correctly.
   
   • Click Start Menu
   • Click My Computer
   • Go to C:\WIndows\System32\drivers\
   • Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)

Crashes are being caused by L1E62x64.sys, your Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (NDIS6.20) driver. You should be able to obtain an updated driver for it from your motherboard support site. Do not download the beta version. Use Version 10045/10018/10040 from ASUS - Motherboards- ASUS P5Q PRO under LAN.

To fully re-install a driver, use the following steps.

1. First, download the latest driver. Then do the next steps.
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Find the device you are trying to uninstall by expanding Network adapters
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer only if Windows asks you to.
11. Install the latest driver for the device.

Alternatively:

1. Login as an adminstrative user.
2. First, download the latest driver. Then do the next steps.
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Find the device you are trying to uninstall by expanding Network adapters
8. Right click the device
9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
11. Restart your computer only if Windows asks you to.
12. Install the latest driver for the device.

Ok so I updated the ASACPI.SYS file and so far today I haven't had a single BSOD. Reinstalling my network driver gave me the exact same version number and driver date as before, so I don't think it was that.

Thank you for your help! Hopefully I won't have to post in this again.

The point of the re-install of the network drivers was to remove the possibility of the old drivers being corrupted and causing issues. Even if you re-install the same version, it can help by removing any corrupted drivers that result in conflicts with the system.

When you are confident the problem is solved, you may mark this thread solved. :)