OS NameMicrosoft Windows 10 Home

Version10.0.15063 Build 15063

Other OS Description Not Available

OS ManufacturerMicrosoft Corporation

System Name______

System ManufacturerGigabyte Technology Co., Ltd.

System ModelTo be filled by O.E.M.

System Typex64-based PC

System SKUTo be filled by O.E.M.

ProcessorIntel(R) Core(TM) i7-6700 CPU @ 3.40GHz, 3401 Mhz, 4 Core(s), 8 Logical Processor(s)

BIOS Version/DateAmerican Megatrends Inc. F6, 23/02/2016

SMBIOS Version2.8

Embedded Controller Version255.255

BIOS ModeUEFI

BaseBoard ManufacturerGigabyte Technology Co., Ltd.

BaseBoard ModelNot Available

BaseBoard NameBase Board

Platform RoleDesktop

Secure Boot StateOff

PCR7 ConfigurationBinding Not Possible

Windows DirectoryC:\WINDOWS

System DirectoryC:\WINDOWS\system32

Boot Device\Device\HarddiskVolume2

LocaleAustralia

Hardware Abstraction LayerVersion = "10.0.15063.0"

User NameEARTH\Martin

Time ZoneAUS Eastern Standard Time

Installed Physical Memory (RAM)16.0 GB

Total Physical Memory15.9 GB

Available Physical Memory12.6 GB

Total Virtual Memory18.3 GB

Available Virtual Memory14.7 GB

Page File Space2.38 GB

Page FileC:\pagefile.sys

Device Encryption SupportReasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, TPM is not usable

Hyper-V - VM Monitor Mode ExtensionsYes

Hyper-V - Second Level Address Translation ExtensionsYes

Hyper-V - Virtualization Enabled in FirmwareYes

Hyper-V - Data Execution ProtectionYes

Fault Log

10/06/2017 12:56 PMApplication ErrorFaulting application name: dwm.exe, version: 10.0.15063.0, time stamp: 0x982d0cc7
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80070057
Fault offset: 0x0000000000000000
Faulting process id: 0x315c
Faulting application start time: 0x01d2e1990a395bf9
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: unknown
Report Id: ed211637-511f-4abd-9f0f-bdf79f8f6bbd
Faulting package full name: 
Faulting package-relative application ID:

10/06/2017 12:56 PMWindows Error ReportingFault bucket 120731694033, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.15063.0
P3: 982d0cc7
P4: StackHash_1d2f
P5: 0.0.0.0
P6: 00000000
P7: 80070057
P8: PCH_C0_FROM_KERNELBASE+0x000000000007FE24
P9: 
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_2514df17\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB60.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB70.tmp.txt
\\?\C:\Windows\Temp\WERCBB2.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_2514df17\memory.hdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE1A7.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_11f4e8ac

Analysis symbol: 
Rechecking for solution: 0
Report Id: ed211637-511f-4abd-9f0f-bdf79f8f6bbd
Report Status: 268435456
Hashed bucket: dc964a02e8f943a8b01a7e0a492bf61e

10/06/2017 12:56 PMWindows Error ReportingFault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.15063.0
P3: 982d0cc7
P4: StackHash_1d2f
P5: 0.0.0.0
P6: 00000000
P7: 80070057
P8: PCH_C0_FROM_KERNELBASE+0x000000000007FE24
P9: 
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_2514df17\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB60.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB70.tmp.txt
\\?\C:\Windows\Temp\WERCBB2.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_2514df17\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_2514df17

Analysis symbol: 
Rechecking for solution: 0
Report Id: ed211637-511f-4abd-9f0f-bdf79f8f6bbd
Report Status: 4
Hashed bucket:

10/06/2017 3:03 AMApplication ErrorFaulting application name: dwm.exe, version: 10.0.15063.0, time stamp: 0x982d0cc7
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80070057
Fault offset: 0x0000000000000000
Faulting process id: 0x3274
Faulting application start time: 0x01d2e13a676e6767
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: unknown
Report Id: 686e2853-bd1d-47bc-ab86-fbc95f85d625
Faulting package full name: 
Faulting package-relative application ID:

