dwm.exe crash when running game



  • I recently built a new computer after my old one's power supply died, but tonight I went to run World of Warcraft and the screen went black after a few minutes in the game (though I could still hear the game audio and Windows sounds). I force shut down the computer and tried to run WoW again a few more times, but the same thing happened each time.

    I connected my monitor to the integrated graphics and ran WoW again, this time it seemed to work (though the framerate was terrible).

    A similar thing happened a few days ago when I was playing a video through the Films & TV Windows 10 app, but it only happened once and I'm not sure if it's the same issue.

    I looked in the Event Viewer logs and it seems that dwm.exe is crashing:

    Fault bucket 1895486962480874040, type 4
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: dwm.exe
    P2: 10.0.18362.387
    P3: 8e064b77
    P4: StackHash_7f4f
    P5: 0.0.0.0
    P6: 00000000
    P7: e0464645
    P8: PCH_EC_FROM_KERNELBASE+0x00000000000FF10F
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B65.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_62b61aa115cd6065912fc7782076fba880302372_25529819_39bbe390-a1b3-4234-ab19-0d879d755ea5
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: bfb6f12b-df52-4a8f-8c78-584844d33228
    Report Status: 268435456
    Hashed bucket: 8472bb8709b37f44fa4e1f59830e8238
    Cab Guid: 0
    

    This is the metadata XML mentioned in the log:

    <?xml version="1.0" encoding="UTF-16"?>
    <WERReportMetadata>
    	<OSVersionInformation>
    		<WindowsNTVersion>10.0</WindowsNTVersion>
    		<Build>18362</Build>
    		<Product>(0x30): Windows 10 Pro</Product>
    		<Edition>Professional</Edition>
    		<BuildString>18362.418.amd64fre.19h1_release.190318-1202</BuildString>
    		<Revision>418</Revision>
    		<Flavor>Multiprocessor Free</Flavor>
    		<Architecture>X64</Architecture>
    		<LCID>1033</LCID>
    	</OSVersionInformation>
    	<ProblemSignatures>
    		<EventType>APPCRASH</EventType>
    		<Parameter0>dwm.exe</Parameter0>
    		<Parameter1>10.0.18362.387</Parameter1>
    		<Parameter2>8e064b77</Parameter2>
    		<Parameter3>StackHash_7f4f</Parameter3>
    		<Parameter4>0.0.0.0</Parameter4>
    		<Parameter5>00000000</Parameter5>
    		<Parameter6>e0464645</Parameter6>
    		<Parameter7>PCH_EC_FROM_KERNELBASE+0x00000000000FF10F</Parameter7>
    	</ProblemSignatures>
    	<DynamicSignatures>
    		<Parameter1>10.0.18362.2.0.0.256.48</Parameter1>
    		<Parameter2>3081</Parameter2>
    		<Parameter22>7f4f</Parameter22>
    		<Parameter23>7f4f3d90dbcb9bd946b480dc62d37386</Parameter23>
    		<Parameter24>66ec</Parameter24>
    		<Parameter25>66ec3fff4cedc205dc86904d4833396d</Parameter25>
    	</DynamicSignatures>
    	<SystemInformation>
    		<MID>2A6EE996-6858-4813-B84B-C5CF6F393A1D</MID>
    		<SystemManufacturer>Micro-Star International Co., Ltd.</SystemManufacturer>
    		<SystemProductName>MS-7B98</SystemProductName>
    		<BIOSVersion>1.60</BIOSVersion>
    		<OSInstallDate>1570374562</OSInstallDate>
    		<OSInstallTime>2019-10-06T15:09:22Z</OSInstallTime>
    		<TimeZoneBias>-10:00</TimeZoneBias>
    	</SystemInformation>
    	<SecureBootState>
    		<UEFISecureBootEnabled>0</UEFISecureBootEnabled>
    	</SecureBootState>
    	<ReportInformation>
    		<Guid>39bbe390-a1b3-4234-ab19-0d879d755ea5</Guid>
    		<CreationTime>2019-10-19T09:50:01Z</CreationTime>
    	</ReportInformation>
    </WERReportMetadata>
    

    And this is the .wer file mentioned in the log:

    Version=1
    EventType=APPCRASH
    EventTime=132159521610683010
    ReportType=2
    Consent=1
    UploadTime=132159561968295707
    ReportStatus=268435456
    ReportIdentifier=39bbe390-a1b3-4234-ab19-0d879d755ea5
    IntegratorReportIdentifier=bfb6f12b-df52-4a8f-8c78-584844d33228
    Wow64Host=34404
    NsAppName=dwm.exe
    OriginalFilename=dwm.exe
    AppSessionGuid=00001c78-0002-000d-72d5-727a6286d501
    TargetAppId=W:0000f519feec486de87ed73cb92d3cac802400000000!0000b545ec0b2f9a97cc61668cb81131c90bdeeb8558!dwm.exe
    TargetAppVer=2045//07//04:10:33:27!213d6!dwm.exe
    BootId=4294967295
    ServiceSplit=4073189793
    TargetAsId=497
    UserImpactVector=48
    IsFatal=1
    EtwNonCollectReason=1
    Response.BucketId=8472bb8709b37f44fa4e1f59830e8238
    Response.BucketTable=4
    Response.LegacyBucketId=1895486962480874040
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=dwm.exe
    Sig[1].Name=Application Version
    Sig[1].Value=10.0.18362.387
    Sig[2].Name=Application Timestamp
    Sig[2].Value=8e064b77
    Sig[3].Name=Fault Module Name
    Sig[3].Value=StackHash_7f4f
    Sig[4].Name=Fault Module Version
    Sig[4].Value=0.0.0.0
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=00000000
    Sig[6].Name=Exception Code
    Sig[6].Value=e0464645
    Sig[7].Name=Exception Offset
    Sig[7].Value=PCH_EC_FROM_KERNELBASE+0x00000000000FF10F
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.18362.2.0.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=3081
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=7f4f
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=7f4f3d90dbcb9bd946b480dc62d37386
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=66ec
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=66ec3fff4cedc205dc86904d4833396d
    UI[2]=C:\Windows\System32\dwm.exe
    UI[5]=Check online for a solution (recommended)
    UI[6]=Check for a solution later (recommended)
    UI[7]=Close
    UI[8]=Desktop Window Manager stopped working and was closed
    UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
    UI[10]=&Close
    LoadedModule[0]=C:\Windows\System32\dwm.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\System32\KERNEL32.DLL
    LoadedModule[3]=C:\Windows\System32\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\SYSTEM32\apphelp.dll
    LoadedModule[5]=C:\Windows\System32\ucrtbase.dll
    LoadedModule[6]=C:\Windows\System32\advapi32.dll
    LoadedModule[7]=C:\Windows\System32\msvcrt.dll
    LoadedModule[8]=C:\Windows\System32\sechost.dll
    LoadedModule[9]=C:\Windows\System32\RPCRT4.dll
    LoadedModule[10]=C:\Windows\System32\gdi32.dll
    LoadedModule[11]=C:\Windows\System32\win32u.dll
    LoadedModule[12]=C:\Windows\SYSTEM32\udwm.dll
    LoadedModule[13]=C:\Windows\System32\gdi32full.dll
    LoadedModule[14]=C:\Windows\SYSTEM32\dwmredir.dll
    LoadedModule[15]=C:\Windows\System32\msvcp_win.dll
    LoadedModule[16]=C:\Windows\System32\cfgmgr32.dll
    LoadedModule[17]=C:\Windows\System32\USER32.dll
    LoadedModule[18]=C:\Windows\System32\combase.dll
    LoadedModule[19]=C:\Windows\System32\bcryptPrimitives.dll
    LoadedModule[20]=C:\Windows\System32\dxgi.dll
    LoadedModule[21]=C:\Windows\System32\dwmcore.dll
    LoadedModule[22]=C:\Windows\System32\CoreMessaging.dll
    LoadedModule[23]=C:\Windows\System32\powrprof.dll
    LoadedModule[24]=C:\Windows\System32\UMPDC.dll
    LoadedModule[25]=C:\Windows\System32\dcomp.dll
    LoadedModule[26]=C:\Windows\SYSTEM32\dxcore.dll
    LoadedModule[27]=C:\Windows\System32\d3d11.dll
    LoadedModule[28]=C:\Windows\System32\D3DCOMPILER_47.dll
    LoadedModule[29]=C:\Windows\System32\d2d1.dll
    LoadedModule[30]=C:\Windows\System32\CRYPTSP.dll
    LoadedModule[31]=C:\Windows\System32\kernel.appcore.dll
    LoadedModule[32]=C:\Windows\System32\IMM32.DLL
    LoadedModule[33]=C:\Windows\system32\uxtheme.dll
    LoadedModule[34]=C:\Windows\SYSTEM32\dwmghost.dll
    LoadedModule[35]=C:\Windows\System32\dwmapi.dll
    LoadedModule[36]=C:\Windows\System32\avrt.dll
    LoadedModule[37]=C:\Windows\SYSTEM32\ism.dll
    LoadedModule[38]=C:\Windows\System32\shcore.dll
    LoadedModule[39]=C:\Windows\System32\bcrypt.dll
    LoadedModule[40]=C:\Windows\System32\CoreUIComponents.dll
    LoadedModule[41]=C:\Windows\System32\OLEAUT32.dll
    LoadedModule[42]=C:\Windows\System32\PROPSYS.dll
    LoadedModule[43]=C:\Windows\System32\HID.DLL
    LoadedModule[44]=C:\Windows\System32\NInput.dll
    LoadedModule[45]=C:\Windows\SYSTEM32\ntmarta.dll
    LoadedModule[46]=C:\Windows\SYSTEM32\wintypes.dll
    LoadedModule[47]=C:\Windows\System32\WINSTA.dll
    LoadedModule[48]=C:\Windows\System32\WindowsCodecs.dll
    LoadedModule[49]=C:\Windows\System32\clbcatq.dll
    LoadedModule[50]=C:\Windows\System32\Windows.Gaming.Input.dll
    LoadedModule[51]=C:\Windows\System32\twinapi.appcore.dll
    LoadedModule[52]=C:\Windows\System32\RMCLIENT.dll
    LoadedModule[53]=C:\Windows\System32\UIAnimation.dll
    LoadedModule[54]=C:\Windows\System32\DispBroker.Desktop.dll
    LoadedModule[55]=C:\Windows\System32\mscms.dll
    LoadedModule[56]=C:\Windows\System32\USERENV.dll
    LoadedModule[57]=C:\Windows\System32\ColorAdapterClient.dll
    LoadedModule[58]=C:\Windows\System32\profapi.dll
    LoadedModule[59]=C:\Windows\System32\OneCoreUAPCommonProxyStub.dll
    LoadedModule[60]=C:\Windows\System32\ActXPrxy.dll
    LoadedModule[61]=C:\Windows\System32\DispBroker.dll
    LoadedModule[62]=C:\Windows\System32\crypt32.dll
    LoadedModule[63]=C:\Windows\System32\MSASN1.dll
    LoadedModule[64]=C:\Windows\System32\WINTRUST.DLL
    LoadedModule[65]=C:\Windows\System32\imagehlp.dll
    LoadedModule[66]=C:\Windows\system32\rsaenh.dll
    LoadedModule[67]=C:\Windows\System32\CRYPTBASE.dll
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    OsInfo[0].Key=vermaj
    OsInfo[0].Value=10
    OsInfo[1].Key=vermin
    OsInfo[1].Value=0
    OsInfo[2].Key=verbld
    OsInfo[2].Value=18362
    OsInfo[3].Key=ubr
    OsInfo[3].Value=418
    OsInfo[4].Key=versp
    OsInfo[4].Value=0
    OsInfo[5].Key=arch
    OsInfo[5].Value=9
    OsInfo[6].Key=lcid
    OsInfo[6].Value=1033
    OsInfo[7].Key=geoid
    OsInfo[7].Value=12
    OsInfo[8].Key=sku
    OsInfo[8].Value=48
    OsInfo[9].Key=domain
    OsInfo[9].Value=0
    OsInfo[10].Key=prodsuite
    OsInfo[10].Value=256
    OsInfo[11].Key=ntprodtype
    OsInfo[11].Value=1
    OsInfo[12].Key=platid
    OsInfo[12].Value=10
    OsInfo[13].Key=sr
    OsInfo[13].Value=0
    OsInfo[14].Key=tmsi
    OsInfo[14].Value=18399
    OsInfo[15].Key=osinsty
    OsInfo[15].Value=2
    OsInfo[16].Key=iever
    OsInfo[16].Value=11.418.18362.0-11.0.155
    OsInfo[17].Key=portos
    OsInfo[17].Value=0
    OsInfo[18].Key=ram
    OsInfo[18].Value=32703
    OsInfo[19].Key=svolsz
    OsInfo[19].Value=465
    OsInfo[20].Key=wimbt
    OsInfo[20].Value=0
    OsInfo[21].Key=blddt
    OsInfo[21].Value=190318
    OsInfo[22].Key=bldtm
    OsInfo[22].Value=1202
    OsInfo[23].Key=bldbrch
    OsInfo[23].Value=19h1_release
    OsInfo[24].Key=bldchk
    OsInfo[24].Value=0
    OsInfo[25].Key=wpvermaj
    OsInfo[25].Value=0
    OsInfo[26].Key=wpvermin
    OsInfo[26].Value=0
    OsInfo[27].Key=wpbuildmaj
    OsInfo[27].Value=0
    OsInfo[28].Key=wpbuildmin
    OsInfo[28].Value=0
    OsInfo[29].Key=osver
    OsInfo[29].Value=10.0.18362.418.amd64fre.19h1_release.190318-1202
    OsInfo[30].Key=buildflightid
    OsInfo[31].Key=edition
    OsInfo[31].Value=Professional
    OsInfo[32].Key=ring
    OsInfo[32].Value=Retail
    OsInfo[33].Key=expid
    OsInfo[34].Key=containerid
    OsInfo[35].Key=containertype
    OsInfo[36].Key=edu
    OsInfo[36].Value=0
    File[0].CabName=WERInternalMetadata.xml
    File[0].Path=WER2B65.tmp.WERInternalMetadata.xml
    File[0].Flags=327682
    File[0].Type=5
    File[0].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B65.tmp.WERInternalMetadata.xml
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=Desktop Window Manager
    AppPath=C:\Windows\System32\dwm.exe
    NsPartner=windows
    NsGroup=windows8
    ApplicationIdentity=298B2F54CE41C4485497DB41AAC56278
    MetadataHash=332060202
    

    It looks like this is usually caused by graphics card/driver issues, so I reinstalled my graphics drivers through GeForce Experience. I also ran dism and sfc as described in this article, but they didn't report any issues and the crash is still happening.

    Is my graphics card dying, or is this caused by something else? I wouldn't be surprised if the graphics card was somehow damaged when the old computer's power supply died.


  • Java Dev

    Are your power supply and cooling sufficient?



  • @PleegWat said in dwm.exe crash when running game:

    Are your power supply and cooling sufficient?

    I believe so, I've got a 650W power supply and the GPU temperature doesn't go above 50°C (usually hanging around 45°C - 47°C). You can see the full parts list here.



  • @Choonster said in dwm.exe crash when running game:

    @PleegWat said in dwm.exe crash when running game:

    Are your power supply and cooling sufficient?

    I believe so, I've got a 650W power supply and the GPU temperature doesn't go above 50°C (usually hanging around 45°C - 47°C). You can see the full parts list here.

    Actually, I turned on logging in MSI Afterburner and ran WoW to try and trigger the issue again. It looks like the temperatures got up to 64°C/65°C just before the crash.



  • @Choonster said in dwm.exe crash when running game:

    @Choonster said in dwm.exe crash when running game:

    @PleegWat said in dwm.exe crash when running game:

    Are your power supply and cooling sufficient?

    I believe so, I've got a 650W power supply and the GPU temperature doesn't go above 50°C (usually hanging around 45°C - 47°C). You can see the full parts list here.

    Actually, I turned on logging in MSI Afterburner and ran WoW to try and trigger the issue again. It looks like the temperatures got up to 64°C/65°C just before the crash.

    That should still be well within the normal operating temperatures of the card, though.

    Honestly, I stopped using nVidia cards a few years back because their drivers started having weird crashes in games, sometimes to the point of causing the computer to do the modern equivalent of a bluescreen unless I used specific driver versions (usually not the latest).


  • Discourse touched me in a no-no place

    Did you do a clean reinstall of the video drivers?

    65°C should be nowhere near problematic for that card.



  • @loopback0 said in dwm.exe crash when running game:

    Did you do a clean reinstall of the video drivers?

    65°C should be nowhere near problematic for that card.

    Yes, I tried a clean reinstall of the video drivers.


  • Discourse touched me in a no-no place

    Have you tried another game? Or even a benchmark like Unigine Superposition?

    It may well be the card if it's the same in other games.



  • @loopback0 said in dwm.exe crash when running game:

    Have you tried another game? Or even a benchmark like Unigine Superposition?

    It may well be the card if it's the same in other games.

    I don't have any other games installed, but I ran a benchmark/stress test through MSI Kombustor and got the crash on the second run.



  • @Choonster said in dwm.exe crash when running game:

    @loopback0 said in dwm.exe crash when running game:

    Have you tried another game? Or even a benchmark like Unigine Superposition?

    It may well be the card if it's the same in other games.

    I don't have any other games installed, but I ran a benchmark/stress test through MSI Kombustor and got the crash on the second run.

    I ran Unigine Superposition on 1080p Medium and got the crash on the third or fourth scene.


  • Discourse touched me in a no-no place

    So... bad card or bad driver. Could be the card having thermal issues (such as a heatsink coming unstuck inside the card enclosure) or something like that. By far the easiest fix is to buy a new one.


  • Notification Spam Recipient

    @dkf said in dwm.exe crash when running game:

    By far the easiest fix is to buy a new one.

    After disassembling and looking if some cheap thermal compound can solve it, of course, Shirley?



  • Try really stressing the card.



  • Hello Choonster,

    I am experiencing the same problem, can you please tell me how you fixed it ?

    Thank you,
    Stelian



  • @Stelian I ended up buying a new graphics card shortly after posting this thread. I don't think I ever fixed my old one.


Log in to reply