Recieve a BSOD after KB2859537.

Susan,

If you do get a case open with Microsoft re KB2859537, can you provide ongoing status in this thread?

Currently the "Known issues with this security update" Section here (http://support.microsoft.com/kb/2859537) is still ominous. The update was first released in August, and Article ID: 2859537 was last reviewed on September 19, 2013 and is on Revision: 4.0 ... so Microsoft seems to be aware of the issues but is no closer to fixing them.

If the BSOD problems are being caused by the missing registry entries (shown in the article), then I wonder why KB2859537 has not been modified to just exit (with a message) if the requisite registry entries are not found on users PC.

Make sure you have a proper video card driver.  BSOD's are not necessarily from patching.

Download the nirsfot bsod tool and see what the true bsod root cause is.

http://www.nirsoft.net/utils/blue_screen_view.html

Can you contact me at susan-at-msmvps.com so we can get a case open?  Hiding this update won't fix anything.  and next month or the month after that there willl be another kernel update.

I started a new hard drive with a clean install but...I had to know... So, here goes!

(Hope your still monitoring the thread Susan.

After getting the BSOD on one computer. I hid KB2859537 and one other KB and did

a restore. Everything was going great UNTIL... I started getting KSOD on both my computers.

(Win7 Ult) The computers would load until it hit the "welcome" screen and nothing but

black and the cursor. I returned to the safe mode to try a "restore" It would work one time until

I booted again and back to the KSOD :(

Now, I searched the net for this KSOD problem and what other people were suggesting for a fix. :(

I decided to start uninstalling recent Sept KB's and both computers stopped the KSOD problem.

I haven't narrowed down which KB but I'm glad I resolved the problem. BSOD and KSOD.

I realized now that if I had a clean install and downloaded ALL the current KB's. I not sure how I could have found which KB(s) was the problem.  I did a search for a list of KB release dates but that still wouldn't have helped me if I had a clean install. I'm just glad that I had a long Win7 run without any problems to see all the KB's updates to reverse the KB problem by install date.   

I still have the new hd with a clean install and ALL the current KB's loaded and I'll probably run it for a awhile to see if any of the KB's give me trouble. I'm still a little dazed and confused on the "Why"

No virus or hardware problems here.

I officially gave up with my fingers crossed that this would be a easy fix from MS.

So, I had an exact spare new HD and it installed everything plus all the updates without

any problems.

So, It's not hardware for me. It had to be corruption. :(

I plan on installing the org win7 HD as a slave and move all my settings and docs over to

the new hd. 

Thanks everybody for some helpful hints on what it could be but they didn't work for me.

Good luck and take care