Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


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

12 May 2018   #1
laidbacktokyo

Windows 7 Ultimate x64 SP1u OEM Dell & OEM Asus
 
 
HELP NEEDED! Win7 DWM.EXE issues upon install any m$ rollup of 2018

Howdy,

Here is a copy of my post @ m$ support forum. Of course it's the unanswered one:

This dwm.exe issue is confirmed to be just another trouble directly from m$ due to the complete mess with a recent years m$ updating, and it affects yet all m$ 2018 massive patches known as rollups & previews at least if installed on win7sp1x64ultimate!

So ANY of these now minimum 7 consecutive m$ updates starting from January 2018 is plagued by this annoying problem - at least on computers with older hardware (CPU & video card) , although with a nice remedy as a simple uninstall of the known culprit.

1.Technically if any 2018 rollup/preview patch installed dwm.exe process performs abnormally and crashes/restarts when acquired some 28MB of its size accompanying by Error ID 9020 – 'The Desktop Window Manager has encountered a fatal error (0x8898009b)' coupled with an info record 'The Desktop Window Manager has exited with code (0x8898009b)' and even occasional screen crashes!

2. Another side effect of this incorrect operation of dwm.exe process, when it's close to some its unclear critical point like 28MB in size, is the 2nd issue as leftovers in taskbar of already closed windows . Please refer to a snapshot below where Registry Editor & Notepad windows are actually closed.




Please consider this message as the official complain to m$ when now I yet can't install any of m$ massive patches 2018 on my 3 genuine win7 laptops around. Also please refer to my currently hidden updates list as below:




Thank you.

Rgds,

A link to original posted in April: https://answers.microsoft.com/en-us/...f-0f4e73856999

Well, now I've tested also May 8, 2018—KB4103718 (Monthly Rollup) as well as May 8, 2018—KB4103712 (Security-only update) and it's all same. These issues persisted as before - maybe less but persisted!

Moreover when dwm.exe is a critical win7 process & therefore not recommended for debagging by m$ SDK 7.1, 8.1, or 10 debugging tools (pls refer to https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx), although it's possible in general by adding to win7 registry a key add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\dwm.exe" /v debugger /t REG_SZ /d ""C:\Program Files\Debugging Tools for Windows (x64)\windbg.exe" -g ", but it returns no crash dumps but just screen crashes, then I've installed another debugger of m$ aka Debug Diagnostic Tool v2 Update 2 https://www.microsoft.com/en-us/down....aspx?id=49924 and short manual https://blogs.msdn.microsoft.com/cha...shing-process/

Well, no dwm.exe crash dumps again! However I got debugging logs with same process exit error 0x8898009b but also a list of files involved like attached below.

Log#1:

Quote:
Loading control script C:\Program Files\DebugDiag\scripts\CrashRule_Process_dwm.exe.vbs
DumpPath set to D:\...skipped...\Logs\Crash rule for dwm.exe
[5/11/2018 7:30:45 PM]
Process created. BaseModule - C:\Windows\system32\Dwm.exe. BaseThread - System ID: 2556
C:\Windows\SYSTEM32\ntdll.dll loaded at 0x77340000
Thread created. New thread - System ID: 2704
Thread created. New thread - System ID: 2708
Thread created. New thread - System ID: 2940
Thread created. New thread - System ID: 2944
C:\Windows\system32\kernel32.dll loaded at 0x77120000
C:\Windows\system32\KERNELBASE.dll loaded at 0xfd250000
C:\Windows\system32\GDI32.dll loaded at 0xfd850000
C:\Windows\system32\USER32.dll loaded at 0x77240000
C:\Windows\system32\LPK.dll loaded at 0xfd710000
C:\Windows\system32\USP10.dll loaded at 0xfd640000
C:\Windows\system32\msvcrt.dll loaded at 0xfdcd0000
C:\Windows\system32\UxTheme.dll loaded at 0xfb3c0000
C:\Windows\system32\IMM32.dll loaded at 0xff4f0000
C:\Windows\system32\MSCTF.dll loaded at 0xff520000
C:\Windows\system32\dwmredir.dll loaded at 0xf8100000
C:\Windows\system32\dwmcore.dll loaded at 0xf6a70000
C:\Windows\system32\ADVAPI32.dll loaded at 0xfd560000
C:\Windows\SYSTEM32\sechost.dll loaded at 0xfe470000
C:\Windows\system32\RPCRT4.dll loaded at 0xfe140000
C:\Windows\system32\WindowsCodecs.dll loaded at 0xfae50000
C:\Windows\system32\ole32.dll loaded at 0xfe270000
C:\Windows\system32\d3d10_1.dll loaded at 0xf80c0000
C:\Windows\system32\d3d10_1core.dll loaded at 0xf8060000
C:\Windows\system32\dxgi.dll loaded at 0xf6a10000
C:\Windows\system32\VERSION.dll loaded at 0xfbef0000
C:\Windows\system32\dwmapi.dll loaded at 0xfb000000
C:\Windows\system32\d3d11.dll loaded at 0xf6730000
C:\Windows\system32\WINTRUST.dll loaded at 0xfd1e0000
C:\Windows\system32\CRYPT32.dll loaded at 0xfd070000
C:\Windows\system32\MSASN1.dll loaded at 0xfd010000
C:\Windows\system32\nvwgf2umx.dll loaded at 0xf33a0000
C:\Windows\system32\uDWM.dll loaded at 0xf64f0000
C:\Windows\system32\slc.dll loaded at 0xfa8b0000
C:\Program Files (x86)\ABBYY Lingvo x5\LvHook64.dll loaded at 0x80000000
C:\Program Files (x86)\ABBYY Lingvo x5\Detoured64.dll loaded at 0xe89b0000
C:\Windows\system32\OLEAUT32.dll loaded at 0xfd8c0000
C:\Windows\system32\MSIMG32.dll loaded at 0xfa2f0000
C:\Windows\system32\USERENV.dll loaded at 0xfd380000
C:\Windows\system32\profapi.dll loaded at 0xfd020000
C:\Windows\system32\SHELL32.dll loaded at 0xfe490000
C:\Windows\system32\SHLWAPI.dll loaded at 0xfd720000
Thread created. New thread - System ID: 8544
Initializing control script
Clearing any existing breakpoints

Current Breakpoint List(BL)
Thread exited. Exiting thread - System ID: 8544. Exit code - 0x00000000
[5/11/2018 7:33:43 PM]
C:\Windows\system32\setupapi.dll loaded at 0xfdd70000
C:\Windows\system32\CFGMGR32.dll loaded at 0xfd030000
[5/11/2018 7:33:44 PM]
C:\Windows\system32\DEVOBJ.dll loaded at 0xfd3b0000
C:\Windows\system32\setupapi.dll Unloaded from 0xfdd70000
C:\Windows\system32\DEVOBJ.dll Unloaded from 0xfd3b0000
C:\Windows\system32\CFGMGR32.dll Unloaded from 0xfd030000
C:\Windows\system32\nvwgf2umx.dll Unloaded from 0xf33a0000
Thread exited. Exiting thread - System ID: 2944. Exit code - 0x8898009b
Thread exited. Exiting thread - System ID: 2940. Exit code - 0x8898009b
Thread exited. Exiting thread - System ID: 2708. Exit code - 0x8898009b
Thread exited. Exiting thread - System ID: 2556. Exit code - 0x8898009b
Process exited. Exit code - 0x8898009b
Debugging Overhead Cost:
Total Elapsed Ticks = 179276 (100%)
Total Ticks Spent in Debugger Engine = 624 (0%)
Total Ticks Spent in Crash Rule Script = 233 (0%)
Log#2:

Quote:
Loading control script C:\Program Files\DebugDiag\Scripts\CrashRule_Process_dwm.exe.vbs
DumpPath set to D:\....skipped...\Logs\Crash rule for dwm.exe
[5/11/2018 7:33:44 PM]
Process created. BaseModule - C:\Windows\system32\Dwm.exe. BaseThread - System ID: 9036
C:\Windows\SYSTEM32\ntdll.dll loaded at 0x77340000
C:\Windows\system32\kernel32.dll loaded at 0x77120000
C:\Windows\system32\KERNELBASE.dll loaded at 0xfd250000
C:\Windows\system32\GDI32.dll loaded at 0xfd850000
C:\Windows\system32\USER32.dll loaded at 0x77240000
C:\Windows\system32\LPK.dll loaded at 0xfd710000
C:\Windows\system32\USP10.dll loaded at 0xfd640000
C:\Windows\system32\msvcrt.dll loaded at 0xfdcd0000
C:\Windows\system32\UxTheme.dll loaded at 0xfb3c0000
C:\Windows\system32\IMM32.dll loaded at 0xff4f0000
C:\Windows\system32\MSCTF.dll loaded at 0xff520000
C:\Windows\system32\dwmredir.dll loaded at 0xf8100000
C:\Windows\system32\dwmcore.dll loaded at 0xf6a70000
C:\Windows\system32\ADVAPI32.dll loaded at 0xfd560000
C:\Windows\SYSTEM32\sechost.dll loaded at 0xfe470000
C:\Windows\system32\RPCRT4.dll loaded at 0xfe140000
C:\Windows\system32\WindowsCodecs.dll loaded at 0xfae50000
C:\Windows\system32\ole32.dll loaded at 0xfe270000
C:\Windows\system32\d3d10_1.dll loaded at 0xf41b0000
C:\Windows\system32\d3d10_1core.dll loaded at 0xf8060000
C:\Windows\system32\dxgi.dll loaded at 0xf6a10000
C:\Windows\system32\VERSION.dll loaded at 0xfbef0000
C:\Windows\system32\dwmapi.dll loaded at 0xfb000000
C:\Windows\system32\d3d11.dll loaded at 0xf6730000
Thread created. New thread - System ID: 2372
Initializing control script
Clearing any existing breakpoints

