BSoD screens

[DereX888]

Post BSoD screens here, lets have some laugh
(blue screen of death - as originally referred to windows' crash screen)




Here is a mighty linux's bsod i've found:

[valvehead]

This was the screen my friend and I got when putting together a system from old parts. There is nothing like beginning a fresh install of XP, waiting 40 minutes for all the files to copy and then restarting to end up at this screen. We tried all sorts of bios settings to no avail. I thought for sure that the hard drive was shot, but it turned out to be incompatible memory.

This is why I'm glad I spent time researching and buying new warrantied parts for my custom PC. I've never had a BSOD or automatic restart. Even program crashes are very rare.

[Conquest10]

^ I got the same screen when I tried tp just upgrade from ME to XP. Full install gave me nothing.

[lordsmurf]

IRC_NOT_LESS_OR_EQUAL is a RAM issue most of the time. Or a problem with the motherboard or CPU communicating with the RAM. Or heat. Or all of the above.

[Faustus]

IRC_NOT_LESS_OR_EQUAL is a RAM issue most of the time. Or a problem with the motherboard or CPU communicating with the RAM. Or heat. Or all of the above.

Actually. Usually if windows is installed already and it suddenly comes up its a Driver issue. If reinstalling from scratch doesn't fix it THEN its likely a RAM issue.

[DereX888]

IRC_NOT_LESS_OR_EQUAL is a RAM issue most of the time. Or a problem with the motherboard or CPU communicating with the RAM. Or heat. Or all of the above.

everyone usually point to faulty ram in such cases, but in my experience it was always the heat or overclocked ram.
I cant tell you how much time i have spent trying to figure it out with one of my old laptops (acer tm 312t). I changed rams, run memtest on them, they were all perfect. yet when it was running it always gave me that irq_not_less... crap and crashed after an hour two or more.
Finally i tested the laptop opened up (literally - all components on my table, without case) and it was running for a week without a problem. It as the heat inside the laptop's case, not the faulty ram itself.
Another common problem is overclocking FSB (and ram) when using cheap ram sticks. Same errors are bound to happen.

So in my opinion 9 out of 10 cases is not the faulty ram piece itself, i am sure they dont die as often as urban myth would like you to believe.

[lordsmurf]

I never meant that the RAM was bad, but more that it was hot (rather than CPU), or needed heat spreaders, or was not in the slot correctly, etc. I don't think RAM dies that often either.

[DereX888]

Yes I agree completely.
Come to think of that - in 10 years and probly hundreds of different machines I had only 1 case of bad ram stick - and today im not so sure was it really bad piece of ram, as i dont think i knew 9-10 years ago about i.e. memtest...

just to keep it with the subject:

[DereX888]

and a more recent BSOD at RSA
Feb 13, 2006

...Perhaps the most odd thing of the evening was when I found a Blue Screen of Death prominently displayed on a vendor system, and realized I was the only person who seemed to realize that it was a bad thing.
LOL!!!
(whole story here)

[waheed]

http://www.quicktime3.com/samples/humorous/win98crash.html

[Garibaldi]

There is a linux screensaver that will display all sorts of BSODs, I don't have it anymore though

[whitejremiah]

IRC_NOT_LESS_OR_EQUAL is a RAM issue most of the time. Or a problem with the motherboard or CPU communicating with the RAM. Or heat. Or all of the above.

yea, it can be ram OR heat for sure, i got the same message once when i had a faulty stick of ram......and again at another point when my processor fan started dying.....

and just located this......
http://www.sysinternals.com/Utilities/BlueScreen.html