10/06/2017 3:03 AMWindows Error ReportingFault bucket 120731694033, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.15063.0
P3: 982d0cc7
P4: StackHash_1d2f
P5: 0.0.0.0
P6: 00000000
P7: 80070057
P8: PCH_C0_FROM_KERNELBASE+0x000000000007FE24
P9: 
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_0ede30b2\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3074.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3084.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3094.tmp.txt
\\?\C:\Windows\Temp\WER30B4.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_0ede30b2\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_1b6239ab

Analysis symbol: 
Rechecking for solution: 0
Report Id: 686e2853-bd1d-47bc-ab86-fbc95f85d625
Report Status: 268435456
Hashed bucket: dc964a02e8f943a8b01a7e0a492bf61e

10/06/2017 3:03 AMWindows Error ReportingFault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.15063.0
P3: 982d0cc7
P4: StackHash_1d2f
P5: 0.0.0.0
P6: 00000000
P7: 80070057
P8: PCH_C0_FROM_KERNELBASE+0x000000000007FE24
P9: 
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_0ede30b2\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3074.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3084.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3094.tmp.txt
\\?\C:\Windows\Temp\WER30B4.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_0ede30b2\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_0ede30b2

Analysis symbol: 
Rechecking for solution: 0
Report Id: 686e2853-bd1d-47bc-ab86-fbc95f85d625
Report Status: 4
Hashed bucket:

10/06/2017 3:24 AMApplication ErrorFaulting application name: dwm.exe, version: 10.0.15063.0, time stamp: 0x982d0cc7
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80070057
Fault offset: 0x0000000000000000
Faulting process id: 0x1fdc
Faulting application start time: 0x01d2e196331d810f
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: unknown
Report Id: 9f772587-2ab8-4ac8-b1d1-ee9f65be8f63
Faulting package full name: 
Faulting package-relative application ID:

10/06/2017 3:24 AMWindows Error ReportingFault bucket 120731694033, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.15063.0
P3: 982d0cc7
P4: StackHash_1d2f
P5: 0.0.0.0
P6: 00000000
P7: 80070057
P8: PCH_C0_FROM_KERNELBASE+0x000000000007FE24
P9: 
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_1ae0cccc\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC5E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC5E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC6F.tmp.txt
\\?\C:\Windows\Temp\WERCCBE.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_1ae0cccc\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_1c98d72c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9f772587-2ab8-4ac8-b1d1-ee9f65be8f63
Report Status: 268435456
Hashed bucket: dc964a02e8f943a8b01a7e0a492bf61e

10/06/2017 3:24 AMWindows Error ReportingFault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.15063.0
P3: 982d0cc7
P4: StackHash_1d2f
P5: 0.0.0.0
P6: 00000000
P7: 80070057
P8: PCH_C0_FROM_KERNELBASE+0x000000000007FE24
P9: 
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_1ae0cccc\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC5E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC5E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC6F.tmp.txt
\\?\C:\Windows\Temp\WERCCBE.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_1ae0cccc\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_1ae0cccc

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9f772587-2ab8-4ac8-b1d1-ee9f65be8f63
Report Status: 4
Hashed bucket:

10/06/2017 6:35 AMWindows Error ReportingFault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 021185bf-a23a-49cd-b753-fa57478aebed

Problem signature:
P1: 141
P2: ffffa08bd9641110
P3: fffff8033978f44c
P4: 0
P5: 3ae0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170610-1635.dmp
\\?\C:\Windows\Temp\WER-80218625-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1069.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1079.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER107A.tmp.txt
\\?\C:\Windows\Temp\WER4862.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_52a3684f4e1f25b3d646bb99531fabad326c64c7_00000000_cab_323850ed

Analysis symbol: 
Rechecking for solution: 0
Report Id: 35b558cd-0b34-4d17-a4af-5f22c10a996f
Report Status: 268435456
Hashed bucket:

10/06/2017 6:35 AMWindows Error ReportingFault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffa08bd9641110
P3: fffff8033978f44c
P4: 0
P5: 3ae0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170610-1635.dmp
\\?\C:\Windows\Temp\WER-80218625-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1069.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1079.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER107A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_52a3684f4e1f25b3d646bb99531fabad326c64c7_00000000_cab_322c1088

Analysis symbol: 
Rechecking for solution: 0
Report Id: 35b558cd-0b34-4d17-a4af-5f22c10a996f
Report Status: 4
Hashed bucket:

11/06/2017 5:09 AMApplication ErrorFaulting application name: dwm.exe, version: 10.0.15063.0, time stamp: 0x982d0cc7
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80070057
Fault offset: 0x0000000000000000
Faulting process id: 0xeb4
Faulting application start time: 0x01d2e1e9016b8b9b
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: unknown
Report Id: c90a80ad-1d36-450b-823f-4d80f1b1cb40
Faulting package full name: 
Faulting package-relative application ID:

11/06/2017 5:09 AMWindows Error ReportingFault bucket 120731694033, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.15063.0
P3: 982d0cc7
P4: StackHash_1d2f
P5: 0.0.0.0
P6: 00000000
P7: 80070057
P8: PCH_C0_FROM_KERNELBASE+0x000000000007FE24
P9: 
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_2c53bd29\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBCEB.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBCEB.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBCFB.tmp.txt
\\?\C:\Windows\Temp\WERBD1C.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_2c53bd29\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_1617ca1a

Analysis symbol: 
Rechecking for solution: 0
Report Id: c90a80ad-1d36-450b-823f-4d80f1b1cb40
Report Status: 268435456
Hashed bucket: dc964a02e8f943a8b01a7e0a492bf61e

11/06/2017 5:09 AMWindows Error ReportingFault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.15063.0
P3: 982d0cc7
P4: StackHash_1d2f
P5: 0.0.0.0
P6: 00000000
P7: 80070057
P8: PCH_C0_FROM_KERNELBASE+0x000000000007FE24
P9: 
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_2c53bd29\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBCEB.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBCEB.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBCFB.tmp.txt
\\?\C:\Windows\Temp\WERBD1C.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_2c53bd29\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_5b5d85f4679d3da7c9dc67a63795be297d415bb_9adbe171_cab_2c53bd29

Analysis symbol: 
Rechecking for solution: 0
Report Id: c90a80ad-1d36-450b-823f-4d80f1b1cb40
Report Status: 4
Hashed bucket:

11/06/2017 5:21 AMApplication ErrorFaulting application name: FreemakeUtilsService.exe, version: 1.0.0.0, time stamp: 0x592510b7
Faulting module name: KERNELBASE.dll, version: 10.0.15063.296, time stamp: 0x28e9cf15
Exception code: 0xe0434352
Fault offset: 0x000eb802
Faulting process id: 0xd2c
Faulting application start time: 0x01d2e2728a7a92f0
Faulting application path: C:\ProgramData\Freemake\FreemakeUtilsService\FreemakeUtilsService.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 2f64b4ed-e8c5-4ade-b09b-3e91836bb94f
Faulting package full name: 
Faulting package-relative application ID:

11/06/2017 5:21 AMWindows Error ReportingFault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: FreemakeUtilsService.exe
P2: 1.0.0.0
P3: 592510b7
P4: FreemakeUtilsService
P5: 1.0.0.0
P6: 592510b7
P7: 4a
P8: 7
P9: System.IO.FileNotFoundException
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1cf81f30\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E74.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E84.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E95.tmp.txt
\\?\C:\Windows\Temp\WER1ED4.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1cf81f30\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1cf81f30

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2f64b4ed-e8c5-4ade-b09b-3e91836bb94f
Report Status: 100
Hashed bucket:

11/06/2017 5:21 AMWindows Error ReportingFault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: FreemakeUtilsService.exe
P2: 1.0.0.0
P3: 592510b7
P4: FreemakeUtilsService
P5: 1.0.0.0
P6: 592510b7
P7: 4a
P8: 7
P9: System.IO.FileNotFoundException
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1cf81f30\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E74.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E84.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E95.tmp.txt
\\?\C:\Windows\Temp\WER1ED4.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1cf81f30\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1cf81f30

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2f64b4ed-e8c5-4ade-b09b-3e91836bb94f
Report Status: 4
Hashed bucket:

11/06/2017 5:24 AMWindows Error ReportingFault bucket 129458263905, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: FreemakeUtilsService.exe
P2: 1.0.0.0
P3: 592510b7
P4: FreemakeUtilsService
P5: 1.0.0.0
P6: 592510b7
P7: 4a
P8: 7
P9: System.IO.FileNotFoundException
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1cf81f30\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E74.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E84.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E95.tmp.txt
\\?\C:\Windows\Temp\WER1ED4.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1cf81f30\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_060f7e39

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2f64b4ed-e8c5-4ade-b09b-3e91836bb94f
Report Status: 268435556
Hashed bucket: 3f1d79cb6d9b5346268905b4e6ed7af1