Current Breakpoint List(BL)
[5/11/2018 7:33:45 PM]
Thread exited. Exiting thread - System ID: 2372. Exit code - 0x00000000
Thread created. New thread - System ID: 9192
Thread created. New thread - System ID: 8856
Thread created. New thread - System ID: 3160
Thread created. New thread - System ID: 9120
C:\Program Files (x86)\ABBYY Lingvo x5\LvHook64.dll loaded at 0x80000000
C:\Program Files (x86)\ABBYY Lingvo x5\Detoured64.dll loaded at 0xe89b0000
C:\Windows\system32\OLEAUT32.dll loaded at 0xfd8c0000
C:\Windows\system32\MSIMG32.dll loaded at 0xfa2f0000
C:\Windows\system32\USERENV.dll loaded at 0xfd380000
C:\Windows\system32\profapi.dll loaded at 0xfd020000
C:\Windows\system32\SHELL32.dll loaded at 0xfe490000
C:\Windows\system32\SHLWAPI.dll loaded at 0xfd720000
C:\Windows\system32\POWRPROF.DLL loaded at 0xfb470000
C:\Windows\system32\SETUPAPI.dll loaded at 0xfdd70000
C:\Windows\system32\CFGMGR32.dll loaded at 0xfd030000
C:\Windows\system32\DEVOBJ.dll loaded at 0xfd3b0000
C:\Windows\system32\POWRPROF.DLL Unloaded from 0xfb470000
C:\Windows\system32\SETUPAPI.dll Unloaded from 0xfdd70000
C:\Windows\system32\DEVOBJ.dll Unloaded from 0xfd3b0000
C:\Windows\system32\CFGMGR32.dll Unloaded from 0xfd030000
C:\Windows\system32\POWRPROF.DLL loaded at 0xfb470000
C:\Windows\system32\SETUPAPI.dll loaded at 0xfdd70000
C:\Windows\system32\CFGMGR32.dll loaded at 0xfd030000
C:\Windows\system32\DEVOBJ.dll loaded at 0xfd3b0000
C:\Windows\system32\POWRPROF.DLL Unloaded from 0xfb470000
Thread exited. Exiting thread - System ID: 3160. Exit code - 0x00000000
C:\Windows\system32\WINTRUST.dll loaded at 0xfd1e0000
C:\Windows\system32\CRYPT32.dll loaded at 0xfd070000
C:\Windows\system32\MSASN1.dll loaded at 0xfd010000
C:\Windows\system32\SETUPAPI.dll Unloaded from 0xfdd70000
C:\Windows\system32\DEVOBJ.dll Unloaded from 0xfd3b0000
C:\Windows\system32\CFGMGR32.dll Unloaded from 0xfd030000
C:\Windows\system32\nvwgf2umx.dll loaded at 0xd2760000
C:\Windows\system32\nvwgf2umx.dll Unloaded from 0xd2760000
C:\Windows\system32\nvwgf2umx.dll loaded at 0xd1910000
C:\Windows\system32\nvwgf2umx.dll Unloaded from 0xd1910000
C:\Windows\system32\nvwgf2umx.dll loaded at 0xd2760000
Thread exited. Exiting thread - System ID: 9120. Exit code - 0x00000000
Thread created. New thread - System ID: 8512
C:\Windows\system32\uDWM.dll loaded at 0xf64f0000
C:\Windows\system32\slc.dll loaded at 0xfa8b0000
Thread created. New thread - System ID: 4832
[5/11/2018 7:34:15 PM]
Thread created. New thread - System ID: 9004
Thread created. New thread - System ID: 7284
[5/11/2018 7:35:22 PM]
Thread exited. Exiting thread - System ID: 9004. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 7284. Exit code - 0x00000000
Skipping exception event during detach/reload
Request to reload script recieved. Loading control script C:\Program Files\DebugDiag\Scripts\CrashRule_Process_dwm.exe.vbs
Loading control script C:\Program Files\DebugDiag\scripts\CrashRule_Process_dwm.exe.vbs
DumpPath set to D:\...skipped...\Logs\Crash rule for dwm.exe
[5/11/2018 7:36:45 PM]
Initializing control script
Clearing any existing breakpoints

