Computer Crash Simulator
Simulate classic OS crash screens for fun or display testing. Runs entirely in browser, click anywhere to exit.
Select System Type
Click anywhere on screen to exit simulation
What is a Computer Crash Simulator?
Computer Crash Simulator is a fun tool that simulates classic crash screens from various operating systems. It supports Windows Blue Screen of Death (BSOD), macOS Kernel Panic, Linux Kernel Crash, and Android Application Not Responding (ANR) dialogs.
The tool runs entirely in your browser and has zero impact on your actual system. Click anywhere to safely exit the simulation. Perfect for pranking friends or testing display screen effects.
A crash simulator is meant for testing and learning: it can show how applications, error pages, monitoring, recovery flows, or browser behavior respond to an intentionally triggered failure. These tests should be run only in controlled environments, not during important work or on shared production machines. Unsaved data should be closed first, because the purpose is to make unstable behavior visible rather than to provide a normal productivity tool.How to Use
How to use
- Select the operating system type to simulate (Windows, macOS, Linux, or Android)
- Set the simulation duration (3s, 5s, 10s, or 15s)
- Click the "Start Crash Simulation" button to begin
- Full-screen crash screen appears, click anywhere to exit
Safe Use
- The crash screen is only a browser simulation; clicking or pressing the exit shortcut returns to the page.
- Avoid using it where it may interrupt work, cause panic, or be mistaken for a real system failure.
Use Cases
Technical Principle
The simulator is a pure DOM and CSS overlay - no system call, kernel driver, or device IOCTL is invoked. When the user clicks the start button, the page calls element.requestFullscreen() from the Fullscreen API (W3C Fullscreen LS); browsers require this method to originate from a trusted user gesture (UIEvent.isTrusted === true), which is why a page cannot autoplay a fake crash on load. The overlay then swaps a CSS class to render the chosen OS skin: Windows 10/11 BSOD with sad-face glyph and stop-code text (e.g. IRQL_NOT_LESS_OR_EQUAL 0x0000000A, KERNEL_SECURITY_CHECK_FAILURE 0x00000139), macOS Kernel Panic with the five-language "You need to restart your computer" banner introduced in OS X 10.2, Linux Oops/Panic with a fake call trace including symbols like inode_permission+0x1e/0x60, and Android ANR with the Application Not Responding dialog and a 5-second input dispatch timeout reference. Layout is driven by CSS Grid and flexbox at viewport units (100vw x 100vh) with z-index high enough to sit above any sticky header. The QR code on the Windows screen is rendered as an inline SVG, and the simulated text is a static template - the real BSOD also includes a process name (e.g. ntoskrnl.exe) and a memory address, both of which are fabricated here. The five-language macOS panic text matches the actual order shipped by Apple (English, Japanese, Chinese Simplified, Chinese Traditional, French). Exit is handled by listening for click, keydown (Escape), and the fullscreenchange event, then removing the overlay and calling document.exitFullscreen() to release the lock. Because everything is just markup, the host OS uptime, scheduler, and processes are untouched: pressing Cmd+Tab / Alt+Tab on most desktops still works, screen readers continue to announce focus changes, and remote-meeting screen capture will see the overlay rather than a real graphics-driver failure. The simulator therefore cannot be used to test real crash recovery, kernel dump collection, or Windows minidump generation - those require actual kernel-mode events such as a BugCheckEx call from a faulting driver. Treat the page strictly as visual content and obtain consent before pranking, since a sudden fullscreen takeover plus audio cue can be genuinely alarming on a shared workstation.
- Fullscreen API requestFullscreen() must be called inside a user-gesture handler (UIEvent.isTrusted check).
- Windows BSOD stop codes shown are static templates (e.g. 0x0000000A IRQL_NOT_LESS_OR_EQUAL); no BugCheckEx is invoked.
- macOS panic banner reproduces the five-language order shipped since OS X 10.2 (EN, JA, ZH-Hans, ZH-Hant, FR).
- Exit listeners: click, keydown (Escape), fullscreenchange; cleanup calls document.exitFullscreen().
- Optional beep is generated through a short AudioContext OscillatorNode burst, gated by autoplay policy.
- The overlay sits at z-index high and occupies 100vw x 100vh; host OS process table is unchanged.
- Cannot trigger real kernel dumps, minidump collection, or driver verifier - those need actual kernel-mode events.
Examples
Windows 10/11 BSOD - IRQL_NOT_LESS_OR_EQUAL
:( Your PC ran into a problem and needs to restart.
We're collecting some error info, and then we'll restart for you.
100% complete
Stop code: IRQL_NOT_LESS_OR_EQUAL
What failed: ntoskrnl.exe
QR code -> https://www.windows.com/stopcodemacOS Kernel Panic
panic(cpu 2 caller 0xffffff8002a3b1e2): Kernel trap at 0xffffff7f8b9a4c00,
type 14=page fault, registers:
CR0: 0x0000000080010033 CR2: 0x0000000000000010
CR3: 0x000000010d9e0000 CR4: 0x00000000003626e0
You need to restart your computer. Hold down the Power button
for several seconds or press the Restart button.Linux Kernel Oops / Panic
[ 1234.567890] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
[ 1234.567893] IP: [<ffffffff812a3b1e>] inode_permission+0x1e/0x60
[ 1234.567899] PGD 0
[ 1234.567902] Oops: 0000 [#1] SMP
[ 1234.567910] Kernel panic - not syncing: Fatal exception
[ 1234.567915] ---[ end Kernel panic - not syncing: Fatal exceptionAndroid ANR dialog
Application Not Responding
App: com.example.demo
Process: com.example.demo (PID 12345)
Reason: Input dispatching timed out (10005ms)
[ Close app ] [ Wait ]FAQ
Will this actually crash my computer?
No. It only displays a fake crash screen in the browser. Nothing on your operating system is changed and no data is lost. Click anywhere or press Esc to exit the screen.
Which crash screens are simulated?
Common ones include the Windows Blue Screen of Death (BSOD), macOS Kernel Panic, Linux kernel panic / oops trace, and Android 'Application Not Responding' (ANR). The look matches each platform's real screen for visual authenticity.
Why would I want a fake crash screen?
Common uses are pranking a friend, populating a screenshot for a tutorial about troubleshooting, stress-testing a display or projector, filling a screen during a livestream skit, or producing visuals for a 'tech humor' video. Coworkers seeing it on a left-unlocked laptop is the most common scenario.
How do I exit the crash screen?
Click anywhere on the page or press Esc. On a touch device, tap the screen. The simulator never blocks the OS, so you can always switch tabs or close the browser to leave.
Does it work in fullscreen?
Yes. Click the fullscreen button (or press F11 in most browsers) for the most convincing effect. Some browsers ask for explicit permission before entering fullscreen; allow it once and the page fills the display.
Will the BSOD show a realistic stop code?
The simulator shows representative stop codes (e.g. KERNEL_SECURITY_CHECK_FAILURE, IRQL_NOT_LESS_OR_EQUAL) and address-style hex values for visual fidelity. They are static placeholders, not derived from your actual system, so do not paste them into a real troubleshooting search.
Is it safe to leave on a public computer as a prank?
It is safe in the sense that it cannot break anything. Be careful about pranks in workplaces and schools - someone seeing the screen may file a real IT ticket, restart the machine and lose unsaved work, or escalate to security. Use it only on your own machine or with the owner's permission.