Recieve a BSOD after KB2859537.

Interesting indeed, especially as my machine (in working state, i.e. without KB2859537 installed) does not have any of the registry entries listed.

I have tried running Startup Repair on the 'working' system and it does not find any issues or restore these registry entries as this article suggests it should.

The questions now are (a) what are these registry entries for, (b) were they ever present in my hardware configuration and (c) if so, what removed them. The only registry entry I have wth 'ntdll' in this section is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ntdll.resources_31bf3856ad364e35_en-us_4ed606df6fa4d74f.

Well all be gobsmacked..... so it is

Follow the trail of the KBs just as you say

Last month's kernel update of MS13-063  https://support.microsoft.com/kb/2859537

is replaced by this month's Service Control manager update and in THIS one it lists the reasons for those BSOD's 6B errors:

http://technet.microsoft.com/en-us/security/bulletin/ms13-077

Lists "known issues"

None

Yet in https://support.microsoft.com/kb/2872339

Clearly there are known issues....

Known issues with this security update

After you install this security update, you may experience any of the following issues:

• You may receive a STOP 0x6B error message when you restart a computer that is running an x86-based version of Windows 7 SP1. This problem may occur if the following registry entry is missing:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ntdll_31bf3856ad364e35_none_b79ff9b5a57efc44

The missing registry entry could be caused by corruption in the registry or elsewhere in the system.

• You may receive a STOP 0x6B error message when you restart a computer that is running an x64-based version of Windows 7 SP1. This problem may occur if either of the following registry entries is missing: 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-ntdll_31bf3856ad364e35_none_1e133f8b923d2f75

The missing registry entry could be caused by corruption in the registry or elsewhere in the system.

• You may receive a STOP 0x6B error message when you restart a computer after you perform a specific System Restore operation. For example, the issue might occur in the following scenario: 
  1. You install this security update. During the installation, a restore point is automatically created.
  2. You perform a System Restore operation to restore the system to the restore point that was created by this security update.
  3. The computer is restarted. Notice that the system is now in an unprotected state because the security update was removed.
  4. You try to undo the System Restore operation.
  5. The computer is restarted, and then you receive the STOP 0x6B error message.

To resolve these issues, you can use the Startup Repair recovery tool. For more information, go to the following Microsoft webpage:

http://windows.microsoft.com/en-ca/windows7/startup-repair-frequently-asked-questions

(http://windows.microsoft.com/en-ca/windows7/startup-repair-frequently-asked-questions)

Note Not all STOP 0x6B errors are caused by the issues that are described in this article.

That one doesn't, but there is another update, just for Windows 7, that supersedes KB2859537, again, just on Windows 7, so much so that you can uninstall KB2859537 after installing it. It's KB2872339.

Different files are being fixed.  The August file impacted:

The September one is "kernel mode drivers" not "kernel" and is impacting

So, no it's not a replacement.  I go slow on any patch with the word "kernel" in it and do not install it on the first day it's out.

how about the new update kb2876315 it is for kernal drivers also, this this update the fix for the kb28595937? or is this one a new one that will cause more problems.  It is rated as important so I am not doing a thing until i see others complain or not about it in windows update forum