bluescreenofdeath
Latest
Windows metadata bug has been waiting to cripple older machines (updated)
If you're still using Windows 7 or Windows 8, there's another security issue you need to be aware of aside from Wannacry. This one won't hold your computer ransom for bitcoin, though. Actually, it might be more annoying than it is dangerous. Researchers from Aladdin RD, an information security company, recently discovered (translated) that a bad image call embedded into a website can bring older computers to a grinding halt. In this case, it's filename "$mft."
The blue screen of death is going green for Windows testers
If there's one color guaranteed to strike fear into the hearts of Windows users, it's blue. But as one Twitter sleuth has discovered, the iconic and always alarming "blue screen of death" is going green, and not because Microsoft is feeling festive. The new crash screen was spotted in a recently leaked preview version of Windows 10 (build 14997, to be exact), which isn't expected to be formally released until early next year. Microsoft's Matthijs Hoekstra has confirmed the color change is specific to test builds released through the Windows Insider program, which makes sense. Where bugs and crashes are reported, Microsoft will immediately be able to distinguish between problems with consumer Windows 10 builds, and those found on early, less stable preview builds.
Lexus software update gives new meaning to 'car crash'
Last year, headlines made everyone fearful of hackers taking over cars on the freeway. Turns out the real menace to owners of connected cars are the loopy manufacturers themselves. Toyota had to suck it up this week and admit to Lexus owners, who were going nuts on Facebook and Twitter on Tuesday, about why the climate control, radio, GPS, USB, Bluetooth, and other features suddenly stopped working for a range of 2014-2016 Lexus models. Or, their dashboard console would reset itself repeatedly.
Steve Ballmer wrote Windows' first Ctrl-Alt-Delete message (updated)
Whether Microsoft likes it or not, Windows' blue screen messages are iconic -- they're universal signs that something really bad has happened to your software. But who wrote the original Ctrl-Alt-Delete message that would grace the screens of sick PCs worldwide? None other than Steve Ballmer, according to company veteran Raymond Chen. The executive (then in charge of the Systems Division) reportedly didn't like the text that engineers first wrote, and took up a challenge to write better material himself. As it turns out, Ballmer did a good enough job that his version made it into the shipping product "pretty much word for word." The message has long since changed and isn't nearly as much of an issue on modern computers, but it's fun to think that the owner of the LA Clippers is also responsible for an app crash alert seen by millions of people. Update: Chen has since updated his story to emphasize that this is the Ctrl-Alt-Delete screen, not the infamous BSOD; the two just look pretty similar. We've tweaked our story accordingly.
Windows 8 BSoD ditches confusing error codes for uninformative frowny face
As with any version of Windows, the Metro-slathered Win 8 has one of those oh so familiar Blue Screen of Death thingies. But, this time around, there's a change. Gone are the confusing and uninformative error codes, and in its place you get an equally uninformative sad emoticon. OK, there's also some text informing you that your PC is about to reboot, but it still doesn't get you any closer to tracking down the root of the problem. Well, at least it's little less cutesy than the Sad Mac (though, no less infuriating).
StarCraft II easter eggs include iPistol, BSOD, and misplaced characters (video)
You'd think with all the pressure of making a StarCraft sequel worthy of the name, Blizzard wouldn't have time for humorous insider references, but StarCraft II begs to differ. The game's designers have expended some of their creative juices on concocting a jolly little iPod-esque advert for a fictional iPistol, which is supposed to let you "take your shot at life." And just in case anyone thought them biased, the Blizzard devs have also had a little swipe at Microsoft, with a Blue Screen of Death adorning the control console of a drill inside the game. Other than those techie witticisms, the eagle-eyed gamer will be able to spot a dancing Night Elf and a Tauren Space Marine from World of Warcraft, as well as Diablo from, well, Diablo -- but we'll let you play the game and figure out where they are for yourself! Skip past the break to see the iAd homage and BSOD screenshot. [Thanks, Michael]
Blue Screen of Death amongst issues that plagued Deepwater Horizon
A recent report in the New York Times details a myriad issues that led up to the eventual explosion that started the mess known as the "BP oil spill," but aside from obvious mishandling of warnings and red flags, one particular issue was troubling those working on the Deepwater Horizon oil rig long before April 20th. Mike Williams, the rig's chief electronics technician, has come forward with a multitude of icky details surrounding the negligence that was involved in the catastrophe, with the one most germane to our discussion being the following: "For months, the computer system had been locking up, producing what the crew called the Blue Screen of Death." Williams continued, noting that "it would just turn blue," with "no data coming through." Of course, it's not as if BSODs are totally uncommon out in the working world -- Microsoft's Windows powers the vast majority of systems that corporations rely on daily -- but this one rubs just a wee bit differently. Hit the source link for the full spill. [Image courtesy of Ultrasaurus]
Microsoft confirms rootkit caused Windows XP blue screens
When malware writers fail to generate clean, reliable code, just who can you trust? On the heels of many Windows XP 32-bit users facing blue screen of death errors and unwanted reboots, Microsoft is now confirming that there's a little bit of malicious code sitting at the root of it all. A rootkit, to be specific, one called Alureon that compromises the atapi.sys file and others. This rootkit makes a system call via an address that, after the update, no longer corresponds to the particular call Alureon is trying to make. This is apparently the cause of the BSODs, not the update itself, and so those suffering from similar issues can resolve them by simply replacing corrupted system files via the recovery console. It won't be as much fun as using Microsoft's more popular console, but should at least cure what ails you.
Windows XP patch fiasco gets even crazier, Microsoft now scrambling for solutions
If you ever needed a reason to go Linux, here you go. The noise surrounding this patently obscure Windows XP bug / patch fiasco has just reached a fever pitch, and now we've got engineers within Redmond scratching their heads, too. As the story goes, Microsoft recently patched a security hole that took care of an antediluvian DOS vulnerability, and in doing so, some users began to see BSODs and endless reboots. Today, we've learned that the patch has been yanked, and Microsoft is suggesting that malware is to blame. But here's the skinny -- the patch simply disturbed the malware, which called a specific kernel code that directs your PC to keel over; in other words, any application that calls that same code could theoretically leave your machine in dire straits. And that, friends, probably explains the software giant's following quote: "In our continuing investigation in to the restart issues related to MS10-015 that a limited number of customers are experiencing, we have determined that malware on the system can cause the behavior. We are not yet ruling out other potential causes at this time and are still investigating." Rock, meet hard place.
Patch for ancient DOS bug in latest Windows XP update causing blue screen errors
Looks like Patch Tuesday turned into BSOD Tuesday for some Windows XP users -- Microsoft's latest security updates for the venerable OS are causing blue screens and endless reboots for people. That's the word according to a growing support thread on Microsoft's site -- and making matters just slightly worse / funnier, it's apparently the patch for that 17-year-old DOS vulnerability that's causing all the trouble. You win some, you lose some, right? Microsoft's identified a fix for those with access to an XP install disc and an optical drive, but that leaves most netbook users out in the cold -- and considering netbooks are where most of the recent XP action's been going down lately, we're hoping a better solution comes down the pike soon. P.S.- That's the BSOD tattoo guy in the photo -- remember him? [Thanks, HyperSl4ck3r]
Getting Leopard's BSOD? Try uninstalling APE.
While there's no easy way to account for everybody Leopard user's crashing, Unsanity's Application Enhancer is apparently the cause of many a BSOD turning up on a range of user's systems during a system update to Mac OS X 10.5. If, after selecting "update," you're getting a perpetual blue screen, follow Apple's instructions for booting into single-user mode to remove the offending software. If you haven't updated yet, make sure you get rid of the software before you do: alternatively, do a fresh install and it'll overwrite any of the conflicts you would encounter otherwise. And remember to backup, backup, and backup.[Thanks, Dilan J.]
PSP Fanboy hands-on: Metal Gear Solid Portable Ops
A few steps away from Sega's booth at DigitalLife was Konami's. I got a chance to talk to Matt Knoles, product manager for Konami, and play a few rounds of multiplayer from the upcoming Metal Gear Solid: Portable Ops. Although Matt couldn't reveal anything new to you guys, the ability to go hands-on with the game was exciting. Four PSPs engaged in the battle, and I got into the control scheme very quickly. It was relatively simple to move around, lock on and start firing away. It was a great deal of fun, but I worry that the multiplayer may be a bit too shallow. The gameplay was fun, easy to pick up, and graphically very impressive, but at the same time, it felt unrefined. It wasn't hard to find yourself fighting with the camera, and entering first-person view seemed to give you a distinct disadvantage in the game.I previously questioned whether or not controlling the game using the PSP's analog nub would be effective. The answer is: yes. But, I think it will work much better in Portable Ops' crucial single player story mode, where the pace should be slower, and the game should be... well, stealthier. A slower pace will certainly make the controls much more forgiving. However, the production values of the multiplayer game are so amazing, that I believe that the game should be quite amazing when it comes out in December.The PSP met the Blue Screen of Death for this unfortunate player.
