I Tried low ram on Windows XP Too, but on virtualbox, and here are the results: 4MB - Windows NT can't start because of RAM. 8MB - An system file missing or corrupted. 16MB - Infinity reboot. 32MB - Extremely laggy and 2 messages appear while logging in. 64MB - Very laggy and explorer.exe won't start for some reason. 128MB - So laggy, but it works. 256MB - Works fine. 12:00 at 17/12/2017: at 8MB, an system file is missing or corrupted not the machine hasn't enough ram. i memorized that and fixed it. 8:58 at 30/12/2017: 33 likes? thanks! i can't wait for this to hit 40 or more likes at the beginning of 2018! :D 17:20 at 9/9/2018: why does this have so many likes
0:22 **Boots Windows XP with 4MB RAM** "Okey then, let's boot it up with more than 7MB of RAM." 0:45 **Boots Windows XP with 8MB RAM** "I guess it meant 4MB+7MB RAM." 1:18 **Boots Windows XP with 16MB RAM** "Windows XP is the biggest liar I've ever saw."
@Christian Kjær Meltesen and i think reddit has nothing to do in the comments... I mean its not wrong to think win xp is a liar.. i mean he probably know that is was a joke.
4 M bytes: Not enough extended memory to boot 8 M bytes: Windows kernel might be missing or corrupt 16 M bytes: System configuration missing or corrupt 32 or 64 M bytes: Fatal error while booting, not even Safe Mode starts 128 M bytes: Graphical glitches (but otherwise boots fine) Note: this is only valid on 64-bit XP. 32-bit may give you different results.
I remember it was common to ship 128mb ram on xp desktop machines. Some of the nicer machines had 256. I later added a 512 stick giving me a cool 768 megs of ram. That was an p4 Northwood core, running at 2.4ghz on socket 478. Lots of memories with that machine... 😊
God I remember those budget machines with 128mb ram back in the day were slowwww. So many made it to the trash after only a couple years and all they needed was a ram upgrade.
Might have gotten different results if 1. Used the x86 version and 2. Used the non-updated version with no service packs or programs preinstalled. I still have an XP x86 finnish disc laying around without service packs, and from what i remember on a 3 GB ram laptop it consumed 80 MB of ram on the desktop on a fresh install.
Back in the day i used to have a pentium 166mmx laptop with windows xp. It had 48 mb of ram. Was slow on startup and until it loads. After it finished loading was usable. I used office 2003 on it, and after program load, i was able to do work with no problems.
That first "Windows NT has not found enough extended memory" message seems like it's highly outdated, probably originates from the earliest Windows NT versions such as 3.1 or 4.0 since even in Windows XP a lot of the boot code is similar to those (uses NTLDR).
Why all of ur videos looks soo oldschool, like they were made 10 years before this date. And im not telling ya that it is bad, its actually very cool! Keep on going 0:10 Understandable, have a Russian day
The reason Windows XP did that was that the VMware Tools script failed to initiate. Meaning a normal laptop or PC with 16 MB of RAM would run normally.
When on 32mb of ram try it but in ide / compatibility mode that's why it blue screens on the booting process, sometimes the VM changes to AHDI Mode I think that's what it's called correct me if I'm wrong anyways hope this tip fixes the blue screen!
obviously when windows tries to boot up, it copies some files into RAM and because there is almost nothing to store in RAM, the system cannot put more files into RAM to boot it up. I dont really know, you can correct me I tried to understand that first time, but this crazy graphical issue though o_o
It looks weird to me that those glitches occur because I remember working on Windows XP with 128MB of ram installed in my PC (of course many years ago). Maybe it's caused by x64 edition though.
Funny, it looks like at the beginning it literally doesn't have enough memory to find a program, go deep down the folders long enough or something. The file is not corrupted, it's there, it just doesn't have enough RAM to do anything with it. It looks at it and goes like "damn my brain hurts"
I try myself Booting Windows with 4,8,16,32,64,128 This is my results: Windows XP Professional Service Pack 3 4MB = Windows needs 7MB or more to boot 8MB = BlueScreen 16MB = Extremely Laggy but explorer.exe couldn't boot for some reason. 32MB = Infinite Reboot 64MB = Works well, but with crazy display glitches 128MB = Works fine 256MB = Works fine too My host machine is: Windows 10 Pro 64bit 8GB RAM
You: Our windows xp has BAD display. Please? Your mom: That is not a display issue, that is the RAM. We need to replace it. You: oh. But still, PLEASE? Your mom: no. I go to buy new RAM. OK? You: Ok. YYYYYAAAAAAYYYY
I have a question that might seem random, but... When talking about your videos with my friends, I'm not sure whether to refer to you as a guy or a girl. Do you have a preference?
I have a laptop with 64MB RAM (later upgraded to 192MB) and it worked perfectly with XP but was just very slow with 64MB. You should've tried 32 bit XP instead
I had the same display glitches after turning at 64 MB. After using Explorer for 1 minute i had blue screen.... 128 MB worked not that bad that i thought
Well, i managed it to work on 16MB of ram on virtualbox by disabling additional drivers, and force deleting some pre-installed apps.(I used Windows XP Home Edition SP1 32-bit)
you copy someone else's comment. I wrote this reply: You: Our windows xp has BBBBBBAAAAAAAAAADDDDDDDD display. Please? Your mom: That is not a display issue, that is the RAM. We need to replace it. You: oh. But still, PLEASE? Your mom: no. I go to buy new RAM. OK? You: Ok. YYYYYAAAAAAYYYY
I Tried low ram on Windows XP Too, but on virtualbox, and here are the results:
4MB - Windows NT can't start because of RAM.
8MB - An system file missing or corrupted.
16MB - Infinity reboot.
32MB - Extremely laggy and 2 messages appear while logging in.
64MB - Very laggy and explorer.exe won't start for some reason.
128MB - So laggy, but it works.
256MB - Works fine.
12:00 at 17/12/2017: at 8MB, an system file is missing or corrupted not the machine hasn't enough ram. i memorized that and fixed it.
8:58 at 30/12/2017: 33 likes? thanks! i can't wait for this to hit 40 or more likes at the beginning of 2018! :D
17:20 at 9/9/2018: why does this have so many likes
got it starting on 28mb ram, but i used microxp
I Try Windows 98 Tho. :)
Wtf!? *Delete it* I got my own summary from the video! Just look!
Im the 41th like :p
I've got my own XP running on actual hardware- 64MB of RAM it started up and explorer started :D
Windows XP will turn on with 32 MB but it is x64 Edition.
+Super 155 CZ that's right
Windows XP x86 Is Slow on VMware 14 pro
počkej nejseš čech ? / hey are you czech in yor name is cz that mean czech republic
@@Anthonythetechguy2004 It worked with 128MB and 256MB too.
@@Anthonythetechguy2004 but 192 mb recommended for xp 32 bit
Haha! Interesting experiments
What?!?!?
So little likes and comments.
YOU HERE!
wow how are you verified
iiJamie 💯 000 subscribers
0:22 **Boots Windows XP with 4MB RAM** "Okey then, let's boot it up with more than 7MB of RAM."
0:45 **Boots Windows XP with 8MB RAM** "I guess it meant 4MB+7MB RAM."
1:18 **Boots Windows XP with 16MB RAM** "Windows XP is the biggest liar I've ever saw."
**Boots Windows XP with 32MB RAM** "Actually, I think 7MB was the amount required for this bootup manager"
@Christian Kjær Meltesen **Boots Windows XP with 64MB RAM** I changed the desktop background to "I don't care."
@Christian Kjær Meltesen i hate jokes
i also hate when xp lies
@Christian Kjær Meltesen and i think reddit has nothing to do in the comments... I mean its not wrong to think win xp is a liar.. i mean he probably know that is was a joke.
@Christian Kjær Meltesen he had "" so yeah idiot
4 M bytes: Not enough extended memory to boot
8 M bytes: Windows kernel might be missing or corrupt
16 M bytes: System configuration missing or corrupt
32 or 64 M bytes: Fatal error while booting, not even Safe Mode starts
128 M bytes: Graphical glitches (but otherwise boots fine)
Note: this is only valid on 64-bit XP. 32-bit may give you different results.
You’re having troubles because that’s the x64 edition, it was designed for higher end PCs.
:( i had Windows XP installed (by manufacturers) 32 bit version but on gaming pc. retarded manufacturers
3:20 When you actually get aero working in 2007
???
@@Clyde6790pRUclipsmost windows computers weren't fit for vista, which came out in 2007.
I remember it was common to ship 128mb ram on xp desktop machines. Some of the nicer machines had 256.
I later added a 512 stick giving me a cool 768 megs of ram.
That was an p4 Northwood core, running at 2.4ghz on socket 478.
Lots of memories with that machine... 😊
Those were fun days back when even a RAM upgrade would make a huge difference in performance.
I have a ThinkPad R40 2723-CTO. I upgraded the RAM from 256mb to 2gb. Much smoother.
gateway?
God I remember those budget machines with 128mb ram back in the day were slowwww. So many made it to the trash after only a couple years and all they needed was a ram upgrade.
@@9852323 yeah, today 8gb ram machines from like 5 years ago are now unusable
64-bit versions of windows require twice as much Ram compared to the 32-bit
True
True
I was just going to say that
64-bit requires 64mb minimum
32-bit requires 32mb minimum
Interesting, I never knew that!
3:32 the best thing i've ever seen!
>_> y is this mama fukin nuts in 3:32
Привет весёлая винда)) Неожиданно
i saw your virus
A E S T H E T I C
@@meithenoob5394 Это можно использовать даже для Memz
Might have gotten different results if
1. Used the x86 version and
2. Used the non-updated version with no service packs or programs preinstalled.
I still have an XP x86 finnish disc laying around without service packs, and from what i remember on a 3 GB ram laptop it consumed 80 MB of ram on the desktop on a fresh install.
Even if you install sp3 same amount of RAM is consumed but after installing drivers the consumption goes up.
Windows XP: I need at least 7mb of ram
Also windows XP: *crashes on 64mb*
it did not say xp, it said for nt, or i guess the boot loader
@@winksplorer windows xp is windows nt
@@Maciek2846 I get it, I am not stupid, what I meant by nt is the core ntoskernel.exe
fair windows 98 will fine on 14mb
3:11 when you compressed system32
Everyone: witch language do you speak?
Enderman: Russia soviet russia!
3:11 when computers take drugs
Bro smoked capsaicin or allyl isothiocyanate 😂😂😂
That's why, i have installed 4 gigs of RAM. 2 gigs each module. 😂
3:04 *O O P S W I N D O W S X P C R A S H E D*
Nice video bro!And where you download old windows for vm?
WinWorldpc.com
Enderman: *buys bleach to drop on its eyes*
Windows XP: STOP THIS IM SUFFERING
3:12 Windows XP Acid Edition
2:10 DING TOUCH JAMMED
Its THINK PROTOGENT
Windows XP
Glitched Edition
3:46 What happens if you pour Clorox on an XP installation disc.
Lmao xd
Get the thing washed with chlorine bleach lol
Or better: trichloroethane/trichloromethane 😂😂😂😂😂
Hey Enderman I Love Your Video Great Job
Enderman you are pro men :) nice videos nice music etc :D
Skol: Tayk iyt or leayv iyt
Students: Why did our school hire soviet peasent for computer science?
The "64 (Or 128) MB Bug" is because a Glitch with VMware drivers for Windows XP
And Windows XP needs much more ram for 64-bit edition (Obviusly)
LMAO THE SYNC IN 3:20
3:09 Bro moved his mouse, entire graphics driver got corrupted🤣
I believe the display glitches were caused because of VMware. This wouldn't happen on a physical computer (or VirtualBox maybe)
yeah exactly. I remember I had an XP machine with 128mb in 2005 and it worked fine, without any glitches
Bro looked up bleach 💀
#notificationsquad That Clorox bleach in 3:42 tho... epic.
3:12
Windows Glitch XP
This is a very good video! And RUclips recommends me your channel, so why not, I subscribe to your channel :3
3:18 yeah, I like vaporwave.
3:32 rip Windows XP
Enderman: gives low quantity of RAM
Windows xp: I realized that I want to die.
3:12 This will happen if your graphic card is toasted lol
Nice Vid Enderman! :3
2:03 *J O E L*
Enderman is cute!
Enderman:screams
WinXP required 64MB Ram. I normally used it on 64MB PC some time. It was laggy, but everything worked normally.
3:17
Recording software: This is fine.
Little Brother-Can I use you computer?
Me-Ok
A few moments later 3:20
the 'YOU NEED PROTOGENT' is so funny
2:10 DING TOUCH JAMMED (protegent meme)
Back in the day i used to have a pentium 166mmx laptop with windows xp. It had 48 mb of ram. Was slow on startup and until it loads. After it finished loading was usable. I used office 2003 on it, and after program load, i was able to do work with no problems.
that's because you're using 32 bit xp
That first "Windows NT has not found enough extended memory" message seems like it's highly outdated, probably originates from the earliest Windows NT versions such as 3.1 or 4.0 since even in Windows XP a lot of the boot code is similar to those (uses NTLDR).
Why all of ur videos looks soo oldschool, like they were made 10 years before this date.
And im not telling ya that it is bad, its actually very cool! Keep on going
0:10
Understandable, have a Russian day
Fun fact! If you do the command “cd con/con” it will BSOD
The reason Windows XP did that was that the VMware Tools script failed to initiate.
Meaning a normal laptop or PC with 16 MB of RAM would run normally.
Windows XP 32-bit can boot with 32 MB of RAM
Still faster than my Windows 10 laptop with 8GB RAM and a core i5 7th gen
The graphics corruption is not an issue with Windows XP, but instead it's VMWare.
3:47 Why is there a clorox bleach liquid bottle in the explorer?
3:00 and the windows XP VM got a Crazy display glithes.
Windows XP: Deep Fried Edition
me even keeps freezing while watching yt windows on 5gb ram : o_o
me on win xp : oh sh*t
0:52 WINDOWS COULDNT START CAUSE THE FILE IS MISSING OR CORRUPT?! Wait did you delete system32 again?
No, low RAM made the file missing or corrupt (lel)
@@ChloekabanOfficial that makes no sense
@@minix07 Okay, I'll tell the three-years-ago me to fix his grammar.
@@ChloekabanOfficial no I mean that because its low on memory it lost the file, which is pretty funny
@@minix07 Oh.
3:38 Windows : Enderman!! Help me
Enderman: Alright I'll clean you up * searches clorox and buy it to clean the windows* 😂😃
“Mom, where’s the bleach?”
“You drank it already”
“Oh, well now we need more..”
O P E R A W I N D O W S B L E A C H
Ender now try to remove the RAM Stick with the computer power on
PD: Sorry for my bad English
quimey fusaro
Done that before. It freezes the machine
How2KillUrPC.mp4
I did that and it frose the computer and made screeching noises from my hearphones...
earphones*
When on 32mb of ram try it but in ide / compatibility mode that's why it blue screens on the booting process, sometimes the VM changes to AHDI Mode I think that's what it's called correct me if I'm wrong anyways hope this tip fixes the blue screen!
obviously when windows tries to boot up, it copies some files into RAM and because there is almost nothing to store in RAM, the system cannot put more files into RAM to boot it up. I dont really know, you can correct me I tried to understand that first time, but this crazy graphical issue though o_o
It looks weird to me that those glitches occur because I remember working on Windows XP with 128MB of ram installed in my PC (of course many years ago). Maybe it's caused by x64 edition though.
Funny, it looks like at the beginning it literally doesn't have enough memory to find a program, go deep down the folders long enough or something. The file is not corrupted, it's there, it just doesn't have enough RAM to do anything with it.
It looks at it and goes like "damn my brain hurts"
I try myself Booting Windows with 4,8,16,32,64,128
This is my results:
Windows XP Professional Service Pack 3
4MB = Windows needs 7MB or more to boot
8MB = BlueScreen
16MB = Extremely Laggy but explorer.exe couldn't boot for some reason.
32MB = Infinite Reboot
64MB = Works well, but with crazy display glitches
128MB = Works fine
256MB = Works fine too
My host machine is: Windows 10 Pro 64bit 8GB RAM
3:20
Kind of drugs has windows XP been taking
Windows XP low RAM:
4-64 MB: Doesn't work.
128 MB: *D E E P F R I E D W I N D O W S*
2:03 protegent moment
The fact that he typed up clorox buy online💀💀💀💀💀💀💀
when i drink the magic juice in thee lava lamp: 3:10
Me: mom can we have windows xp at home
Mom: No, we already have windows xp at home
Windows XP at home: 3:20
You: Our windows xp has BAD display. Please?
Your mom: That is not a display issue, that is the RAM. We need to replace it.
You: oh. But still, PLEASE?
Your mom: no. I go to buy new RAM. OK?
You: Ok. YYYYYAAAAAAYYYY
@@andreisurubaru6389 ...ok
The last part I was just kidding, sorry =)
Imagine using a 64-bit Windows XP for the tests.
Ultimate Bruh moment.
me: *looks at the 64MB screen* hmmm yes i dont speak memory leak
The nostalgia of that intro.
damn that's crazy
you should try 8 gigs next i heard it's insane with windows 10
I have a question that might seem random, but... When talking about your videos with my friends, I'm not sure whether to refer to you as a guy or a girl. Do you have a preference?
the PC be like: tell me how to work with no RAM, I cant do anything with no RAM
yes clorox i wanna buy that
Türklerden uzak takıldığımı sanıyordum yanılmışım .WQ.W.E.W.EQ.
Sarp Ersoy bende varım unutma!
@@SarpErsoy Bende varım :P
Selam :)
3:10 i had something like that when i dropped my pc, ejecting the ram
you have found the secret windows vaopware mode :o that is so cool
When you're poor so instead of making a 10TB RAM you make a 4MB RAM.
I have a laptop with 64MB RAM (later upgraded to 192MB) and it worked perfectly with XP but was just very slow with 64MB. You should've tried 32 bit XP instead
Idk but these colors remember me a really old PC that the monitor was bugging colors
you mean your pc didn't have a graphics card?
Windows XP & Opera 12.10. Those were times...
win xp but drinked clorox
THINK
P R O T E G E N T
XP do be looking very Vaporwave though
I had the same display glitches after turning at 64 MB. After using Explorer for 1 minute i had blue screen.... 128 MB worked not that bad that i thought
3:09 me when my computer got virused
*randomly found this legendary video
Back when legends carry 512 mb of ram who remember?
3:32 windows XP but only 128 megabytes of ram
Well, i managed it to work on 16MB of ram on virtualbox by disabling additional drivers, and force deleting some pre-installed apps.(I used Windows XP Home Edition SP1 32-bit)
oskarplayer27 try the RTM version you might be able to run it on 12MB RAM. If you want to try it I have an ISO
you got a new sub!
4:38 My GD Dominator effect
Mr Rads Variety Channel nine circles
@@voidyt9939 I cant remember why I put Dominator effect. Lol. But yeah, nine circles effect
Mr Rads Variety Channel ah ok
Also, what’s ur gd username I’d like a collab
@@voidyt9939 MrRadYT
Visual bugs like these happened for me in DosBox at Windows 3.1, when i tried to use a high resolution display
Mom can we have windows xp?
no we have windows xp at home.
windows xp at home 3:11
you copy someone else's comment. I wrote this reply:
You: Our windows xp has BBBBBBAAAAAAAAAADDDDDDDD display. Please?
Your mom: That is not a display issue, that is the RAM. We need to replace it.
You: oh. But still, PLEASE?
Your mom: no. I go to buy new RAM. OK?
You: Ok. YYYYYAAAAAAYYYY
I have a pc with XP and 128 Mb of ram and it's working perfectly.
me when i drink the white stuff in daddys cabinet :
3:23