2 Replies Latest reply on Jun 29, 2018 10:03 PM by goodplay

    wdm.exe crash

    divineknight

      Specs:

      • AMD Graphics Card
        • AMD Radeon Vega Frontier Edition (air cooled)
      • Desktop or Laptop System
        • Desktop
      • Operating System
        • Windows 10 64bit Pro
      • Driver version installed
        • Radeon Pro Software Adrenalin Edition 18.5.2
      • Display Devices
        • Samsung UN40JU6500 4096x2160 @60Hz HDMI
      • Motherboard + Bios Revision
        • Asus Crosshair Hero VI Wifi Bios Version 6201
      • CPU/APU
        • Ryzen 1800X
      • Power Supply Unit  Make, Model & Wattage
        • Thermaltake Toughpower DPS G RGB 1500W Titanium
      • RAM
        • 64GB

       

      Was running WoW (World of Warcraft), and the game froze / took out Windows 10; was able to get information from Event Viewer:

      Error    6/29/2018 6:12:27 AM    Application Error    1000    (100)

      Faulting application name: dwm.exe, version: 10.0.17134.1, time stamp: 0xf5178e97

      Faulting module name: ntdll.dll, version: 10.0.17134.137, time stamp: 0xf4df6dc2

      Exception code: 0xc0000005

      Fault offset: 0x00000000000103c5

      Faulting process id: 0x640

      Faulting application start time: 0x01d40f13b3a869db

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

      Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

      Report Id: 7549c78d-3932-4595-a53d-03420e5e34de

      Faulting package full name:

      Faulting package-relative application ID:

       

      Followed by:

      Error    6/29/2018 6:12:27 AM    Application Error    1000    (100)

      Faulting application name: Explorer.EXE, version: 10.0.17134.1, time stamp: 0x425b30b2

      Faulting module name: ntdll.dll, version: 10.0.17134.137, time stamp: 0xf4df6dc2

      Exception code: 0xc0000005

      Fault offset: 0x00000000000103c9

      Faulting process id: 0x283c

      Faulting application start time: 0x01d40f13bc16b370

      Faulting application path: C:\Windows\Explorer.EXE

      Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

      Report Id: 2d1edd84-50f6-45eb-a19b-0864c1130b65

      Faulting package full name:

      Faulting package-relative application ID:

       

      Error    6/29/2018 6:12:27 AM    Application Error    1000    (100)

      Faulting application name: wmiprvse.exe, version: 10.0.17134.1, time stamp: 0x53519375

      Faulting module name: ntdll.dll, version: 10.0.17134.137, time stamp: 0xf4df6dc2

      Exception code: 0xc0000005

      Fault offset: 0x00000000000103c5

      Faulting process id: 0x13a0

      Faulting application start time: 0x01d40f13b506788d

      Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe

      Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

      Report Id: 71315559-e622-4d5a-a56b-27cf64974bfa

      Faulting package full name:

      Faulting package-relative application ID:

       

      Error    6/29/2018 6:12:27 AM    Application Error    1000    (100)

      Faulting application name: AUDIODG.EXE, version: 10.0.17134.137, time stamp: 0xecd85e98

      Faulting module name: ntdll.dll, version: 10.0.17134.137, time stamp: 0xf4df6dc2

      Exception code: 0xc0000005

      Fault offset: 0x00000000000103c5

      Faulting process id: 0x3bec

      Faulting application start time: 0x01d40f13cf4318b0

      Faulting application path: C:\Windows\system32\AUDIODG.EXE

      Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

      Report Id: 1ff2baa8-7ba7-4d61-ba35-9a557bd768ee

      Faulting package full name:

      Faulting package-relative application ID:

       

      Information    6/29/2018 6:12:27 AM    Windows Error Reporting    1001    None

      Fault bucket , type 0

      Event Name: APPCRASH

      Response: Not available

      Cab Id: 0

       

      Problem signature:

      P1: dwm.exe

      P2: 10.0.17134.1

      P3: f5178e97

      P4: ntdll.dll

      P5: 10.0.17134.137

      P6: f4df6dc2

      P7: c0000005

      P8: 00000000000103c5

      P9:

      P10:

       

      Attached files:

       

      These files may be available here:

      C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_347429ae24e958dfdf78d9854c28dec89e04d76_a2bcf5bb_4729d0c0

       

      Analysis symbol:

      Rechecking for solution: 0

      Report Id: 7549c78d-3932-4595-a53d-03420e5e34de

      Report Status: 4

      Hashed bucket:

      Cab Guid: 0

       

      Warning    6/29/2018 6:12:28 AM    Dwminit    0    None

      The Desktop Window Manager process has exited. (Process exit code: 0x000000ff, Restart count: 1, Primary display device ID: Radeon Vega Frontier Edition)

       

      Error    6/29/2018 6:12:28 AM    Application Error    1000    (100)

      Faulting application name: SecurityHealthService.exe, version: 4.13.17134.137, time stamp: 0x1b0bf725

      Faulting module name: ntdll.dll, version: 10.0.17134.137, time stamp: 0xf4df6dc2

      Exception code: 0xc0000005

      Fault offset: 0x00000000000103c5

      Faulting process id: 0x16bc

      Faulting application start time: 0x01d40f13b5380385

      Faulting application path: C:\Windows\system32\SecurityHealthService.exe

      Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

      Report Id: e93a217c-950a-4f1c-8a40-bcc29fe3d21c

      Faulting package full name:

      Faulting package-relative application ID:

       

      Error    6/29/2018 6:13:30 AM    Application Hang    1002    (101)

      The program svchost.exe version 10.0.17134.1 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

      Process ID: ecc

      Start Time: 01d40f13b51c52d8

      Termination Time: 4294967295

      Application Path: C:\Windows\System32\svchost.exe

      Report Id: e2f363d2-27bf-425c-97f1-83c519b13966

      Faulting package full name:

      Faulting package-relative application ID:

       

      One event precedes the first event:

      Information    6/29/2018 6:11:12 AM    SecurityCenter    15    None

      Updated Bitdefender Antivirus status successfully to SECURITY_PRODUCT_STATE_SNOOZED.

       

      These crashes have occurred multiple times in the past. Any ideas who is to blame here?>

       

      Message was edited by: Ryan Ross