Current Breakpoint List(BL)
[5/11/2018 9:01:01 PM]
Thread created. New thread - System ID: 8456
Thread created. New thread - System ID: 9440
[5/11/2018 9:01:13 PM]
C:\Windows\system32\setupapi.dll loaded at 0xfdd70000
C:\Windows\system32\CFGMGR32.dll loaded at 0xfd030000
C:\Windows\system32\DEVOBJ.dll loaded at 0xfd3b0000
C:\Windows\system32\setupapi.dll Unloaded from 0xfdd70000
C:\Windows\system32\DEVOBJ.dll Unloaded from 0xfd3b0000
C:\Windows\system32\CFGMGR32.dll Unloaded from 0xfd030000
Thread created. New thread - System ID: 2520
Thread exited. Exiting thread - System ID: 4832. Exit code - 0x8898009b
Thread exited. Exiting thread - System ID: 9440. Exit code - 0x8898009b
Thread exited. Exiting thread - System ID: 2520. Exit code - 0x8898009b
Thread exited. Exiting thread - System ID: 8456. Exit code - 0x8898009b
Thread exited. Exiting thread - System ID: 8856. Exit code - 0x8898009b
Thread exited. Exiting thread - System ID: 9036. Exit code - 0x8898009b
Thread exited. Exiting thread - System ID: 9192. Exit code - 0x8898009b
Process exited. Exit code - 0x8898009b
Debugging Overhead Cost:
Total Elapsed Ticks = 5249012 (100%)
Total Ticks Spent in Debugger Engine = 421 (0%)
Total Ticks Spent in Crash Rule Script = 265 (0%)
Log#3:

Quote:
Loading control script C:\Program Files\DebugDiag\Scripts\CrashRule_Process_dwm.exe.vbs
DumpPath set to D:\....skipped....\Logs\Crash rule for dwm.exe
[5/11/2018 9:01:14 PM]
Process created. BaseModule - C:\Windows\system32\Dwm.exe. BaseThread - System ID: 9740
C:\Windows\SYSTEM32\ntdll.dll loaded at 0x77340000
Thread created. New thread - System ID: 4048
Thread created. New thread - System ID: 9264
Thread created. New thread - System ID: 9004
C:\Windows\system32\verifier.dll loaded at 0xf4180000
C:\Windows\system32\kernel32.dll loaded at 0x77120000
C:\Windows\system32\KERNELBASE.dll loaded at 0xfd250000
C:\Windows\system32\GDI32.dll loaded at 0xfd850000
C:\Windows\system32\USER32.dll loaded at 0x77240000
C:\Windows\system32\LPK.dll loaded at 0xfd710000
C:\Windows\system32\USP10.dll loaded at 0xfd640000
C:\Windows\system32\msvcrt.dll loaded at 0xfdcd0000
C:\Windows\system32\UxTheme.dll loaded at 0xfb3c0000
C:\Windows\system32\IMM32.dll loaded at 0xff4f0000
C:\Windows\system32\MSCTF.dll loaded at 0xff520000
C:\Windows\system32\dwmredir.dll loaded at 0xf8100000
C:\Windows\system32\dwmcore.dll loaded at 0xf6a70000
C:\Windows\system32\ADVAPI32.dll loaded at 0xfd560000
C:\Windows\SYSTEM32\sechost.dll loaded at 0xfe470000
C:\Windows\system32\RPCRT4.dll loaded at 0xfe140000
C:\Windows\system32\WindowsCodecs.dll loaded at 0xfae50000
C:\Windows\system32\ole32.dll loaded at 0xfe270000
C:\Windows\system32\d3d10_1.dll loaded at 0xf6c50000
C:\Windows\system32\d3d10_1core.dll loaded at 0xf8060000
C:\Windows\system32\dxgi.dll loaded at 0xf6a10000
C:\Windows\system32\VERSION.dll loaded at 0xfbef0000
C:\Windows\system32\dwmapi.dll loaded at 0xfb000000
C:\Windows\system32\d3d11.dll loaded at 0xf6730000
C:\Program Files (x86)\ABBYY Lingvo x5\LvHook64.dll loaded at 0x80000000
C:\Program Files (x86)\ABBYY Lingvo x5\Detoured64.dll loaded at 0xe89b0000
C:\Windows\system32\OLEAUT32.dll loaded at 0xfd8c0000
C:\Windows\system32\MSIMG32.dll loaded at 0xfa2f0000
C:\Windows\system32\USERENV.dll loaded at 0xfd380000
C:\Windows\system32\profapi.dll loaded at 0xfd020000
C:\Windows\system32\SHELL32.dll loaded at 0xfe490000
C:\Windows\system32\SHLWAPI.dll loaded at 0xfd720000
C:\Windows\system32\WINTRUST.dll loaded at 0xfd1e0000
C:\Windows\system32\CRYPT32.dll loaded at 0xfd070000
C:\Windows\system32\MSASN1.dll loaded at 0xfd010000
Thread created. New thread - System ID: 10852
Initializing control script
Clearing any existing breakpoints

