Help me diagnose why DWM.exe crashes at least once per day!

This is the message from Control Panel\System and Security\Security and Maintenance\Problem Details

Source
Desktop Window Manager

Summary
Stopped working

Date
‎Wed ‎09/‎12/‎2015 1:30 PM

Status
Report sent

Description
Faulting Application Path: C:\Windows\System32\dwm.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: dwm.exe
Application Version: 10.0.10586.0
Application Timestamp: 5632d756
Fault Module Name: combase.dll
Fault Module Version: 10.0.10586.0
Fault Module Timestamp: 5632d3ca
Exception Code: c0000005
Exception Offset: 0000000000067e5c
OS Version: 10.0.10586.2.0.0.768.101
Locale ID: 5129
Additional Information 1: 4a22
Additional Information 2: 4a223f60382fa2d34e6a47e2139f1f17
Additional Information 3: ab88
Additional Information 4: ab888da10f9f005aa150bcd5f2273de0

Extra information about the problem
Bucket ID: c2a9595f678be5a757c5ebddefac08b7 (120348642845)




Here is what I've tried so far:

SFC /SCANNOW (No problems found)
Reinstalled Nvidia GPU Drivers
Virus Scan (Windows Defender)
Malware Scan (Malwarebytes)

If anyone can suggest a potential solution I would be very grateful!

Thanks.

IGot99Crashes said:

This is the message from Control Panel\System and Security\Security and Maintenance\Problem Details

Source
Desktop Window Manager

Summary
Stopped working

Date
‎Wed ‎09/‎12/‎2015 1:30 PM

Status
Report sent

Description
Faulting Application Path: C:\Windows\System32\dwm.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: dwm.exe
Application Version: 10.0.10586.0
Application Timestamp: 5632d756
Fault Module Name: combase.dll
Fault Module Version: 10.0.10586.0
Fault Module Timestamp: 5632d3ca
Exception Code: c0000005
Exception Offset: 0000000000067e5c
OS Version: 10.0.10586.2.0.0.768.101
Locale ID: 5129
Additional Information 1: 4a22
Additional Information 2: 4a223f60382fa2d34e6a47e2139f1f17
Additional Information 3: ab88
Additional Information 4: ab888da10f9f005aa150bcd5f2273de0

Extra information about the problem
Bucket ID: c2a9595f678be5a757c5ebddefac08b7 (120348642845)




Here is what I've tried so far:

SFC /SCANNOW (No problems found)
Reinstalled Nvidia GPU Drivers
Virus Scan (Windows Defender)
Malware Scan (Malwarebytes)

If anyone can suggest a potential solution I would be very grateful!

Thanks.

Hi I've had the same issue, I got in touch with the help desk at Microsoft, after tons of tests they decided to tell me to refresh my machine, which I did!

I've just had the same issue today again it seems to be back. Exactly where yours is. Personally I think it's a bug in the latest Nvidia Drivers and something between them an Microsoft.

Keep me posted how you get on.

But I have tried all the same stuff as you and even tested memory etc.. with no issues detected. It's not a virus or hardware failure, there's something more going on, and I feel it's an issue with win 10 and Nvidia.

Fearfulcoder said:

Hi I've had the same issue, I got in touch with the help desk at Microsoft, after tons of tests they decided to tell me to refresh my machine, which I did!

I've just had the same issue today again it seems to be back. Exactly where yours is. Personally I think it's a bug in the latest Nvidia Drivers and something between them an Microsoft.

Keep me posted how you get on.

But I have tried all the same stuff as you and even tested memory etc.. with no issues detected. It's not a virus or hardware failure, there's something more going on, and I feel it's an issue with win 10 and Nvidia.

This might be the issue ok I know it's an windows 8 error but could be related?

Solved dwm.exe stopped working.

Do you have an xbox 360 controller or wireless dongle plugged in? I was having the same error and had been trying to solve it for the past few weeks. For me it looks like the issue was related to the driver for my xbox controller. When I disabled the driver through my device manager I stopped getting the error.

sopey15 said:

Do you have an xbox 360 controller or wireless dongle plugged in? I was having the same error and had been trying to solve it for the past few weeks. For me it looks like the issue was related to the driver for my xbox controller. When I disabled the driver through my device manager I stopped getting the error.

I do have an x-box controller and it is usually plugged in - but I need to use it! I'm hoping for another option...

I understand, I use mine every day and leave it plugged in too. If it is a driver issue with the controller though, I don't think there is anything anyone can do except for Microsoft updating/fixing the drivers. For me it's kind of a "non-issue", I still see the error with my controller plugged in but at least now I know what it is and it doesn't cause any problems for me.