11/06/2017 5:26 AMWindows Error ReportingFault bucket 127862691748, type 5
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.15063.168
P2: 800704cf
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 0
P7: 0
P8: UpdateOrchestrator
P9: {8B24B027-1DEE-BABB-9A95-3517DFB9C552}
P10: 0

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD7E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCDAC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCDBD.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_10.0.15063.168_62292b507e232ab645e5c06472209eb3a9cc82a9_00000000_1938d2ae

Analysis symbol: 
Rechecking for solution: 0
Report Id: 36dc18d1-3660-4dcb-b167-447a351c0a65
Report Status: 268435456
Hashed bucket: fdfec29fe7171bd8b70a09a92fa3e5a3

11/06/2017 5:26 AMWindows Error ReportingFault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.15063.168
P2: 800704cf
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 0
P7: 0
P8: UpdateOrchestrator
P9: {8B24B027-1DEE-BABB-9A95-3517DFB9C552}
P10: 0

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD7E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCDAC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCDBD.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_10.0.15063.168_62292b507e232ab645e5c06472209eb3a9cc82a9_00000000_cab_15c8cdbc

Analysis symbol: 
Rechecking for solution: 0
Report Id: 36dc18d1-3660-4dcb-b167-447a351c0a65
Report Status: 4
Hashed bucket:

11/06/2017 5:26 AMWindows Error ReportingFault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.15063.168
P2: 800704cf
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 0
P7: 0
P8: UpdateOrchestrator
P9: {8B24B027-1DEE-BABB-9A95-3517DFB9C552}
P10: 0

Attached files:

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 36dc18d1-3660-4dcb-b167-447a351c0a65
Report Status: 1074003968
Hashed bucket:

11/06/2017 5:35 AMApplication ErrorFaulting application name: FreemakeUtilsService.exe, version: 1.0.0.0, time stamp: 0x592510b7
Faulting module name: KERNELBASE.dll, version: 10.0.15063.296, time stamp: 0x28e9cf15
Exception code: 0xe0434352
Fault offset: 0x000eb802
Faulting process id: 0xc74
Faulting application start time: 0x01d2e27481c9ccfc
Faulting application path: C:\ProgramData\Freemake\FreemakeUtilsService\FreemakeUtilsService.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 80d3a1b2-5401-4df3-9d50-1e11c3f01ad6
Faulting package full name: 
Faulting package-relative application ID:

11/06/2017 5:35 AMWindows Error ReportingFault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: FreemakeUtilsService.exe
P2: 1.0.0.0
P3: 592510b7
P4: FreemakeUtilsService
P5: 1.0.0.0
P6: 592510b7
P7: 4a
P8: 7
P9: System.IO.FileNotFoundException
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1a281d0d\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C03.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C13.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C53.tmp.txt
\\?\C:\Windows\Temp\WER1CA2.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1a281d0d\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1a281d0d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 80d3a1b2-5401-4df3-9d50-1e11c3f01ad6
Report Status: 100
Hashed bucket:

11/06/2017 5:35 AMWindows Error ReportingFault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: FreemakeUtilsService.exe
P2: 1.0.0.0
P3: 592510b7
P4: FreemakeUtilsService
P5: 1.0.0.0
P6: 592510b7
P7: 4a
P8: 7
P9: System.IO.FileNotFoundException
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1a281d0d\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C03.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C13.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C53.tmp.txt
\\?\C:\Windows\Temp\WER1CA2.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1a281d0d\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1a281d0d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 80d3a1b2-5401-4df3-9d50-1e11c3f01ad6
Report Status: 4
Hashed bucket:

11/06/2017 5:38 AMWindows Error ReportingFault bucket 129458263905, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: FreemakeUtilsService.exe
P2: 1.0.0.0
P3: 592510b7
P4: FreemakeUtilsService
P5: 1.0.0.0
P6: 592510b7
P7: 4a
P8: 7
P9: System.IO.FileNotFoundException
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1a281d0d\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C03.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C13.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C53.tmp.txt
\\?\C:\Windows\Temp\WER1CA2.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_cab_1a281d0d\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FreemakeUtilsSer_a192abcdae2f4b1adea3921d7fa835fbf2e4830_bdbe2fae_2edae91e

