Computing.Net > Forums > Windows XP > IRQL_NOT_LESS_OR_EQUAL bsod

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Click here to start participating now! Also, check out the New User Guide.

IRQL_NOT_LESS_OR_EQUAL bsod

Reply to Message Icon

Name: Roadfood
Date: September 11, 2003 at 18:39:27 Pacific
OS: Windows XP Home
CPU/Ram: Pentium III 700 / 128mb
Comment:

I just installed a new Western Digital 60-gig hard drive on this PC, and ran a clean install of Windows XP. I have downloaded the service pack and all patches. The PC spontaneously reboots every 15 minutes or so, but only when it is left idle--the PC doesn't crash if it is being used. The error message on the stop screen is:
IRQL_NOT_LESS_OR_EQUAL

STOP: 0x0000000A

(0x7FFFFFFF, 0x00000002, 0x00000001, 0x804E40B0)

The error log reads as follows:

OSVer 5_1_2600 SP:1_0 Product 768_1

I've already tried reseating the RAM; that didn't help. I've checked all the drivers and there are no conflicts. All of the drivers are 2001 or newer.

I can't run disk defrag on the hard drive because as soon as I try I get the BSOD with the above error messages.

So I think the problem may be with the new hard drive. I have not installed any hardware--just took the old hard drive out, put a new hard drive in, and installed Windows XP. Anyone have any ideas?



Sponsored Link
Ads by Google

Response Number 1
Name: Kevin193
Date: September 11, 2003 at 18:58:42 Pacific
Reply:

Sounds like a driver issue, try this link.

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/reskit/prmd_stp_hwpg.asp

Good Luck


0

Response Number 2
Name: Johnw
Date: September 12, 2003 at 01:01:24 Pacific
Reply:

http://support.microsoft.com/default.aspx?scid=kb;en-us;314063
Troubleshooting a Stop 0x0000000A Error in Windows XP
The information in this article applies to:
* Microsoft Windows XP Home Edition
* Microsoft Windows XP Professional
IRQL_NOT_LESS_OR_EQUAL

-------

http://support.microsoft.com/default.aspx?scid=kb;EN-US;311564
Stop 0x0000000A Irql_Not_Less_or_Equal" Error Message During Windows XP Upgrade

---------

http://support.microsoft.com/default.aspx?scid=kb;en-us;810093
Error Message with RAM Problems or Damaged Virtual Memory Manager
The information in this article applies to:
* Microsoft Windows XP Home Edition
When your computer restarts after you install Windows XP Home Edition, you may receive either of the following error messages:
System has recovered from a serious error
DRIVER_IRQL_NOT_LESS_OR_EQUAL

-------

http://www.geocities.com/marfer_mvp/xp_notes.htm
You have some driver or card that needs updating. Installing an old version of EZ CD Creator with Direct CD will cause this, bad RAID or SCSI drivers, and other reasons If applicable, apply the upgrade to XP downloadable from Roxio's web site. http://www.roxio.com/en/support/ecdc/index.html

--------------

http://www.winnetmag.com/Articles/Index.cfm?ArticleID=2504
Q: We have recently been getting the infamous Stop error message, IRQL_NOT_LESS_OR_EQUAL Address. What does it mean, and how can I find out the cause?


0

Response Number 3
Name: Roadfood
Date: September 12, 2003 at 06:03:36 Pacific
Reply:

I don't have any CD creator software installed yet, so there are no Roxio-related conflicts. Right now all the devices are using the drivers that came on the Windows XP installation disk. Device manager shows no conflicts.

I just tried the above fix that recommends resetting the Virtual Memory settings. That didn't work either. PC is still spontaneously rebooting.

I'm not a newbie but I'm not an experienced PC tech either, meaning I don't know enough about interpreting the error log to identify the faulty driver from there. I want to try disabling devices to troubleshoot. Can I disable everything except the processor and the hard drive and then go from there? Do I do that in Hardware Profiles?

Any suggestions would be greatly appreciated.


0

