View Full Version : Blue screen: driver_not_less_than_or_equal_to!
whentoquit
25th January 2003, 18:28
Concerned when fatal blue screen appears stating message in post. Do not know what program is causing this. Is it CCE 2.5 or possibly VFAPI? Have not attempted to master AviSynth. Am running XP Home on a AMD 1700+. When screen appears it starts dump but i just restart & things are fine until next time. Any info would be helpfull. Thanks!!
MasterYoshidino
25th January 2003, 22:19
i think your cpu did a miscalculation and caused an error
if you are overclocking your cpu it can happen due to instability in MMX calculations.
errors also tend to happen to me if i try to overclock beyond the cpu's general stablilty settings.
I am overclocking a 1.8GHz Pentium4 to 2.4GHz and if i try to go an higher, say 2.5GHz, then my system will boot but after some sustained stress, applications will fail.
try to increase your cpu's voltage, soften your memory timings, and benchmark using a program such as sisoft sandra, to make sure that your system can sustain stability for at least 24 hours of stress
CaPPyD
26th January 2003, 17:45
If you give us the ENTIRE ERROR MESSAGE, I might be able to find out more, a quick search of the MICROSOFT TECHNET (http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/reskit/prmd_stp_ottj.asp) produced this information:
Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL
The Stop 0xD1 message indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.
Interpreting the Message
This Stop message has four parameters:
Memory referenced.
IRQL at time of reference.
Type of access (0x00000000 = read operation, 0x00000001 = write operation).
Address that referenced memory.
Resolving the Problem
For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.
Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
For more information about Stop 0xD1 messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x000000D1, and 0xD1.
CaPPyD
26th January 2003, 17:46
Here's another one (http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/reskit/prmd_stp_hwpg.asp):
Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
The Stop 0xA message indicates that a kernel-mode process or driver attempted to access a memory location to which it did not have permission, or at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own. This Stop message is typically due to faulty or incompatible hardware or software.
Interpreting the Message
This Stop message has four parameters:
Memory address that was improperly referenced.
IRQL that was required to access the memory.
Type of access (0x00000000 = read operation, 0x00000001 = write operation).
Address of the instruction that attempted to reference memory specified in parameter 1.
If the last parameter is within the address range of a device driver used on your system, you can determine which device driver was running when the memory access occurred. You can typically determine the driver name by reading the line that begins with:
**Address 0xZZZZZZZZ has base at <address>- <driver name>If the third parameter is the same as the first parameter, a special condition exists in which a system worker routine, carried out by a worker thread to handle background tasks known as work items, returned at a higher IRQL. In that case, some of the four parameters take on new meanings:
Address of the worker routine.
Kernel interrupt request level (IRQL).
Address of the worker routine.
Address of the work item.
Resolving the Problem
The following suggestions are specific to Stop 0xA errors. For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.
A Stop 0xA message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.
A Stop 0xA message might also be due to failing or defective hardware. If a Stop message points to a category of devices (video or disk adapters, for example), try removing or replacing the hardware to determine if it is causing the problem.
If you encounter a Stop 0xA message while upgrading to Windows XP Professional, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP Professional, contact the hardware manufacturer to obtain compatible updates. For more information about simplifying your system for troubleshooting purposes, see " Troubleshooting Concepts and Strategies" and "Troubleshooting Startup" in this book.
For more information about Stop 0xA messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x0000000A, and 0xA.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.