Man gets BSOD message tattooed on his arm
By Darren Murph 
posted July 28th 2007 4:45AM
posted July 28th 2007 4:45AM
[Via Tumbl, thanks Laura]
posted July 28th 2007 4:45AM
A look back on popular stories from today in a specific year.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
look how red is arm is lol...
look how red his arm is lol...
never been tattooed before eh?
Its red with shame!
I wish people would wait until the redness goes away before showing people their tattoo... yuck. I dont know why they think the best time to take a picture of a tattoo is immediately afterwards when it looks like they have some infectious rash.
MORON!
Legend!
That's what happens when you try to run a desktop windows on an ARM processor. He shoulda gone with windows ce.
sooo nerdy and i laughed =)
good luck getting laid with that
I'd sleep with him... for a price :P
eh... i'd call it RSOP > red screen of pain.
Way cool ... !!!!
a billion times more original than havin some tribal thing from a tattoo catalog on ya body somewhere .. cos that is pathetic ..!!!
You go man !!!
EXIT.
15min geek credit... but the tattoo is nice, must be very difficult to get the font right.
totally - its as if the tattoo was done by some robot arm...
It's freaky how accurate that tattoo is. Even the font spacing is perfect....
Oh dear. What an idiot.
Except of course the BSOD is disabled by default in XP and Vista so most people probably wouldn't even know what it is.
you don't have mess around much, do you?
The only people who would mess about are geeks who want to see what caused the error. Most normal users wouldn't want to see the BSOD or even know what it is.
I dont know what is dumber ... the guy getting this tat or your statement that BSODs are disabled by default.
You dont have to be a geek or screwing around with computer to get a BSOD.
You can have a failing harddrive and easily get a "Unmountable Boot Volume" BSOD.
Or you can install something new like a new printer and on the next boot your PC may not like the drive so you will get the wonderful "IRQ Not Equal or Less" BSOD
Its a part of life when we use Windows. I have accepted this, but this guy has taken the acceptance to a whole new level.
Funny because in all the years I have been using XP and more recently Vista I have never had a BSOD.
As to the IRQ error thats something you should really only get if you've tried manually configuring your IRQ's and didn't know what you were doing.
seriously, can i come live with you in your fantasy world? of course, i've never had a bsod when i wasn't personally messing around with my pc, but i've cleaned out people's computers that would bsod whenever you'd boot in normal mode... loaded up with tons upon tons of malware. so yea, it can happen to non "geek" people.
oh and "As to the IRQ error thats something you should really only get if you've tried manually configuring your IRQ's and didn't know what you were doing." is one of the most laughable things i've ever heard. anyone who has spent enough time fixing other people's computers knows that windows isn't always savvy when it comes to irq conflicts.
Yes we all bow down because Only Clayton and SpeedMonkay know computers. They are the only computer techs in the world. The rest of us are just poor users.
Given that nearly all home printers these days are USB the odds on an IRQ conflict are slim to none.
I love the comment about if you spend al your time fixing computers you're going to find BSOD's. Thats like saying if you deal with ill people all the time you're going to find a dead one.
Most USERS, note the word users and not techs or repairman, will never see a BSOD on XP nor on Vista because it only happens on an exceptionally few errors. Anything else just results in the machine rebooting with a little message explaining that an error has occured and the machine will now reboot. Windows 98 on the other hand would BSOD for every little thing.
Yes we all bow down because Only Clayton and SpeedMonkay know computers. They are the only computer techs in the world. The rest of us are just poor users.
Given that nearly all home printers these days are USB the odds on an IRQ conflict are slim to none.
I love the comment about if you spend al your time fixing computers you're going to find BSOD's. Thats like saying if you deal with ill people all the time you're going to find a dead one.
Most USERS, note the word users and not techs or repairman, will never see a BSOD on XP nor on Vista because it only happens on an exceptionally few errors. Anything else just results in the machine rebooting with a little message explaining that an error has occured and the machine will now reboot. Windows 98 on the other hand would BSOD for every little thing.
Stupid bloody works proxy made my post get sent twice.
Nerd fight!
FWIW, I've had BSODs on XP. It can happen if a virus takes out a system file, or you have corrupt RAM, as well as all the various other reasons you've mentioned.
"I love the comment about if you spend al your time fixing computers you're going to find BSOD's. Thats like saying if you deal with ill people all the time you're going to find a dead one."
you're still defending your comment that the bsod is disabled. my comment was a demonstration that bsods happen to non-tech people. you know, you can work at a hospital and never find a dead person, that doesn't mean dead people are disabled at the hospital. continuing with this analogy, as medical equipment and techniques get better, less people die from various ills. on the other side of this equation now, it's nice xp (and presumably vista) handles memory read and write failures better and pnp has come a long way, but this doesn't mean that things still don't kill it... :P
So we agree that 98% of normal users will never see a BSOD and this guy who got the tat is a tit. A tat for a tit. Better than tit for tat.
Kids!
As 20+ yr engr using Win...I can state I only see these every blue moon (being once every 6 months perhaps)...and doing upnp, mediacenter, etc.
It still happens but is fairly infrequent even with heavy pounding.
All depends on the crap you have installed and how much it stresses your system...(i.e. your mileage may vary).
As far as being 'disable' though...hmmm...that's a new one.
Ok disabled was probably the wrong term. Replaced for all but the most serious/fatal errors.
98% of normal users will never see a BSOD? I think you highly underestimate just how ****ed up the average user's computer is. Not to mention that they also have no idea how to fix it, so the problems just pile up more and more...
Fatal? ive goten BSODs ages ago, i didnt know what it was for, or why it happend, so i just restarted and went along my happy little way. 4 years later, im fixing these things as a hobby, my parent's computers have had BSODs, but i wasnt there when it happend, so i didnt know what happend, but most of the BSODs ive had to deal with were rare, and a restart later, nothing was broken, computer acted fine. as far as non computer geeks getting them, anyone who has had one of those creative X-Fi cards know that they are prone to IRQ errors, ive seen many other people with them on creative's forums. the simple fix is just moving the card to a new PCI slot, and everything is fine. BSODs are not disabled, ive goten them on my old HP a735w computer 4 years ago running XP. knock the OS back to something like 95 or 98, then yeah, BSODs happen a lot more often, they have improved windows since then.
he has more muscle mass than any nerd of his caliber should.
ctrl+alt+tool
That's cause it's his jerking arm... his left is probably spaghetti thin.
how g33k!!!
AHAHA love it.
i already have BSOD in vista ...
Can't wait to see someone get the Mac OSX Kernel Panic tattooed.
Lol, they havn't found someone with long enough arms yet.
you mean the grey screen of panic and disarray?
would love to punch this guy on the face.. what a moron.
I would feel stupid later in life with a regular tattoo. I would probably shoot myself with that shit on my arm.
At that time Microsoft is a party which enslaves linux enthusiasts, gas them to death and use the gold in their teeths to build up a new empire. History comes and goes to be repeated over and over again.. humans never learn.
What I wanted to say with that is that; then, this tatoo will be his fall.
Oh.... my god....
I'm not convinced.
To be a real blue screen, the blue would have to be the background of the text and the text would have to remain white-ish.
I call for inversing of colour :)
Dude, it's not IRQ, it's IRQL, or Interrupt Request Level and it's caused by a driver attempting to either read/write data structures at an interrupt level that is too high or attempting to access paged data while at a IRQL that is too high. You have no control over it. The IRQ's you're referring to are hardware IRQs and do NOT cause this BSOD.
And thus the seeds of a new religion are sewn...
Steve Balmer is Lord Vader and Bill Gates the emperor who rules behind the scenes...
i found it alot easier to just switch to mac os.