Best BSOD evar.

[toxico.livejournal.com]

While a coworker was repairing a Windows install, this happened:



Mmm, burgers...

This explains a few more like this, in case someone isn't familiar with values like this. I'd read up on them but never seen one occur. I especially like 0xDEFEC8ED.

Comments

[doublefelix.livejournal.com]

0xDEADBEEF is a special number in many systems, but Windows is generally not one of them...
http://en.wikipedia.org/wiki/0xDEADBEEF#Magic_debug_values

[doublefelix.livejournal.com]

Oh, you already got that. >_>

[toxico.livejournal.com]

I thought that odd too.

I found a couple of forum threads where it's happened on some Dell machines during a repair of Windows, and her machine is a Dell.

Also of note is the fact that the fates chose World Vegetarian Day to deliver unto us this message...

[hotclaws.livejournal.com]

(http://s216.photobucket.com/albums/cc290/hotclaws/?action=view&current=lol_cat_icanhascheezburger.jpg)

[mattcaron.livejournal.com]

Did that computer happen to have some variety of photo ID printer hooked to it?

[jon787.livejournal.com]

Since 0xDEADBEEF isn't an assigned bug check number, I'm going to assume someone's code had some very weird pointers running around.

[doublefelix.livejournal.com]

Maybe the system crashed precisely because something explicitly accessed the address 0xDEADBEEF with ill-used admin privileges :P

[jon787.livejournal.com]

Well its not *supposed* to be a memory address, but I guess there is nothing stoping some dumbass programmer from putting one there.

I was mostly thinking that either:
a) Someone didn't want to use codes from the actual list of them, or
b) Someone didn't initialize a variable that later got passed to KeBugCheckEx as the stop code.

[kayfox.livejournal.com]

I second this, its extremely unlikely that someone would get a bugcheck 0xDEADBEEF.

But its extremely likely that one would see such a bugcheck coming from the systernals BSOD screensaver.

[toxico.livejournal.com]

Normally I would chalk it up to such a thing; however, it's hard to fake a BSOD using a screensaver when in the middle of Windows setup. That, and our antivirus solution blocks that screensaver.

[jedisamui.livejournal.com]

Funny.

My guess would be XP SP3 and it didn't like the SATA HD controller drivers. That would be my guess. But the error is definitely funny.

[amynnah.livejournal.com]

What? Dead Tauren? I didn't do it!

And "ox defecated" indeed. :)

[toxico.livejournal.com]

Liar. My Tauren Druid (who may be named Toxicow *cough*) is dead because of YOU.

[amynnah.livejournal.com]

.....maybe... but not from my Nelf Druid(s). One's about as dangerous as a mouse fart (Horde-sympathizing tree-hugging love-the-world make-love-not-warcraft hippie that she is), and the other is semi-retired from PVP, only because there wasn't enough money in it for her ("Do I have a hit or a bounty out on that guy? No? All right, he can live.").

Maybe my Belf Priest killed you... not enough heals. :)
"Okay, keeping the Druid up, keeping the Druid up... by the LIGHT a FLOWER!" /scampers off to go pick. So yeah. Blame the ditzy Sin'dorei.

[pehteyemdjehuty.livejournal.com]

Someones been running Diablo II's cow level once too often. ;)

[toxico.livejournal.com]

Now now; we all know there is no secret cow level.

[pehteyemdjehuty.livejournal.com]

That's what THEY want you to think. ;)