Fake OS screens

“This is a harmless prank tool for entertainment purposes only. It simulates a fake error screen to play jokes on friends — no actual system damage occurs.”

🔄 Update Screens

💀 Error Screens

Please wait while Windows updates your system files…
0% complete
Do not turn off or unplug your computer.
This may take several minutes.
Configuring Windows updates — Stage 1 of 3
0% complete
Do not turn off your computer. This will take a while.
Your computer will restart several times.
Working on updates
0% complete
Don’t turn off your PC
This will take a while.
Your PC will restart several times.
Your update is in progress
we’ll take it from here
Please keep your PC plugged in and connected to the internet.
Installing system updates…
0%
Preparing packages…
Do not unplug your computer during the update.
ChromeOS
Updating…
Windows
A problem has been detected and Windows has been shut down to prevent damage to your computer.

IRQL_NOT_LESS_OR_EQUAL

If this is the first time you’ve seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing.
Technical information:
*** STOP: 0x0000000A (0x00000034, 0x00000002, 0x00000000, 0x804E5186)

Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further assistance.
🙁
Your PC ran into a problem and needs to restart.
We’re just collecting some error info, and then we’ll restart for you.
If you’d like to know more, you can search online later for this error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
*** STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF88007B65C68, 0xFFFFF88003B7D748)
*** athrx.sys – Address 0xFFFFF88007B65C68 base at 0xFFFFF88007AE0000
🙁
Your PC ran into a problem and needs to restart.
We’re just collecting some error info, and then we’ll restart for you.
For more information about this issue and possible fixes, visit
https://www.windows.com/stopcode
0% complete
Stop code: CRITICAL_PROCESS_DIED
What failed: ntoskrnl.exe
🙁
Your device ran into a problem and needs to restart.
We’re collecting some error info, and then we’ll restart for you.
Visit https://www.windows.com/stopcode for more info.
0% complete
Stop code: KERNEL_SECURITY_CHECK_FAILURE
What failed: win32kbase.sys
⚙️
Your computer restarted because of a problem.
Press a key or wait a few seconds to continue startup.
Votre ordinateur a redémarré suite à un problème.Der Computer wurde aufgrund eines Problems neu gestartet.Il computer è stato riavviato a causa di un problema.El ordenador se reinició debido a un problema.
Panic(cpu 0 caller 0xffffff8000316c2a): “zalloc: zone map exhausted”
Backtrace: 0xffffff80004c3e80 0xffffff8000237cab
[ 0.000000] Kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 0.000012] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-51-generic
[ 0.000013] Hardware name: QEMU Standard PC (i440FX), BIOS 1.16.3
[ 0.000014] Call Trace:
[ 0.000015]  <TASK>
[ 0.000016]  panic+0x147/0x16c
[ 0.000017]  mount_root_generic+0x1f3/0x210
[ 0.000018]  prepare_namespace+0x14a/0x180
[ 0.000019]  kernel_init_freeable+0x22d/0x240
[ 0.000020]  kernel_init+0x16/0x130
[ 0.000021]  ret_from_fork+0x34/0x50
[ 0.000022]  </TASK>
[ 0.000023] —[ end Kernel panic – not syncing: VFS: Unable to mount root fs ]—

[ 0.000030] Kernel panic occurred. System halted.
😢
Chrome OS is missing or damaged.
Please insert a USB stick or SD card for recovery.
To get a recovery image, visit
google.com/chromeos/recovery
CHROMEOS_RECOVERY_ERROR
Error code: 0x04 — Invalid partition table
Device: SAMSUNG MZNLN256HAJQ-000
Firmware: Google_Kindred.12768.66.0
Scroll to Top