Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 9/22/2017 3:11:00 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\092217-25062-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Fri 9/22/2017 3:10:00 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x52A1)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80931C552A1, 0xFFFFAC01C699CAC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
On Fri 9/22/2017 2:00:24 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\092217-30000-01.dmp
This was probably caused by the following module: afd.sys (afd+0x58AF0)
Bugcheck code: 0xBE (0xFFFFF80FC8ED8AF0, 0x2167CB121, 0xFFFFF8027709EB20, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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.
On Thu 9/21/2017 9:42:16 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\092217-41953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x171859)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8009598A859, 0xFFFFD280EE39CBC8, 0xFFFFD280EE39C410)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 a system thread generated an exception which the error handler did not catch.
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 Thu 9/21/2017 6:15:28 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\092117-42515-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
16 crash dumps have been found and analyzed. Only 5 are included in this report. 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: