Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • KB 4025341, KB 4025337 cause crashes on some older hardware running Win7

    Posted on July 14th, 2017 at 15:48 PKCano Comment on the AskWoody Lounge

    There have been reports of BSODs after installing the July 11 patches on some older Win7 machines. Both KB 4025337, the security-only Update, and KB 4025341, the Monthly Rollup have been involved. Uninstalling the update fixes the problem.

    Many posters have reported successful installation of the updates. So it doesn’t appear that the updates themselves are broken, but, when combined with specific drivers, BSODs result. It is likely due to some of the changes Microsoft has made to Win7 via the patches. @NetDef reports that updating the Intel C600 chipset driver fixed the problem. Another report possibly points to AMD graphics drivers.

    If you have experienced a BSOD after installing the July 11 patches, your information would be helpful. The errors on the blue screen can pinpoint a conflict with a device. The Device Manager in the Control Panel is also an excellent source of information on installed drivers. What was the source of your drivers – from the manufacturer or were they Microsoft drivers?

    This is an example of the type of information that is useful:

    OS: Win7 Ultimate SP1 64bit
    PATCH: KB 4025337
    CPU: Intel Core 2 Quad Q8200
    GRAPHICS: ATI AMD Radeon HD6450 v15.300.1025.0
    CHIPSET: Intel P35/G35/G31 r.10 (or version)
    FIX: Uninstalled update, or Rolled back HD6450 driver to n.15.200.1052.0, or Updated Intel chipset drive to…

    Any luck in identifying the the exact driver(s) involved would be most helpful to a lot of people.

  • July 11 security-only patch KB4025337 causes BSOD

    Posted on July 13th, 2017 at 06:40 PKCano Comment on the AskWoody Lounge

    Poster @skunk1966 reports

    I just installed KB 4025337 for Windos 7 (x64). After rebooting my system I got BSOD. Started up in safemode and ran sfc /scannow. Rebooted in normal mode and again BSOD.

    In the end I couldn’t fix it so uninstalled KB 4025337 using wusa cmd. Rebooted in normal mode and all is fine again,

    The computer, running Win7 Ultimate has an older Intel Core 2 Quad Q8200 (Yorkfield) and ATI AMD Radeon HD6450 graphics.

    Is anybody else seeing problems with the July 11 Security-only patch for Windows 7?

  • Blue Screen Stop 0x050 error reported for this week’s Black Tuesday KB2976897, KB2982791, and KB2970228

    Posted on August 14th, 2014 at 06:31 woody Comment on the AskWoody Lounge

    Sporadic reports of BSODs associated with this month’s Black Tuesday patches. If you hit one, head over to the Microsoft Answers forum and tell ’em all about it.

    InfoWorld Tech Watch

  • Users hit by Blue Screen, 0xC1900101 – 0x40017 error with Windows 8.1 update

    Posted on October 18th, 2013 at 19:31 woody Comment on the AskWoody Lounge

    So far there don’t appear to be any fixes.

    InfoWorld Tech Watch

  • Symantec Endpoint Protection 2.1 causing BSODs

    Posted on July 14th, 2012 at 11:00 woody Comment on the AskWoody Lounge

    If you are running Windows XP and Symantec’s Endpoint Protection 2.1, beware of the latest update. (Endpoint Protection is generally a corporate product, but if you have a company laptop, you may be affected too.)

    According to Reuters, Symantec admits that the latest updates are blue-screening XP machines.


  • MS10-015 Blue Screens due to TDL3 rootkit infection

    Posted on February 18th, 2010 at 05:05 woody Comment on the AskWoody Lounge


    Last week I wrote about Microsoft’s security patch MS10-015 causing Blue Screens of Death on some machines: if you install MS10-015/KB 977165, or it gets installed for you, your machine may BSOD on reboot. Every reboot.

    Marco Giuliani on the Prevx site has this explanation:

    TDL3 rootkit looks incompatible with MS10-015 update. This is the cause of the BSOD. Problem resides in the lazyness of rootkit writers when writing the driver infection routine.

    When the rootkit dropper is run, the infection calculates the RVA offsets of some Windows kernel APIs and hard code them so that at every restart the portion of the rootkit loader injected inside the infected driver can use these offsets to immediately calculate the address of the wanted functions.

    This worked well until the MS10-015 update, when Microsoft updated Windows NT kernel. This update changed those offset values and consequently broke the rootkit code. When the update procedure is finished, system is restarted. At system restart, the rootkit code tries to call a non-valid address and this causes the BSOD.

    Good news is that TDL3 authors care about us and they released in a couple hours a new updated version of the rootkit compatible with the Microsoft patch.