HELP NEEDED! Win7 DWM.EXE issues upon install any m$ rollup of 2018

Assurancetaurix

well, well, well... there are some progress from m$ in Aug 2018 Rollup support.microsoft.com/en-us/help/4343900

due to some acknowledged mess with AMD CPUs m$ updated its both win7 integrated CPU drivers intelppm.sys & Processr.sys from v6.1.7600.16385 to v6.1.7601.24214. however more changes seem done into Processr.sys and now if you change your Intel CPU driver from its default intelppm.sys to Processr.sys then there are no more dwm.exe issues...

actually the trick is a simple one:

1) change the CPU driver thru device manger driver update to the 2nd listed as Processr.sys and it will keep your CPU frequency at its max specified value by itself; or
2) you can still use the default Intel CPU driver intelppm.sys but is such case you must keep a multiplier of your CPU frequency at its maximum, and you can easily do it thru a laptop power plan advanced settings by changing min state of CPU from its default 5% to 100% or do actually same by use of Core Parking utility as above - to move a slider for frequency to the right from default 5% to 100%.

that's all.

p.s. basically your don't need that Core Parking utility anymore. however if/when you'll remove it pls don't forget to return its CPU parking value set manually to its default value as 10% (at least 10% was default in my case of 2 laptops + 1 desktop)

p.p.s report results here.

hansduif

well, now you can enjoy September 11, 2018—KB4457144 (Monthly Rollup) support.microsoft.com/en-us/help/4457144 that includes IE11 v11.0.85 OR September 11, 2018—KB4457145 (Security-only update) support.microsoft.com/en-us/help/4457145 on absolutely same prerequisite condition - CPU Min state must be set to 100% instead of its default value as 5%, which is equal to setting of its frequency to 100% or a frequency multiplier to Max.

however, all this jazz is clearly the problem of m$ rollups 2018 and m$ yet did nothing to resolve this issue thru 9 months of 2018 almost passed by...

thus, shall I end up this my brief summary as usual - F*CKKKKKK M$!


UPDATE: it has been tested that 50% as min cpu state seems enough to be on safe side concerning dwm.exe crashes... if it matters after all...

although maybe it's worth to mention here that:

I'm still using win7 pagefile size as Recommended i.e. the visible by win7 RAM x 1.5

and the Spectre-Meltdown protection win7 registry keys as:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
"FeatureSettingsOverride"=dword:00000008
"FeatureSettingsOverrideMask"=dword:00000003

on all of my win7 machines under testing.

rgds,


P.S. m$ has updated both win7 integrated CPU drivers as above twice thru Sep2018:

Sep 2018 full rollup - up from V6.1.7601.24214 to V6.1.7601.24231
Sep 2018 Preview - up from V6.1.7601.24231 to V6.1.7601.24236

but the dwm.exe issues tested as remaining unresolved if CPU Min state is set to default 5%!

Am back to testing here. I just installed the 10-2018 October roll-up. I did not do anything yet, like change the CPU driver or the power plan. Also did not install the Core Parking utility. Everything plain default Windows + updates.

After just a few minutes the first DWN 9020 crash. I now changed the Min CPU setting to 50 % as mentioned by you in the update. Let's wait and I will report back.

Can you, please, expand a little on the Spectre-Meltdown registry settings, Which value effects what patch ?

Update: Nope, 50 % is not enough. Increasing to 100%

Can you, please, expand a little on the Spectre-Meltdown registry settings, Which value effects what patch ?

Pls refer to z official m$ details here:

support.microsoft.com/en-us/help/4073119/protect-against-speculative-execution-side-channel-vulnerabilities-in

If I encounter a further DWM crash also at 60% I will report it here.

Still I consider this fix a dirty trick. It completely defies the Intel SpeedStep technology. My fan is now almost always on.

Your cpu tested min as 60% vs mine 50% is likely due to your win7 pagefile auto settings = default. Pls try to change it from Auto = win7 visible RAM x 1 to Recommended = win7 visible RAM x 1.5. All about pagefile size has been already discussed here earlier.

When your cpu is now (after applying any of 2018 rollup or preview) heavier loaded and you can do nothing with this common problem, the only thing you can do is a try to reduce this cpu load a bit in someway by increasing a size of pagefile aimed to make sending the system pages from cpu to pagefile and backwards a bit easier. Me comprenez-vous?

p.s. November 13, 2018—KB4467107 (Monthly Rollup) support.microsoft.com/en-us/help/4467107 seems pretty nice but don't forget to install the latest servicing stack update (SSU) prior to its install:
support.microsoft.com/en-us/help/3177467/servicing-stack-update-for-windows-7-sp1-and-windows-server-2008-r2-sp

Here m$ has again updated both win7 integrated CPU drivers & Ntoskrnl.exe to V6.1.7601.24291 but the dwm.exe issues tested as remaining unresolved if CPU Min state is less than 50%!

p.p.s As for your 'dirty trick' so pls offer something better, or you can optionally buy a control share of m$ corp and then screw up all its bigwigs for an idiocy.