DescentBB

0x0000000a (0x0000001c, 0x00000002, 0x00000001, 0x8052487f)

IRQL_NOT_LESS_OR_EQUAL

Dell Dimension 4700 SP2
1024GB RAM
2.8GHz Pent
40GB Hardrive

This error occurs after the computer has been running for a number of hours even if the computer is not being used.

I checked MS's website but came up empty on this one.

Im gonna say its a driver conflict, are all your IRQs full? could also be a memory error,but not as likely.

Is there any more to that error, a file listed or anything? any new USB items plugged in, and this is going to sound odd, a logitech mouse or keyboard?

memory

likely, but not as likely.

Usually having to many USB devices plugged in can generate that error, and out dated logitech drivers are also prone to producing similar errors

Try running a few loops of memtest86+, if it shows errors it is probably a memory problem.

http://www.memtest.org/

I've also seen that BSOD when I was experimenting with my overclocks and voltages, not enough voltage or just pushing the chip too far can cause an IRQ_NOT_LESS_OR_EQUAL, but it is hit and miss. Though whatever it is, if it is a voltage or memory problem tweaking it out of a dell is going to be a major pain. Also check for dust and slow fans, if a fan failed or there is too much dust it could lead to the same types of instability I get when undervolting.

yeah, I do get a similar error when pushing the ram to far under an overclock, but normally I get the added lines of \"begin physical dump of memory\" other times i just get the stand of code which Ive come to associate with a corrupted driver, or to many used IRQs

Ended up being the memory...

I ran Dell's memory test and it came up that I had a bad stick. Fortunatly, Corsair has a lifetime guarantee.

Immortal Lobster wrote:Im gonna say its a driver conflict, are all your IRQs full? could also be a memory error,but not as likely.

Just FYI, IRQL is an assembly variable, and has absolutely nothing to do with IRQs like you're thinking of. Its referencing an address in system memory.