Response Number 4
Name: Roadfood
Date: September 12, 2003 at 06:16:14 Pacific
Reply:

I noticed something that might be significant. I mentioned I can't run disk defragmenter because as soon as I start it the BSOD comes up. I noticed when I start Disk Defragmenter that the file system being used is FAT32. Shouldn't it be NTFS? If so how do I change that? Do I have to go into CMOS setup? Or (please no) do I have to reformat the hard drive and start all over?


0

Response Number 5
Name: keef444
Date: September 12, 2003 at 13:37:56 Pacific
Reply:

If u partitioned, formatted and installed via the XP disk, then yes, u should have NTFS (a clean install using this method doesn't give u a choice !!)
If u right-click My Computer/Manage, Disk Management, it will tell u what file system u have.
If it is FAT32, u can convert to NTFS by typing: CONVERT C:/FS:NTFS at a command prompt (no loss of data) - it's a one-way process tho, there's no easy way to convert back to FAT32
If u haven't installed any 3rd party drivers for additional hardware, I strongly suspect the RAM is faulty.
I have fixed a few PC's with this prob by simply replacing the RAM

Hope this helps


0

Related Posts

See More



Response Number 6
Name: Sabertooth
Date: September 12, 2003 at 14:54:04 Pacific
Reply:

Remove all cards in your system except the video card and all memory chips except one,restart the system,if you don't get the message then you have a better chance of isolating the cause by adding other component one at a time.


0

Response Number 7
Name: Roadfood
Date: September 12, 2003 at 17:12:04 Pacific
Reply:

Re FAT32/NTFS--actually it is an option, it's on the third or fourth setup (blue) screen for Windows XP Home. Not knowing what NTFS is, I picked FAT32.

I'm not a computer tech and the next time I open that case will be the last. There is only one RAM module--the 128mb SDRAM that came with the system and has worked fine for three years. All I did was take the old 20G hard drive out and replace it with a new 60G hard drive.

So my question is--since the STOP/BSOD screen with the error message only occurs when the computer is idle, never when it is being used, does that narrow the problem down--without having to remove all the cards? (And, if I remove all the cards do I also have to disconnect the modem, the CD/DVD-ROM and the CD/RW?

I started this project on Sept 1. As soon as I started downloading the patches from Microsoft the PC got hit with W32.Welchia. I had to stop, install NAV, download patches, reinstall Windows XP, redownload all the patches--with a 56k modem. This alone took days.

Does any of this info help? I am having nightmares. Thanks.


0

Response Number 8
Name: Johnw
Date: September 12, 2003 at 17:39:19 Pacific
Reply:

I would be inclined to get the latest Windows Updates .


0

Response Number 9
Name: keef444
Date: September 12, 2003 at 18:18:19 Pacific
Reply:

XP 'Pro' doesn't give u a file-system format choice unless the drive was previously formatted in FAT32 - don't know about 'Home' tho....

But two other things u can try.....

1) Re-start the PC in safe mode. As most drivers aren't loaded in this mode, it might give a clue as to whether it's a driver or not.

2) Run chkdsk in recovery console, this will repair any errors on ur HD.

I still think it's RAM tho - some RAM just doesn't seem to be compatible with some XP/HD combinations - as u only have 128mb, it's gotta be worth upgrading that anyway !!


0

Response Number 10
Name: Roadfood
Date: September 12, 2003 at 18:28:17 Pacific
Reply:

I have already downloaded all the Windows updates.

Safe Mode is a good idea. I'll try that. Do I boot in Safe Mode and then just let the PC run to see if it crashes? Or load the drivers one at a time?

And you're right about the RAM, I do need more. Unfortunately I listened to someone who told me that SDRAM PC133 would work on this PC (which is supposed to take SDRAM PC100)--wrong. I just had to return 2 256mb sticks that didn't work.

Do you have a resource url for running chkdsk in Recovery Console? I was going to try that but on Microsoft TechNet it said Recovery Console was for experienced administrators only, which scared me off. Thanks for your help.


0

