Repeated Daily Crashes of Desktop Window Manager in Reliability Monitor When Using Pen

Anonymous
2020-11-13T05:11:27+00:00

Is anyone also having problems? I am all updated to 2009, all drivers updated. SFC reports no issues. Occasionally, when there's a crash my screen goes black for a few seconds.

Source

Desktop Window Manager

Summary

Stopped working

Date

‎11/‎12/‎2020 1:07 PM

Status

Report sent

Description

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

Problem signature

Problem Event Name: BEX64

Application Name: dwm.exe

Application Version: 10.0.19041.508

Application Timestamp: cd97c98b

Fault Module Name: HeatCore.dll

Fault Module Version: 0.0.0.0

Fault Module Timestamp: c6130bfa

Exception Offset: 0000000000035afd

Exception Code: c0000409

Exception Data: 0000000000000002

OS Version: 10.0.19042.2.0.0.768.101

Locale ID: 1033

Additional Information 1: b111

Additional Information 2: b111fda7573a1e10441015376b653053

Additional Information 3: 02f1

Additional Information 4: 02f1489b0e3ef25dd4a9c89674c90c7c

Extra information about the problem

Bucket ID: 0329fc9be08ddbf2c3f9318478ced3bf (1439236000953848767)

Surface | Surface Pro | Install and update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

92 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-11-29T21:27:51+00:00

    I haven't used my Surface dock in many months, so for me that's not related.

    Depending upon the day, my Surface may be in sleep mode the entire day. Or on some days, in and out of sleep mode throughout the day. Sometimes for brief periods to look up stuff at work and sometimes for more extended sessions when writing memos, doing scheduling, etc. 

    I do run the Microsoft PowerToys on my computers. Do you? I've been running them for a while and didn't have this issue in the past while running them. So I can't see them explicitly causing the problem...But I just updated from 0.20 to 0.25 after posting my original message just to see if it makes a difference this week. 

    I just tried my pen while my Surface was connected to my second screen and it crashed, so I'm starting to think it's the being in sleep and coming back from that increases the propensity of the crashes. No, I don't have Powertoys installed.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-11-29T21:20:58+00:00

    I haven't used my Surface dock in many months, so for me that's not related.

    Depending upon the day, my Surface may be in sleep mode the entire day. Or on some days, in and out of sleep mode throughout the day. Sometimes for brief periods to look up stuff at work and sometimes for more extended sessions when writing memos, doing scheduling, etc. 

    I do run the Microsoft PowerToys on my computers. Do you? I've been running them for a while and didn't have this issue in the past while running them. So I can't see them explicitly causing the problem...But I just updated from 0.20 to 0.25 after posting my original message just to see if it makes a difference this week.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-11-29T20:07:41+00:00

    I've been having the same exact problem lately. I've had my SP7 for a while and used the pen frequently in the past without issue. I haven't been using the pen much lately so I can't point to a certain date it began, but I know it's been popping up a lot over the last week or so. It's probably been a good month since I've used my pen. I would think this would be related to one of the newer Windows updates. 

    Similar issues. I'll go to use my pen, touch the screen, the screen will go black (but I'm pretty sure the screen is still technically 'on' as I think last time I could still see a bit of the backlight glow), for a few seconds, flicker, and then come back to what I was doing. It finally occurred to me to check the Event Viewer to grab info. Seems like similar details:

    These errors showed within seconds of eachother, this is the first:

    Fault bucket , type 0

    Event Name: BEX64

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: dwm.exe

    P2: 10.0.19041.508

    P3: cd97c98b

    P4: HeatCore.dll

    P5: 0.0.0.0

    P6: c6130bfa

    P7: 0000000000035afd

    P8: c0000409

    P9: 0000000000000002

    P10: 

    Attached files:

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA5A.tmp.mdmp

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAD8.tmp.WERInternalMetadata.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAE9.tmp.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAF8.tmp.csv

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB28.tmp.txt

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_61834f26acb3207736bd28e17e9162b8f68ba9_0a9ac62d_cab_4e7fee89-bcd2-4f07-a697-02a15bf13b1b\memory.hdmp

    These files may be available here:

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_61834f26acb3207736bd28e17e9162b8f68ba9_0a9ac62d_cab_4e7fee89-bcd2-4f07-a697-02a15bf13b1b

    Analysis symbol: 

    Rechecking for solution: 0

    Report Id: b6e1ed8f-e5b3-4bbb-9488-0aa7e37f6b37

    Report Status: 4

    Hashed bucket: 

    Cab Guid: 0

    This is the next one after that one:

    Fault bucket 1439236000953848767, type 5

    Event Name: BEX64

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: dwm.exe

    P2: 10.0.19041.508

    P3: cd97c98b

    P4: HeatCore.dll

    P5: 0.0.0.0

    P6: c6130bfa

    P7: 0000000000035afd

    P8: c0000409

    P9: 0000000000000002

    P10: 

    Attached files:

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA5A.tmp.mdmp

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAD8.tmp.WERInternalMetadata.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAE9.tmp.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAF8.tmp.csv

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB28.tmp.txt

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_61834f26acb3207736bd28e17e9162b8f68ba9_0a9ac62d_cab_4e7fee89-bcd2-4f07-a697-02a15bf13b1b\memory.hdmp

    These files may be available here:

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_61834f26acb3207736bd28e17e9162b8f68ba9_0a9ac62d_4e7fee89-bcd2-4f07-a697-02a15bf13b1b

    Analysis symbol: 

    Rechecking for solution: 0

    Report Id: b6e1ed8f-e5b3-4bbb-9488-0aa7e37f6b37

    Report Status: 268435456

    Hashed bucket: 0329fc9be08ddbf2c3f9318478ced3bf

    Cab Guid: 0

    This is the next and final one:

    Fault bucket 1439236000953848767, type 5

    Event Name: BEX64

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: dwm.exe

    P2: 10.0.19041.508

    P3: cd97c98b

    P4: HeatCore.dll

    P5: 0.0.0.0

    P6: c6130bfa

    P7: 0000000000035afd

    P8: c0000409

    P9: 0000000000000002

    P10: 

    Attached files:

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF0D4.tmp.mdmp

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF1DF.tmp.WERInternalMetadata.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF1F0.tmp.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF1FD.tmp.csv

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF21E.tmp.txt

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_61834f26acb3207736bd28e17e9162b8f68ba9_0a9ac62d_cab_3767d09c-5b6c-4966-8889-dfbc6cddef77\memory.hdmp

    These files may be available here:

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_61834f26acb3207736bd28e17e9162b8f68ba9_0a9ac62d_3767d09c-5b6c-4966-8889-dfbc6cddef77

    Analysis symbol: 

    Rechecking for solution: 0

    Report Id: 18daead7-4ad5-4612-8762-b37127b9001f

    Report Status: 268435456

    Hashed bucket: 0329fc9be08ddbf2c3f9318478ced3bf

    Cab Guid: 0

    Thanks for sharing!

    Do you use a second screen / undock throughout the day by any chance? Do you tend to leave your device on sleep throughout the day? I want to confirm if these might be some situations where it increases the likelihood of it happening.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-11-29T19:52:07+00:00

    I've been having the same exact problem lately. I've had my SP7 for a while and used the pen frequently in the past without issue. I haven't been using the pen much lately so I can't point to a certain date it began, but I know it's been popping up a lot over the last week or so. It's probably been a good month since I've used my pen. I would think this would be related to one of the newer Windows updates. 

    Similar issues. I'll go to use my pen, touch the screen, the screen will go black (but I'm pretty sure the screen is still technically 'on' as I think last time I could still see a bit of the backlight glow), for a few seconds, flicker, and then come back to what I was doing. It finally occurred to me to check the Event Viewer to grab info. Seems like similar details:

    These errors showed within seconds of eachother, this is the first:

    Fault bucket , type 0

    Event Name: BEX64

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: dwm.exe

    P2: 10.0.19041.508

    P3: cd97c98b

    P4: HeatCore.dll

    P5: 0.0.0.0

    P6: c6130bfa

    P7: 0000000000035afd

    P8: c0000409

    P9: 0000000000000002

    P10: 

    Attached files:

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA5A.tmp.mdmp

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAD8.tmp.WERInternalMetadata.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAE9.tmp.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAF8.tmp.csv

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB28.tmp.txt

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_61834f26acb3207736bd28e17e9162b8f68ba9_0a9ac62d_cab_4e7fee89-bcd2-4f07-a697-02a15bf13b1b\memory.hdmp

    These files may be available here:

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_61834f26acb3207736bd28e17e9162b8f68ba9_0a9ac62d_cab_4e7fee89-bcd2-4f07-a697-02a15bf13b1b

    Analysis symbol: 

    Rechecking for solution: 0

    Report Id: b6e1ed8f-e5b3-4bbb-9488-0aa7e37f6b37

    Report Status: 4

    Hashed bucket: 

    Cab Guid: 0

    This is the next one after that one:

    Fault bucket 1439236000953848767, type 5

    Event Name: BEX64

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: dwm.exe

    P2: 10.0.19041.508

    P3: cd97c98b

    P4: HeatCore.dll

    P5: 0.0.0.0

    P6: c6130bfa

    P7: 0000000000035afd

    P8: c0000409

    P9: 0000000000000002

    P10: 

    Attached files:

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA5A.tmp.mdmp

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAD8.tmp.WERInternalMetadata.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAE9.tmp.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFAF8.tmp.csv

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB28.tmp.txt

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_61834f26acb3207736bd28e17e9162b8f68ba9_0a9ac62d_cab_4e7fee89-bcd2-4f07-a697-02a15bf13b1b\memory.hdmp

    These files may be available here:

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_61834f26acb3207736bd28e17e9162b8f68ba9_0a9ac62d_4e7fee89-bcd2-4f07-a697-02a15bf13b1b

    Analysis symbol: 

    Rechecking for solution: 0

    Report Id: b6e1ed8f-e5b3-4bbb-9488-0aa7e37f6b37

    Report Status: 268435456

    Hashed bucket: 0329fc9be08ddbf2c3f9318478ced3bf

    Cab Guid: 0

    This is the next and final one:

    Fault bucket 1439236000953848767, type 5

    Event Name: BEX64

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: dwm.exe

    P2: 10.0.19041.508

    P3: cd97c98b

    P4: HeatCore.dll

    P5: 0.0.0.0

    P6: c6130bfa

    P7: 0000000000035afd

    P8: c0000409

    P9: 0000000000000002

    P10: 

    Attached files:

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF0D4.tmp.mdmp

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF1DF.tmp.WERInternalMetadata.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF1F0.tmp.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF1FD.tmp.csv

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF21E.tmp.txt

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_61834f26acb3207736bd28e17e9162b8f68ba9_0a9ac62d_cab_3767d09c-5b6c-4966-8889-dfbc6cddef77\memory.hdmp

    These files may be available here:

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_61834f26acb3207736bd28e17e9162b8f68ba9_0a9ac62d_3767d09c-5b6c-4966-8889-dfbc6cddef77

    Analysis symbol: 

    Rechecking for solution: 0

    Report Id: 18daead7-4ad5-4612-8762-b37127b9001f

    Report Status: 268435456

    Hashed bucket: 0329fc9be08ddbf2c3f9318478ced3bf

    Cab Guid: 0

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-11-27T01:56:00+00:00

    I have even tried reinstalling Windows. I got the exact same dwm crash upon using my pen on the screen. I suppose I can wait a few more days to see if it reoccurs. But I find it notable I got the exact same error code as before doing a clean installation of Windows

    Source

    Desktop Window Manager

    Summary

    Stopped working

    Date

    ‎11/‎26/‎2020 3:42 PM

    Status

    Report sent

    Description

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

    Problem signature

    Problem Event Name: BEX64

    Application Name: dwm.exe

    Application Version: 10.0.19041.508

    Application Timestamp: cd97c98b

    Fault Module Name: HeatCore.dll

    Fault Module Version: 0.0.0.0

    Fault Module Timestamp: c6130bfa

    Exception Offset: 0000000000035afd

    Exception Code: c0000409

    Exception Data: 0000000000000002

    OS Version: 10.0.19042.2.0.0.768.101

    Locale ID: 1033

    Additional Information 1: b111

    Additional Information 2: b111fda7573a1e10441015376b653053

    Additional Information 3: 02f1

    Additional Information 4: 02f1489b0e3ef25dd4a9c89674c90c7c

    Extra information about the problem

    Bucket ID: 0329fc9be08ddbf2c3f9318478ced3bf (1439236000953848767)

    Was this answer helpful?

    0 comments