Slashdot Mirror

← Back to Stories (view on slashdot.org)

Windows 8.1 Update Crippling PCs With BSOD, Microsoft Suggests You Roll Back

Posted by samzenpus on from the back-to-the-old dept.

MojoKid writes Right on schedule, Microsoft rolled-out an onslaught of patches for its "Patch Tuesday" last week, and despite the fact that it wasn't the true "Update 2" for Windows 8.1 many of us were hoping for, updates are generally worth snatching up. Since the patch rollout, it's been discovered that four individual updates are causing random BSoD issues for its users, with KB2982791, a kernel-mode related driver, being the biggest culprit. Because of the bug's severity, Microsoft is recommending that anyone who updated go and uninstall a couple of the specific updates, or rollback using Windows Restore. You can uninstall these updates in much the same way you uninstall any app; the difference is that once you're in the "Programs and Features" section, you'll need to click on "View installed updates" on the left. While it's mostly recommended that you uninstall 2982791, you may wish to uninstall the others as well, just in case.

2 of 304 comments (clear)

  1. They fired 30% of their testers by Anonymous Coward · · Score: 5, Interesting

    The Windows Serviceability team (dealing with updates) was decimated in the middle of last month, losing about 30% of their testers. This outcome is not surprising at all. Expect things to get much worse soon.

  2. Re:It's pretty hard to roll back automated updates by danknight48 · · Score: 5, Interesting

    I hadn't realised it was an update which caused the error, so when I finally resorted to system restore it just auto-updated immediately and broke again.

    Rule number 1 = Dont use system restore
    Rule number 2 = Dont use system restore
    Rule number 3 = Google "Stop 0x0000000e" error code on your BSOD.
    Rule number 4 = Remember the last thing you did before the BSOD started happening, reverse the process. Job fixed.

    One thing I learned: Disable fast boot, if it's enabled, on your Windows machine. Your startup time will be a little slower, but you might just save that time if something ever goes wrong with your Windows install and system restore fails.

    All fastboot does is skip a few bios checks (eg: fast memory scan instead of full). It will not effect anything else, unless you have a hardware fault which can be detected at BIOS post.

    Apparently a Ubuntu boot dvd cannot mount an NTFS partition with write enabled if a hiberfile.sys is present (apparently windows leaves its mounts active and stored in said file, so modifying the file system would cause problems).

    Sounds like the Ubuntu DVD doesnt include NTFS-3G which is required for NTFS write ability on linux. Or simply its a safey feature to prevent you deleting the hibernation file.
    The only time you need to keep this file is if your machine is in hibernation and powered off. Only then will it contain possible data your working on that isnt technically saved. If you wernt in hibernation when you powered the machine off, the file is just a placeholder for the next hibernation.