On mydigitallife forums someone has observed that the latest Intel AHCI drivers on a Z77 chipset motherboard can cause file corruption which is detected by sfc.
Recieve a BSOD after KB2859537.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
When I install KB2859537 on my Windows 7 X64 machine I get a BSOD during reboot either trying to boot normally or trying to boot in safe mode. Had to restore the primany disk three times now to get the PC bac. Can someone report to MS tech please.Anyone else seen this
Windows for home | Previous Windows versions | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
216 answers
Sort by: Most helpful
-
Anonymous
2013-09-10T13:30:54+00:00 -
Anonymous
2013-09-10T13:20:06+00:00 Servicing stack corruption shouldn't crash the system - it should just render it - obviously - unservicable. Since I am running just fine with this update, I would place my bets on some third party WoW64 code (e.g. AV, OEM bloatware and the likes).
-
Anonymous
2013-09-09T22:04:50+00:00 Servicing stack corruption is such that the system works just fine....until you go to update it. It's deep in the cbs.logs and the sfc scannow and all that low level component based servicing stuff.
-
Anonymous
2013-09-09T21:46:28+00:00 Looking forward to hearing about this from MS as I'm unaware of any corruption - the system has been working perfectly for over 2 years prior to applying this update.
-
Anonymous
2013-09-09T19:58:33+00:00 The update isn't bad. This isn't a widespread issue.
In the case of English I have word that his is due to interaction with system corruption. At this time they are not sure of the underlying cause of the system corruption that then manifests a BSOD when this update is applied.
In the case of the Application errors of 0xc00000005, that is most often caused by the fact that the operating system is not running 100% Microsoft bits but a mismatch of a bogus or pirated kernel code.
I have this installed on approx 50 machines with no issues. The chances that you will hit issues with this update is low. That said Microsoft is obviously holding back to ensure that they understand the issues going on.
But bottom line, I do not expect a new fix, nor should you.