Current Breakpoint List(BL)
Thread exited. Exiting thread - System ID: 10852. Exit code - 0x00000000
C:\Windows\system32\nvwgf2umx.dll loaded at 0xd1490000
C:\Windows\system32\nvwgf2umx.dll Unloaded from 0xd1490000
C:\Windows\system32\nvwgf2umx.dll loaded at 0xd2760000
C:\Windows\system32\nvwgf2umx.dll Unloaded from 0xd2760000
C:\Windows\system32\nvwgf2umx.dll loaded at 0xd1490000
Thread exited. Exiting thread - System ID: 9004. Exit code - 0x00000000
Thread created. New thread - System ID: 8556
C:\Windows\system32\uDWM.dll loaded at 0xf64f0000
C:\Windows\system32\slc.dll loaded at 0xfa8b0000
Thread created. New thread - System ID: 8120
[5/11/2018 9:01:44 PM]
Thread created. New thread - System ID: 9904
Thread created. New thread - System ID: 9824
[5/11/2018 9:02:51 PM]
Thread exited. Exiting thread - System ID: 9904. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 9824. Exit code - 0x00000000
Skipping exception event during detach/reload
Request to reload script recieved. Loading control script C:\Program Files\DebugDiag\Scripts\CrashRule_Process_dwm.exe.vbs
Loading control script C:\Program Files\DebugDiag\scripts\CrashRule_Process_dwm.exe.vbs
DumpPath set to D:\...skipped....\Logs\Crash rule for dwm.exe
[5/11/2018 9:09:31 PM]
Initializing control script
Clearing any existing breakpoints

Current Breakpoint List(BL)
[5/11/2018 9:46:13 PM]
C:\Windows\system32\setupapi.dll loaded at 0xfdd70000
C:\Windows\system32\CFGMGR32.dll loaded at 0xfd030000
C:\Windows\system32\DEVOBJ.dll loaded at 0xfd3b0000
C:\Windows\system32\setupapi.dll Unloaded from 0xfdd70000
C:\Windows\system32\DEVOBJ.dll Unloaded from 0xfd3b0000
C:\Windows\system32\CFGMGR32.dll Unloaded from 0xfd030000
Thread exited. Exiting thread - System ID: 9264. Exit code - 0x8898009b
Thread exited. Exiting thread - System ID: 9740. Exit code - 0x8898009b
Thread exited. Exiting thread - System ID: 8120. Exit code - 0x8898009b
Thread exited. Exiting thread - System ID: 8556. Exit code - 0x8898009b
Process exited. Exit code - 0x8898009b
Debugging Overhead Cost:
Total Elapsed Ticks = 2699473 (100%)
Total Ticks Spent in Debugger Engine = 203 (0%)
Total Ticks Spent in Crash Rule Script = 299 (0%)
Can anybody experienced be so kind to point me on a potential culprit or at least suspect? If it's possible after all.

Appreciate!

P.S. Of course an easy answer is that it's surely one of win7 critical files like ntdll.dll etc listed, and all updated to v6.1.7601.24117 2018-04-23-Mon 9:00AM comparing to v6.1.7601.23915 of Dec2017 rollup by either KB4103712 or KB4103718 but in this case it seems here is no solution except removal of rollup.

P.P.S. It's not a NVidia driver problem when I've tested various ones including the latest applicable from nVidia.


My System SpecsSystem Spec
.
12 May 2018   #2
Snick

Win 10 x64, Linux Lite, Win 7 x64, BlackArch, Kali, VMWare Workstation Player, OpenVPN
 
 

Hi laidbacktokyo,

Excellent tutorial by Jonathan_King, run it!

How to Enable or Disable Driver Verifier in Windows 7

Also see this post on your issue

dwm.exe (0.0000006) error on startup

Curious: Try running SURT tool
logs at:
C:\Windows\Logs\CBS
CheckSUR.log open in notepad, it there are errors, errors not fixed, post please. If not just indicate no errors.



Nic
My System SpecsSystem Spec
13 May 2018   #3
laidbacktokyo

Windows 7 Ultimate x64 SP1u OEM Dell & OEM Asus
 
 

Howdy Nick,

Thanks for your kind attention to this odd m$ stuff!

1. A tutorial

A Driver Signature Verifying is always disabled on my win7 machines:

