When your OS goes crazy - Screenshots

[Kaius]

Here's one:

This happened when I accidentally tried to boot a full GRUB .iso image as a kernel in Qemu. Took me longer than I'd care to admit to figure out what was causing it

[NotYourFox]

I have a problem with old (24 y.o.) hardware. When I try to scroll in VESA (using fast memcpy), it starts the simulation of a broken display (color flooding and occasional strips). Just on this one, and only with my OS.
Can't really take a screenshot of it though, unfortunately

[EmanueleDavalli]

Some years ago, when I tried to write a native driver for the Intel integrated GPU of my old PC.
I was accidentally writing in text mode (0xb8000) after modesetting (or viceversa writing in the framebuffer while still in text mode, my memory of this particular bug is fuzzy)

[techdude17]

Left on the stove for too long...

[Ketsch]

My OS dying in pretty boring way :/

[EmanueleDavalli]

Ported libjpeg-turbo but used it wrong

[adev5311]

Craziest bug in my OS has been removed, but...
When paging error occurred in the OS, qemu actually crashes.

[AnotherIdiot]

POV:
https://imgur.com/a/jq7EDcJ

[eekee]

this is what happens when you turn a riva 128 off mid-frame by disabling the entire gpu. not my os but someone writing direct access code. the os was still active and they were able to acpi power down.

[max]

I'm working on the desktop being an own application and if it dies it looks funny. I know the partial screen refreshing is working though

[rdos]

This is how errors are shown in my current FPGA development:



An PCIe connected FPGA can really break anything in an OS, and in BIOS too. In the current scenario, a bug creates errors in a physical memory structure, which crashes the driver & application. I''ve also had crashes caused by writing to physical address zero, which makes the PC fail to boot.