My sytem just goes black and reboots every now and then withour warning. When it wakes up it often gets a blue screen with IRQL_NOT_LESS_OR_EQUAL first and requires another reboot. I have no idea what it might be.

0

Same problem here (IRQL_NOT_LESS_OR_EQUAL, page_fault in a non-paged area).... Running XP on a KT7-Raid. Could all this be just a VIA chipset or bios issue?

0

I'm getting both the IRQL_NOT_LESS_OR_EQUAL and the page_fault in the non-paged aread on an IBM T22 laptop with XP-Pro, so it's likely not limited to VIA chipset.

0

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 - 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. ------------------

0

I was on the phone for about 4 eight hour days on the tech line with Dell. They sent various pieces of hardware and software as replacements. Nothing worked, not even replacing the mother board! The computer was down for almost 3 weeks. It would never boot fully before I got this stupid message. I finally exchanged the cpu for a new one. What a pain!

0

I have this same problem. When I'm playing a game or listening to music sometimes the screen turns blue with the IRQL_NOT_LESS_OR_EQUAL message. I'm thinking of buying a new mother board and a new CPU. Will this problem keep coming even though I have a new system? It could be my video-card (Geforce 2 MX200 64mb). because XP said that the graphics-card didn't had a XP logo on it. So maybe it's my video-card causing the blue screen.

0

nope I have an athlon 800mhz with a voodoo3 I think it's the via 4-in-1 piece of s--- drivers I've recently started getting them more and more since I deathmatch a lot. It's always because of games. Having bad SDRAM causes some other error so I know its not that again...

0

Ive get it only when writing CDs, im using XP pro on a KT7a, it seems like its a problem relating to memory... though i was actually watching the task manager when the pc rebooted itself, and the memory usage was low, as was the cpu usage. Its very strange..

0

I always gets the one of the following errors (totally at random?!?) when i try to do something with my computer: DRIVER_IRQL_NOT_LESS_OR_EQUAL IRQL_NOT_LESS_OR_EQUAL PAGE_FAULT_IN_NONPAGED_AREA After I reboot, the computer freezes in the BIOS check, no matter what i do. (i have to cut the power supply in order to get the d*mn thing to start again) It often occurs when i try to use the internet, or my cdr-device. I've tried to disable as many units as possible (also tried uninstalling Norton 2002) but nothing seems to help. I cant sort out any pattern when the errors occur, it seems to be at random. What is really strange is that my computer worked just fine, and suddenly (without any changes) it started to "freak out". I have an AMD XP 1600+, MSI K7T266 PRO2, 256 DDR, IBM HDD, ELSA Erazor X2, AC97 sound

0

I have the problem when I run Baldur's GAte II: Shadows of Amn. I have a ASUS Board (VIA DRIVERS) with a chaintech GeForce3 Ti200 and the game will run for about 20 seconds before it crashes. I have an AMD 1900+ 512 MB of ram, SB Audigy Card, etc. I think it might be either the Video CArd or the Audigy Card. Tomorrow I head to computer store to have them swap video cards and try again. The writeup about a hardware failure seems to be a good possibility. I keep getting these errors in Win XP more and more often (as of late in other programs as well). I also have troubles running the game and some other programs in Win 98 ( I dual boot machine). There seems to be a common thread here and I think it leads back to hardware...at least I hope. I'll update later.

0

I've noticed that some of you have PAGE_FAULT_IN_NONE_PAGED_AREA of something similar. That message show that u have faulty memory either the Dimm or the actuall chip itself. borrow someone elses and see if that works. as for IRQL_NOT_LESS_OR_EQUAL im still trying to find an answer for that

0

The IRQL_NOT_LESS_OR_EQUAL or Stop 0x0000000A errors are able to be generated by both software and hardware issues. The message indicates that a kernel mode process or driver attempted to access a memory address that it did not have access to. These error messages are generally formatted in the following fashion: STOP: 0x0000000A (0xwwwwwwww, 0xxxxxxxxx, 0xyyyyyyyy, 0xzzzzzzzz) 0xwwwwwwww The address that was referenced improperly. 0xxxxxxxxx IRQL that was required to access the memory. 0xyyyyyyyy Type of access. 0xzzzzzzzz Address of instruction that attempted to access 0xwwwwwwww. Cause: This issue can be caused by any of the following possibilities: Mcafee VirusScan for Windows NT issue Windows NT 3.51 upgrade from Windows NT 4.0 Service Pack Driver issue Hardware issue Solution: Mcafee VirusScan for Windows NT issue Exact error is as follows: STOP: 0x0000000A (0x0000015a, 0x0000001c, 0x00000000, 0x80116bf4) IRQL_NOT_LESS_OR_EQUAL Mcafee VirusScan for Windows NT 2.5.1(9607) and 2.5.2(9609) are not compatible with Windows NT 4.0 Uninstall Mcafee Windows NT 3.51 upgrade from Windows NT 4.0 Exact error is as follows: STOP: 0x0000000A (0x0000015a, 0x0000001c, 0x00000000, 0x80116bf4) IRQL_NOT_LESS_OR_EQUAL If you have upgraded your computer to Windows NT 4.0 from Windows NT 3.51 and have a server with Gateway Services for Netware to Windows NT 4.0 installed remove the Gateway Services for Netware and reinstall the service to resolve this issue. Service Pack Exact error is as follows: STOP 0x0000000a (0x00000006, 0x00000002, 0x00000000, **********) IRQL_NOT_LESS_OR_EQUAL ********** - This portion may vary Earlier service packs may have had issues with the TCP handling and updating the Service Pack will resolve the issue. Ensure you have the latest service pack installed in the computer. Links to locations to download the latest service packs can be found through our Windows NT download section. Driver issue Drivers which have errors of their own can also cause the IRQL_NOT_LESS_OR_EQUAL error. Consider updating or reinstalling your drivers (more specifically your network and/or SCSI drivers). For a listing of driver manufacturer company pages see our drivers page. Hardware issue In the event that the above information does not help to resolve your issue it is possible that the computer may be encountering a hardware issue. Attempt to exchange or replace hardware in the computer. Our recommendation would be: RAM / CPU / NIC

0

CHECK YOUR SIMMs !! I HAD ALL THOSE PROBLEMS !! I took the bad memory out, and I am back to gaming !!

0

Try replacing your NIC or graphics card. I did that, and my PC is much more reliable now.

0

I have the same pronblems and have just completed some research which could help us all... Let me know how you get on - especially with the Winnt32 /checkupgradeonly option as this my expose hardware incompatabilities we may have forgotten about - I guess that this is a little old but will help narrow down any hardware suspects - those with manufacturer claimed 2000 compatibility should be OK. Does everyone use microsoft update regularly? If so the recent posting timings may indicate a dodgy update... I get this on a number of machines - sometimes associatred with AOL, Norton or even virus scanners I use PC Cillian and Norton on different machines also mainly non-intel except for Dell Laptop where AOL seems to kill it off. But I'm using Win 2000 Prof ao all. Check the Hardware compatability list for Win 2000 as well. http://www.microsoft.com/windows2000/server/howtobuy/upgrading/compat/default.asp Using Check Upgrade Only Mode: http://www.microsoft.com/WINDOWS2000/techinfo/reskit/en/ProRK/prbb_iwp_fvvo.htm The Setup procedure for Windows 2000 Professional includes a �Check Upgrade Only� mode, which can be used to test the upgrade prior to a real upgrade. This produces a report that flags potential problems that might be encountered during the actual upgrade, such as hardware compatibility issues or software that might otherwise not be migrated during the upgrade. Figure 4.1 shows the Windows 2000 Check Upgrade tool. Figure 4.1 Check Upgrade Tool The format used from Windows 95 and Windows 98 is Winnt32 /checkupgradeonly. The report is saved to %windir%\upgrade.txt. You can change this location if you want. The format used from Windows NT Workstation 4.0 and 3.51 is alsoWinnt32 /checkupgradeonly. The report is saved to %windir%\win32.log. There are known problems with CD Burners Nero V3 I think and also with VIA mothher boards with VIA chipsets < V5 http://www.hp.com/cposupport/multifunction/support_doc/bpu03103.html This link seems to offer some good suggestions. http://www.microsoft.com/windows2000/techinfo/reskit/samplechapters/fnhd/fnhd_exe_woti.asp

0

I have another version of this error: I've been running into lots of issues getting WinXP to install- both as the only OS on C:, and now as a multi-boot on D:. I did finally get WinXP installed, and it even appears now to boot reliably, after a dozen failed attempts at installation. Each install would start with the message "One of your disks needs to be checked for consistency". I have no idea of what that means, but the time included a message about running CHKDSK /F; which I did from Win98, which in turn invoked SCANDISK, which found some boot sector issues on D:. However, every subsequent attempt at installation included that "...disks needs to be checked for consistency" message. I would get into various phases of install of XP before a stop code, one even got me into "less than 1 minute". Most included this phrase "IRQL_NOT_LESS_OR_EQUAL", plus a stop code. After 13 attempts, I finally got it to install, now it appears to boot OK (10 out of 10 times). I just know it will show up again though! My system: ABit BD7II P4 1.8A (512K cache) 512M PC-2100 DDR (single stick) GeForce 3 Ti200 I have yet to install a sound card and NIC, plus various drivers for Intel that come with the motherboard. I use my PC for flight simulation, which is very demanding, so I know it's only a matter of time before it shows up again. I di have various POST errors when trying to first boot my new system, which resulted in the "A7" error (Award BIOS). I'm told that this may be a memory error, although it ceased suddenly and has never re-appeared. So, maybe replacing RAM may be the first step. Bruce.

0