Quote:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\...>bcdedit
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume3
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {ed411ce2-9c20-11e5-bb6e-d63dea0cb483}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 0
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
loadoptions DISABLE_INTEGRITY_CHECKS
inherit {bootloadersettings}
recoverysequence {ed411ce8-9c20-11e5-bb6e-d63dea0cb483}
recoveryenabled Yes
testsigning Yes
osdevice partition=C:
systemroot \Windows
resumeobject {ed411ce2-9c20-11e5-bb6e-d63dea0cb483}
nx OptIn
usefirmwarepcisettings No
useplatformclock Yes
C:\Users\...>
2. A link to post regarding like my issue

Sorry it's incorrect - my error code is different. It matters!

As for win7 repair install so I'm familiar with howto but don't think it's a right time to repair well working win7 install due to this m$ mess with rollups 2018 only, when I can easily get rid of this issues just by removal of rollup!

BTW, the latest good rollup is of Dec2017 - AMD64-all-windows6.1-kb4054518-x64.msu and it's installed now.

3. Thanks for idea to check my win7 install with windows update readiness tool Windows6.1-KB947821-v34-x64.msu. Actually I never consider this option.

Anyhow here is a result of initial scan:

Quote:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-05-13 18:48
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Payload File Missing 0x00000000 cng.sys amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.24117_none_04fce0048c860966
(f) CSI Payload File Missing 0x00000000 InetRes.adml amd64_microsoft-windows-inetres-adm.resources_31bf3856ad364e35_11.2.9600.18952_en-us_51c2734892af7288
(fix) CSI Payload File Missing CSI File Replaced File: InetRes.adml From: C:\Windows\winsxs\amd64_microsoft-windows-inetres-adm.resources_31bf3856ad364e35_11.2.9600.18837_en-us_51cad0b892a9a40e\InetRes.adml
(f) CSI Payload File Missing 0x00000000 cng.sys amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.23915_none_04fb05688c87a64f
(f) CSI Payload File Missing 0x00000000 InetRes.adml amd64_microsoft-windows-inetres-adm.resources_31bf3856ad364e35_11.2.9600.18860_en-us_51ce710e92a63cac
(fix) CSI Payload File Missing CSI File Replaced File: InetRes.adml From: C:\Windows\winsxs\amd64_microsoft-windows-inetres-adm.resources_31bf3856ad364e35_11.2.9600.18837_en-us_51cad0b892a9a40e\InetRes.adml
Summary:
Seconds executed: 269
Found 4 errors
Fixed 2 errors
CSI Payload File Missing Total count: 4
Fixed: CSI Payload File Missing. Total count: 2
and then I've managed to repair 2 missed files:

Quote:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-05-13 23:48
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 312
No errors detected
Unfortunately this doesn't help either when the problem persists!

More ideas?

Thank you.
My System SpecsSystem Spec
.

13 May 2018   #4
Snick

Win 10 x64, Linux Lite, Win 7 x64, BlackArch, Kali, VMWare Workstation Player, OpenVPN
 
 

Out of relevant one for now, more researching though! I don't give up easily!
My System SpecsSystem Spec
11 Jun 2018   #5
laidbacktokyo

Windows 7 Ultimate x64 SP1u OEM Dell & OEM Asus
 
 

Well, well, well... Here are a bit more details on this dwm.exe issues based on extensive testing of May 17, 2018—KB4103713 (Preview of Monthly Rollup) https://support.microsoft.com/en-us/help/4103713 installed right over December 12, 2017—KB4054518 (Monthly Rollup) https://support.microsoft.com/en-us/help/4054518, which in its turn is clearly confirmed to be the yet last good rollup as absolutely free of these issues.

And it's clearly confirmed that these issues plague ONLY laptops with old NVidia (and likely ATI) videocards of nowadays small amounts of dedicated memory onboard like 256MB and/or 512MB, and/or old Intel chipsets like 965 series. Such videocards are more likely involved than chipsets, although the problem could be linked to not updated in 2018 videodriver when NVidia unfortunately stopped further driver updating for older GPUs http://nvidia.custhelp.com/app/answers/detail/a_id/3473 and moreover changed the driver structure that made it now impossible to mod a R375/R390 of 2018 driver's .inf file and then install it on older hardware!

Also it's confirmed that a culprit is the already mentioned above in my initial post ntdll.dll revision v6.1.7601.24117 dated of 2018-04-23-Mon 9:00AM. And this file affects the heap memory management in some wrong way. Once I already described this problem here as now incorrect heap management:
https://www.********.com/forums/topi...s/#post-192531

oops, it seems sevenforums doesn't like ask woody com!

Moreover, I found the exactly applicable m$ hotfix for ntdll.dll KB2545627 https://support.microsoft.com/en-us/...in-windows-ser issued in earlier days of win7 to repair the similar problems as acknowledged by m$ those days as below, which is still accepted by win7 to be installed over current system state on KB4103713:

