Desktop Window Manager has stopped working after 10/12/10 MS updates loaded

After downloading and installing the 10/12/10 Windows Updates patches, Desktop Window Manager has stopped working.  Event Viewer lists the following under Applications:

Name:      Application
Source:        Application Error
Date:          10/13/2010 9:59:47 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      A
Description:
Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: nvwgf2umx.dll, version: 8.17.12.5922, time stamp: 0x4c5424d5
Exception code: 0xc0000005
Fault offset: 0x000000000007c160
Faulting process id: 0xb0c
Faulting application start time: 0x01cb6aefa117a51c
Faulting application path: C:\Windows\system32\Dwm.exe
Faulting module path: C:\Windows\system32\nvwgf2umx.dll
Report Id: e6dfd048-d6e2-11df-9660-00271383b7fe

The OS is Win 7 x64.  Video card is a Gigabyte GTS450OC1 with their latest driver running on an Intel DP55KG mb with 8 gb of Corsair XMS3 memory.  The system was fully functional and stable immediately prior to the update.  I'm not sure which of the 18 patches is conflicting with the nvwgf2umx.dll file.  Device Manager reports no hardware problems with any component.

In my attempts to fix the problem, I've run chkdsk /f, sfc /scannow (which reported no problems), and reloaded the video driver (without uninstalling it first).   Nothing works so far.  I even tried defragging the Master File Table with Diskeeper 2010 Boot Time Defragger (based on another post I found), also to no avail.

What's the fix for this? 

Answer
Answer
This may seem like the most janky thing to post, but I had the same error for the past several months:

 Problem Event Name: APPCRASH
  Application Name: Dwm.exe
  Application Version: 6.1.7600.16385
  Application Timestamp: 4a5bc541
  Fault Module Name: nvwgf2umx.dll
  Fault Module Version: 9.18.13.1422
  Fault Module Timestamp: 51427a68
  Exception Code: c0000005
  Exception Offset: 000000000013fe0b
  OS Version: 6.1.7601.2.1.0.256.1
  Locale ID: 1033
  Additional Information 1: bd9d
  Additional Information 2: bd9dfb84ef7bbf0c089fd3d5f079469b
  Additional Information 3: ec39
  Additional Information 4: ec39233315f018bea3fd5d4de7e9458f

And couldn't unregister/reregister the dll as it error'd out on a missing entry-point or whatever.

So what for some reason worked for me is renaming C:\Windows\System32\nvwgf2umx.dll to nvwgf2umx.dll.bak (all other copies of this file were in the DriverStore folder).

After that, I ran from an administrator command prompt
net stop uxsms
net start uxsms

And through some miracle everything started working again.  I'm running a GTX570 with the latest nvidia drivers as of writing.

Note:  You probably shouldn't be moving/renaming things in System32 unless you are confident and have your data backed up.  This worked for me, but who knows for you.

11 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

 
 

Question Info


Last updated December 8, 2018 Views 22,711 Applies to: