I saw that and agree that they probably don’t have a mylex raid. Either way, it’s the best place to start. (the knowledge base, that is) I’ve seen IRQL_NOT_LESS_OR_EQUAL with bad memory, and a bad network card. I’m biased to blame some kind of hardware fault. Or overheating. Check the CPU fan. If you have 2 sticks of memory in there, take one out and run for a few hours, then run on the other. Sometimes the hex code can help too: try searching on the STOP number (looks like STOP:0xD1), sometimes a general yahoo search on the exact error message can give you some leads as well. http://search.yahoo.com/bin/search?p=“DRIVER_IRQL_NOT_LESS_OR_EQUAL” good luck!
[solemn talking sheep]But don’t you see, fauxpas? You do have a sin to confess: the sin of jealousy.[/solemn talking sheep]
Heh heh. And you never will.
Earlyout:
I was thinking along the same lines.
It’s possible a cord got jerked somehow and momentarily cut power to just the computer. My guess is it was power-supply related.
Lobsang, I might appreciate some details, like what kind of computer it is, how old it is, system specs, when you ran defrag on it, etc. most likely it’s a heat issue, clogged vents, dirty fans, etc.
I was getting IRQL_NOT_LESS_OR_EQUAL errors when my system, for no apparent reason, kept trying to move all plug-n-play devices onto the same IRQ (17, IIRC). This was a W2K system, but it would display similar behavior under Linux. If I reserved 17 in the bios, then it would move everything to 11, or some other IRQ.
The weird thing was, if I moved a card from one slot to another or removed something, it would go back to normal for a while, then over several reboots it would gradually mess up the IRQs again. Which meant that every time I tried something - switch out RAM, change network cards, strip down to a barebones system, it looked like I had solved the problem. Then the problem would come back a couple of days later.
That whole issue nearly drove me to become Amish. Everything seemed to be the problem, and it wasn’t till I looked at the device manager by resource (right click on My Computer, go down to Properties, click the “Hardware” tab, click the “Device Manager” button, go to the view menu and select “resources by type” and then open the “Interrupt Request (IRQ)” menu. It really should’ve been one of the first things I checked, but I haven’t had to debug problems like that in a while.
Since it appeared to be a hardware problem, not software, I wound up replacing my motherboard (it was a Soyo Dragon, it was replaced with an Asus A7V333). The problem has not returned. I know I could’ve turned off acpi and reinstalled windows and set all the resources by hand, but at that point I wanted to kill the computer, not baby it more.
On the other hand, random reboots usually mean I need to clean the cat fur out of my cooling fans and power supply. Or stop playing Sim City 4.
I run Windows 2000 Profesisonal at work. Part of my job is creating PDF files from Microsoft Word documents using Adobe Acrobat Distiller. Periodically, I would run into a document that, every time I tried to create a PDF from it, my computer would spontaneously reboot just before the PDF creatiion process reached 100%. This was, as you may guess, extremely annoying, espeically since it didn’t give me the ol’ BSOD, a General Proteciton Fault, or any other error message. This would happen over and over again with certain documents, but not with others, and I was never able to figure out what was going on.
I fianally upgraded to a newer version of Adobe Acrobat Distiller and the problem went away. But it really surprised me that a program could cause my computer to reboot like that, especially with Windows 2000.
Barry
My computer did this, I thought it was a CPU overheat, but upon closer inspection I found that one of those 1/4th inch cylinder things that sticks up perpindicular from the motherboard (someone fill in term there please!) had leaked a liquid that had turned a rusty brown color. I had to buy a new motherboard.
I think you are referring to electrolytic capacitors, Bob55. These can indeed leak a caustic liquid when excessive heating creates steam inside which can ultimately rupture the can. There was a big issue with bad caps being used on motherboards a while back, apparently caused by a flawed design.
Just a bump because I have the same question as PurplePerson. How do you turn this auto-reboot function off? In ME for my case. Some people have said it is done through the crtl panel, but where specifically? I’m having a similar problem, and I want to rule out a software issue before I start looking at hardware.
TIA
Pebs