Analysis symbol: 
Rechecking for solution: 0
Report Id: 80d3a1b2-5401-4df3-9d50-1e11c3f01ad6
Report Status: 268435556
Hashed bucket: 3f1d79cb6d9b5346268905b4e6ed7af1

11/06/2017 5:41 AMApplication ErrorFaulting application name: dwm.exe, version: 10.0.15063.0, time stamp: 0x982d0cc7
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80070057
Fault offset: 0x0000000000000000
Faulting process id: 0x4b4
Faulting application start time: 0x01d2e2748185f473
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: unknown
Report Id: 57170ddf-a8c6-47d7-af35-333e2343454d
Faulting package full name: 
Faulting package-relative application ID:

11/06/2017 5:41 AMWindows Error ReportingFault bucket 120731694033, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.15063.0
P3: 982d0cc7
P4: StackHash_1d2f
P5: 0.0.0.0
P6: 00000000
P7: 80070057
P8: PCH_3E_FROM_KERNELBASE+0x000000000007FE24
P9: 
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_23d2b434f9e1686a19f72d9075ae4175126284_9adbe171_cab_2a19cb37\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCAE9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCAF8.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB09.tmp.txt
\\?\C:\Windows\Temp\WERCB29.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_23d2b434f9e1686a19f72d9075ae4175126284_9adbe171_cab_2a19cb37\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_23d2b434f9e1686a19f72d9075ae4175126284_9adbe171_20d9d3e1

Analysis symbol: 
Rechecking for solution: 0
Report Id: 57170ddf-a8c6-47d7-af35-333e2343454d
Report Status: 268435456
Hashed bucket: dc964a02e8f943a8b01a7e0a492bf61e

11/06/2017 5:41 AMWindows Error ReportingFault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.15063.0
P3: 982d0cc7
P4: StackHash_1d2f
P5: 0.0.0.0
P6: 00000000
P7: 80070057
P8: PCH_3E_FROM_KERNELBASE+0x000000000007FE24
P9: 
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_23d2b434f9e1686a19f72d9075ae4175126284_9adbe171_cab_2a19cb37\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCAE9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCAF8.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB09.tmp.txt
\\?\C:\Windows\Temp\WERCB29.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_23d2b434f9e1686a19f72d9075ae4175126284_9adbe171_cab_2a19cb37\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_23d2b434f9e1686a19f72d9075ae4175126284_9adbe171_cab_2a19cb37

Analysis symbol: 
Rechecking for solution: 0
Report Id: 57170ddf-a8c6-47d7-af35-333e2343454d
Report Status: 4
Hashed bucket:

11/06/2017 6:25 AMApplication ErrorFaulting application name: dwm.exe, version: 10.0.15063.0, time stamp: 0x982d0cc7
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80070057
Fault offset: 0x0000000000000000
Faulting process id: 0x1598
Faulting application start time: 0x01d2e27561385678
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: unknown
Report Id: 9bbe5e66-9d46-49e2-a5bb-4d1fd2f49035
Faulting package full name: 
Faulting package-relative application ID:

11/06/2017 6:25 AMWindows Error ReportingFault bucket 120731694033, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.15063.0
P3: 982d0cc7
P4: StackHash_1d2f
P5: 0.0.0.0
P6: 00000000
P7: 80070057
P8: PCH_3E_FROM_KERNELBASE+0x000000000007FE24
P9: 
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_23d2b434f9e1686a19f72d9075ae4175126284_9adbe171_cab_1fee491f\minidump.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48F0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48F0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4900.tmp.txt
\\?\C:\Windows\Temp\WER4921.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_23d2b434f9e1686a19f72d9075ae4175126284_9adbe171_cab_1fee491f\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_23d2b434f9e1686a19f72d9075ae4175126284_9adbe171_1cb674b3

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9bbe5e66-9d46-49e2-a5bb-4d1fd2f49035
Report Status: 268435456
Hashed bucket: dc964a02e8f943a8b01a7e0a492bf61e