|
|
| Page 1 of 1 |
|
|
 Posted: Thu, 16th Sep 2004 22:27 Post subject: Error message: "IRQL_LESS_OR_NOT_EQUAL" |
|
 |
"IRQL_LESS_OR_NOT_EQUAL....beginning dump of physical memory" is an error message I've gotten for the third time now. When the blue screen turns up, the hardrive shuts down and the only way out is to restart the computer. The info given in the blue screen refers to newly installed hardware but I haven't installed any new hardware in the last six months or so. Ideas anyone?
|
|
| Back to top |
|
|
[mrt]
[Admin] Code Monkey
Posts: 1338
|
| Posted: Thu, 16th Sep 2004 23:11 Post subject: |
|
|
| Quote: | 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1539.)
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried 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.) |
Head on over here for a ton of resources on how to possibly solve that lil' prob. Pretty usefull site 
Maybe a quick link to the KB article ripped off that site above Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors
teey
Last edited by [mrt] on Thu, 16th Sep 2004 23:13; edited 1 time in total
|
|
| Back to top |
|
|
Starter
Banned
Posts: 1622
Location: Green Bay, Wisconsin
|
| Posted: Thu, 16th Sep 2004 23:12 Post subject: |
|
|
try a different video card.
but more specs. info would be helpful.
.
sexyjesus is the only person on this forum, that cuts down his own, so-called country.
The only one.
Never once anything positive, only negative.
And you people fall for it hook line and sinker.
.
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
|
|
| Posted: Fri, 17th Sep 2004 08:41 Post subject: |
|
|
Thanks for the info! The solutions provided on those sites involved tinkering with the BIOS settings so I'm a little anxious about that... Anyway, my specs are:
Abit AI7
P4 2.8 GHz C, HT enabled
A-DATA 2x256 MB (Dual Chanel enabled)
Club3D Radeon 9800Pro 128 MB
Western Digital Caviar 120 GB
That's allt I can think of now, let me know if you need anything else. By th way, I doubt this is caused by a hardware malfcuntion since it's worked fine for a long time and I haven't installed any new hardware.
|
|
| Back to top |
|
|
[mrt]
[Admin] Code Monkey
Posts: 1338
|
|
| Back to top |
|
|
|
|
| Posted: Fri, 17th Sep 2004 11:33 Post subject: |
|
|
| [mrt] wrote: | Try it, if you screw something up you can still reset the bios to factory defaults
Did you try formatting and reinstalling winblows? i'd try that first cos you know how M$ OS's are, one day they work fine, the other they go loony. |
I would advise to do things the other way around:
1. Make sure your BIOS is up to date and you're CMOS settings are fine - find the newest BIOS updates on the manufacturer's site, don't be affraid to flash BIOS, anyone can do it and you can ALWAYS reset yer BIOS (refer to manual for this, or just take out the system battery for a while). Usually flashing BIOS puts CMOS settings back to standard too, but for some known issues this may not be sufficient; it never hurts to use this line to flash BIOS:
AWDFLASH.EXE filename.bin /py /sn /cc /cp /cd /R
This will clear CMOS for sure and flashes BIOS to newest release.
2. Blue screens and messages like you mentioned may be caused by drivers but usually seem to be caused by way more complicated issues, or even chainreactions of multple problems... So if the first step don't work get ready to just format C: and reinstall... This is why I love Norton Ghost 
I don't have much experience with things like WinDoctor 'cause I like to use the violent way of format, but i doubt whether it'll be able to fix (if it'll find anything at all)
" The power of accurate observation is often called cynicism by those who don't have it... " |
|
| Back to top |
|
|
|
|
| Posted: Sat, 18th Sep 2004 12:24 Post subject: |
|
|
Before anything id suggest you go in bios and load the FAILSAFE. Then if you still experience problems you should checkout the other options given
|
|
| Back to top |
|
|
|
|
| Posted: Sat, 18th Sep 2004 17:36 Post subject: |
|
|
My experience with this nice blue screen tells me that you might have a faulty ram stick here.
I suggest you unplug one ram stick at a time see if it happnes and try to identify the faulty stick.
|
|
| Back to top |
|
|
Starter
Banned
Posts: 1622
Location: Green Bay, Wisconsin
|
| Posted: Sat, 18th Sep 2004 17:46 Post subject: |
|
|
| exon wrote: | My experience with this nice blue screen tells me that you might have a faulty ram stick here.
I suggest you unplug one ram stick at a time see if it happnes and try to identify the faulty stick. |
true, or video card or nic card, so on. I don't think the BIOS will give you a blue screen. seems like it is after the BIOS loads and before/start of windows.
.
sexyjesus is the only person on this forum, that cuts down his own, so-called country.
The only one.
Never once anything positive, only negative.
And you people fall for it hook line and sinker.
.
|
|
| Back to top |
|
|
|
|
| Posted: Tue, 12th Oct 2004 10:35 Post subject: |
|
|
I'd have to agree with the RAM remark. If the BSOD are completely random (like, not occuring while you do a particular thing), I would say its faulty RAM. Get the Ultimate Boot CD, (http://www.utlimatebootcd.com), there's MemTest86 on there, run it and figure out if you have a faulty stick. (Note that MemTest doesnt like dual channel, so dont test both your sticks at the same time, it *WILL* fail)
I've had that problem with my 1gb stick. Basically my stick was a 333 and my board wouldnt do 333, would only do 320. I tried the stick in a lot of computers, it was FINE. So if you're overclocking (or downclocking), it might be your problem too. Note that on mine, no errors would show up in MemTest, because it was most likely just a ONCE IN A WHILE deal.
|
|
| Back to top |
|
|
| Page 1 of 1 |
All times are GMT + 1 Hour |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB 2.0.8 © 2001, 2002 phpBB Group
|
|
 |
|
