here it is, the last video for 2022. '22 was a mediocre year for me at least. anyway, last kill screen for now. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ discord: langzorth reddit: / nervouscranberry5 bitview: www.bitview.ne...
Everything screams realism here. The excruciating wait times, visual glitches that don't look fake, a recovery process that looks genuine and isn't using creepypasta stereotypes, long and hopeful waits for automatic recovery to fix your computer, feeling defeated when the computer ends up breaking again... R.I.P. to the computer...
Wow, so realistic, everything, it just feels so real. Nothing creepy or anything, no jumpscares, just brilliant. You put some hard work into this, 10/10.
as someone who grew up with vista, i appreciate and love the sheer amount of detail and accuracy this has. from the startup to safe mode. if you ever chose to make another vista killscreen (i highly doubt it but i wanna throw this idea in), you could later make the ivons shifted around on the desktop, with a combination of color channels (like red, green, and blur) missing. this is an actual windiws vista glitch, caused by severe file corruption due to the hard drive going doopus kapoot. it happened to my grandmothers vista computer not long before it died.
you make the best kill screens in youtube, they're so realistic, brilliant and some kind of sad and scary, idk maybe just me. hope you're doing better by now, not every year is going to be a 2022
2 funny things I saw: 1. The 7B code BSOD: it can't appear when the system is on. The 0x0000007B decrypts as Inaccessible Boot Device, which means that there's a drive error on the boot, so it can appear on boot only. 2. Recovery mode and it's warnings. The recovery mode can be used only via the installation media, and only on WIM-like NT systems (Vista and higher), and to access it, on the "Install" button screen, you need to press the "Computer repair". And the restoration mode itself looks fully different, and can't overwrite the BIOS, 'cause it doesn't have the access to it.
I would object about second point. Well, in windows me and higher, Microsoft made "timepoints", that could open that recovery mode, also if you don't let windows to boot up for 3 times, it will initiate recovery mode. Also i would add 3 point: Windows can't freeze like that, and also - i think that bsod from other windows. Plus, that glitches don't belongs for system. And it runs windows on a virtual machine - VMware
@@Byt3pixe1 "Windows cannot freeze like that" It can, actually. This is called "computer lockup." A computer lockup happens whenever your PC lags so hard that everything just freezes to the point your mouse and/or keyboard would stop working (therefore you would have to hard reset it) This actually happened to me once, I kid you not. I remember when I was in my "Black MIDI" phase I tried to open a midi file with 10 million notes in PFA, and my computer froze up before it could actually open it.
" '22 was a mediocre year for me at least." it was also for me but, i dont really wanna explain about somethings making it "the worst year" i experienced.
Cool video dude, reminded my times when I tried to repair pc (win 7) in 2017-2018. (pc was broken and not recoverable, then I bought a new pc with win 10)
i remember in like 2015 (when windows 10 just launched), i had to recover my computer with certain network issues after upgrading because windows 10 screwed up my internet connection
It can be more realistic if you edit out those vmware startup screens, since it means the system is running in a VM and VMs shouldn't encounter any kind of hardware error (since they don't really have one)
I once almost got a kill screen on my Windows 10, though it did some automatic repairs so that’s good. It doesn’t really play out as a kill screen, it was just slow to start up.
i still remember when i had a PC that was a total pile of shit, and for a moment it froze up to the point of me fully restarting, and hell it led to it bsoding for just a few times before it could even get to the login screen
if you're talking about it being absolutely slow, the screen recorder actually caused it to run like shit. if anything, this was made on a PC that was just too slow to even handle a modern VM (i had from may 2018 to july 2023)
Probably could be the cause of the VM’s crashes and bluescreens. on my home laptop, which doesn’t have virtualization support because it was a laptop made for windows 7 which was when virtualization and UEFI wasn’t really a big thing, i just multiboot most operating systems, and it runs smoothly. It supports im sure XP or older but haven’t done xp because i only had usb drives for installation media back then and the installer did boot off of usb but just detected the usb drive itself as the hard disk, but i haven’t tried CDs as installation media yet because i recently got a bunch of 700 MB CD-RWs which i’m pretty sure the xp installer can fit on but idk, and i also cannot fit any more partitions on my MBR disk even though i have more than enough disk space, just the MBR restrictions. One of the downsides of having a legacy BIOS system, not being able to use GPT disks to cave virtually infinite partitions, but even if i did, pretty much only windows 8 and newer support GPT. I multiboot linux mint, windows 11 (had to bypass system requirements because not supported), windows 7, and windows vista(without networking because drivers are a pain and my networking randomly stopped working on vista despite working for a few days after installing it, anyways this comment is getting a bit too long so yeah
This is actually realistic to era of when not a lot of PC and laptops could handle Windows Vista (yes it was pretty far ahead of its time so that it could get pretty laggy and yes sometimes crashing their PC) Edit: I completely forgot about this one. IIRC that why Windows Vista got bad rep back when it was released (yes there was a friciking lawsuit with laptop that has Win Vista Basic-compatible sticker
Yep, Vista is actually a good OS if you have the hardware for it, which I did and it ran without any real issues, it also introduced many good things such as UAC (which was annoying at first but by the time 7 was out everyone is used to it, and generally increased security), and the design is still timeless.
The question is, where did you do this (Vegas, After Effects and so on), and also how? I really liked the idea with this, and I would like to try this myself. Of the problems I can only describe the "No Signal" screen when, in terms of recording, it is a virtual machine. Including "Recovery Mode" with a warning for strange reason. However, even with this, I want to praise the "realism" of the video. I apologize for my English, because i dont speak English.
This is the most realistic killscreen I've seen in my life. I tried making a Windows XP and a Windows 1.0 killscreens, combining both realism and horror, the results were not bad, but this... is the goat.
it's not really possible to do so - at the end of the video I simply took a screenshot of the vmware logo and tried to symbolize that the VM was completely dead. for the slowing performance, this was completely unintentional. my screen recorder kept affecting the performance of it (along with other programs in the background of my host PC) and this caused the VM to somehow slow down so much.
@@skexofiner.nsystemz 1._ I was joking with the "damaging hardware" thing. Obviously it's not possible! 2._ Wait- it was unintentional?! Interesting...
10:52 has a blue screen with a code of 0x0000007B, when something is wrong with the system not causing it to boot. This error code doesn’t appear when you are in windows, it appears during startup. Not saying this is bad at all.
This happened to me back in 2015. For some reason, my Windows Vista computer - which was 4 years old at the time - would crash everytime I tried to boot it up, and it would only work in Safe Mode. Maybe because I accidentally spilled water on top of it a while before that happened.
If you gave 100 MB of RAM to guest windows vista and on slower HDD that's how it freezes. I actually ran windows vista on pentium 4 with 512 MB ram. I done same with windows 7, Which is also slow, but not that slow. But your video is genuinely realistic and amazing.
Let me guess after the video: Him: brings pc to repair shop A few minutes later... He gets the pc "Boots up pc" Turns out it ran perfectly and he runs chkdsc "All goes perfect Good ending
I can confirm that black screen with Activate now/later is true. I had this one time and its not going to give you explorer.exe and any option to open it. Only hope is to restart and activate it.
i dont get it, just your average windows vista experience. the lag, crashes, it just looks like you recorded your experience with windows vista lol. lmao in all seriousness great job it actually looks like something that could happen
yeah thanks, this video was made on a PC that was so bad, it couldn't handle a modern VM because it ran on an old AMD cpu (specifically the athlon 2 x4 630)
it also happened to be a problem in vmware - where the cursor would just fly around a certain corner and the only way to fix it was by pressing ctrl+alt and then going inside the vm again
11:33 If you're screen recording vmware you (probably) wouldn't be getting "No Signal" popups, still well above average kill screen quality though 15:14 Okay this whole segment does not read like an official piece of software and i don't think it is, correct me if i'm wrong
i actually added the "no signal" on purpose to make it feel more like an actual cheap monitor 15:14 was kinda meant to look like that, one of these programs that may feel genuine and real but deep inside you might think it might not be
@@skexofiner.nsystemz Ye, i probably would've picked the no signal and edited the vmware out Still enjoyed the video, much better than pretty much every other kill screen. Just my nitpicks lol
If I was you, I would change VMware logo, to some dell dimension startup screen, or IBM thinkpad, for more realistic effect, I hope you take this into consideration and use my advice next time, I wish you good luck, but as it is, the video turned out very realistic.
If kill screen was real What will you do? A. Restart multiple times B. Turn off and wait until it gets fixed C. Turn on recovery mode D. Click restart then turn off What would you rather do? 👇
