dragonoflife: (Default)
Dragon of Life ([personal profile] dragonoflife) wrote2006-08-26 06:12 pm
Entry tags:

(no subject)

Any computer people want to interpret this one?

DRIVER_IRQL_NOT_LESS_OR_EQUAL
STOP 0X000000D1


I mean, aside from "Dude, your computer is screwed." I know that already.

[identity profile] siliconrose.livejournal.com 2006-08-28 03:25 am (UTC)(link)
Note: Actually, this is probably one of the best possible stop codes you could be running into, all things considered. It doesn't mean your system is trashed - it's just the code that's providing communication between the operating system and the machine isn't well written. This is a common stop code, it's very easy to prove the driver is at fault, and it's also relatively easy to diagnose and fix.

[identity profile] dragonoflife.livejournal.com 2006-08-28 06:31 am (UTC)(link)
Thank you for the explanation. (You know, if I can understand Magic: the Gathering rules for the stack, I should be able to understand computer processing at the machine level. But I have yet to encounter a handily downloadable document that explains the latter...)

Hmm. The only driver I was trying to update lately was the NVIDIA GeForce driver, which I really hope is not at fault, since apparently the most recent driver version doesn't support my chipset (even though it says it does, when I tried to install it it detected no compatible hardware...)

Oh well. If just playing music while writing is enough to crash the system, I know I'll encounter it again. Hopefully I can track down the responsible driver and repair it. I trust myself to do THAT much at least, if it's possible for me to do so. (Or I trust myself NOT to delete the motherboard drivers again at least.)

Incidentally, any chance this could also be the source of my previous kernal fault?

[identity profile] siliconrose.livejournal.com 2006-08-29 03:59 am (UTC)(link)
Go Wikipedia? This is a description of the virtual memory part of the explanation. (The bits that discussed paging and memory not being there.)

If you mean what was causing your computer to reboot randomly, yes, this could very well be the cause. This blue screen would have resulted in the system abruptly rebooting. Of course, if there's something I missed in this saga, let me know and I can try to dig into it/explain.