Driver IRQL not less or equal

October 21, 2005 at 01:40:48
Specs: Win XP Pro SP2, AMD Athlon XP 1800+ / 256

Hey.

I have this annoying problem concerning system failure. I have had system crashes before and then it took about seven times to boot my system before it got stable. Then i had these failure messages: "page fault in non paged area" and "driver irql not less or equal". Now i have installed a clean version of Win XP Pro and i have Service Pack 2. All I have installed with it are Firefox, Norton Internet Security 2005 and Forceware 78.01 driver for my Geforce 6600GT.

I have cleaned my case and tried to switch my memorysticks and nothing works. My system won´t stay up at all now. These are the error messages:

Driver irql not less or equal

Stop: 0x000000D1 (0x85FFFFE4, 0x00000002, 0x00000000, 0x85FFFFE4)
and
Stop: 0x0000000A (0x006018C8, 0x00000002, 0x00000000, 0x804D9092)
and
Stop: 0x0000008E (0xC0000005, 0x00000045, 0xF894CB9C, 0x00000000)

Please, if someone could help me with this problem I would appreciate it a lot.
Thank You. (Feel free to ask any additional information)

My computer specs are:

AMD Athlon XP 1800+
Epox 8KHA+
Geforce 6600GT
Seagate Barracuda 80 GB & Maxtor Diamond Plus9 80 GB
Creative SoundBlaster PCI128
Codegen case with Nexus Silent 300W Power supply

Kokovartalo


See More: Driver IRQL not less or equal

Report •


#1
October 21, 2005 at 03:47:18

This is my latest minidump:

Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\admin\Desktop\Minidump\Mini101805-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Tue Oct 18 21:51:40.613 2005 (GMT+3)
System Uptime: 0 days 0:00:30.243
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................................................................
Loading unloaded module list
..
Loading User Symbols
The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {6018c8, 2, 0, 804d9092}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.
The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.

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

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 006018c8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804d9092, address which referenced memory

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.
The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

READ_ADDRESS: The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
006018c8

CURRENT_IRQL: 2

FAULTING_IP:
nt+2092
804d9092 8a02 mov al,[edx]

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 82089ac8 to 804d9092

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
820f1830 82089ac8 00000002 00000001 00000000 nt+0x2092
00000000 00000000 00000000 00000000 00000000 0x82089ac8


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

Kokovartalo


Report •

#2
October 21, 2005 at 09:13:18

download memtest86 from www.memtest86.com. Put it on a floppy or cd and boot to it. then let the memory test run overnight. I didnt read all the error messages but I think you have faulty memory. check that first and let me know what it comes up with.

Report •

#3
November 13, 2005 at 21:58:50

Try uninstalling Norton 2005 Internet Security. Use the regular windows firewall. Also, if possible, give me a feedback at arjun.singhal@gmail.com

I have been suffering with the same problem since the last 1 month. I've changed memory sticks and the hard-drive on my Compaq Presario 2134AD.

Last evening, I re-formatted and continued to use Norton 2002 that comes with the Quick Restore. I so far have not faced the problem. Keeping my fingers crossed now.



Report •

Related Solutions

#4
November 15, 2005 at 22:42:57

I've had exactly the same problems (page fault in non paged area" and "driver irql not less or equal") cropping up sporadically on a Dell Dimension 8300 running XP Pro SP2. I thought it was hardware, so I reseated memory and I/O boards, ran MemTest86+, etc. But it wasn't hardware, it was driver conflict.

A month ago I bought a Freecom FHD-3 250 GB USB-connected external drive. It came bundled with Freecom Personal Media Suite, and that had a USB driver, bonifay.sys, that crashed the system. The hard drive is absolutely fine, but if you get it DON'T install the Media Suite. For one thing it relies on Microsoft Briefcase, and that's absolutely hopeless for backing up multi-gigabyte drives. (Try Microsoft's SyncToys instead.)

Here's the test, even if it's not bonifay.sys but something else sitting there with your regular (Win XP) USB drivers.
First, open Device Manager, under USBs, choose any one of your USB Universal Host Controllers, right-click, choose Properties, Driver tab, then the Driver Details button.
On my machine, it has:
usbhub.sys, usbport.sys,usbuhci.sys, and usbui.dll, all 5.1.2600.2180 (xpsp2_rtm.040803-2158).
You may also see usbehci.sys, or usbohci.sys, which are both MS Windows drivers.
But are there any other NON-MS drivers?
Here is where I found bonifay.sys. I uninstalled Freecom Personal Media Suite, bonifay.sys went away and my BSODs went away.
For you the problem may not be a tagalong USB driver, but a driver for some other device. Even so, you may be able to see what's up by using Verifier.exe.

I found a way of **reproducibly** tripping the BSODs, which is how I know that bonifay.sys was the problem. I wish I'd known earlier, but there's a program called Verifier.exe that lives in C:\WINDOWS\system32. It's used for driver development and testing. Run it and a GUI opens up. To let you know, with all the options and buttons you'll click, Verifier does nothing until you get to a "Finish" button, at which point you can still opt out and "Cancel", so don't sweat it.
The overview is you set Verifier to run tests you choose on any drivers you choose. Click "Finish" and then you have to reboot. If during reboot you get a BSOD, it'll tell you that some driver is being bad while verification is running, in which case you'll have to hard boot. This time on bootup select "Choose last known good configuration",
and you'll get a clean boot back to where you were. Now that you've logged on again,
change settings, then re-run Verifier, re-boot etc. until you get a clean boot.
NOTE: "change settings" here means change device settings OR unstall software OR disable devices via Device Manager. The latter is the quick and easy way to home in on the problem device, but after that you'll have to home in on the particular drivers or uninstall the software they came with.
NOTE 2: Disable rather than delete devices if you get to that.

Running Verifier.exe:
On the first screen, choose "Create Custom Settings (for code developers)" and click Next.
Then click "Select individual settings from a full list" (and Next).
Then tick any particular check boxes you want (and click Next).
Special pool, Pool tracking, and Force IRQL sound like the ones that relate to your crashes, but if you want to know if you truly have a clean install, then check all except the Low resources simulation. The Pool-related tests isolate and double-check each tested driver's memory usage.
The documentation for Verifier, telling you what these settings do, is at:
http://support.microsoft.com/default.aspx?scid=kb;en-us;244617
But back to Verifier...
Once you've checked the tests you want then select the drivers you want to test. With My USB problem, I found that selecting ANY driver would make it BSOD on reboot,
so I stuck to choosing just beep.sys (innocent as it is) as the driver to be Verified. [BTW, it wasn't beep.sys at fault, but boniface.sys trying to used beep.sys's memory space (I think) that was the problem.]

Once (if...) you've sorted out your driver problem, then ideally you'll want to select all drivers and have Verifier not throw up a BSOD on reboot. This is the stage that I got to (big yay after a month of BSODs).

Hope this helps, and good luck.

Anon2


Report •


Ask Question