Response Number 11
Name: keef444
Date: September 13, 2003 at 07:22:28 Pacific
Reply:

Just let it run in safe mode and see if it crashes.

Recovery console for experienced administrators only ?? - Na - just boot from the XP disk and when the option comes up, press R.

At the 'command prompt', type: chkdsk and let XP do its thing.

That's it - easy !!


0

Response Number 12
Name: Roadfood
Date: September 13, 2003 at 09:44:27 Pacific
Reply:

The PC has now been running in Safe Mode for two hours without a stop screen. Presumably that rules out all the basic drivers? Now I'd like to load the drivers one at a time to determine if one of them is causing the spontaneous shutdown problem. How do I do that in Safe Mode? Do I use Safe Mode with Networking? Or one of the other options? I seem to remember that in previous versions of Windows there was an option to load device drivers one at a time. That option isn't readily apparent to me in Windows XP. We are making progress--thanks.


0

Response Number 13
Name: Roadfood
Date: September 13, 2003 at 12:01:34 Pacific
Reply:

Things have gone from slight improvement to dramatic deterioration. The DVD-ROM and CD-RW drives are gone. Vanished. I can see ATAPI CD-ROM in CMOS as the third boot device but when I boot into Windows XP--nothing. When I run "New Hardware Wizard" to detect them, Windows doesn't detect them. How to fix this?? Help!


0

Response Number 14
Name: Roadfood
Date: September 13, 2003 at 12:56:28 Pacific
Reply:

Disregard above post regarding DVD-ROM & CD/RW. I disconnected the computer, took off the cover, unplugged and replugged the cable, and nothing. Then I went into CMOS and changed some settings (I don't remember which). After that Windows XP recognized the D: (CD-ROM) and E: (CD-RW) drives again.

I'm back to requesting help on Safe Mode troubleshooting. Should I start from Command Prompt? How? The last time I did this was with Windows 98 SE which let me choose step-by-step. Thanks.


0

Response Number 15
Name: keef444
Date: September 13, 2003 at 16:40:10 Pacific
Reply:

Ah - I'm back !!

First run 'sigverif' in the RUN box, click Advanced and browse to C:\Windows\System32\Drivers
Click Start and a record of all ur 'unsigned' drivers will be shown and saved to C:\Windows\sigverif.txt
One of these could well be the rogue driver - u could try renaming a few of them at a time from xxx.sys to xxx.bak and re-starting, but I'm not sure what effect this would have, so try the following first.....

Run 'msconfig' in the RUN box and disable all startup items in the startup tab.

Reboot the machine in normal mode and see if it crashes.
If it doesn't, go back to msconfig/startup tab and enable half of them - reboot and see what happens.
By trial & elimination (50%) at a time, u should be able to isolate the bad startup item.

Hope some of this works !!


0

Response Number 16
Name: Roadfood
Date: September 13, 2003 at 16:52:13 Pacific
Reply:

Solid advice, thanks. I'll be back with an update.


0

Response Number 17
Name: Roadfood
Date: September 16, 2003 at 14:30:08 Pacific
Reply:

OK, I'm finally back. First chance I had to apply your suggested troubleshooters.

Ran msconfig and disabled all startup items. Rebooted back into XP. BSOD after about 15 min, same errors, which are:

STOP: 0x000000000A (0x7FFFFFFF, 0x00000002, 0x00000001, 0x804E40B0)

So I ran sigverif, and came up with these unverified files:

savrtpel.inf
savrt.inf
symredir.cat
symredir.inf
radio11.bin
wlangen.bin
radio0d.bin

But I think this approach is a sidetrack. Once again I tried to run Disk Defragmenter; that brings up the BSOD immediately with the same STOP message and error codes as above.

So I'm hoping these two events are a clue:
(1) Why does the PC crash ONLY when it is idle, not when it is in use? It was in almost continuous use for about 6 hours yesterday with no crash.
(2) Why does Disk Defragmenter bring up BSOD immediately?

Thanks for your continuing help. I'm not giving up.


0

Response Number 18
Name: Roadfood
Date: September 16, 2003 at 14:39:26 Pacific
Reply:

Addendum to most recent post. Just googled all the files listed above, which are all fine, except the first two. Have no idea what they are but the search results come up in German. (!)


0

Response Number 19
Name: wallace1234
Date: October 5, 2003 at 15:21:05 Pacific
Reply:

I have been reading this thread. Here's a good one: I am getting the same error messages, only they are showing up when I am trying to load W2kPro on a blank HDD. Replaced the RAM, CD, HDD, cable between the CD and motherboard, reseted the CPU. Maybe need to change the spark plugs?!?!?!

ggrrrrr! Frustrated!

I also get "cannot load dos! try any key" when trying to load a HDD diag disk (floppy). Tried new floppies, downloaded new diag software. I even get the "cannot load dos!" error when I just have video card, RAM (512m) and floppy; no HDD hooked-up yet!!

Bummer.
Thanks.
Any help.


0

Response Number 20
Name: Roadfood
Date: October 5, 2003 at 18:37:40 Pacific
Reply:

Wallace1234,

Since I last posted I have removed an unused PCI card and the modem, have updated the printer drivers, and have removed and re-re-seated everything, but to no avail.

Were you able to accomplish a full install of Win2kPro? If so, do you get the BSOD/error messages after the PC sits idle for 15 or so minutes? It has been our experience that the PC only crashes when idle, never when in use. We have found that if we continuously run an audio/video feed in Windows Media Player the PC does not crash. A clumsy workaround, but it will keep the PC running until I can replace the RAM (or buy a new PC--now it sounds like the fan is starting to go!).

Best of luck.
Roadfood


0

Response Number 21
Name: mtcon
Date: October 9, 2003 at 07:49:59 Pacific
Reply:

My problem is identical to yours. I would like to compare our system information to see if it helps to narrow down the problem. My config is the following:
motherboard: ASUS A7N8X deluxe
memory: Corsair PC2700 256MB (1 stick)
HDD: Maxtor 60GB (primary)
Western Digital 13 GB
Video Card: creative labs 32mb (nvidia)
CDROM: IOMEGA CDRW 16x10x40
Are you using any firewall, like ZoneAlarm?
I am able to run disk defrag on my secondary hdd without any problems. Not sure if that means anything. I appreciate any info you can provide. Maybe together we can beat this problem.
-MTCON



0

Response Number 22
Name: Roadfood
Date: October 9, 2003 at 14:15:20 Pacific
Reply:

MTCON,
Here's what I know about the hardware. Hope it helps.
Dell Dimension XPS T700r
P3 700mhz PC100 128mb 1 stick
ACPI-compliant
HDD WDC 60GB
CD/DVD ROM Samsung SD612
CD-RW Imation IMW1610321A (16x10x32)
I am using Zone Alarm (free version).


0

Response Number 23
Name: The Negative One
Date: October 27, 2003 at 04:30:02 Pacific
Reply:

Hi :-)

I also have this problem with my Notebook.
It's a HP/Compaq Evo N610c.
I had a clean harddisk and tried to install Win XP.
During the installation I had this IRQL_NOT_LESS_OR_EQUAL Error.
After that I changed the Memory and also the Systemboard.
It didn't help - I had the same error again.
Has anybody an idea what I could do to solve this problem?
Thanks!

The Negative One


0
Reply to Message Icon

Question about Spybot problem with directX



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows XP Forum Home


Sponsored links

Ads by Google


Results for: IRQL_NOT_LESS_OR_EQUAL bsod

Irql_not_less_or_equal bsod www.computing.net/answers/windows-xp/irqlnotlessorequal-bsod-/77456.html

Irql_not_less_or_equal (bsod) www.computing.net/answers/windows-xp/irqlnotlessorequal-bsod/175232.html

Windows XP Blue Screens with NDIS.SYS www.computing.net/answers/windows-xp/windows-xp-blue-screens-with-ndissys/3662.html