On a computer that is running Windows 7 or Windows Server 2008 R2, you use a multithreaded application that uses a heap. (This is literally matches dwm.exe status!) In this situation, the application might crash unexpectedly because of a race condition.

However this fix can't be a solution now when it doesn't replace ntdll.dll itself while install, when the current ntdll.dll is of later version than a one providing by hotfix.


Pls refer to attached snapshots taken from 3 PCs under testing by use of the System Internals Process Explorer utility aimed to see all actual processes/threads involved in dwm.exe performance:

1. Laptop#1 of Intel 965 chipset and integrated mobile NVidia Quadro FX 256MB GPU. It's surely affected by these dwn.exe issues! A snapshot status - KB4103713 installed + latest applicable NVidia R340 driver 342.01 of 2016 installed!

2. Laptop#2 of Intel 965 chipset and non-integrated mobile NVidia Quadro FX 512MB GPU. It's surely affected by these dwn.exe issues! A snapshot status - KB4103713 NOT installed + latest applicable NVidia R340 driver 342.01 of 2016 installed!

3. Desktop (!) with just a bit younger Intel chipset G43 and NVidia 4GB videocard. It's surely NOT affected by these dwn.exe issues! A snapshot status - KB4103713 installed + latest applicable NVidia R390 driver of 2018 installed!

UPDATE!

Same story on June 12, 2018—KB4284826 (Monthly Rollup) https://support.microsoft.com/en-us/help/4284826 or expectedly on June 12, 2018—KB4284867 (Security-only update) https://support.microsoft.com/en-us/help/4284867 both on ntdll.dll v6.1.7601.24150 2018-05-29-Tue 11:35AM

In short this problem can be summarized as a damaged interaction in-between m$ new 2018 ntdll.dll files and old NVidia driver components. Pls refer to snapshots below:
after any 2018 rollup installed like pic #1 or #3 then the thread between ntdll.dll & dwm.exe changed to ntdll.dll!RtllsCriticalSectionLockedByThread+0xc00 but with the new R390 2018 driver as of pic #3 the videodriver component nvwgf2umx.dll also involved. However this new scheme doesn't work on laptop #1 as of pic #1, which operates in same new style of interaction with ntdll.dll as ntdll.dll!RtllsCriticalSectionLockedByThread+0xc00 but w/o nvwgf2umx.dll support! And pic#2 refers to laptop #2 on Dec2017 rollup w/o any issues and the standard interaction with ntdll.dll as ntdll!TpIsTimerSet+0x8a0 prior to 2018 rollups' interaction change. However, if any 2018 rollup installed on laptop #2 it's all same problems as on pic#1 of laptop #1.


Attached Thumbnails
HELP NEEDED! Win7 DWM.EXE issues upon install any m$ rollup of 2018-2018-06-06-wed_m4300-laptop_sysinternalsprocessexplorer_dwm.exe_threads_may2018rolluppreviewinst.png   HELP NEEDED! Win7 DWM.EXE issues upon install any m$ rollup of 2018-2018-06-06-wed_m6300-laptop_sysinternalsprocessexplorer_dwm.exe_threads_no2018rollupsinstalled-.png   HELP NEEDED! Win7 DWM.EXE issues upon install any m$ rollup of 2018-2018-06-06-wed_asus-desktop_sysinternalsprocessexplorer_dwm.exe_threads_may2018rolluppreviewinst.png  
My System SpecsSystem Spec
21 Jun 2018   #6
Assurancetaurix

Windows 7 Ultimate x86
 
 

Thanks very much laidbacktokyo ! I have exactly the same problem. The graphics card in my notebook (NVidia) is also from an older generation but I cannot change it. I can also not upgrade to Windows 10 (even if I would want to do that) since there is no updated WiFi driver from Intel.

Looking at the problem as you diagnosed it, I do not think that MS will backtrack on this. That means that the solution will have to come from NVidia. The latest driver is from 2016.

The rollup and security-only updates cannot be split into individual updates, it seems, except for the IE11 update. That is KB4230450. I have installed that from MS Catalog. Works fine, no issue.

If nVidia does not provide a new driver I fear that this is the end of Windows 7 updates ! Could you perhaps copy your post in the nVidia support forum, please ?
My System SpecsSystem Spec
21 Jun 2018   #7
Megahertz07

Windows 7 HP 64
 
 

M$ rollups updates has given a lot trouble. I now install SP2 and then security only updates.
MS releases SP2 for Windows 7 - Windows 7 Help Forums
https://support.microsoft.com/en-us/...update-history

Have you tried to disable Aero and set Classic to see if the issue persists?
My System SpecsSystem Spec
21 Jun 2018   #8
Assurancetaurix

Windows 7 Ultimate x86
 
 

Thanks for your reaction. In fact, I did not think of disabling Aero. Did not think it could be in the list of suspects. I would not want to do that as a solution in any case.

However, I did uninstall the nVidia driver. Windows then reverts to the standard VGA driver. With this driver absolutely no problem. Everything fine. As soon as I re-install the nVidia driver (most recent for my graphics card) the DWM process starts crashing regularly.

What I do now is exactly what the TS explained above. I installed the latest good rollup, that is December 2017. Then added only the IE11 security update as I mentioned before. My system is now as stable as it was before for so many years. Any rollup from January 2018 onwards in combination with the same NVidia drivers makes DWM crash very frequently. That is totally unacceptable.

Thanks for the SP2 hint. I will have a look but I am skeptical that it would solve this problem in combination with the same nVidia driver.
My System SpecsSystem Spec
21 Jun 2018   #9
Megahertz07

Windows 7 HP 64
 
 

My System SpecsSystem Spec
22 Jun 2018   #10
laidbacktokyo

Windows 7 Ultimate x64 SP1u OEM Dell & OEM Asus
 
 

Assurancetaurix

First pls calm down & relax. These dwm.exe issues are neither end of life nor end of updating of win7. And it's neither a problem of ANY NVidia driver at all but just the m$ crap of 2018 due to all this hype around the newly introduced SpectreMeltdawn protection and the appropriate but not well done change in win7 memory management in general, and the heap memory in particular. Although it's a common pity that now we don't have an option of trying to update NVidia driver even just to check how a videodriver update can affect these issues.

These issues occur ONLY after install any of m$ rollups or previews (both full or security-only) of 2018 so you can easily install all other m$ updates except rollups/previews when offered if you wish to do so.

Also as far as I can see you did everything right so far. I mean your return of win7 to Dec2017 rollup state, which is confirmed to be free of these issues, and then install KB4230450 as IE11 latest update as standalone.

Well now pls make your win7 restore point and then install just in ordinary way thru win7 update center June 21, 2018—KB4284842 ( Preview of Monthly Rollup) https://support.microsoft.com/en-us/help/4284842 and due to the included fix of

Updates the Universal CRT to include parity with the Windows 10 Universal CRT build 10.0.14393.0.
Addresses an issue in which SmartHeap didn't work with UCRT.

your dwm.exe issues MAYBE will be resolved or partly resolved! And if not you'll be able to safely return on this created in advance restore point or just remove KB4284842 to get back on safe Dec2017 rollup + latest IE11 KB4230450.

Then prompt results here.

c ya,
My System SpecsSystem Spec
Reply

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




Thread Tools




Similar help and support threads
Thread Forum
Cannot install: 2018-02 Security Monthly Quality Rollup for Windows 7
Ever since February I've had this update pending but I just can't get it to install. Every time I try it gives me this: https://i.imgur.com/T4EgepN.png I used the MS update database and downloaded the update manually and tried to install it. Got this: https://i.imgur.com/Vm7v7DM.png
Windows Updates & Activation
May 8, 2018 - KB4103718 (Monthly Rollup) Windows 7
Source: https://support.microsoft.com/en-us/help/4103718 See also: https://support.microsoft.com/en-us/help/4095874/description-of-the-security-and-quality-rollup-for-net-framework-3-5-1 Direct download links for KB4103718 MSU file from Microsoft Update Catalog: :ar: Download KB4103718...
News
April 10, 2018—KB4093118 (Monthly Rollup) Keeps On Popping Up
April 10, 2018—KB4093118 (Monthly Rollup) has been installed now 6 times and still I am being offered the same update over & over again, what is going on? This has happened before if I recall correctly and I can't remember what the fix was, was it another update ? I'll run the troubleshooter to...
Windows Updates & Activation
February 13, 2018 - KB4074598 (Monthly Rollup) Windows 7
Source: https://support.microsoft.com/en-us/help/4074598 Direct download links for KB4074598 MSU file from Microsoft Update Catalog: :ar: Download KB4074598 MSU for Windows 7 32-bit (x86) - 137.1 MB :ar: Download KB4074598 MSU for Windows 7 64-bit (x64) - 233.9 MB
News
January 4, 2018 - KB4056894 (Monthly Rollup) Windows 7
Source: https://support.microsoft.com/en-us/help/4056894 Direct download links for KB4056894 MSU file from Microsoft Update Catalog: :ar: Download KB4056894 MSU for Windows 7 32-bit (x86) - 135.8 MB :ar: Download KB4056894 MSU for Windows 7 64-bit (x64) - 231.1 MB
News


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 23:11.
Twitter Facebook Google+