Funny Windows 7 beta bug

I still can't believe people are commenting on this video!

Way back in 2009, I found a bug in the Windows 7 beta (build 7000) that gives you a BSoD and was easily reproducible. Back in the Windows Vista days, the Win7 beta was so popular that people used it as their primary OS, despite the fact that it was very buggy. (People really hated Vista that much!) Here's one such example of a major bug, and below is how I did it:

1. Right-click the desktop
2. Select Personalize, then Window Color, then Advanced appearance settings...
3. Select Active Title Bar from the Item drop-down
4. Hold the up arrow under Size for a few seconds
5. ???
6. Profit

Specs I had in 2009:
Core 2 Duo E8400 @ 3.80GHz
2x2GB A-Data DDR2 1000
512MB Sapphire HD 4850
Gigabyte GA-X48-DS4
750GB Samsung Spinpoint F1
ASUS Xonar DX

Some of you were asking the name of the song in the video -- It's from George Bizet's opera, "Carmen". That piece is called "Habanera".

[richardbirch]

I'm not trying to annoy anyone or piss them off but this is exactly what beta builds are for; to track down bugs like this. Every bit of software goes through this process.

[fovfloor]

I love windows seven beta builds they were cool to try them out.

[Psythik]

This happens when scrolling through fonts as well, so it's more than just a small bug that "nobody" will come across.

[chihofung]

Thanks Youtube for recommending this to me after 15 years and I tried them in my own (VM).
In addition of build 7000, this bug also presents in builds 6956 and 7022. Just input any size greater than 72 will trigger this BSOD.
And yes, Windows 7 was truly the best operating system ever.

[fishyer]

I LOVED THIS BUG WHEN I HAD WINDOWS 7 LOL

[ShadowwwLFS]

But seriously, M$ did very good job this time. For me, RC of Seven is much more stable than Vista64 + SP1

[CarlosVirgilioAltOficial]

Windows 7 Beta Build 7000 launched December 13, 2008 expired July 1, 2009.

[hakemon]

@Psythik I never said I worked FOR Microsoft, I said I worked with Microsoft. Yes, the blue screen comes from the kernel executable, but it's in a 80x50 text mode. If this is real, snap a pic of the monitors info screen when it comes up.

Even wikipedia has it right this time: In Windows NT-based operating systems, the Stop error, (which is displayed in 80-column 50-line text mode) occurs when the kernel, or a driver running in kernel mode, encounters any error from which it cannot recover.

[medman]

Nice presentation. Hopefully the people at windows saw this demo.

[carlos_did_a_thing]

Why did this get recommended to me 14 years later?

[Psythik]

@dommyreg24
I did a long time ago. If you'll notice, I posted this video WAY back in January 2009, right when the beta came out.

[jwd]

Fixed in the RC1 - that's good...

[Psythik]

Then my work here is done. I'm glad that MS listens to feedback.

[hakemon]

@TNFlightNurse Thank you, that's what I'm saying, it's text mode, it's not going to have a mouse cursor, especially if the kernel crashed, it can't read the mouse interrupts anyway.

[Psythik]

@mushroomhead104 The retail version of Windows 7, a.k.a. the one you buy from the store (and comes with all new computers). The Beta expired a long time ago, so I'm surprised you are even able to run it.

[Psythik]

@Kevincat2 Nope, not virtualbox at all. I simply installed it like a normal OS (in fact, I used it as my primary OS since it was better than Vista). For some reason the cursor stayed behind when you got a BSoD in the Beta. Simple as that.

[Psythik]

@ jackhillevans:
Other than this bug I find it very stable, so much that I've made it my primary OS. I haven't tried Windows Live Messenger yet though...

[Psythik]

@DanielChristy19 It was a BETA. Beta means that it's possible for things to not work the way they're supposed to. Try for yourself if you don't believe me. And if you can come up with any ways for me to prove to you that this is real, by all means inform me. I have no problems with making a follow-up video.

[MrFeelGoodJsonYTP]

@Intellmac This is a Windows 7 Beta not RTM or RC edition and on RC version was the bug fixed!

[enixsmith]

Note that this bug doesn't work starting from the RC (Release Candidate) or build 7100. Neither this release and the RTM have it.