BSODs from MS Office 2013 Security Updates on new build i7 6700K PC

Hi, I have tried a lot of diagnostic work before putting my hand up as I am not finding a path out of the bsods and miscellaneous errant behavior of this new build which works great sometimes and then falls over. I can duplicate the principle faults (bsods) reliably but doubt my reasoning is conclusively accurate. Basically whenever I install the last 7 security updates for MS Office 2013 it will bsod within 5 - 10 seconds of logging in. Always works in safe mode and restoring to pre-update always fixes it. This was a list of 70 before I got it down to 7, of which I know at least 2 directly cause a bsod and I am unsure of how complicit the others / combinations are. I have tried MS help and it is very slow going over there - after some hours and losing the remote connection on a restart as I needed to do a restore to sort some of their experimenting just to get proper control back! Sure would appreciate some more pointed help, thank you.

I have done a fresh install of Win 7 after maybe a decade or more of living with an XP upgraded to Win 7 PC based on an original QX9650 in an Asus Maximus X38 board. Made mistakes like not understanding junctions properly and took over some permissions I shouldn't have, etc etc. New build, backed up everything (in duplicate) and bit the bullet.

All I have been trying to do is get a fully stable machine on no overclocking and live with that for a few months before even thinking about serious tinkering. The ASUS Maximus 8 Assembly with 64Gb Corsair RAM and an i7 6700K cpu was a pig to get going. It needed to have no graphics cards or anything else before finally on progressive installs of the various bits it was all connected, four monitors running and seemingly stable. This is a serious PC for engineering applications, plus I have a Rift I am yet to get out of the box for both gaming and tech applications I have in mind.

Attached is the bsod info and requested diagnostics. Also I have run the windows diagnostics on it and attached results.

Separately, or maybe related, I keep getting big slowdowns due to dwm.exe (Windows Desktop Manager) which after a while decides to hit me with the option to go to a high contrast color scheme which I say No and don't ask again. Within a couple of hours it will ask. Right now Resource Monitor shows it has about 70 handles open and using 11% cpu. But the most bizarre one is mscorsvw.exe which Google teels me is the .NET Framework trying to update itself so I should run 7318.DrainNGenQueue.wsf to give it a hurry up, which I typically need to do twice to get the rather dramatic result shown in attached 3 pager telling this bizarre story (have you ever seen 64Gb RAM cycling so impressively?!!!)

PC Summary:
ASUS MAXIMUS-VIII-EXTREME-ASSEMBLY Z170 Express, E-ATX, LGA1151 DDR4 Motherboard
Intel Core i7 6700K Skylake Quad-Core CPU LGA1151 Unlocked BX80662I76700K
4x16GB Corsair Dominator Platinum 64GB DDR4 3466MHz C16 with AirFlow for Intel 100 series (CMD64GX4M4B3466C16)
Asus STRIX-GTX980Ti-DC3OC-6Gb D5
ASUS Strix GTX 960 OC 4GB D5
Samsung SSD 2TB 850 EVO
Samsung SSD 250Gb 840 Pro
BARRACUDA XT 7200.12,2TB
1000W "Silverstone" ST1000 Power Supply
Corsair Cooling Hydro Series H50 High-performance CPU Cooler

The plot thickened, a little. Using the PC ok all morning on MS Office products, FF browsing, Paintshop Pro X8 64bit and a bit of file mgt and the slowing down happened due to dwm.exe again. Just causes slower typing / display but otherwise seems to work. While I wasn't touching it for a minute the PC bsods, this time to an error 51. I went round a couple of safe mode boots then normal and kept getting same 51 bsod, which I captured the attached WinDbg for. Finally did a safe mode restore which removed WinDbg and hey presto all good. I have made some dummy restore points so I can use them to go back to where I already was since this is looking like some "other problem" that is triggered by particular things I can't currently identify, or know how to tackle doing same!

I did run Memtest round a couple of full passes with zero errors showing. I will leave it going longer later just to be sure, but my experience has been if you don't get Memtest chucking an error in the first couple of passes it never will. Even second pass after a clean first hasn't happened to me before, and I have sent a few chips back over the years!

Surprisingly I have had a 50 error again - after I did the WinDbg but before the restore. I know this because I went to do a dm log collector to add to this post and see the last error was a 50. At least 4 of the 6 bsods I had before getting control back were 51's - I had a colleague visiting so didn't pay attention as cycled round a couple more times before running the restore. I added it anyway - this was made while dwm.exe running at 11%cpu (only about 40 handles atm).

I don't mind that people may regard this as too complex a situation to give me a direct answer, but sure would appreciate suggestions on what diagnostic work to do next. Thank you.

I have just enabled driver verifier per Driver Verifier - Enable and Disable so will see what that does. If no bsods in 24 hrs I will go update a MSO security item and see how that goes...

Hmm, diagnostics 101 - run sfc/scannow elevated! Look at all these beauties (attached) - 45kB of just the [SR] entries from the CBS.log, wow - how did that happen??? Maybe this will give me some stability as at least the issues were all reported as fixed (how often does that happen? NEVER!)....

PS: haven't touched this PC for an hour since I ran sfc and there is dwm.exe just churning away at 11%. It keeps one processor (out of eight) churning away at 80% and just a smidgin from 3 others)

The driver verifier tripped up alternately on SvAuxSvr.sys and BrUsbSIb.sys, which I caught pics of but see little point in putting up. Had to go to safe mode to turn verifier off as the trip happened for one before I logged on and the other within a second of logging on. Very repeatable but I forget which was which. It has been rock solid since turning off verifier; even dwm.exe is behaving at 0.1% cpu - which I see involves 25 open handles.

SvAuxSvr.sys is for the ASUS high end SupremeFX Hi-Fi audio system and comes as part of the latest Realtek Audio driver set. This is only a couple of weeks old and I see no point in going through the Realtek uninstall - reinstall loop to get back to exactly the same place. Is there any?

BrUsbSIb.sys is for my Brother laser MFC-8890DW printer. These drivers are some years old but I downloaded them and reinstalled again. It is the same version as I had before.

What does one do about reportedly flaky drivers noted above? I have attached the ASUS related WinDbg as that one may be of particular interest to others, but I struggle to see how they are related to the OP report as they have never featured until I set out to trap them. Worth putting a report in to ASUS? I would rather I had a rock solid system and see if I can trap the sucker then, before putting in reports that may have a spurious cause.

I am hoping sfc fixed my issues....

PS: I see there are reports of a virus disguising itself as dwm.exe - that is not me as none of the related AppData files are to be found. I also have pretty good discipline in this arena, although am taking the MSE / Windows Defender "solution" as my protection, such as it is but so far so good, apparently anyway!

OK re dwm.exe it just ramped up when I opened Outlook 2013. Probably this has been the cause all along. Closing Outlook doesn't fix it. I have just disabled graphic hardware acceleration in Outlook Advanced settings so will see what that does after a reboot.

Also I have re-run sfc twice now - once in safe mode during the verifier adventure. It has come back clean each time. Interesting that it doesn't complain about the "you need a Win 10 Upgrade" stuff I deleted and GWX control panel assures me is still gone!

I am sneaking up on resolving this problem. As with any unguided resolution one does a lot of things, not all remembered or documented. I am pretty sure removing Intel Rapid Store technology has been the critical change here. Another thing I did is remove all .net framework versions then reinstall them. Neither of these things are straightforward to do, but there are some great guides via Google.

But I did also uninstall anything that looked like bloatware from ASUS, and I also turned off the Thunderbolt controller via BIOS and uninstalled all related software. Even so I still found things via msconfig that didn't look useful so shut them down too.

Not marking this as solved yet as I am not convinced it is. I have had a number of other bsods in the interim but didn't report here due to the not-so-deafening assistance responding to earlier posts. Also I earlier reported Memtest had gone two full cycles and come up clear - as it happened I was mistaken then, but it has since. This takes 8 hrs to do, but zero errors. I note the RAM I have is not actually on ASUS list, and consequently it is running at 2133 not 3466 nameplate (and does O/C fail if I force it) and just this by itself may be my issue, although I doubt it.

OK I am calling out Intel Rapid Store Technology as the culprit here, with a slight possibility it was the bluetooth drivers as they reportedly have known compatibility issues with Office. I deleted bluetooth and wireless features of the mobo as I have a perfectly good whole of house wireless system and the PC is LAN connected by the rather useful dedicated 10Gb card that comes with the mobo.

My issues are not over as now there are 5 MSO updates that refuse to install due to the infamous WU unknown 80070663 error and/or "an error occurred while running detection" on running the full KB download. That remains a work in progress as it seems nobody has a reliable solution to this nonsense, and hiding the offending updates is pretty tempting!

For anyone remotely interested, the following are the ones that won't install, everything else is good:

Security Update for Microsoft Office 2013 (KB3115016) 64-Bit Edition
Security Update for Microsoft Publisher 2013 (KB3085561) 64-Bit Edition
Security Update for Skype for Business 2015 (KB3039779) 64-Bit Edition
Security Update for Microsoft Word 2013 (KB3115173) 64-Bit Edition
Update for Microsoft Office 2013 (KB3115167) 64-Bit Edition

While I have no idea what I did to change the situation that previously some / all of these KB's would install and create bsods to now when they won't but no bsods, that remains my problem to solve. However when you compare this list with the OP you can see that 4 previously proven offenders have now installed and 2 new items have joined the party.

SFC /scannow still comes up clean. Interestingly the "Change" option for Microsoft Office Repair doesn't work, as in the window launches then closes without error and nobody is reporting this issue anywhere I can find via Google so an Office reinstall is looking like the next viable solution, complete with a forensic uninstall I expect.