System Information (local)
--------------------------------------------------------------------------------
Computer name: PC_MATERIEL_NET
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\windows
Hardware: ASUSTeK COMPUTER INC., STRIX Z270I GAMING
CPU: GenuineIntel Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17114312704 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\windows\Minidump
Crash dumps are enabled on your computer.
On Mon 22/05/2017 22:07:11 your computer crashed
crash dump file: C:\windows\Minidump\052217-7171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x50 (0xFFFFAF8155AA7854, 0x2, 0xFFFFF804007C9C27, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 22/05/2017 22:07:11 your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFAF8155AA7854, 0x2, 0xFFFFF804007C9C27, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 20/05/2017 23:36:23 your computer crashed
crash dump file: C:\windows\Minidump\052017-6328-01.dmp
This was probably caused by the following module: wdfilter.sys (WdFilter+0x1EF00)
Bugcheck code: 0x135 (0xFFFFFFFFC0000005, 0xFFFFD781414EB670, 0xFFFFF8070832EF00, 0xFFFF8481BF346D90)
Error: REGISTRY_FILTER_DRIVER_EXCEPTION
file path: C:\windows\system32\drivers\wdfilter.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft antimalware file system filter driver
Bug check description: This bugcheck is caused by an unhandled exception in a registry filtering driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Google query: Microsoft Corporation REGISTRY_FILTER_DRIVER_EXCEPTION
On Sat 20/05/2017 23:25:32 your computer crashed
crash dump file: C:\windows\Minidump\052017-6687-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x820F8)
Bugcheck code: 0xBE (0xFFFFF80075A820F8, 0x8900000436F06121, 0xFFFFAB803857F370, 0x
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
wdfilter.sys (Microsoft antimalware file system filter driver, Microsoft Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.