Posted on 04/16/2010 4:07:32 PM PDT by ConservativeStatement
Computerworld - Microsoft took steps Tuesday to avoid repeating the debacle two months ago that left Windows XP users staring at the notorious "Blue Screen of Death" error message after they applied a patch.
In February, a security update that fixed two flaws in the Windows kernel -- the operating system's most important component -- wreaked havoc when it was applied by users, who almost immediately flooded Microsoft's support forum with reports of crippled computers.
(Excerpt) Read more at computerworld.com ...
I should add that I tried signing on earlier today and it failed. Then I tried the System Restore and it worked.
The last event was caused by a root kit (aka trojan).
I use SpySweeper, not sure if that is a necessary part of the discussion. Tech skills are about a 6 on a 10-scale. I see that Microsoft will install updates when I sign off tonight. Do you think I will get the BSoD again?
I use W2k.
Meh...I use MSDOS! It crashes just as much, but it reboots faster!
I don’t care...
You would think they would test these patches better before releasing them
DOS??
People still use DOS?
Does it still come with the oh so user friendly Dosshell?
My Vista had a weird event this morning. Programs just started shutting down, and the system shut itself down before I could do it myself.
Are you looking at the error message that it gives you when you reboot? Sometimes it is due to a driver issue.
And yes, once you start getting them you will usually continue unless you fix the problem.
That’s what heppened to me. I’m hoping this system restore helps. I guess I’ll have to wait for the morning to see if the BSoD reappears. When it happened in Nov/Dec, the nastiness took place in the first five minutes. If I made it past that point, all seemed OK. The problem subsided (I’m guessing with the subsequent monthly updates). Then it happened again this week after the latest install update.
I was kidding. But there are no doubt a few nutjobs somewhere who still use it. And almost everybody still uses that yucky old DOS filesystem.
IIRC, the message was 0x0000008e yesterday but today’s was 0x000000c2 (not 100% sure). I read the Microsoft forum and others seem to have similar, though not exact, problems. Computer is less than three years old.
"Think INDIA! Two for the price of one!" -- Brian Valentine
Today’s patch caused a BSOD with my Intel internal WiFi on my laptop.
WinXP Pro 32 bit.
NETw5x32.sys didn’t play well with one of the updates. Had to roll back manually through safe mode while the WiFi chip was turned off from boot up. Not sure which update is the culprit yet.
**My Windows Xp just crashed bc my kid hit the power button while it was powering down....ughhh!
I get the error screen and have options to Start in Safe Mode, Restart normally, Restart with last Known Config., etc.
No matter what option I choose, it cycles back to the same error screen with the above options.
Any of you fine techie FReepers ever heard of this one?
My Windows Vista will not install the Sevice Pack 2 from last year.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.