Weirdest BSOD you've ever gotten

[poochyena]

I got this today. I think I fixed the issue (dusty motherboard/usb ports I guess), but its the weirdest blue screen I ever got.

[ARikozuM]

Not a BSOD, but my server monitor would go out whenever I would scream. Loud or heavy footsteps? Perfectly fine! Loud jet-engine server fans? Perfectly fine! A manly (not really) scream? Too spooky for that monitor!

[8uhbbhu8]

14 minutes ago, ARikozuM said:

Not a BSOD, but my server monitor would go out whenever I would scream. Loud or heavy footsteps? Perfectly fine! Loud jet-engine server fans? Perfectly fine! A manly (not really) scream? Too spooky for that monitor!

And HOW did you find that out in the first place? 

[ARikozuM]

3 minutes ago, 8uhbbhu8 said:

And HOW did you find that out in the first place? 

My dog barked and the monitor flickered. Barked again; flicked. I screamed; it flickered. 

 

Me: Amazed.

Monitor: Dead.

Dog: [in a German accent] "Squirrel bastard! Get off my lawn!"

[8uhbbhu8]

2 minutes ago, ARikozuM said:

My dog barked and the monitor flickered. Barked again; flicked. I screamed; it flickered. 

 

Me: Amazed.

Monitor: Dead.

Dog: [in a German accent] "Squirrel bastard! Get off my lawn!"

Ok. That's hilarious.

 

 

35 minutes ago, poochyena said:

I got this today. I think I fixed the issue (dusty motherboard/usb ports I guess), but its the weirdest blue screen I ever got.

 

That is one weird bsod

[poochyena]

1 minute ago, 8uhbbhu8 said:

That is one weird bsod

How it blue screened is actually the weirdest thing really. At first it was when I plugged in or unplugged a usb device, but then I just simply touched the usb port, and it caused it to crash. I think this screen was the 3rd or 4th time i crash. The other crashes were normal.

[Sylvie]

49 minutes ago, poochyena said:

I got this today. I think I fixed the issue (dusty motherboard/usb ports I guess), but its the weirdest blue screen I ever got.

Pfft what the heck

The weirdest one I've ever had was when my ram wasn't working and I just got random characters in place of the expected ones

[ARikozuM]

The QR code corrupted and leads to Fortnite. 

[Sylvie]

Just now, ARikozuM said:

The QR code corrupted and leads to Fortnite. 

It's official, you need to replace your components. 

[straight_stewie]

1 hour ago, poochyena said:

I got this today. I think I fixed the issue (dusty motherboard/usb ports I guess), but its the weirdest blue screen I ever got.

IRQL_NOT_LESS_OR_EQUAL is actually pretty common. Although I've never heard of dust causing a system level application to request an interrupt handler out of it's permission ring... Normally it's caused by bad/corrupt drivers or ram problems.

I got a FLOPPY_INTERNAL_ERROR once. FLOPPY_INTERNAL_ERROR is a weird one, and the only information available on it from Microsoft is in the developers section and it just says "This bug check occurs very infrequently" (gee, I would hope so).

 

[drinklime]

10 - 20 German cockroaches crawled out of a used laptop we gave to a new employee

[rcorkum]

for me it was an 'oops' message on a linux box never ran into one before. so fired up laptop did some googling and voila learned what an 'oops' was and laughed at bsod from them on as an 'oops' is nothing to laugh at.

'

[Guest]

BSOD? What are you talking about? I don't format my Windows since 3943 bC and never had one.
 

Spoiler

I was listening to music while suddenly the system froze and just run into an infinite music-loop which was very scary, not even a BSOD because it just froze but when I rebooted the BSOD message just appeared, so I guess it was something similar

 

4 hours ago, rcorkum said:

for me it was an 'oops' message on a linux box never ran into one before. so fired up laptop did some googling and voila learned what an 'oops' was and laughed at bsod from them on as an 'oops' is nothing to laugh at.

'

the BSOD equivalent is not an oops btw, it's called kernel panic

[poochyena]

10 hours ago, straight_stewie said:

IRQL_NOT_LESS_OR_EQUAL is actually pretty common. Although I've never heard of dust causing a system level application to request an interrupt handler out of it's permission ring... Normally it's caused by bad/corrupt drivers or ram problems.

I think it gave a different code each time, and when it restarted, a message came up saying there was a usb malfunction. I reinstalled usb drivers and applied some other fixes, but still had the crashes, so I cleaned out the dust and now its working fine, no crashes. ¯\_(ツ)_/¯

This was the back usb ports. I had similar problems with the front ports in the past, an cleaning them out fixed them too.

[wasab]

No bsod on Linux. 

[imreloadin]

15 minutes ago, wasab said:

No bsod on Linux. 

Well since BSOD is a Windows thing I'd be really worried if you have one on a Linux distro

Linux graces users with the much less cryptic phrase "Kernel Panic"

[Ithanul]

12 minutes ago, imreloadin said:

Well since BSOD is a Windows thing I'd be really worried if you have one on a Linux distro

Linux graces users with the much less cryptic phrase "Kernel Panic"

Or, at least when I'm at work dealing with our distro, either hanging up on PCI errors or just a solid black screen.  On some occasions, even a black screen with the cursor shaped as a X.   

So, now I have a silly habit of referring to those as Black Screen of Deaths.

[TH3R34P3R]

worst i got was where i got a windowed BSOD... i officially gave up with everything and returned the HP desktop i had just bought back to best buy. I was just done. 

 

ended up finding out it was my monitor... not the pc. the monitor didn't accept fullscreen anything. 

[imreloadin]

29 minutes ago, Ithanul said:

Or, at least when I'm at work dealing with our distro, either hanging up on PCI errors or just a solid black screen.  On some occasions, even a black screen with the cursor shaped as a X.   

So, now I have a silly habit of referring to those as Black Screen of Deaths.

Ouch I just hate it when those certain people who use Linux try to act superior go "wE dOn'T gEt BlUe ScReEnS oF dEaTh" which is completely true, because it's not a Windows device...not because it doesn't crash...a crash is a crash in my opinion, doesn't matter what you call it lol.

[Ithanul]

1 hour ago, imreloadin said:

Ouch I just hate it when those certain people who use Linux try to act superior go "wE dOn'T gEt BlUe ScReEnS oF dEaTh" which is completely true, because it's not a Windows device...not because it doesn't crash...a crash is a crash in my opinion, doesn't matter what you call it lol.

Indeed.  I seen Cisco routers and switches hang (or the o so fun of dropping configs), netApps do crazy stuff (controller lossing owner ship of drives and not wanting to retake owner ship of said drives), a SUSE distro going corrupt (...was the darn VMWare controller too....), and a few other odd stuff on a variety of setups.    I consider it a good day when it is a boring day. 

[Murasaki]

11 hours ago, campy said:

Not really a bsod but definitely the weirdest windows error I've ever gotten

my turn

[aezakmi]

I used to get a BSOD whenever I tried to use google chrome

 

and here's the weirdest, it happened on three different builds, don't want to try with this one 

[another random person]

My computer ran out of ram, froze and restarted, thanks adobe. 

 

(for reference I have 16gb of ram)

[Murasaki]

4 hours ago, another random person said:

My computer ran out of ram, froze and restarted, thanks adobe. 

 

(for reference I have 16gb of ram)

[screams in keyboard shortcuts] 

[poochyena]

2 hours ago, Mayushii said:

[screams in keyboard shortcuts] 

That actually reminds me, on my parent's computer, if you press the email shortcut key on the keyboard, it would crash the computer. I ended up just taking the key cap off so I wouldn't accidentally hit it again.