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 No comments

92 answers

Sort by: Most helpful
  1. Anonymous
    2021-03-16T20:49:48+00:00

    Funny, I was doing something and got a blue screen shortly after posting that and my Surface did the first two updates during the restart. Used the pen and had the issue again. 

    Error: 

    Faulting application name: dwm.exe, version: 10.0.19041.746, time stamp: 0x6be51595

    Faulting module name: HeatCore.dll, version: 0.0.0.0, time stamp: 0x54ab4a1a

    Exception code: 0xc0000409

    Fault offset: 0x0000000000035b5d

    Faulting process id: 0x3f4c

    Faulting application start time: 0x01d71aa575b73c6e

    Faulting application path: C:\WINDOWS\system32\dwm.exe

    Faulting module path: C:\WINDOWS\system32\HeatCore.dll

    Report Id: 32c0853a-eb8c-418f-bf07-bf1189c89608

    Faulting package full name: 

    Faulting package-relative application ID:

    Warning:

    The Desktop Window Manager process has exited. (Process exit code: 0xc0000409, Restart count: 2, Primary display device ID: Intel(R) Iris(R) Plus Graphics)

    I know these updates occurred a few days back as well:

    Surface - Extension - 2.9.139.0

    Intel Corporation - Extension - 27.20.100.8681

    Will report back later today after doing the optional KB5001567 I mentioned above. 

    Edit: Problem still persists after the optional KB5001567 I mentioned.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-03-16T02:14:28+00:00

    Still having this issue. Surface pen causes heatcore.dll and dwm.exe to crash. Everything is up to date and has always been. Been crashing for literally 4 months straight.

    I should have just bought an ipad to do school work on.... jesus.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-03-07T23:41:36+00:00

    Okay, so even on the 26. Version driver I had a black screen crash this morning.

    Seen some reports that this "might be due to onenote" so uninstalled the Office version of OneNote 2016.

    Will see how that goes and maybe upgrade the drivers to latest again.

    I've seen this issue persist even upon upgrading to OneNote "2019," so I don't think it's that either. I would guess it's the combination of the Intel driver and 20H2, since I want to say I didn't have this issue before the October update.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-03-03T11:21:09+00:00

    This is likely to be more of a problem now as the February 2021 updates contain an update to Intel Corporation – Display - 27.20.100.8681 which apparently also contains whatever this bug is.

    The build number suggests somewhere in the third quarter of last year as being the driver date, and Intel themselves released that driver on the 15th September. Microsoft presumably "validated" it by checking that it had a valid signature and that it didn't crash while installing and left it at that. Good job QA Team, oh wait you got dissolved...

    So that at least narrows down this bug appearing between December 2019 and September 2020.

    It is entirely possible that it is not the Intel drivers that are at fault, and it is instead some way that the Microsoft drivers for the touchscreen and pen are interacting with it causing it to crash out and restart the driver.

    Or Intel could just be releasing gloriously broken drivers. I do see a lot of **igccservice "**PowerEvent handled successfully by the service." messages in Event Viewer, like one message every 3-5 seconds for days... hard to know if some Microsoft power driver is constantly spewing events, or if the driver simply isn't actually handling them properly.

    The fact of the matter for me is that rolling back the driver seems to help. One way or another both of these companies need to slow down and actually look at the steaming piles that they are releasing into the wild.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2021-03-03T08:37:14+00:00

    The only fix I can suggest is downgrading to older graphics drivers. The latest drivers 27.20.100.9168 also has the black screen problem. Windows Update helpfully gave me Intel drivers which were upgraded to this problem a week or two ago.

    The version from the last Surface Driver pack is 26.20.100.7641, dated December 2019 and I've not seen the black screen since installing them. If you want those drivers you can apparently download them from Microsoft here.

    Since rolling back the driver I haven't been able to provoke a black screen.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments