- Q: "what does this error messege means?"
- Posted by Mas on December 25th, 2003
wat does this error mean? "Driver irql not less or equal"
thnx in advance
- Posted by Dave Patrick on December 25th, 2003
http://msdn.microsoft.com/library/en...codes_6vxj.asp
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
http://www.microsoft.com/protect.
"Mas" wrote:
| wat does this error mean? "Driver irql not less or equal"
|
| thnx in advance
- Posted by Doug Allen [MSFT] on March 4th, 2004
The error you're describing is a STOP 0x0000000A bluescreen. This is a very
common STOP error, and virtually any hardware or software could be the
cause. However, in the circumstances that you're describing, I would
suspect hardware first because you get this STOP during a clean install.
This to me rules out any software or drivers, etc. So I would say make sure
that you have the latest BIOS, etc.
As far as bad hardware, I would start with RAM. We have a hardware RAM
diagnostic tool that will run from a floppy. Verify that all of the RAM is
good, and we'll go from there. Also, the exact parameters of the STOP would
be helpful. It will say STOP 0x0000000A then parenthesis and 4 more hex
parameters. It would be great if you could document those for me as well.
--
Doug Allen, Windows 2000 MCSE
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
"Mike Kimmel" <mgk114@swbell.net> wrote in message
news:7F527D27-1317-4439-B259-AB0BF22E0004@microsoft.com...
install 2000 on the selected partition and formatting the partition FAT32
(NTFS format fails).
- Posted by Bob I on March 4th, 2004
It is probably an issue with the Compaq Presario. Is it compatible with
Windows 2000? If you were having problems with installing Windows 98
then Windows 2000 is probably out of the question.
Mike Kimmel wrote:
- Posted by Mike Kimmel on March 4th, 2004
Thanks for the quick response! After trying a couple of things, I found that the IRQL error is not appearing any more. Now it's a whole different blue screen issue! The most recent one is PAGE FAULT IN NON PAGED AREA. The particulars are now
STOP 0x0000005
(0xA0817AEB, 0x00000001, 0x80434D04, 0x00000002
80434D04 base at 8040000
Date Stamp 384d5a76 ntoskrnl.ex
Hopefully this will give a better idea of what dragon I'm trying not to get killed by (I've given up slaying them on Compaqs)
Thank you
Mike
- Posted by Mike Kimmel on March 5th, 2004
I was having what I thought to be hardware issues during the 98 installs. I was finally able to get 98 installed successfully, and then they decided they wanted 2000 on it instead. Checking HP, it doesn't specifically state 2000 is compatible or is not compatible
All the HP site offers are updates for 98 and ME with respect to the Presario 5240. And now the error is "PAGE FAULT IN NON PAGED AREA." And all of these errors wouldn't present such a problem to me if they'd occur after the O/S was installed. I haven't seen them before this early in the install process
Thanks for the help, though
Mike
- Posted by Bob I on March 5th, 2004
Really looks like a memory problem. (or a hardware problem)
http://aumha.org/win5/kbestop.htm
0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online Win XP Resource Kit article, or see Windows
2000 Professional Resource Kit, p. 1548.)
Requested data was not in memory. An invalid system memory address was
referenced. Defective memory (including main memory, L2 RAM cache, video
RAM) or incompatible software (including remote control and antivirus
software) might cause this Stop message, as may other hardware problems
(e.g., incorrect SCSI termination or a flawed PCI card). Use the
Mike Kimmel wrote:
- Posted by Doug Allen [MSFT] on March 5th, 2004
I'm terribly sorry I forgot to post the link to our memory diag tool.
Download it and run it on this machine.
http://oca.microsoft.com/en/windiag.asp
When we're talking about the more common STOP error messages like the first
STOP 0xA and now the STOP 0x50, these are not always either hardware or RAM
or software. However, when you start seeing varying STOPs on the same
machine, hardware does become suspect. You also mentioned a good point that
could very well be your issue - compatibility. While this is probably not
bluescreening because of BAD hardware, but more likely incompatible
software. I looked on Compaq (HPs) site, and found the compatibility info
for the Presario:
http://h20015.www2.hp.com/en/documen...7686&cat=setup
"Compaq does not recommend upgrading Compaq Presario PCs from Windows 98 to
Windows 2000; although some may wish to upgrade for specific needs.
Compaq does not support Windows 2000 Professional or Windows NT on any
models that were not sold with that software."
So basically, after making sure you have the latest BIOS, if you still have
problems, there is no recourse and you won't be able to run Windows 2000.
Do you know if the model# is just a Presario 5420, or 5420AU, 5420CA, etc?
The 5420 only did not have any drivers or updates for Win2k or XP. However,
the other models did. To find that, click here:
http://welcome.hp.com/country/us/en/support.html
and search "Download drivers and software" with the keywords "presario
5420". Perhaps you will have some luck that way. Hope this helps!
--
Doug Allen, Windows 2000 MCSE
Microsoft Enterprise Support
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bob I" <birelan@yahoo.com> wrote in message
news:404886BF.1010808@yahoo.com...
decided they wanted 2000 on it instead. Checking HP, it doesn't specifically
state 2000 is compatible or is not compatible.
of these errors wouldn't present such a problem to me if they'd occur after
the O/S was installed. I haven't seen them before this early in the install
process.