Microsoft Black Tuesday Patches Bring Blue Screens of Death
snydeq (1272828) writes "Two of Microsoft's kernel-mode driver updates — which often cause problems — are triggering a BSOD error message on some Windows systems, InfoWorld reports. 'Details at this point are sparse, but it looks like three different patches from this week's Black Tuesday crop are causing Blue Screens with a Stop 0x50 error on some systems. If you're hitting a BSOD, you can help diagnose the problem (and perhaps prod Microsoft to find a solution) by adding your voice to the Microsoft Answers Forum thread on the subject.'"
This is why you should NEVER apply patches that ANY vendor has just released.
Fresh patches are barely beyond alpha tested, if that.
Yes, there's zillions of platforms, but how much of this suck is a result of how Microsoft has architected this crap?
Their years of stealing other people's ideas and then doing a piss poor job of implementing them means they publish so much un-maintainable crap it isn't funny.
Let's face it, Microsoft releases shitty code all of the time. This is nothing new.
Someone right now is looking at that error and figuring out how to exploit it.
"If any question why we died, Tell them because our fathers lied."
Auto Update on by default, one of the updates bricks your server.
Oh wait, I'm on Linux.
I work in schools, preparing for a huge summer deployment, just re-imaged every PC on-site.
Fortunately, although I pushed the updates out over WSUS, my image was taken BEFORE patch Tuesday. Anything that hasn't been out for a least a month is in beta testing, as far as I'm concerned, and after a month it either "works" (for some definition) or something like this will come to my attention.
Have all the PC's imaged in my rooms, but only have a handful actually deployed at the moment while I test. The very first blue-screen I see, any kernel-mode patch this month will be changed to "Declined" so no further PC's get it.
Yet again, those people who get all stroppy about "you should install updates the SECOND they come out".... real life hits you again. And the downtime from a potential "zero-day" that I'll probably never witeness is nothing compared to potentially rolling out faulty updates to hundreds of PC's that would then have to be re-imaged, and/or having a faulty update inside your images forcing you to reverse changes (in my case, to pre-summer images which is a HUGE step backwards) and re-deploy.
So it looks like certain video drivers are barfing the system (itching the gdi32.dll the wrong way). If you can, roll back to an earlier system restore point, update the video drivers, then re-apply the updates again.
Life is not for the lazy.
If your computer BSODs, then post on a forum about it. Of course, how does one post on a forum if they can't boot up? Might as well add in a www site for network connnectivity problems too.
If I get the BSOD, I'm not going to have a computer that I can use to "drop by" the Microsoft Forum and report anything.
Note to self: Always, always put a Linux partition on EVERY Windoze machine!
Yeah, yeah, I could carry a bootable USB around, but this way, it's always IN the machine.
My problem is this: WHO is going to PAY me for my time? Isn't it time that a consumer watchdog agency said: "Enough is enough, Microsoft. You have cost users countless BILLIONS of hours and money. If this were a car, Ford or GM or Toyota would be BANKRUPTED by the recalls."
*** Don't be dull.***
This rollback procedure got my Win7 x64 system booting again:
From another system with the same bit width and service pack level, grab the files C:\Windows\System32\gdi32.dll and C:\Windows\System32\Win32k.sys.
Using HBCD or a similar boot disc, boot your defunct system. You can also snag the hard drive and plug it into another working computer.
BACK UP the gdi32.dll and win32k.sys files from System32 to another location just in case. Overwrite those two files in System32 with the ones you grabbed from the other system.
Your system is now bootable, having effectively rolled back the KB2982791 update. This is a quick and dirty procedure and leaves the update itself in an indeterminate state.
Oh wait, I'm on Linux.
Which distribution? I have had issues with Linux patches too.. Not as often as with Microsoft patches, but problems none the less.
"File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
don't kill the persistent task bar and add it + start menu to windows 9.
On my private machines, I have been using Linux and *BSD for more than ten years, and I only once had a problem with an update (and that was on a Gentoo box that had not been updated for more than a year - in other words, it was to be expected). About one and a half years ago, I started working as a sysadmin at a Windows shop, and I have been enraged, shocked, scared, and surprised more or less continuously ever since.
On the one hand, you want to keep your systems up to date. On the other hand, installing updates on Windows is like Russian roulette with five out of six chambers loaded. I am constantly torn between my deply ingrained reflex, acquired on Linux/BSD, to install any update as soon as it becomes available, and painful experiences I've had on Windows.
Can't Microsoft just get their act together and do some freaking *TESTING* before shoveling their crap out of the door, instead of having their customers do it for them?
This is yet another reason all versions of Vista are failures. Doesn't surprise me as M$ is doing what they always do, using their illegal monopoly to distribbute sub-par, non-free software to its lusers. M$ also uses restricted boot to ensure all systems must use their non-free software. Without their power to reinforce their illegal monopoly people would be fleeing M$ Windoze with its bugs that cause Windoze machines to BSOD and going over to GNU/Linux and use nothing but free software over using non-free software.
--
Friends don't help friends install M$ junk.
Friends do assist M$ addicted friends in committing suicide.
So happy I'm running XP right now. No patch for me.
Oh my god... is that Twitter?
You posted something bad about Windows so they very quickly buried you.
I miss when this site had technical users instead of being run by Microsofties.
I prefer to play Russian Roulette with a semi-auto with 3 out of 6 rounds loaded. The odds are better.
"File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
Who uses microsoft corporation's 'windows' product nowadays?
Did this problem really affected someone?
Or is it just some unimportant news for plebs, stuff that doesn't matter?
I just checked my update history for my Dell XPS 15 running up to date Windows 7 SP 1 and the three patches listed in the OP post were installed and I have no problems. One was recommended and the other two were listed as important.
In a time of universal deceit, telling the truth is a revolutionary act. George Orwell
Mod up. Anyone who has ever been cast from a professional *nix environment into an MS shop has experienced the same horror (raises hand).
And the difference in tool and OS quality between the two environments produces a totally different mindset. Like designing a jet engine vs. building a castle in the sandbox.
Oh, and if you are allowed a 15 round magazine, 3 out of 15 is even better!
"File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
My win7 desktop is bricked after patch Tuesday updates. Even my win7 install DVD is not working due to Master boot record being damaged. Supposedly the same DVD I used to fix my desktop a few months ago is now not the same version of windows that I installed.
Stop errors 0x50 and 0xc000000f
... Throwback Tuesday!
Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
If it was a M$ gun it would lock up, or empty the entire magazine.
880 w/512 Megs of fucking confirmed: slings are limited, bought the farm... BSD had become that *BSD 0wned. took precedence obligated to care this is consistent OpenBSD wanker Theo
If it was a M$ gun it would lock up, or empty the entire magazine.
No, they'd just hide the trigger and require you to hit three separate buttons requiring at least two hands to fire it, then totally disassemble and reassemble it between shots... ([Ctl][Alt][Del] followed by reboot)
Yea, I know, OLD NT joke.....But it's still funny.
"File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
If it was a M$ gun it would lock up, or empty the entire magazine.
and auto-aim at one of your pedal extremities.
There is no right to feel safe thru security vaudeville at the expense of everyone's freedom, privacy and tax money.
Updates Win 8.1 x64 all patches. No problems.
Reading slashdot one-liner: (irm http://rss.slashdot.org/Slashdot/slashdot).rdf.item | fl title,desc*
Once again, Microsoft discovers what's obvious anyone else who's been in the business for 25 years or so.
You have to have manual and automated GUI testers. Unit testing is nifty, but that's like testing just the spark plug, or maybe the spark plug and the ignition timing. Not a bad idea, but listen. If you knew about a new car, but knew that nobody had ever actually *driven* the car, much less taken it out on the road on a regular basis, would you buy that car?
For that matter, would you fly in a plane tested that way?
Developers testing their little piece of code isn't ever going to cut it. Neither is unit testing. Thinking it will is just managerial fantasy, or an idea that lets you fire a bunch of testers so the books look better and some manager or bean counter. can get a one time bonus.
Please do not read this sig. Thank you.
Enterprise quality software.
I never understood why drivers had to be on the kernel ring anyway. Every single peripheral (GPU, sound card, etc.) driver I've ever encountered has had a history of stability problems. You'd think the largest point of failure on the computer could be moved to userland and restarted when necessary.
I run Ubuntu on my laptop and there are patches a few times a week for various items and I haven't had any trouble or issues post installation. I can't speak for all Linux flavors, but I can say that for a general purpose web browsing/office productivity laptop, Ubuntu is great.
You should also close your /.-account — and never come back, for all I care...
In Soviet Washington the swamp drains you.
They want to force everyone onto smart phones that store all data on the cloud, and do not function off network. Once they capture all your data, it's easy to blackmail you. So Microsoft might deliberately be castrating themselves, to push the IBM mainframe-cloud in businesses, and smart phone could terminals, for everyday users. The cloud the cloud the cloud, you can't have your own data, like on a USB stick no more. Microsoft might be willing to offer themselves as a sacrifice to accomplish this. Which is why it might be an interesting idea to sell short, but that's a really lame way of making money. Ballmer in 2001 or 3 shouter at a dev conference "I love this company." Which means his mentality is not one of sacrifice for greater good, or greater money, but greater ego. Sometimes corporations, that are treated like people when it comes to taxes, take on a life of their own and want to survive even if there are other sub-collective faction interests, that would make the collective more exploitable, like there is a new set of greater predators that would be much better off with the old top predator gone, even if closely related by kinship to the old one, but the old top predator might want to survive anyway, without transformation. The transformation itself would mean Windows Phone always on the cloud, for everyday people, and Windows Mainframe cloud based servers, for businesses. So forget your old desktops, and your old business investments into apps, they are offered as a sacrifice Microsoft and gang to the Gods, burning on an altar, hoping to be forever gone from the world.
THAT'S WHAT THAT WAS?! I thought it was just a problem with our new computer. For the record, it only happens upon login when a computer is running a fresh install of AutoCAD 2014. At least that's been my experience. I need to go block this from WSUS immediately.
Same here. XP became a whole lot more reliable when Microsoft stopped messing with it. I will upgrade my toy operating system when the next Windows version is no longer updated, and it runs as well as XP on my (then) current hardware.
(and keep using Linux for more serious work, and when I don't feel like tying with an operating system)
The way to fix this is to delete \Windows\System32\FNTCACHE.DAT. The file will automatically be regenerated on the next boot.
(Information found on Microsoft Support Forum and used to successfully fix my own system.)
How do you delete the file if you can't boot?
(1) Press F8 during boot to get to the Windows boot manager advanced options screen.
(2) Select "Repair".
(3) Provide password for a local account that's a member of the Administrator group.
(4) Select "Command Prompt".
(5) Find drive letter assigned to Windows partition (may not be C: in the repair environment!).
(6) Delete \Windows\System32\FNTCACHE.DAT.
(7) Exit command prompt and reboot system.
(8) Fixed!
----------
And now, since this is /., here is the required Windows bashing...
This bug demonstrates the danger of running your GUI in kernel mode (win32k.sys). One stray pointer can ruin your whole day. In this case the pointer was sufficiently invalid to cause a bugcheck. A stray pointer that silently scribbles on other kernel data structures is even worse.
"Those who would give up essential Safety, to purchase a little temporary Performance, deserve neither Performance nor Safety."
The key sequence to access my Slashdot bookmark in Firefox is Alt-B-S. I don't believe this is a coincidence.
Hello,
I know that Slashdot loves to bash Microsoft, but calling it's monthly patching cycle "Black Tuesday" is pushing it. Black Tuesday was the name for the stock market crash that preceded the Great Depression, and for all the negativism about Microsoft, I have yet to hear of someone committing suicide over a Microsoft patch.
Frankly, using Woody "I'm a Windows victim" Leonhard as a source of information about Microsoft patches isn't a good idea, at least until he stops grinding whatever axe it is he has against Microsoft. Go read Microsoft's Security TechCenter if you want to know the patches are for, or at least blogs like ComputerWorld o ZDNet's r>Ed Bott, both of whom are more likely to put facts ahead of opinions. Even Paul Thurrott provides some good coverage, although I think he often is the opposite of Woody Leonhard, e.g.doesn't critical enough coverage.
Regards,
Aryeh Goretsky
Dexter is a good dog.
I use my laptop at night. Last night I could not get in at all. Constant upgrades or updating. 45 000 it said. Then I was offline. Then once online again, my screen sent blank. What is this. Why am I paying for something that does not work. I need my laptop to be working all times.
Very rare compared to how it used to be (situation normal on XP early on) maybe but not imaginary. I've had a couple of users with blue screens in the past few months, and there's only about a dozen MS workstations in the place. The problems went away after fully applying updates but they were real. Maybe it's the culture of people not rebooting their machines for months due to it being a *nix shop that resulted in the people on MS not shutting their machines down for updates every week.