locked
WePOS 1.1 Blue Screen after applying KB2758857, KB2770660, KB2753842 RRS feed

  • Question

  • I have 20 machines that are IBM SurePOS 742 running WePOS 1.1 that have been running have fine and updating without issue until today after these Windows Critical Security Updates were applied:

    KB2770660

    KB2758857

    KB2779030

    KB2753842

    After the machines were rebooted it would not boot to a Blue Screen Windows Stop error.  We had to direct associates to boot-into Safe Mode and manually remove these updates to get these POS machines operational.  I have since made these critical updates inactive to avoid a major disaster to the rest our environment.  These 20 machines are a test environment before the mass deployment.

    These machines are running ESET antivirus as well.

    Thursday, January 3, 2013 9:29 PM

All replies

  • Eurkie,

    Please report this problem through your IBM Support channels. IBM may already be aware of this situation and if not they can quickly get support through our OEM support channels to resolve.

    Terry Warwick
    Microsoft

    Sunday, January 6, 2013 5:28 AM
  • Terry,

    Thank you for the reply.  I have engaged IBM support and it has progressed to L2.  My organization is getting close to panic mode as this has started to affect a large amount of machines and it is not related to the KB Updates in the title.  I have seen machine Blue Screen with a stop error Ox0000007e.  All the machines affected are configured with SATA Mode=RAID in the BIOS and have the Intel 82801 SATA RAID Contorller v.5.0.0.1032 driver date 3/9/2005.  No updated driver is listed on IBM's support website.

    I have examined the memory.dmp file which has a Bug Check String SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Buck Check Code: 0x0000007e

    I have installed Windows Debugger and it indicated a problem with the driver Ehdrv.sys with a date stamp of April 2010 which is related to ESET 4.2.58 Antivirus installation.  ESET is installed on other non-RAID without the Intel 82801 SATA Controller that are not blue screening.  Those machines are the same model but are configured to IDE

    I have tried to update the BIOS and ESET to latest version but did not make a difference.  Once the machine blue screens it will constantly do so until you boot into Safe Mode remove the Intel 82801 SATA RAID Controller and reboot.  This works breifly.  This all started to occur after 1/1/2013 and only some machine updated with Microsoft Updates and ESET signature updates after 1/12013, but machines are crashing without receiving the Dec. 11, 2012 MS updates.

    Thanks.

    Wednesday, January 9, 2013 10:00 PM
  • I have had a similar problem and think I narrowed the problem down to KB2779030

    I customers machine was blue screening in various activities such as opening particular web pages in chrome, opening attachments in outlook etc

    I used the Nir Soft BlueScreenView Utility that showed for all these BSODs the driver responsible was C:\Windows\System32\Win32k.sys

    In the crash dump it was showing as version 6.1.7600.16385, when I checked the file properties of C:\Windows\System32\Win32k.sys it showed version 6.1.7601.18009

    (doing a search of C: for all the files like win32k.sys (and other files) was also causing the BSOD so I could not check further)

    I could see that KB2779030 has that version of the file so I uninstalled that update and the BSOD problem was solved. (the win32k.sys version on disk then showed as 6.1.7601.17803)

    I let Windows reapply the update and the BSOD problem did not come back.  Somehow there was a different version in memory at the time of the BSOD compared to the file on disk.

    I found the same problem on one of our companies laptops and suspect it as the cause of 6 other machines at another site that started doing BSOD on 19/12/2012

    (but they did system restore and also wiped the minidump files)

    Hope this helps

    Tim



    • Proposed as answer by micmact Wednesday, January 9, 2013 11:34 PM
    • Edited by micmact Friday, January 11, 2013 4:18 AM better grammar
    Wednesday, January 9, 2013 11:15 PM