Recieve a BSOD after KB2859537.

If you have installed the update, and didn't have the freeze up or bsod you won't have any issues with the update.  Seriously, there will not be a bsod spontaneously out of the blue.  These symptoms are due to the fact that the kernel the impacted systems are using is not the proper true windows code.

BSOD's don't spontaneously occur.  There is always a cause and effect.

They are 'throttling" the update as they typically do when they see issues with an update.  For those that have installed it and see no issues (as I have here personally) there is no need to uninstall the update.  For those that see it unchecked, leave it be and it will be 'unthrottled' at a later time.

 

 

Well I had no issues at all on all 4 computers with the specific update installed. That doesn't mean that they are not present and could occur any second. Out of precaution I've uninstalled the update and did hide it (many did by now). That doesn't mean that I have Auto-Update disabled. Got all other updates just installed. But I've read multiple forums (including the ones of games) of people with trouble after this update. The damage it could cause has a severe impact.  BSOD is unacceptable, same goes with a corrupt Windows Profile or that some programs does not want to run anymore. For me is that enough reason to hold back the update for a while, till the cause of these issues are determined.

I have to agree with you that apparently not everyone in the world has trouble with this update. Else we would see millions of posts within a day. Mind that a lot of people do not have the knowledge and just say : Oh my computer is defect, let's bring it to a repaircenter. Or "Bluescreen, whatever I just restart". Or even worse "like 70% of the population is not installing updates at all (so they won't be affected by the update)". Also it seems that the people with (this update) problems have a rootkit/malware on his computer without knowning it.  I did just read a recently released article with the information that 12% of the computers is affected with different kind of malware. A small ammount of these might have the specific root-kit that is causing this trouble with the update, those are reaching out to these forums. A couple of them did send their crashreports to you by now. Hopefully it does clear some things up.

But till the moment that Microsoft determine and publish a article with the cause of this reported issues,

I stay skeptical about the update. I understand that you need labrats/testobjects, so did re-install the update on one computer and will monitor the behavior of it during the week. I will report back here.

Just keep us updated about the development on solving this mystery. Thanks in advance.

No such files.

I'll await more posts on suggestions for fixes and keep my fingers crossed before I try installing KB 537

again.

. Thx Susan

English is based out of England and thus works on the machine at odd hours.  The 6B bsod error (I think) they understand but they want to see if we can find anymore 6B's out here.  I've emailed a couple.  I don't see as many BSOD/6B's as I do this 0x freeze up issue.

As to root kits, this critter is not being found with our usual tools.  Just about everyone reports back that they've scanned with various tools and no root kit reports being found.

Look to see if you have any of the following files on your system:

xOSLoad.exe

xNTKrnl.exe

oem-drv64.sys

In the properties of oem-drv64.sys - if you have it - who's the author of the file?

Susan.. Thx for the continued posting updates and to the great posts

from the community

I've been following and reading with my fingers crossed that somebody figured out the fix.

I've read all the posts about what could cause the problem

Rootkit (Virus) or Hardware

On my computer it installed no problem Win7 64 Intel Duo GigaByte MB.

My daughters computer had the problem. Win7 64 Intel Duo GigaByte MB.

I ran F-Prot, MSE and MBAM and TDDSKiller.  No problem in the Rootkit

but MBAM did find two virus. I haven't tried to install the KB-537 since cleaning it.

I would hate to be locked out without the chance of doing a restore on a reboot.

I've been lucky so far installing all the other KB's.

I appreciate all the posts here because somebody with more smarts than me will

figure this out. I guess the question is; Is it hardware or a virus ?  

What happened to EnglishM45 ? That last post talked about MS helping

him/her on the problem. I think one post mentioned MS was able to

reproduce the problem? or did I read that wrong.

Thanks to ALL !