Driver_irql_not_less_or_equal

CarnageA · 08-11-2008, 11:20 PM

Here is my story.
A year ago after a nasty problem with the infamous avg.dll my computer turned into a miniature hell. It would give me the blue screen of death every 30 minutes and caused me a lot of greef. My disk drive was busted so I could not perform a system restore. It was all bad...

However, a few days ago I got a new disk drive and was able to use the system restore disk to revert my PC to factory settings. I was thinking that it si all over. Oh no it wasn't. I still get the blue screen. But this time it is a bit of an improvement. I just get one type. Before I would get 10. The message that I get is:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
AFD.SYS- adress F5D3273A base at F5D32000, Date stamp 48a4002e

I am sick and tired of this busted heap and will do anything in my ability to get it fixed. However, I am not much of a PC wiz. Any help would be apreciated.
Thank you.

TaZMAn · 09-11-2008, 12:33 AM

Do you have Zone Alarm installed?
There are some known issues with Z/A and driver IRQ's.
If you do then I would try uninstalling it, reboot and see what happens. Just make sure you have the Windows firewall enabled.

Another problem it could be is a corrupted device driver.
You can go into the device manager and update the drivers for each piece of hardware.

What has me puzzled is that you said you did a restore to a new hard drive.
If you did a restore with the Cd's that came with the computer then there is no way that your previous problems with AVG could be present on the new drive.
If however you used the old drive and a Ghost type program to image the old system to the new drive then it may be a pre-existing problem.

If you did a factory Cd restore to a new hard drive then this problem would mean you have a piece of hardware going bad, you installed a new piece of hardware or replaced hardware after you bought the computer and the restore Cd installed the wrong driver.

TaZMAn

CarnageA · 09-11-2008, 01:28 AM

I have never heard of Zone Alarm.

Oh my God!!! Those things are breeding. Now I recieved a message about win32k.sys and something trying to execute non-executable memory. I can hardly use the computer. Gonna try a hotfix. If that doesn't work- system restore and then try to catch the problem from there.

My PC is a Packard Bell. The recovery disk did not arrive in the package. Instead, I had to burn it later thru some Packard Bell programm on the PC. I think it just copied the hidden partition to the disk so it is probably not the main problem.

Also, my PC is a double-drive. The recovery CD erases only one drive, leaving the other intact. Might be something there.

I doubt the hardrive problem. The only new addition to the system was the disk drive. I'll try to update it nevertheless. Maybe its because the old drive was NEC and new one is different.

TaZMAn · 09-11-2008, 02:04 AM

Quote:

trying to execute non-executable memory

This is starting to sound like a case of bad Ram. It can be system Ram or Video Card Ram.
Below is a portion of a post at Tech Spot. It will shed some light on your problems.
I only mentioned the hardware as a problem because I know of people who change a video card or sound card then use their reinstall disk and wonder why the device doesn't work properly. Being that you only changed a hard drive won't matter and it doesn't make a difference what brand of hard drive you use as long as it uses the same interface of which yours does.

FYI;
Zone Alarm is a Firewall / Security Suite.

The following is from a post found here;
Other BSOD problem - TechSpot Troubleshooting

Random restarts/reboots/resets/crashes/freezes could be due to several reasons, including overheating, RAM, hardware issues, etc., just do the following and post back with the info so that we can narrow it down some.

Try rebooting(restarting) in safe mode, then go to control panel/ system / advanced Tab/ startup and recovery box/ settings button/ sytem failure and uncheck "restart on system failure" ( take the check out of automatically restart box ) , and check the Write a system event, and the Admin alert boxes (check "send admin alert"). This will force a BSOD on the next crash (freezes/restarts = crashing) that posts the Stop Error Code. On the next crash write down the exact Stop Error Code and post that exact error here back on this thread. (While you're waiting for a reply, you can put that error code in Google search, and in the MS Support Knowledge Base (KB) = to check it out.-
Advanced Search ).

Also go to your device manager (devmgmt.msc) and check the properties and look for anything suspicious and check that the settings are where they should be.

Check:
1. Overheating(Open the case and check to see how much dust has collected inside it, and if there is alot of dust get a can of compressed air and blow the dust out and clean out all dust bunnies, etc. on the heatsink/;fan combo,etc.; and be sure all the fans are spinning and properly functioning ). Install diagonstic tools like MotherboardMonitor= http://mbm.livewiredev.com or Everest = |MG| EVEREST Free Edition 2.20 , and check the tempurature.

2. Poor power supply (weak power supply or noisey / dirty electricity). If possible, swap the RAM and Power Supply (PSU) around with another computer.

3. Bad driver or drivers not updated, or a device conflict. Pull the connectors and push them back on. Reseat all of the cards. RightClick - my comp/properties/select the hardware tab/click device manager/see if there are any "!" next to anything. Try updating the drivers from the manufacturers' websites.

4. Not enough memory or bad Ram. You might need to add more Ram. Missmatched ram or a bad stick of ram will cause this also. Try reseating and or swaping the ram sticks. Make sure they are seated/snaped in firmly.
Run Memtest86: = Memtest86+ - Advanced Memory Diagnostic Tool
and
FREE RAM Diagnostic Tool. - CST Inc.s DOS based DocMemory = Bucaro TecHelp Computers .

5. Could be IRQ conflict

6. Perhaps the CMOS battery on the motherboard is going bad and needs to be replaced. Check it to be sure.
Also check your pc clock's time and day, to be sure it is set correctly.

7. Hard drive could be failing.

8 Right click desktop/properties/screen saver/Power/Hibernate tab ,and make sure hibernation is not enabled, and cleann out your Cache & Cookies & Temporary Internet Files and Folder: = http://www.coloarts.state.co.us/cleanFiles.asp[/L]

9. Make sure you have updated all programs and hadrdware.

10. Motheboard short (loose screw, misplaced mounting standoff , etc.?)

PcTestCard.com · 09-11-2008, 09:22 AM

If you have installed the OS ok and boot ok before the blue screen.

You may try to use Last Known Good configuration to load the working profile.
"IRQ" driver problem most of time can corrected by the LKGC.